View Single Post
12 Jun 2010  
Microsoft MVP


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:
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;

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 )
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 )
PROCESS_NAME:  svchost.exe
My System SpecsSystem Spec