Solved BSOD "Driver power State Failure" every few days

[Trinnion]

Every couple of days, I get a BSOD "Driver power State Failure".

Drivers are up-to-date, no overclocking.

Please see attached zip file with debug info (which is pretty much abracadabra to me).

Thanks for your help!

 

[essenbe]

Trinnion, I'll see if I can help you. I have looked at your last 6 dump files. 5 of the 6 blamed

 usbaapl64
start             end                 module name
fffff880`07e36000 fffff880`07e48000   usbaapl64 T (no symbols)           
    Loaded symbol image file: usbaapl64.sys
    Image path: \SystemRoot\System32\Drivers\usbaapl64.sys
    Image name: usbaapl64.sys
    Timestamp:        Tue Nov 27 17:38:02 2012 (50B54EDA)
    CheckSum:         0001669F
    ImageSize:        00012000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Which is your Apple iPod/iPhone Mobile USB device driver

Also blamed in 1 each was

EpfwLWF
start             end                 module name
fffff880`043eb000 fffff880`043f9000   EpfwLWF  T (no symbols)           
    Loaded symbol image file: EpfwLWF.sys
    Image path: \SystemRoot\system32\DRIVERS\EpfwLWF.sys
    Image name: EpfwLWF.sys
    Timestamp:        Thu Aug 15 09:55:11 2013 (520CEBCF)
    CheckSum:         0000AF76
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Which is ESET ESS/NOD32 driver
and

atikmpag
start             end                 module name
fffff880`03e7d000 fffff880`03f11000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Thu [COLOR=red]Mar 28 20:09:45 2013[/COLOR] (5154E9D9)
    CheckSum:         00091A60
    ImageSize:        00094000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Due to the frequency, I think Apple may be much of your problem. But, the other 2 do need to be updated as well. Was the graphics card preinstalled in the computer from Dell?

 

[Trinnion]

Hi essenbe, thanks,

Both the Apple and ESET drivers appear to be up-to-date (no updates required by ITunes or ESET, latest file/drivers versions when checked manually). I will update the graphics driver.

If the Apple USB driver is the most probable culprit, yet the driver (and iTunes) is the latest version, then what should be my next step?

Kind regards,
Bas

 

[Trinnion]

Oh, and yes, the Radeon HD 5870 is the original, pre-installed graphics card

 

[essenbe]

My experience with Apple is that it always causes problems with Windows, for me at least. I've had to do 2 reinstalls to completely get rid of it. Some people use it with no problems. Others have continuous problems with it. It has so many parts/services that seem to want to 'take over' that if you disable/uninstall any part of it, the program won't work or recognize your devices. You may try their support forums or troubleshooting guides to see if there is a fix for your problems. But, I know of none.

 

[Trinnion]

