7 memory dump files - from 25 May to 30 May 2010 (6 days)
6 different STOP error codes, with 4 different causes blamed.
If you are overclocking, please stop and return the system to default values while we're troubleshooting.
Most likely this is a hardware problem - so let's try this:
It's called for in response to the first 2 errors - which point at the storage sub-system.
If that passes, then try these free stress tests:
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.
Also, please remove or update 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: Driver Reference
- - 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:
Alpham164.sys Mon Jul 23 03:57:03 2007 - Ideazon ZBoard - http://www.carrona.org/dvrref.html#Alpham164.sys
Alpham264.sys Tue Mar 20 05:51:03 2007 - Ideazon ZBoard - http://www.carrona.org/dvrref.html#Alpham264.sys
ENTECH64.sys Fri Mar 26 07:44:04 2004 - PowerStrip support NT kernel-mode driver - http://www.carrona.org/dvrref.html#ENTECH64.sys
Lachesis.sys Fri Aug 17 03:48:44 2007 - Razer Lachesis Mouse driver - http://www.carrona.org/dvrref.html#Lachesis.sys
Summary of the BSOD's:
Code:
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 29 18:16:25.871 2010 (GMT-4)
System Uptime: 0 days 0:21:53.369
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 29 08:22:00.595 2010 (GMT-4)
System Uptime: 0 days 0:28:54.719
BugCheck A, {1f04c6f6f48, 2, 0, fffff80002cd90ec}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+1cc )
BUGCHECK_STR: 0xA
PROCESS_NAME: Wow.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 29 07:49:47.840 2010 (GMT-4)
System Uptime: 0 days 2:40:58.339
BugCheck 1000007E, {ffffffffc0000005, fffff880053a00a4, fffff880025bd788, fffff880025bcff0}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 )
PROCESS_NAME: System
BUGCHECK_STR: 0x7E
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 26 12:17:31.571 2010 (GMT-4)
System Uptime: 0 days 0:32:18.695
BugCheck 3B, {c0000005, fffff80002f5ebb9, fffff8800a26ca60, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpGetNameControlBlock+12e )
BUGCHECK_STR: 0x3B
PROCESS_NAME: TrustedInstall
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 25 12:50:44.608 2010 (GMT-4)
System Uptime: 0 days 0:02:11.106
BugCheck 1000007E, {ffffffffc0000005, fffff880047d21d8, fffff88004194658, fffff88004193ec0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+6c )
PROCESS_NAME: System
BUGCHECK_STR: 0x7E
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 25 11:40:09.013 2010 (GMT-4)
System Uptime: 0 days 0:04:32.137
BugCheck 50, {fffffa0008431050, 0, fffff8800149e118, 7}
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : iaStor.sys ( iaStor+f118 )
BUGCHECK_STR: 0x50
PROCESS_NAME: System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 25 11:32:39.919 2010 (GMT-4)
System Uptime: 0 days 0:00:13.043
BugCheck 24, {1904fb, fffff8800358c278, fffff8800358bae0, fffff880018d5795}
Probably caused by : Ntfs.sys ( Ntfs!NtfsMapStream+25 )
PROCESS_NAME: System
BUGCHECK_STR: 0x24