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).

I just got to thinking, can BSODs be caused by insufficient power being supplied to my computer? The wiring in my house is old, and most of our outlets are two pronged. Right now my computer is plugged into a power strip (along with my monitor and speakers) and the power strip is plugged into the wall via a cheater plug. Is there a possibility that the issue lies in the power and the problems with my drivers were just a coincidence?

Try this "clean" install first - it'll test the Windows installation only. Then you can add your programs and stuff if it proves to be stable: http://www.carrona.org/canned.html#clean *********************************** BSOD BUGCHECK SUMMARY Loading Dump File [C:\Users\FUBAR\ jcgriff2_\dbug\ _Kernel__\052112-25256-01.dmp] Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504 Debug session time: Mon May 21 22:27:33.296 2012 (UTC - 4:00) System Uptime: 0 days 3:13:32.340 BugCheck 101, {19, 0, fffff88002f65180, 2} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: FL.exe FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE Bugcheck code 00000101 Arguments 00000000 00000019 00000000 00000000 fffff880 02f65180 00000000 00000002 BiosVersion = F9 BiosReleaseDate = 05/11/2012 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Yeah, it just BSOD'd again. Here's the dump just in case you want to take a peek at it: https://skydrive.live.com/redir?resid=5F2452D737B22C73!115&authkey=!ABio7ViiCA59yt0 At this point I'm just going to back up all my stuff to an external drive and re-install Windows. Thanks again for all your help.

It's not HP drivers, it's the pattern of drivers that I usually see on HP systems. Here's a link describing the drivers: http://www.carrona.org/hpdv4dvr.html They would have to have been on the disk that you used to install Windows 7. I'm glad that it's working for you now!

Computer keeps Blue Screening, can't figure out why

Answer accepted by question author

Anonymous

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

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

0 comments

Computer keeps Blue Screening, can't figure out why

65 additional answers