Computer keeps Blue Screening, can't figure out why

Anonymous
2012-05-21T04:18:47+00:00

I just finished building my own gaming PC the other day. And yesterday my computer BSODed while playing Just Cause 2, and today it did again while playing the same game. The Event Viewer says it's an Error 41 (Kernel-Power). I really have no idea what to do. All my drivers are up to date, my power supply is defiantly big enough, and all my hardware is more then enough to handle anything I'm doing. What should I do?

EDIT: I should clarify that I know it's not a problem with overheating as well. My video card (Radeon 6950) has stayed under 60(c) the whole time, as well as my processor (AMD8150 8 core) staying under 40(c).

Windows for home | Windows 11 | Gaming

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2012-05-21T18:10:02+00:00

Just FYI - sometimes lower level drivers (such as AMD Overdrive or Gigabyte EasyTune) can cause systems to act as if there is a hardware problem.  So, we're still not certain if this is hardware or software - so please continue to run the diagnostics suggested previously.

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center.  This driver is known to cause BSOD's on some Win7 systems.  If doesn't appear to be installed on your system, then it may be a part of the Gigabyte EasyTune6 program (another one that's known to cause BSOD's on Win7 systems).

*******

Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program

Then, download and install a fresh copy of the ATI drivers from http://www.ati.com (in the upper right corner of the page)

  • Select the "Custom" installation option and don't let it install AMD OverDrive or the VISION Engine Control Center (if present)

Then use the ATI uninstall manager to uninstall the Catalyst Control Center (CCC).  This is a separate issue and isn't required for the AMD OverDrive removal.

If the device (AODDriver or AODDriver4.01) remains a problem in perfmon /report, open Device Manager, select the "View" item.

Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.

Locate the AODDriver entry, right click on it and select "Uninstall".  Reboot for changes to take affect.

*******

Sometimes the driver remains and continues to cause BSOD's.  If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Also, please uninstall the Gigabyte Easy Saver - mobo power utility driver and the Gigabyte EasyTune6 program (it may contain the AMD Overdrive program).  Both are known to cause BSOD's on some Win7 systems.

I am suspicious of the Applecharger program also, but have no firm evidence for it.  Please just keep an eye on it for now.

If that doesn't stop the BSOD's, please run Driver Verifier according to these directions:  http;//www.carrona.org/verifier.html

*****************************************************************************

BSOD BUGCHECK SUMMARY

Loading Dump File [C:\Users\FUBAR\jcgriff2_\dbug\_Kernel__\051912-22464-01.dmp]

Built by: 7600.16988.amd64fre.win7_gdr.120401-1505

Debug session time: Sat May 19 16:39:43.993 2012 (UTC - 4:00)

System Uptime: 0 days 0:31:58.600

BugCheck A, {6, 2, 0, fffff80003095a93}

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+e3 )

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+e3

Bugcheck code 0000000A

Arguments 0000000000000006 0000000000000002 0000000000000000 fffff80003095a93

BiosVersion = F7

BiosReleaseDate = 10/13/2011

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Loading Dump File [C:\Users\FUBAR\jcgriff2_\dbug\_Kernel__\052012-25287-01.dmp]

Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504

Debug session time: Mon May 21 00:00:30.836 2012 (UTC - 4:00)

System Uptime: 0 days 0:29:47.101

BugCheck 101, {19, 0, fffff8800316d180, 7}

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

Bugcheck code 00000101

Arguments 0000000000000019 0000000000000000 fffff8800316d180 0000000000000007

BiosVersion = F7

BiosReleaseDate = 10/13/2011

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Was this answer helpful?

1 person found this answer helpful.
0 comments

