Solved Random BSOD - DRIVER_POWER_STATE_FAILURE

[ImpetuousRacer]

Who crashed tells me this:

This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800C4B5060, 0xFFFFF80000B9C518, 0xFFFFFA800DE912B0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe

Can you guys help me narrow it down from my dump files what could be causing this? A lot of times I just come back to the computer and see that it recovered from a serious error. Other times Ive just been doing nothing more than web browser.
I used driver genius to keep all my drivers up to date. Thanks for the help.

 

[zigzag3143]

AiCharger.sys is causing your USBHUB to collapse. I would remove it to test.

You also have a bunch of drivers needing updating

lmimirr.sys    4/10/2007 6:32:45 PM       
BisonCam.sys    4/30/2007 12:03:08 PM        
RaInfo.sys    1/4/2008 2:57:14 PM       
LMIRfsDriver.sys    7/14/2008 12:26:56 PM       
UltraMonUtility.sys    11/13/2008 9:10:30 PM       
spldr.sys    5/11/2009 12:56:27 PM        
GEARAspiWDM.sys    5/18/2009 8:17:04 AM        
PxHlpa64.sys    6/23/2009 7:16:35 PM        
AsUpIO.sys    7/5/2009 10:21:38 PM

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[ImpetuousRacer]

Thanks for this info!

I have an Asus P6X58D-E motherboard. The manufacture has the latest version of their Ai Charger for my board at 1.00.06

I found a newer version of the Ai Charger for the Asus P6X58-E Pro with version 1.02.01 and used that. It fixed the compatibility issues with various cables I had. Unfortunately, it looks like it isn't fully compatible and causing the Blue Screens It's a new setup so there has been a lot of updates, installs and tweaks and didnt put together this was the culprit.

I've uninstalled it and havent had any more blue screens. I will also look to see if I can find newer driver version of the others listed. Ill keep an eye on it, but pretty sure that was it.

Do you have any documentation you could point me to on how you found that information out from the dump files?

Thanks again for your time and help with this, it's much appreciated!

 

[zigzag3143]

Thanks for this info!

I have an Asus P6X58D-E motherboard. The manufacture has the latest version of their Ai Charger for my board at 1.00.06

I found a newer version of the Ai Charger for the Asus P6X58-E Pro with version 1.02.01 and used that. It fixed the compatibility issues with various cables I had. Unfortunately, it looks like it isn't fully compatible and causing the Blue Screens It's a new setup so there has been a lot of updates, installs and tweaks and didnt put together this was the culprit.

I've uninstalled it and havent had any more blue screens. I will also look to see if I can find newer driver version of the others listed. Ill keep an eye on it, but pretty sure that was it.

Do you have any documentation you could point me to on how you found that information out from the dump files?

Thanks again for your time and help with this, it's much appreciated!

We all use WinDeBugger to analyze the DMP files. Fairly steep learning curve.

 

[carwiz]

We all use WinDeBugger to analyze the DMP files. Fairly steep learning curve.

Not to mention waiting for "Debuggee" to connect.

 

[zigzag3143]

We all use WinDeBugger to analyze the DMP files. Fairly steep learning curve.

Not to mention waiting for "Debuggee" to connect.

There is a special command in WinDB for that !pause:20000. {grin}

Seriously the different timezones can and do, throw a wrench in the works.

 

[ImpetuousRacer]

After uninstalling aicharger, the problem still persists. I've uploaded an updated dump file.

 

[carwiz]

yk62x64.sys appears to be causing the problem. According to the Driver Reference, it's a Marvell YuKon controller driver that caused pci.sys driver to timeout. This sounds like a network driver, but I'm not familiar with WiFi. Are your motherboard drivers up to date?

0: kd> !irp fffffa800e69ccc0
Irp is active with 3 stacks 2 is current (= 0xfffffa800e69cdd8)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa800b268050 00000000 fffff800032cc200-fffffa800d047580 [B][U]Success Error Cancel pending[/U][/B]
       Unable to load image \SystemRoot\system32\DRIVERS\yk62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for yk62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for yk62x64.sys
 \Driver\yukonw7 nt!PopSystemIrpCompletion
   Args: 00014400 00000000 00000004 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800d047580    
   Args: 00000000 00000000 00000000 00000000

 

[carwiz]

I found this Marvell YuKon driver setup from the Marvell site. It's for Windows 7 x64 dated 3/27/12 version 11.45.4.3 but you should check with your motherboard manufacturer and see if they have an update.

Marvell - Support - Driver Downloads#

Hmmmmm That # sign is supposed to be part of the url. If that link doesn't work, try this one:
Marvel Driver Download

 

[ImpetuousRacer]

Thanks. The driver from Marvell is newer than what the manufacturer has listed, so downloaded the driver from the Marvell website.

I've updated the driver to 11.45.4.3 "Windows Setup Installer (32- and 64-bit) for Yukon Controllers" - 03/27/12

I was using the 11.45.3.3 driver listed for "Windows 7 & Server 2008 R2 x64 (64-bit)" - 1/20/12

Device Manager under properties now shows the newer driver of 11.45.4.3.
However, when clicking driver details, I noticed it still says for the yk62x64.sys - the file version is 11.45.1.3?

Is this correct?

 

[carwiz]

Hmmmmm. That doesn't sound right. Did you reboot?

 

[ImpetuousRacer]

I have a PCI express USB Card that I had a Wireless Adapter plugged into. It looks like that wasn't working correctly and causing problems. I moved the wi-fi stick to the motherboard USB. That seemed to have resolved the problem as I havent had a Blue Screen in a couple days. Thanks guys for pointing me in the right direction!

 

[carwiz]

Glad you "got-er-goin"! And thanks for posting back.