6 memory dumps, 5 different BSOD errors ( STOP 0xD1; STOP 0x3D; 2 STOP 0x3B; STOP 0x1A; STOP 0xA) with 6 different causes ( memory_corruption; hardware; dxgkrnl.sys; win32k.sys; ntkrnlmp.exe; hidusb.sys)
Looks like a hardware problem to me (due to the wide variety of errors and causes). Try all these 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)
Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised:
Malware (read the details at the link)
*****
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:
http://www.mersenne.org/freesoft/
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.
Also, please remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (
DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:
Code:
ASACPI.sys Sun Mar 27 22:30:36 2005 - a true BSOD maker, the Asus ATK0110 ACPI utility driver - http://www.carrona.org/dvrref.html#a
nvm62x64.sys Fri Oct 17 17:01:06 2008 - nVidia nForce chipset Networking driver - http://www.carrona.org/dvrref.html#n
Summary of BSOD's:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb 2 19:05:46.020 2010 (GMT-5)
System Uptime: 0 days 8:06:05.095
BugCheck A, {ffffffffffc70017, 0, 0, fffff800038f2995}
Probably caused by : memory_corruption ( nt!MiCheckVirtualAddress+155 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: iexplore.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb 5 20:03:27.543 2010 (GMT-5)
System Uptime: 0 days 9:13:45.494
BugCheck 3D, {fffff88007e01230, 0, 0, fffff88002c2f5da}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : hardware ( dxgkrnl+95db )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: iw4mp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Feb 7 16:52:58.265 2010 (GMT-5)
System Uptime: 0 days 4:51:09.325
BugCheck 3B, {c0000005, fffff88003a89722, fffff880069a3f70, 0}
Probably caused by : dxgkrnl.sys ( dxgkrnl+2722 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: iw4mp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Feb 7 18:12:35.664 2010 (GMT-5)
System Uptime: 0 days 1:18:40.739
BugCheck 3B, {c0000005, fffff96000192b86, fffff880026250c0, 0}
Probably caused by : win32k.sys ( win32k!TimersProc+126 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: csrss.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Feb 10 12:45:21.855 2010 (GMT-5)
System Uptime: 0 days 1:19:34.915
BugCheck 1A, {41287, 19, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42c75 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: iw4mp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb 12 11:27:06.084 2010 (GMT-5)
System Uptime: 0 days 0:19:23.144
BugCheck D1, {3e8, 2, 0, fffff88003d704b1}
Probably caused by : hidusb.sys ( hidusb!HumReadReport+13f )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System