Solved BSOD, DRIVER_POWER_STATE_FAILURE(9f) - ntoskrnl.exe

[nyles02]

Hi All,

Please help me, my PC is BSOD-ing while trying to I don't know, Sleep or Hibernate (I'm using hybrid). Sometimes it happens, and sometimes not for these past few days. I conducted some research and found out that it is because of a somewhat unstable driver. So..

a. I remember upgrading my graphics driver 2 weeks ago
b. I'm having problem with my mouse for this past month getting unplugged - plugged by itself
c. I recently installed HSS (3 days ago)
d. I have a yellow triangle with an exclamation point inside over my Teredo Tunneling Pseudo Interface under Device Manager.

Then here's the latest 3 dump files related to the issue:

https://app.box.com/s/afd7i71k78pv13uj1frq6egh0mfm5tz2

Please help, thanks!

Attached is the ZIP file that was generated by dm log collector, thanks!

 

[Arc]

Go to D-Link - TechSupport .... search for any possible update to the network adapter DGE-560T Gigabit PCI Express Ethernet Adapter. If obtained, download and install it.

Let us know the result.
______________________________________

Irp is active with 4 stacks 3 is current (= 0xfffffa800ba2e3a0)
 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
>[ 16, 2]   0 e1 fffffa8008d3b050 00000000 fffff80003b1a210-fffffa800bf36b70 Success Error Cancel pending
          Unable to load image \SystemRoot\system32\DRIVERS\DLKRTE64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for DLKRTE64.sys
*** ERROR: Module load completed but symbols could not be loaded for DLKRTE64.sys
 \Driver\DLKRTE64    nt!PopSystemIrpCompletion
            Args: 00015400 00000000 00000005 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800bf36b70    

            Args: 00000000 00000000 00000000 00000000
0: kd> lmvm DLKRTE64
start             end                 module name
fffff880`0469c000 fffff880`04726000   DLKRTE64 T (no symbols)           
    Loaded symbol image file: DLKRTE64.sys
    Image path: \SystemRoot\system32\DRIVERS\DLKRTE64.sys
    Image name: DLKRTE64.sys
    Timestamp:        Thu Jul 07 11:21:57 2011 (4E15497D)
    CheckSum:         00094A5A
    ImageSize:        0008A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[nyles02]

Hi Arc,

Thanks for your time, unfortunately the latest driver available from D-Link is the same as what I currently have, http://www.dlink.com.my/support/support_detail.asp . I will instead try re-installing it.

 

[Arc]

Hi Arc,

Thanks for your time, unfortunately the latest driver available from D-Link is the same as what I currently have, http://www.dlink.com.my/support/support_detail.asp . I will instead try re-installing it.

In that case you might need to either stop using that adapter or to disable sleep. Time will tell it clearly.

 

[nyles02]

Hi Arc,

Thanks for your time, unfortunately the latest driver available from D-Link is the same as what I currently have, http://www.dlink.com.my/support/support_detail.asp . I will instead try re-installing it.

In that case you might need to either stop using that adapter or to disable sleep. Time will tell it clearly.

