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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2012-06-03T09:16:23+00:00

    Hi TorrentG!

    I also noticed that AMD Overdrive is present in your memory dumps - it will cause low-level problems that tend to resemble hardware issues.  Please try this:

    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.

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

    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://ati.amd.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, 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, your MagicISO drivers (mcdbus.sys) date from 2009.  Please uninstall this program.  If it's needed, download a fresh copy and install that AFTER uninstalling the current one.

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

    BSOD BUGCHECK SUMMARY

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

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

    Debug session time: Sat Jun  2 17:18:53.417 2012 (UTC - 4:00)

    System Uptime: 0 days 0:05:49.557

    *** 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 = F9

    BiosReleaseDate = 05/11/2012

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

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

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

    Debug session time: Sat Jun  2 17:12:27.341 2012 (UTC - 4:00)

    System Uptime: 0 days 0:03:21.481

    *** 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! ?? ::FNODOBFM::`string'+43d86 )

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  System

    FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+43d86

    Bugcheck code 00000050

    Arguments fffff80003fa81a2 0000000000000008 fffff80003fa81a2 0000000000000002

    BiosVersion = F9

    BiosReleaseDate = 05/11/2012

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

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

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

    Debug session time: Sat Jun  2 17:08:24.198 2012 (UTC - 4:00)

    System Uptime: 0 days 5:33:16.337

    Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonQueryInformation+1a6 )

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x24

    PROCESS_NAME:  Steam.exe

    FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonQueryInformation+1a6

    Bugcheck code 00000024

    Arguments 00000000001904fb fffff88009696e18 fffff88009696670 fffff880012aaa26

    BiosVersion = F9

    BiosReleaseDate = 05/11/2012

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

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-06-03T23:54:42+00:00

    I uninstalled AODdriver (through the device manager) and the AMDVision Engine Software, and I uninstalled mcdbus.sys and MagicDisc, and the game still BSOD'd the very instant I clicked 'play'.

    Dump: https://skydrive.live.com/redir?resid=5F2452D737B22C73!117&authkey=!AHod53aFODatihE

    I also took TorrentG's advice and uninstalled Avast! and installed MSE instead. The dump file I from above occurred after I uninstalled Avast! so that can be ruled out also.

    Also, does the fact that the Memory Checker, chkdsk, and the Windows Diagnostic all came up clean mean that hardware can be reasonably ruled out as the cause? I'm only asking because all my hardware sill has a warranty on it, and I'd prefer to order new hardware now for free than in two weeks and pay for it.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-06-03T23:59:53+00:00

    Go into bios then set Optimized Defaults then save. When back at Windows, install latest CPU-Z, make a screenshot of each of the SPD and Memory tabs. Zip them and upload.

    That should make it well because your memory is either set unwell in the bios or it is defective.

    The screenshots will show us if it is now set right after the bios save.

    (Wrong clocks or timings the likely issue now.)

    I would pull out all the RAM from the machine too, and then firmly reseat all the modules and make sure they are installed physically well.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-06-04T01:01:06+00:00

    I loaded the Optimized Defaults and saved the CPU-Z screenshots (link below)

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

    Quick question though, is it significant that under the 'SPD' tab in CPU-Z, the info on my memory was under 'slot 3' and 'slot 4' instead of 1 and 2? Maybe it's nothing but I just thought I'd ask, you can see it in the screenshots.

    Was this answer helpful?

    0 comments