Thanks. Yeah I know iTunes is crappy. Each update seems to hold new surprises (unable to burn CD's, unable to sync my phone etc.).

I've googled and an Apple support forum suggested a USB conflict. Which triggered me, since my mouse (Steelseries Sensei) is dead after a BSOD reboot. I have to unplug and replug the mouse in order to let it work again (both mouse driver and firmware are up-to-date). Could this be related?

For now, I'll remove iTunes and re-install it and see if that helps.

 

[essenbe]

It's a possibility. Go to Dell's web site and download the latest Chipset driver for your rig. USB Drivers are usually in the chipset driver.

 

[Trinnion]

Thanks, Dell's auto-update feature did not find or install them - yet manually I've found Dell chipset drivers for the PCI Express bus, SMbus and the USB controller. I've installed these as well. Let's see if this gets rid of the BSODs.

Thanks essenbe!

 

[essenbe]

I hope that works for you. I am rapidly running out of solutions. If that does not work, this may http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html

At any rate I would save the drivers I downloaded for future problems/use. Also, I trust you downloaded drivers specific to your model and service number.

 

[Trinnion]

Yes, I got the right ones. Thanks. So, now I have:

- updated the graphics driver
- re-installed iTunes
- updated the USB chipset drivers (and PCI-E drivers)

Let's see if the system holds!

 

[essenbe]

Be sure to let me know.

 

[Trinnion]

Hi essenbe, so far a whole week without a glitch. I think it's fixed! Thanks.
If I run into a new BSOD, I'll make a new post on this forum.

 

[essenbe]

That's fantastic. I am glad you have it running like you want it. If you believe it is fixed, would you please mark this thread as solved. If you have any further problems, you can post back in this thread. I am subscribed and will get an email that you have posted. Thanks very much for giving your feedback and letting us know it is working well. Thanks.

 

[Trinnion]

Darn, just had a BSOD again. Another power driver state failure.

My iPhone was connected by USB (just charging) at the time the BSOD occured.

What file shoud I upload? Or should I follow all steps from the posting instrcuctions (upload a complete zip-file)?

 

[essenbe]

Yea, upload the whole thing. Any Apple stuff causes problems for a lot of people, me included. I had to do 2 clean installs to get rid of iTunes, which gave me a fit. Apple programs what to take over the whole computer and have to run at startup or they won't work right. I run almost nothing at startup, except what I have to have.

 

[Trinnion]

Thanks essenbe. New files uploaded.

 

[essenbe]

Ok, this is pretty much the best I can do, right now

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8005c20710, fffff80000b9c518, fffffa8009ee1110}
*** WARNING: Unable to verify timestamp for usbaapl64.sys
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=red]usbaapl64.sys[/COLOR]
Probably caused by : usbaapl64.sys

usbaapl64
start             end                 module name
fffff880`07059000 fffff880`0706b000   usbaapl64 T (no symbols)           
    Loaded symbol image file: usbaapl64.sys
    Image path: \SystemRoot\System32\Drivers\usbaapl64.sys
    Image name: [COLOR=red]usbaapl64.sys[/COLOR]
    Timestamp:        Tue Nov 27 17:38:02 2012 (50B54EDA)
    CheckSum:         0001669F
    ImageSize:        00012000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

usbaapl64 is your Apple iPod/iPhone Mobile USB device driver

DRIVER_POWER_STATE_FAILURE (9f)
[COLOR=red]A driver has failed to complete a power IRP within a specific time.[/COLOR]
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8005c20710, Physical Device Object of the stack
Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa8009ee1110, The blocked IRP

So, basically your Apple device has blocked an I/O driver request Packet within an allotted time .

Also listed was

em008_64
start             end                 module name
fffffa80`084be000 fffffa80`085c9000   em008_64 T (no symbols)           
    Loaded symbol image file: em008_64.dat
    Image path: C:\Program Files\ESET\ESET Smart Security\em008_64.dat
    Image name: em008_64.dat
    Timestamp:        Wed Jul 09 07:16:02 2014 (53BD3282)
    CheckSum:         00000000
    ImageSize:        0010B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That is your ESET Smart Security

So, the logical assumption is that one is blocking the other or they are most likely having a conflict. Due to the fact that it said it couldn't load the symbols or image for either one, I would assume that the Apple Device is blocking your Eset security or they are probably having a conflict because neither could be loaded, most likely other things too, which made windows crash.

 

[Trinnion]

Thanks essenbe.

iTunes and ESET used to work nicely next to eachother. So, probably somewhere along the line, program-updates started to cause conflicts.

I'm gonna try a driver rollback for usbaapl64.sys

I'll keep you posted,

 

[Trinnion]

Ok, so the driver rollback didn't work (the PC couldn't connect to the iPhone anymore).

What about this hypothesis: ESET tries to scan all attached drives, including USB sticks and mobile devices. The iPhone does not allow to be scanned ("your Apple device has blocked an I/O driver request Packet within an allotted time") and bang! BSOD.

If this may be the case, I can check if I can get ESET *not* to scan my iPhone when it's connected.

 

[Trinnion]

Not allowing ESET to scan the iPhone when it's connected, seems to work. (If not, I'll report back here again).

Essenbe, thanks for your analysis.