BSOD Power Driver State Failure After System Resume

Hi,

I had this problem a while back but it went away by itself (and me making sure all drivers, etc were up to date).
However, it is now back and I'm at a loss as to the cause.

Essentially, after I resume my laptop after sleep/hibernation then it works for 5-10 minutes and then I get the BSOD POWER_DRIVER_STATE_FAILURE. After rebooting everything works great again and I don't get any crashes. This doesn't happen if I switch the laptop off and then switch it on again, only after resume.

I've attached the SF Diagnostics Tool zip, and any pointers would be very much appreciated.

Thanks!

There's no crash dumps in the folder uploaded:

• Blue Screen of Death (BSOD) Posting Instructions

Whoops, sorry about that. I have the kernel memory dump but that is ~600MB.
Should I upload that somewhere (way to big an attachment for here - any preference on file host?), or just wait for the next BSOD now I've switched the settings to Minidump?

Thanks

Wait for the next BSOD, keep the settings for Minidump.

Hi again,

Oddly, I had avoided the BSOD since April, but I've had it a few times again in exactly the same circumstances, so though I would post here again with a minidump and all SF diagnostics

Thanks for any help!

Code:

BugCheck 9F, {3, fffffa800a3d9060, fffff80004a413d8, fffffa800e358b80}

Probably caused by : usbhub.sys

Code:

0: kd> !irp fffffa800e358b80
Irp is active with 10 stacks 9 is current (= 0xfffffa800e358e90)
 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
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa800a3d9060 00000000 00000000-00000000    pending
	       \Driver\usbhub
			Args: 00051100 00000001 00000001 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800b3439b0    

			Args: 00000000 00000000 00000000 00000000

This bugcheck indicates that a device object is blocking a IRP for too long. The major function code 16 (IRP_MJ_POWER), means that the IRP has been sent to a power-related stack, with the minor function code 2 (IRP_MN_SET_POWER), indicating that a request has been sent.

Your raw stack trace indicates that your Intel onboard graphics card is causing issues, please update the driver from here - Intel® Driver Update Utility

Code:

0: kd> lmvm igdkmd64
start             end                 module name
fffff880`0f25a000 fffff880`1006a000   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Mon Mar 19 23:31:54 2012 (4F67C1EA)
    CheckSum:         00E13247
    ImageSize:        00E10000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Reduce the number of programs at startup, to avoid any driver or program conflicts:

• Troubleshoot Application Conflicts by Performing a Clean Startup
• Startup Programs - Change

Great - thanks for your help!

Welcome, any issues so far?

Nope, this seems to have done the trick so far - thanks again!

That's good to know, leave the thread open for a few more days, and then mark it has solved :)