Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

PC crippled by numerous, consecutive BSOD's


  • Please log in to reply
13 replies to this topic

#1 Dave Finlay

Dave Finlay

  • Members
  • 148 posts
  • OFFLINE
  •  
  • Local time:01:49 PM

Posted 16 February 2012 - 03:09 PM

A week or so ago, my PC had an abrupt BSOD. I didn't get to see the error message because it performed a memory dump and soon restarted. I chalked it up to me not having cleaned the CPU/heatsink compartment in a while (CPU temps were high), so I did that this morning, carefully I might add, with a damp cloth and canned air. I did the same with the RAM compartment (which gets dusty as well). After hooking everything up and browsing on the 'net however, I got an abrupt BSOD that rebooted me. Then, all attempts at starting up (regular, safe mode, Startup Repair) were turned away by a BSOD. Most alarmingly, my PC's startup diagnostic (which does a test on the RAM and video card)started reading only 512 MB of my PC's 3 GB of RAM.

Eventually I was able to do Startup Repair (didn't fix anything) and log back on regularly, with my PC reading all of the RAM again. I did that Memory Diagnostic Test and it showed that nothing was wrong. Thinking the issue was gone, I was about to return to my normal duties when the PC BSOD'd again. And it's started reading only 512 MB of RAM again as well.

The two most common messages I've seen in the numerous BSOD's I've gotten in the last couple of hours are "Bad Pool Header" and "Page Fault in Nonpaged Area". Having no idea what they mean, or what to do, I'd like to once again ask for help with this PC, which I've already come to BP's forums for several times. :(

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,116 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:49 PM

Posted 16 February 2012 - 03:14 PM

Right or wrong...I'd be thinking "CMOS battery."

Louis

#3 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:04:49 AM

Posted 16 February 2012 - 04:56 PM

G'day Dave!!!

Make and model of computer? Sounds like the same one > Clevo Sager?
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#4 Dave Finlay

Dave Finlay
  • Topic Starter

  • Members
  • 148 posts
  • OFFLINE
  •  
  • Local time:01:49 PM

Posted 16 February 2012 - 05:54 PM

G'day Dave!!!

Make and model of computer? Sounds like the same one > Clevo Sager?


Hey, fancy meeting you again! You already know the deal, its the same CLEVO D900T, giving me problems AGAIN. :(

#5 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:04:49 AM

Posted 16 February 2012 - 06:46 PM

Until you cleaned, you had only the one BSOD, and your temps were a little high. After cleaning, you are getting the RAM being reported incorrectly (intermittent) and a constant BSOD startup problem. It is possible that you have a dodgy RAM connection and that cleaning upset it. I suggest removing each RAM stick and then re-inserting firmly into place to "re-fresh" the physical connection. Can you now start the computer normally or in Safe Mode?

How many RAM sticks in total? 4? (2x512MB and 2x1GB ???)
Perhaps one has gone "bad"? Try removing "some of them" (for example, just leave a 1GB stick) and test. If no luck, swap the stick for the other 1GB ... and test.

From what you have posted so far, it sounds very much like a dodgy/intermittent RAM connection problem.

If you can get the Clevo up and running (normally or in Safe Mode), transfer the minidump files (copy) to a USB flashdrive > zip them up > attach the .zip file to your reply. (Be aware that you have a 512KB total limit on your allowable attachments here at the BC forums, so if attaching the .zip file ... and including anything else that you have previously attached and not yet removed ... will exceed this limit, we will have to explore another option, such as a file-sharing website.)

Edit: The minidump files will be located at C:\Windows\Minidump <<<folder

Edited by AustrAlien, 16 February 2012 - 06:51 PM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#6 Dave Finlay

Dave Finlay
  • Topic Starter

  • Members
  • 148 posts
  • OFFLINE
  •  
  • Local time:01:49 PM

Posted 17 February 2012 - 12:44 AM

To be honest, I'm fearing that I may have zapped/fried something while cleaning, even though I took extra precaution (I was wearing an anti-static wrist band). When I was cleaning the RAM compartment, I just briefly passed a damp (not soaking wet damp) cloth over them to get the dust off......I'd done so before and everything still worked fine afterwards.

The Clevo has 4 RAM slots, my 3 GB setup is as you said, 2 512 MB sticks and 2 1 GB sticks, each in their own channel. Right now I've removed the 512 MB sticks (seeing that the Clevo occasionally read only 512 MB, I want to see what happens when I remove one or both). I've been able to log in and locate the dump files, which I've attached...mate!

Attached Files



#7 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,109 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:02:49 PM

Posted 17 February 2012 - 01:42 AM

Hi -

From the software end, remove Daemon/ Alcohol; update ATI, Gear and SpeedFan -
sptd.sys        Sat Aug 20 00:33:43 2011 (4E4F3927) - Daemon/ Alcohol
atikmdag.sys    Mon Dec 01 16:01:46 2008 (493450BA) - ATI
GEARAspiWDM.sys Mon Aug 07 13:11:27 2006 (44D7743F) - Gear

speedfan.sys    Fri Mar 18 12:08:45 2011 (4D83838D) - Speedfan
giveio.sys      Wed Apr 03 22:33:25 1996 (316334F5) - Speedfan

http://sysnative.com/drivers/driver.php?id=sptd.sys
http://sysnative.com/drivers/driver.php?id=speedfan.sys
http://sysnative.com/drivers/driver.php?id=giveio.sys
http://sysnative.com/drivers/driver.php?id=atikmdag.sys
http://sysnative.com/drivers/driver.php?id=GEARAspiWDM.sys

Run the Driver Verifier -- http://www.sysnative.com/0x1/Driver_Verifier.htm

Run Speccy - http://www.filehippo.com/download_speccy
- "File" | "Publish Snapshot" | Paste URL into your next post

Regards. . .

jcgriff2

`


BSOD SUMMARY
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021712-19171-01.dmp]Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505Debug session time: Thu Feb 16 14:56:53.347 2012 (GMT-5)System Uptime: 0 days 0:13:13.253BUGCHECK_STR:  0x19_22DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTPROCESS_NAME:  SystemFAILURE_BUCKET_ID:  0x19_22_nt!ExpFindAndRemoveTagBigPages+1fdBugcheck code 00000019Arguments 00000022 a100c000 00000000 00000000BiosVersion = 6.00BiosReleaseDate = 04/07/2005SystemManufacturer = CLEVOSystemProductName = D900TMaxSpeed:     3200CurrentSpeed: 3200ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021612-28328-01.dmp]Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505Debug session time: Thu Feb 16 12:31:23.616 2012 (GMT-5)System Uptime: 0 days 0:02:09.506Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkOpenResource+520 )DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTBUGCHECK_STR:  0x8EPROCESS_NAME:  csrss.exeFAILURE_BUCKET_ID:  0x8E_dxgkrnl!DxgkOpenResource+520Bugcheck code 1000008EArguments c0000005 914371f8 8fd5ba80 00000000BiosVersion = 6.00BiosReleaseDate = 04/07/2005SystemManufacturer = CLEVOSystemProductName = D900TMaxSpeed:     3200CurrentSpeed: 3200ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021612-20171-01.dmp]Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505Debug session time: Thu Feb 16 12:27:33.921 2012 (GMT-5)System Uptime: 0 days 0:00:20.796DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTBUGCHECK_STR:  0x50PROCESS_NAME:  lsass.exeFAILURE_BUCKET_ID:  0x50_nt!ExAllocatePoolWithTag+4abBugcheck code 00000050Arguments 8c34da60 00000000 82b5c4b5 00000000BiosVersion = 6.00BiosReleaseDate = 04/07/2005SystemManufacturer = CLEVOSystemProductName = D900TMaxSpeed:     3200CurrentSpeed: 3200ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021612-18687-01.dmp]Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505Debug session time: Thu Feb 16 12:21:24.920 2012 (GMT-5)System Uptime: 0 days 0:27:42.795Probably caused by : fileinfo.sys ( fileinfo!FIStreamGet+36 )DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTBUGCHECK_STR:  0x8EPROCESS_NAME:  plugin-containFAILURE_BUCKET_ID:  0x8E_fileinfo!FIStreamGet+36Bugcheck code 1000008EArguments c0000005 82a95943 8cdc3978 00000000BiosVersion = 6.00BiosReleaseDate = 04/07/2005SystemManufacturer = CLEVOSystemProductName = D900TMaxSpeed:     3200CurrentSpeed: 3200ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021112-18656-01.dmp]Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505Debug session time: Sat Feb 11 03:08:29.525 2012 (GMT-5)System Uptime: 0 days 0:47:20.400BUGCHECK_STR:  0x1a_41287DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTPROCESS_NAME:  firefox.exeFAILURE_BUCKET_ID:  0x1a_41287_nt!KiTrap0E+dcBugcheck code 0000001AArguments 00041287 5a9cc863 00000000 00000000BiosVersion = 6.00BiosReleaseDate = 04/07/2005SystemManufacturer = CLEVOSystemProductName = D900TMaxSpeed:     3200CurrentSpeed: 3200ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``


Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

#8 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:04:49 AM

Posted 17 February 2012 - 01:50 AM

Maaate!!! Well done!

Dave, I haven't had a close look at your minidumps: That will take me some time. For now, looking at what has already transpired/what you have reported, and looking at the BlueScreenView summary report below, it seems reasonable at this time to assume a RAM problem. I will post the instructions for testing RAM so that you can get started. What combination you choose to test, or if you choose to test the sticks singly (probably the best option!) is up to you. When testing, try to use the same slot(s) in the motherboard to do the testing, rather than using any old slots randomly.

One thing I did notice when looking at the last minidump:

[Physical Memory Array (Type 16) - Length 15 - Handle 0016h]
Location 03h - SystemBoard/Motherboard
Use 03h - System Memory
Memory Error Correction 03h - None
Maximum Capacity 4194304KB
Memory Error Inf Handle [Not Provided]
Number of Memory Devices 2
[Memory Device (Type 17) - Length 27 - Handle 0017h]
Physical Memory Array Handle 0016h
Memory Error Info Handle [No Errors]
Total Width 64 bits
Data Width 64 bits
Size 512MB
Form Factor 09h - DIMM
Device Set 01h
Device Locator J6G1
Bank Locator DIMM 0
Memory Type 02h - Unknown
Type Detail 0080h - Synchronous
Speed 66MHz
Manufacturer [String Not Specified]
Serial Number [String Not Specified]
Asset Tag Number [String Not Specified]
Part Number [String Not Specified]

[Memory Device (Type 17) - Length 27 - Handle 0018h]
Physical Memory Array Handle 0016h
Memory Error Info Handle [No Errors]
Total Width 64 bits
Data Width 64 bits
Size 512MB
Form Factor 09h - DIMM
Device Set 01h
Device Locator J6G2
Bank Locator DIMM 1
Memory Type 02h - Unknown
Type Detail 0080h - Synchronous
Speed 66MHz
Manufacturer [String Not Specified]
Serial Number [String Not Specified]
Asset Tag Number [String Not Specified]
Part Number [String Not Specified]

[Memory Device (Type 17) - Length 27 - Handle 0019h]
Physical Memory Array Handle 0016h
Memory Error Info Handle [No Errors]
Total Width 64 bits
Data Width 64 bits
Size 2048MB
Form Factor 09h - DIMM
Device Set 01h
Device Locator J6H1
Bank Locator DIMM 2
Memory Type 02h - Unknown
Type Detail 0080h - Synchronous
Speed 66MHz
Manufacturer [String Not Specified]
Serial Number [String Not Specified]
Asset Tag Number [String Not Specified]
Part Number [String Not Specified]

[Memory Device (Type 17) - Length 27 - Handle 001ah]
Physical Memory Array Handle 0016h
Memory Error Info Handle [No Errors]
Total Width 64 bits
Data Width 64 bits
Size 1024MB
Form Factor 09h - DIMM
Device Set 01h
Device Locator J6H2
Bank Locator DIMM 3
Memory Type 02h - Unknown
Type Detail 0080h - Synchronous
Speed 66MHz
Manufacturer [String Not Specified]
Serial Number [String Not Specified]
Asset Tag Number [String Not Specified]
Part Number [String Not Specified]



==============================
BlueScreenView report:

==================================================
Dump File : 021712-19171-01.dmp
Crash Time : 17/02/2012 5:18:38 PM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 0x00000022
Parameter 2 : 0xa100c000
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+93e80
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\CactusIsland\Dave Finlay_BC\021712-19171-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
==================================================

==================================================
Dump File : 021612-28328-01.dmp
Crash Time : 17/02/2012 5:18:37 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x914371f8
Parameter 3 : 0x8fd5ba80
Parameter 4 : 0x00000000
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+2a1f8
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\CactusIsland\Dave Finlay_BC\021612-28328-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
==================================================

==================================================
Dump File : 021612-20171-01.dmp
Crash Time : 17/02/2012 5:18:37 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : 0x8c34da60
Parameter 2 : 0x00000000
Parameter 3 : 0x82b5c4b5
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+8e40f
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\CactusIsland\Dave Finlay_BC\021612-20171-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
==================================================

==================================================
Dump File : 021612-18687-01.dmp
Crash Time : 17/02/2012 5:18:37 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x82a95943
Parameter 3 : 0x8cdc3978
Parameter 4 : 0x00000000
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+973b
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\CactusIsland\Dave Finlay_BC\021612-18687-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
==================================================

==================================================
Dump File : 021112-18656-01.dmp
Crash Time : 17/02/2012 5:18:37 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 0x00041287
Parameter 2 : 0x5a9cc863
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : halmacpi.dll
Caused By Address : halmacpi.dll+5ba9
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\CactusIsland\Dave Finlay_BC\021112-18656-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
==================================================


====================================
Test the memory (RAM).

Memory needs to be tested outside of Windows, so memtest86+ is run from a bootable CD.

:step1: To make a bootable CD with memtest86+:
  • Extract the downloaded zip file:
    • In Windows XP, right-click on the zip file and choose Extract all.
      The contents of the zip file (the .ISO image file) will be extracted to a folder in the same location as your zip file.
  • Burn the .ISO image to CD: If you do not already have a suitable burning program for writing .ISO images to disc ...
    • Download and install ImgBurn.
    • Ensure that you UN-check the box agreeing to install the Ask toolbar during the installation.
    • Place a new (blank) CD disc in the drive tray.
    • Choose Write image file to disc.
    • Under Source, click on the Browse button: Navigate to and select the .ISO file that you wish to burn.
    • Place a check-mark in the box beside Verify.
  • Click Posted Image
  • When the CD has been burned and verified as successful, it will be bootable.

:step2: Boot from the newly created CD.
  • You may need to configure BIOS or the Boot Menu to boot first from the CD.
  • memtest86+ will begin running automatically: You need do nothing else at this time.
  • Allow memtest86+ to run un-interrupted.
See the screenshots in this informative link: Diagnose with Memtest86+

There MUST be NO errors what-so-ever:
  • If you see an error, stop the test.
  • Then proceed to test each stick of RAM separately to sort the good from the bad.
A minimum test for some confidence in the result, should be 7 full passes (each "pass" is a series of different types of tests), with NO errors.
  • Allow memtest86+ to run for 24 hours for maximum confidence in the test result.
memtest86+ will continue running until you stop it:
  • Press the <ESCAPE> key to re-boot the computer, removing the memtest86+ CD.

=======================
Thanks to jcgriff2 for input on the minidump analysis. I would also add that the BIOS version is also looking somewhat dated to be running Win7, and it may be worth checking for a more recent version if any problems continue unresolved.

BiosReleaseDate = 04/07/2005


Edited by AustrAlien, 17 February 2012 - 01:51 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#9 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,109 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:02:49 PM

Posted 17 February 2012 - 02:03 AM



Hardware info from the dumps -

The dumps show 4 GB RAM installed -
2x512
1x1024
1x2048

I would suggest removing the 2x512 + 1x1024 sticks for now.

_______________________________________________________


1: kd> !sysinfo cpuinfo;!sysinfo machineid; !sysinfo cpuspeed; !sysinfo smbios
[CPU Information]
~MHz = REG_DWORD 3200
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ x86 Family 15 Model 4 Stepping 1
ProcessorNameString = REG_SZ Intel® Pentium® 4 CPU 3.20GHz
Update Signature = REG_BINARY 0,0,0,0,17,0,0,0
Update Status = REG_DWORD 0
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD 1700000000

Machine ID Information [From Smbios 2.31, DMIVersion 0, Size=1288]
BiosVendor = Phoenix Technologies LTD
BiosVersion = 6.00
BiosReleaseDate = 04/07/2005
SystemManufacturer = CLEVO
SystemProductName = D900T
SystemVersion = Revision A
BaseBoardManufacturer = CLEVO
BaseBoardProduct = D900T
BaseBoardVersion = Revision A
CPUID: "Intel® Pentium® 4 CPU 3.20GHz"
MaxSpeed: 3200
CurrentSpeed: 3200

<..snip...>

[Memory Device (Type 17) - Length 27 - Handle 0017h]
Physical Memory Array Handle 0016h
Memory Error Info Handle [No Errors]
Total Width 64 bits
Data Width 64 bits
Size 512MB
Form Factor 09h - DIMM
Device Set 01h
Device Locator J6G1
Bank Locator DIMM 0
Memory Type 02h - Unknown
Type Detail 0080h - Synchronous
Speed 66MHz
Manufacturer [String Not Specified]
Serial Number [String Not Specified]
Asset Tag Number [String Not Specified]
Part Number [String Not Specified]
[Memory Device (Type 17) - Length 27 - Handle 0018h]
Physical Memory Array Handle 0016h
Memory Error Info Handle [No Errors]
Total Width 64 bits
Data Width 64 bits
Size 512MB
Form Factor 09h - DIMM
Device Set 01h
Device Locator J6G2
Bank Locator DIMM 1
Memory Type 02h - Unknown
Type Detail 0080h - Synchronous
Speed 66MHz
Manufacturer [String Not Specified]
Serial Number [String Not Specified]
Asset Tag Number [String Not Specified]
Part Number [String Not Specified]
[Memory Device (Type 17) - Length 27 - Handle 0019h]
Physical Memory Array Handle 0016h
Memory Error Info Handle [No Errors]
Total Width 64 bits
Data Width 64 bits
Size 2048MB
Form Factor 09h - DIMM
Device Set 01h
Device Locator J6H1
Bank Locator DIMM 2
Memory Type 02h - Unknown
Type Detail 0080h - Synchronous
Speed 66MHz
Manufacturer [String Not Specified]
Serial Number [String Not Specified]
Asset Tag Number [String Not Specified]
Part Number [String Not Specified]
[Memory Device (Type 17) - Length 27 - Handle 001ah]
Physical Memory Array Handle 0016h
Memory Error Info Handle [No Errors]
Total Width 64 bits
Data Width 64 bits
Size 1024MB
Form Factor 09h - DIMM
Device Set 01h
Device Locator J6H2
Bank Locator DIMM 3
Memory Type 02h - Unknown
Type Detail 0080h - Synchronous
Speed 66MHz
Manufacturer [String Not Specified]
Serial Number [String Not Specified]
Asset Tag Number [String Not Specified]
Part Number [String Not Specified]

<...snip...>



Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

#10 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,109 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:02:49 PM

Posted 17 February 2012 - 02:11 AM

Apologies AustrAlien... didn't see you there!

Good catch on the memory info.

Didn't mean to repeat your info... Internet slower here! Posted Image

John

Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

#11 Dave Finlay

Dave Finlay
  • Topic Starter

  • Members
  • 148 posts
  • OFFLINE
  •  
  • Local time:01:49 PM

Posted 17 February 2012 - 08:25 PM

Hi -

From the software end, remove Daemon/ Alcohol; update ATI, Gear and SpeedFan -

sptd.sys        Sat Aug 20 00:33:43 2011 (4E4F3927) - Daemon/ Alcohol
atikmdag.sys    Mon Dec 01 16:01:46 2008 (493450BA) - ATI
GEARAspiWDM.sys Mon Aug 07 13:11:27 2006 (44D7743F) - Gear

speedfan.sys    Fri Mar 18 12:08:45 2011 (4D83838D) - Speedfan
giveio.sys      Wed Apr 03 22:33:25 1996 (316334F5) - Speedfan

http://sysnative.com/drivers/driver.php?id=sptd.sys
http://sysnative.com/drivers/driver.php?id=speedfan.sys
http://sysnative.com/drivers/driver.php?id=giveio.sys
http://sysnative.com/drivers/driver.php?id=atikmdag.sys
http://sysnative.com/drivers/driver.php?id=GEARAspiWDM.sys

Run the Driver Verifier -- http://www.sysnative.com/0x1/Driver_Verifier.htm

Run Speccy - http://www.filehippo.com/download_speccy
- "File" | "Publish Snapshot" | Paste URL into your next post

Regards. . .

jcgriff2

`


BSOD SUMMARY
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021712-19171-01.dmp]Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505Debug session time: Thu Feb 16 14:56:53.347 2012 (GMT-5)System Uptime: 0 days 0:13:13.253BUGCHECK_STR:  0x19_22DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTPROCESS_NAME:  SystemFAILURE_BUCKET_ID:  0x19_22_nt!ExpFindAndRemoveTagBigPages+1fdBugcheck code 00000019Arguments 00000022 a100c000 00000000 00000000BiosVersion = 6.00BiosReleaseDate = 04/07/2005SystemManufacturer = CLEVOSystemProductName = D900TMaxSpeed:     3200CurrentSpeed: 3200ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021612-28328-01.dmp]Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505Debug session time: Thu Feb 16 12:31:23.616 2012 (GMT-5)System Uptime: 0 days 0:02:09.506Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkOpenResource+520 )DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTBUGCHECK_STR:  0x8EPROCESS_NAME:  csrss.exeFAILURE_BUCKET_ID:  0x8E_dxgkrnl!DxgkOpenResource+520Bugcheck code 1000008EArguments c0000005 914371f8 8fd5ba80 00000000BiosVersion = 6.00BiosReleaseDate = 04/07/2005SystemManufacturer = CLEVOSystemProductName = D900TMaxSpeed:     3200CurrentSpeed: 3200ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021612-20171-01.dmp]Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505Debug session time: Thu Feb 16 12:27:33.921 2012 (GMT-5)System Uptime: 0 days 0:00:20.796DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTBUGCHECK_STR:  0x50PROCESS_NAME:  lsass.exeFAILURE_BUCKET_ID:  0x50_nt!ExAllocatePoolWithTag+4abBugcheck code 00000050Arguments 8c34da60 00000000 82b5c4b5 00000000BiosVersion = 6.00BiosReleaseDate = 04/07/2005SystemManufacturer = CLEVOSystemProductName = D900TMaxSpeed:     3200CurrentSpeed: 3200ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021612-18687-01.dmp]Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505Debug session time: Thu Feb 16 12:21:24.920 2012 (GMT-5)System Uptime: 0 days 0:27:42.795Probably caused by : fileinfo.sys ( fileinfo!FIStreamGet+36 )DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTBUGCHECK_STR:  0x8EPROCESS_NAME:  plugin-containFAILURE_BUCKET_ID:  0x8E_fileinfo!FIStreamGet+36Bugcheck code 1000008EArguments c0000005 82a95943 8cdc3978 00000000BiosVersion = 6.00BiosReleaseDate = 04/07/2005SystemManufacturer = CLEVOSystemProductName = D900TMaxSpeed:     3200CurrentSpeed: 3200ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021112-18656-01.dmp]Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505Debug session time: Sat Feb 11 03:08:29.525 2012 (GMT-5)System Uptime: 0 days 0:47:20.400BUGCHECK_STR:  0x1a_41287DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTPROCESS_NAME:  firefox.exeFAILURE_BUCKET_ID:  0x1a_41287_nt!KiTrap0E+dcBugcheck code 0000001AArguments 00041287 5a9cc863 00000000 00000000BiosVersion = 6.00BiosReleaseDate = 04/07/2005SystemManufacturer = CLEVOSystemProductName = D900TMaxSpeed:     3200CurrentSpeed: 3200ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``



