2 STOP 0x124's and a STOP 0x119. I'd suspect your video card or it's
drivers as a first guess. If you are overclocking any components, please return the system to default values (stop the overclock) while we're testing.
Next, please read these links for the STOP 0x124 error (
http://www.sevenforums.com/crash-loc...-what-try.html ) and the STOP 0x116 error (similar to the STOP 0x119 -
http://www.sevenforums.com/crash-loc...eshooting.html )
Please do the following:
- uninstall
ALL ATI stuff from the system using Control Panel...Programs...Uninstall a program
- visit
Advanced Micro Devices Inc. and download the latest Display
Driver (only the display driver, not the entire Catalyst Control Center - the display driver only is usually further down the page) for your video card
- install the new drivers and monitor for further BSOD's
Check the video card to make sure that it's properly seated, that it has power going to it, that the fan is working, and that there's good air circulation around the case and through the card's GPU cooler.
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:
Quote:
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:
ALSysIO64.sys Sun Apr 15 11:56:31 2007 - Core Temp - CPU temperature monitor - http://www.carrona.org/dvrref.html#ALSysIO64.sys
JGOGO.sys Tue Feb 07 06:53:22 2006 - JMicron Hot-Plug Driver - http://www.carrona.org/dvrref.html#JGOGO.sys
jraid.sys Fri Mar 23 23:20:18 2007 - JMicron RAID Driver - http://www.carrona.org/dvrref.html#jraid.sys
Summary of the BSOD's:
Code:
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 8 20:55:58.345 2010 (GMT-4)
System Uptime: 0 days 0:00:10.405
BugCheck 124, {0, fffffa8008cb88f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR: 0x124_GenuineIntel
PROCESS_NAME: System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 2 15:36:17.098 2010 (GMT-4)
System Uptime: 0 days 0:39:31.257
BugCheck 119, {1, a2b6d, a2b72, a2b71}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
BUGCHECK_STR: 0x119
PROCESS_NAME: System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Apr 29 00:01:22.657 2010 (GMT-4)
System Uptime: 0 days 0:00:11.327
BugCheck 124, {0, fffffa8008cbd8f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR: 0x124_GenuineIntel
PROCESS_NAME: System