Errrr, stop using it? :/ Anyway after re-installing the driver and reseating the adapter (it's a replacement adapter),my PC survived the night without BSOD-ing. I have to add that I also uninstalled Hotspot Shield. It went to Sleep with no problem and Hibernated with no problem, I'll continue to monitor this and if problem persist, I guess I'll just have to buy a new adapter?

Thanks for your time Arc!

 

[Arc]

The old driver may fail again. As long as it is working fine, continue using it. But if it starts to fail again, the old driver may not work again.

 

[nyles02]

Hi Arc,

I'm back, and the problem is back as well. I followed what you suggested, I disabled the adapter and now I'm using a USB LAN adapter but the problem still occurs, does disabling it not enough? Anyway, attached is a new ZIP file generated by the DM Log Collector. Also, if it's not too much to ask, can you tell me what file to access so I can check what driver is causing the BSOD?

Thanks!

 

[Arc]

It is ASIX AX88772B USB2.0 to Fast Ethernet Adapter that caused the BSOD.

Search for any possible updates to it in AX88772B - ASIX Electronics Corporation .... if found, apply it. See how it goes.
____________________________________

>[ 16, 2]   0 e1 fffffa800ab68050 00000000 fffff80003b14210-fffffa8008a626a0 Success Error Cancel pending
          Unable to load image \SystemRoot\system32\DRIVERS\ax88772b.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ax88772b.sys
*** ERROR: Module load completed but symbols could not be loaded for ax88772b.sys
 \Driver\AX88772B    nt!PopSystemIrpCompletion
            Args: 00015400 00000000 00000005 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa8008a626a0    

            Args: 00000000 00000000 00000000 00000000
0: kd> lmvm ax88772b
start             end                 module name
fffff880`0a6e9000 fffff880`0a70c000   ax88772b T (no symbols)           
    Loaded symbol image file: ax88772b.sys
    Image path: \SystemRoot\system32\DRIVERS\ax88772b.sys
    Image name: ax88772b.sys
    Timestamp:        Wed Sep 04 09:06:35 2013 (5226AAC3)
    CheckSum:         00025FB8
    ImageSize:        00023000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[nyles02]

Hi Arc,

My network card again? The latest driver is already installed for that adapter. Is it possible that the OS itself is failing on me?

 

[Arc]

Hi Arc,

My network card again? The latest driver is already installed for that adapter. Is it possible that the OS itself is failing on me?

I havent explored that way .... but if you want, I may.
But there is a chance, it seems to be a OEM key on a retail motherboard.

In between, disable sleep/hibernate. It is not very required for desktop computers, but it will minimize the possibility for a driver power state failure.

If it occurs even with sleep disabled, we have to think differently.

 

[nyles02]

Hi Arc,

I havent explored that way .... but if you want, I may.
But there is a chance, it seems to be a OEM key on a retail motherboard.

In between, disable sleep/hibernate. It is not very required for desktop computers, but it will minimize the possibility for a driver power state failure.

If it occurs even with sleep disabled, we have to think differently.

Hi Arc,

Everything is working well now, I think, after disabling sleep but I need it for my work, it's hard to explain but I need it.

If you have time, I would be very grateful if you can check if the OS is failing.

Thanks!

 

[Arc]

No, apparently the OS is not failing.

A stop 0x9F is a situation where a PnP device driver fails to react within a stipulated time, when the power state is changing (sleep/hibernation to wake up or the reverse).

A driver has failed to complete a power IRP within a specific time.

Arg1: 0000000000000003, [COLOR=Red]A device object has been blocking an Irp for too long a time[/COLOR]
Arg2: fffffa8009a48060, Physical Device Object of the stack
Arg3: fffff80000b9a3d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa80093f2b10, The blocked IRP

Why the power IRP is not being completed within the required time? Because it is blocked by a device object. Let us see what is it.

[COLOR=Red][U][B]Device object (fffffa800ab68050) is for:[/B][/U][/COLOR]
[COLOR=SeaGreen] InfoMask field not found for _OBJECT_HEADER at fffffa800ab68020
 \Driver\[COLOR=Red]AX88772B[/COLOR] [/COLOR]DriverObject fffffa8008437d70
Current Irp 00000000 RefCount 0 Type 00000017 Flags 00002050
DevExt fffffa800ab681a0 DevObjExt fffffa800ab698c0 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
[COLOR=Red]AttachedTo (Lower) fffffa8009883cf0 \Driver\[B]ACPI[/B][/COLOR]

So it is clearly stated that it is the ASIX AX88772B device, which troubles during sleep (ACPI).

Unfortunately you are choosing unstable network adapters one by one.

A Qualcomm Atheros one (USB, PCI or PCIe) may change the situation there, IMHO.

 

[nyles02]

No, apparently the OS is not failing.

A stop 0x9F is a situation where a PnP device driver fails to react within a stipulated time, when the power state is changing (sleep/hibernation to wake up or the reverse).

A driver has failed to complete a power IRP within a specific time.

Arg1: 0000000000000003, [COLOR=Red]A device object has been blocking an Irp for too long a time[/COLOR]
Arg2: fffffa8009a48060, Physical Device Object of the stack
Arg3: fffff80000b9a3d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa80093f2b10, The blocked IRP

Why the power IRP is not being completed within the required time? Because it is blocked by a device object. Let us see what is it.

[COLOR=Red][U][B]Device object (fffffa800ab68050) is for:[/B][/U][/COLOR]
[COLOR=SeaGreen] InfoMask field not found for _OBJECT_HEADER at fffffa800ab68020
 \Driver\[COLOR=Red]AX88772B[/COLOR] [/COLOR]DriverObject fffffa8008437d70
Current Irp 00000000 RefCount 0 Type 00000017 Flags 00002050
DevExt fffffa800ab681a0 DevObjExt fffffa800ab698c0 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
[COLOR=Red]AttachedTo (Lower) fffffa8009883cf0 \Driver\[B]ACPI[/B][/COLOR]

So it is clearly stated that it is the ASIX AX88772B device, which troubles during sleep (ACPI).

Unfortunately you are choosing unstable network adapters one by one.

A Qualcomm Atheros one (USB, PCI or PCIe) may change the situation there, IMHO.

Hi Arc,

Thanks for that thorough explanation. I'll buy a new Network Card then according to your advice.

Thank you so much!

 

[Arc]

You are welcome.