Hi J.C I did as you suggested.

As far as Driver Verifier goes, the PC BSOD'd when I restarted it (as mentioned in that link), so I deleted the settings that I set up and turned off the program.

Here's the Speccy screenshot (I've currently removed the two 512 MB RAM sticks):

http://speccy.piriform.com/results/tvIlRd6BMmhz60LgXPp1hXx

I'm also attaching the minidump file that I got after restarting w/ the Driver Verifier settings. I'll respond to you shortly AustrAlien.

Attached Files



#12 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,109 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:02:49 PM

Posted 17 February 2012 - 10:05 PM



The VERIFIER_ENABLED dump named SAS -
FAILURE_BUCKET_ID:  0x7E_VRF_SASKUTIL+7503

SASKUTIL.SYS    Tue Jul 12 16:24:48 2011 (4E1CAD90)
http://sysnative.com/drivers/driver.php?id=SASKUTIL.SYS

Be sure to remove Daemon Tools & SpeedFan for now. I noticed drivers for both were loaded into RAM at the time of this last BSOD.

Regards. . .

jcgriff2



Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

#13 Dave Finlay

Dave Finlay
  • Topic Starter

  • Members
  • 148 posts
  • OFFLINE
  •  
  • Local time:01:49 PM

Posted 18 February 2012 - 03:48 AM

