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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2012-06-24T00:37:45+00:00

    I've literally seen probably 50-100k crash dumps. Never before have I seen this from yours:

    "Probably caused by : hardware_ram ( ZEROED_PAGE_CORRUPTED )"

    All crash dumps are memory.

    Recommend to ensure bios is set to standard values for everything and if it crashes like that again, get memory from another company. Ask for refund from original and show them this thread if necessary.

    Corsair is an excellent name, one of the best, but your either having bad luck with them or setting your motherboard to be well.

    I suppose it could be a faulty motherboard but there is no way to really know by the crashes. You could probably RMA that too.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-06-23T23:50:07+00:00

    Actually, this dump file might be the most useful, it just happened right after my last post. It's a code I've never seen before (Stop 0x01A), and in the blue screen itself it listed 'MEMORY_MANAGEMENT' as the cause of the crash.

    Here's the file:

    https://skydrive.live.com/redir?resid=5F2452D737B22C73!128&authkey=!AH4pO8pTi9kzDuU

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-06-23T23:43:09+00:00

    Well, it actually looks like I celebrated too soon. After trying portal, I booted up L.A. Noire, for the first time ever I actually got to the main menu, then crashed. I restarted and tried the game again, at which point the computer crashed on startup where it normally does. Here's the dumps on both of them: https://skydrive.live.com/redir?resid=5F2452D737B22C73!127&authkey=!ACVBmyzC-SWH0qA

    Turbo Boost is still off, but I don't know if there's other things in BIOS that I should maybe have turned on or off, but I don't want to mess with anything in there if I don't know what it is.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-06-23T22:32:39+00:00

    I thought I had it on Optimized Defaults too, so after I read your last message I went to optimized defaults and lo and behold AMD Turbo Boost was back on. Apparently it's on by default, which strikes me as odd.

    Anyways, everything looks good now, and I haven't blue screened when I tried to launch portal.

    Thank you veeeerrrryyyyy much for all your help, it is greatly appreciated.

    Was this answer helpful?

    0 comments