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-04T03:05:19+00:00

    I just finished trying to run the game one stick at a time. With one stick, the game got to the splash screen (where it normally BSODs) it crashed (the program) instead of blue screening and I got 'L.A. Noire has stopped working message from Windows. I closed the message, then I tried it again immediately after and got a Stop 0x101 error.

    So then I turned it off, removed the stick and put the other one in. I started up Windows, started up the game and I got another BSOD, the bug check code for this one I've never seen before so I'm attaching the dump file here: https://skydrive.live.com/redir?resid=5F2452D737B22C73!121&authkey=!ACVBAOP4VEiux-Q

    I'm looking in BlueScreenView at all my dump files right now. Even though there is a variety of different bug check codes, every single dump file (14 of them) have the same file found in the crash stack. It's 'ntsokrnl.exe', and inside the .zip folder with the dump file in it there's a screen cap I took of my BlueScreenView with the file I'm talking about circled. Maybe it's significant, maybe it isn't, I just figured I had nothing to lose by mentioning it here anyways.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-06-04T02:38:54+00:00

    See page 16 about how to install the memory properly and enable dual channel:

    ftp://download.gigabyte.ru/manual/mb\_manual\_ga-970a-d3\_e.pdf

    Slots 1 + 2 should be used and dual channel enabled.

    (1 + 2 are not next to each other physically.)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-06-04T02:34:48+00:00

    The heatsink that came with the processor already had thermal paste applied to it from the manufacturer, and I'm positive that overheating is not a problem. I can play Battlefield 3 for hours with no problem, and I keep a temperature monitor running all the time, and nothing has even come near the danger zone (I bought a really good case).

    I just switched the memory to slots 1 and 2 and attempted to run L.A. Noire again, maybe it's worth noting that for the first time it didn't BSOD, when I got to the point where it would normally blue screen the computer froze instead, completely unresponsive (caps lock key and everything). I'm not sure if that's relevant information or not but I thought I'd include it anyways.

    I think now I'm going to try to trial and error by removing one stick of memory at a time to see if I can pinpoint it to a particular stick. I'll post back with results.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-06-04T02:20:05+00:00

    Let me ask you this: When you built the machine, did you use a very thin and evenly spread out layer of thermal grease across the cpu before you put the heat sink on?

    In any case, use Speccy to check your voltages and temps. I know it does voltages but not sure about temps. See if they are within spec.

    If you did not put grease on the cpu, buy some Arctic Silver, take the heat sink off and cpu out carefully. Spread some on top of cpu evenly and lightly. Put it all back together.

    ---- Eh, nevermind - just read your OP.

    Still very likely memory defective then. Almost 100% if voltages are well in Speccy.

    Was this answer helpful?

    0 comments