AustrAlien, I ran memtest. In my first tests, I wasn't getting any information on screen until I hit F1 ("Fail-Safe" mode). I ran a pass with just the two 512 MB sticks, and then with just the 1 GB sticks on the same slots, and neither got any errors. I think JC's advice about uninstalling Speedfan and Daemon Tools (which I did) may be what yielded these results, as I'm getting a full reading on my RAM during diagnostics again..for now anyways.

And yes, I am aware that some apps read my PC as having 4GB's of RAM and a 2 GB stick, which is not the case at all. Only additional RAM on the PC is in its video card (256MB). Otherwise its 3 GB (512+512, 1024+1024)

As far as the BIOS go, I've tried searching everywhere for an update but either I can't find it, or I've d/led it and it didn't want to install. Then again, that was when I had XP on it.

#14 noknojon

noknojon

  • Banned
  • 10,871 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:04:49 AM

Posted 18 February 2012 - 04:03 AM

I ran a pass with just the two 512 MB sticks, and then with just the 1 GB sticks on the same slots, and neither got any errors.

Hi Dave -
AustrAlien is not around at the moment, so I just jumped in for my 2 cents -

Also note that Memtest should be run for several hours, not just one pass or the readings may not be true -

Thanks -

EDIT -
Sorry AustrAlien is back to hit me now :whistle:

Edited by noknojon, 18 February 2012 - 04:06 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users