3 BSODs over the last few days

[capheine]

Can anyone help me diagnose them?

I've attached the dmp files

 

[usasma]

3 memory dumps, one from 03 Jun and two from 07 Jun 2010
3 different STOP error codes, with 3 different causes
This could be the start of a pattern that indicated hardware problems - but it's too early to tell. Please submit more memory dumps as they occur.

So, let's start with these free, bootable hardware diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Normally I don't suggest using Driver Verifier for hardware issues - but there's enough doubt here that it may help us out. Please follow these instructions for running it:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD's:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun  7 20:19:45.007 2010 (GMT-4)
System Uptime: 0 days 0:12:37.412
BugCheck 3B, {c0000005, fffff960000a41a2, fffff88006e837b0, 0}
Probably caused by : win32k.sys ( win32k!EngTextOut+11e )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun  7 13:51:34.737 2010 (GMT-4)
System Uptime: 0 days 0:00:39.392
BugCheck 24, {1904fb, fffff88008899858, fffff880088990c0, fffff880012b508f}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCreateScb+10f )
PROCESS_NAME:  firefox.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun  3 20:07:57.773 2010 (GMT-4)
System Uptime: 0 days 0:52:26.428
BugCheck 1A, {403, fffff68000018ab0, f530000011dbe867, fffff680000a1fc2}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31f32 )
BUGCHECK_STR:  0x1a_403
PROCESS_NAME:  dllhost.exe

 

[capheine]

Thanks for the link to the HD diagnostic.

My boot drive is a Kingston SSD, so it looks like I'll be running SeaTools

 

[usasma]

The only SSD tool that I know of is: Crystal Dew World

 

[capheine]

Would it be better to use Crystal Dew World over SeaTools?

(I just ran SeaTools and got no errors on either of my drives)

 

[usasma]

I'd use both.

 

[capheine]

All right, here are the results of Driver Verifier. Two back-to-back crashes this morning.

 

[usasma]

Remove Daemon Tools (these 2 drivers in particular: a5fc4ekc.SYS and sptd.sys)
While I don't suspect it's the cause - it's a possibility that we have to consider.

Remove the Catalyst Control Center as it's known to cause issues for some people. If you have to remove all the ATI stuff, then just use the auto update feature in Device Manager (right click on the device and select Update).

Then test for further BSOD's - if you get any, then it's most likely that you have a hardware problem.
It's less likely to be a Windows problem - but that's still a possibility.

To help rule out Windows problems, please run the System File Checker:

SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.

The two dump files are Verifier Enabled Minidumps.
Don't forget to turn Driver Verifier off by selecting "Delete existing settings" in the first screen.
One dump file points to memory corruption, while the other points to the kernel (core) of the operating system.

Since Driver Verifier was testing 3rd party (non-Microsoft) drivers - then these results tell us that the 3rd party drivers probably aren't at fault. That leaves hardware, compatibility, or Windows as the problem.

Have you run the Memory diagnostic that I suggested earlier? If so, what were the results?
Try these free stress tests also:

Additional tests for certain specific circumstances:
Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Summary of the BSOD's;

[FONT=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 12 12:32:30.506 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:40.926
BugCheck 19, {3, fffff80002c1ccf0, ffbff80002c1ccf0, fffff80002c1ccf0}
Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  CCC.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 12 12:30:55.477 2010 (UTC - 4:00)
System Uptime: 0 days 0:36:14.147
BugCheck A, {fffff80002df46b7, 2, 0, fffff80002b05662}
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe[/FONT]

 

[capheine]

Thanks, I'll try that.

I did run Memtest overnight and everything was fine.