65 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2012-05-22T00:16:03+00:00

    I have no idea why HP drivers would show up. I built this computer from scratch last Friday. None of the parts are from older machines so that confuses me. The only thing I could think of would maybe be getting some bad mobo drivers from Gigabyte.

    I wrestled with finding a mobo BIOS update that would actually work on my computer (all the ones I could find were 32 bit, and Windows refused to run anything unless it was 64), but I eventually found one and things seem to be working fine, that being said I'm certainly not saying I'm sure that fixed it because of the small amount of time I've had with it. But things are looking good so far.

    I think I'm going to keep things the way they are now, but if it happens again I'll re-install Windows.

    Thank you VERY much for all the help you've been, there's no way I'd be typing this on a working computer if it wasn't for all the time you put into this thread. Thanks!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-05-22T00:04:36+00:00

    Only 68 updates since SP1 - most systems have much more than that.  Please visit Windows Update and ensure that you get all available updates.

    Uninstall RainMeter (just a hunch on my part).  If it doesn't fix things feel free to reinstall a freshly downloaded copy of the latest available version.

    Looking through the driverq_v.txt file I noticed a Broadcom NetXtreme driver that dates from 2008.  But the system has a Realtek ethernet card.  There could be conflicts with this device.

    The drivers in this system appear to be from an HP system - so, is this a system that you built using a drive from an HP system?  If so, there may be issues with conflicting drivers.  Take a look at the driverq_v.txt file and notice all the drivers from 2009 or earlier (secdrv.sys is from 2006 and is normal).

    If my suppositions from above are correct and you've passed all the hardware diagnostics - then I'd suggest backing up your stuff and installing Windows "clean".  Here's a link on how I suggest doing a "clean" install:  http://www.carrona.org/canned.html#clean

    ****************************************

    BSOD BUGCHECK SUMMARY

    Loading Dump File [C:\Users\FUBAR\jcgriff2_\dbug\_Kernel__\052112-37814-01.dmp]

    Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504

    Debug session time: Mon May 21 17:08:22.056 2012 (UTC - 4:00)

    System Uptime: 0 days 0:17:22.196

    BugCheck 101, {19, 0, fffff880009b3180, 4}

    *** WARNING: Unable to verify timestamp for win32k.sys

    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys

    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

    Bugcheck code 00000101

    Arguments 0000000000000019 0000000000000000 fffff880009b3180 0000000000000004

    BiosVersion = F7

    BiosReleaseDate = 10/13/2011

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    Loading Dump File [C:\Users\FUBAR\jcgriff2_\dbug\_Kernel__\052112-38329-01.dmp]

    Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504

    Debug session time: Mon May 21 15:51:39.913 2012 (UTC - 4:00)

    System Uptime: 0 days 0:01:52.052

    BugCheck 101, {19, 0, fffff88002fd7180, 3}

    *** WARNING: Unable to verify timestamp for win32k.sys

    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys

    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

    Bugcheck code 00000101

    Arguments 0000000000000019 0000000000000000 fffff88002fd7180 0000000000000003

    BiosVersion = F7

    BiosReleaseDate = 10/13/2011

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    Loading Dump File [C:\Users\FUBAR\jcgriff2_\dbug\_Kernel__\052112-43664-01.dmp]

    Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504

    Debug session time: Mon May 21 16:34:07.813 2012 (UTC - 4:00)

    System Uptime: 0 days 0:00:10.952

    BugCheck 124, {0, fffffa8008415338, 0, 0}

    Probably caused by : hardware

    BUGCHECK_STR:  0x124_AuthenticAMD

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

    Bugcheck code 00000124

    Arguments 0000000000000000 fffffa8008415338 0000000000000000 0000000000000000

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-05-21T22:20:38+00:00

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-05-21T21:31:36+00:00

    Can't tell that from the dump files.  But that won't be obvious from any reports that we ask for (other than you reporting it).

    First memory dump still had the drivers in it (AODDriver2.sys and gdrv.sys)...so I ran the other 2 later one's.

     These 2 memory dumps say hardware to me - so continuing with the hardware diags is the best thing for the present.  These only had 2 drivers - a recent CD/DVD driver and an AMD driver that comes through Windows Update.

    Also, here's 2 different articles to check out.  The first is about one of the initial errors you had (a STOP0x101):  http://www.sevenforums.com/crash-lockup-debug-how/63501-stop-0x101-clock_watchdog_timeout-troubleshtg.html

    The second is about the 2 most recent errors (STOP 0x124):  http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

    Please post back with the results of the hardware diagnostics and we'll move on from there.

    Please also post this information for us to have a look at:  http://www.sysnative.com/forums/showthread.php/68-Blue-Screen-of-Death-%28BSOD%29-Posting-Instructions-Windows-7-amp-Vista

    *************************************************************************************

    BSOD BUGCHECK SUMMARY

    Loading Dump File [C:\Users\FUBAR\jcgriff2_\dbug\_Kernel__\052112-24055-01.dmp]

    Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504

    Debug session time: Mon May 21 16:51:09.549 2012 (UTC - 4:00)

    System Uptime: 0 days 0:00:09.689

    BugCheck 124, {0, fffffa800842b748, 0, 0}

    Probably caused by : hardware

    BUGCHECK_STR:  0x124_AuthenticAMD

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

    Bugcheck code 00000124

    Arguments 0000000000000000 fffffa800842b748 0000000000000000 0000000000000000

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    Loading Dump File [C:\Users\FUBAR\jcgriff2_\dbug\_Kernel__\052112-30310-01.dmp]

    Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504

    Debug session time: Mon May 21 16:22:42.142 2012 (UTC - 4:00)

    System Uptime: 0 days 0:00:10.282

    BugCheck 124, {0, fffffa800841a4f8, 0, 0}

    Probably caused by : hardware

    BUGCHECK_STR:  0x124_AuthenticAMD

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

    Bugcheck code 00000124

    Arguments 0000000000000000 fffffa800841a4f8 0000000000000000 0000000000000000

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    Loading Dump File [C:\Users\FUBAR\jcgriff2_\dbug\_Kernel__\052112-31886-01.dmp]

    Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504

    Debug session time: Mon May 21 15:28:33.847 2012 (UTC - 4:00)

    System Uptime: 0 days 2:54:42.987

    BugCheck 101, {19, 0, fffff88002fd7180, 3}

    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  svchost.exe

    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

    Bugcheck code 00000101

    Arguments 0000000000000019 0000000000000000 fffff88002fd7180 0000000000000003

    BiosVersion = F7

    BiosReleaseDate = 10/13/2011

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    Was this answer helpful?

    0 comments