BSOD DRIVER_POWER_STATE_FAILURE - Windows 8.1 x64

A

architec

Member
Joined
May 29, 2015
Posts
9
Hello,
I have an occasional (~once per day) BSOD on my Asus G771JW laptop. The OS is OEM, already came with 8.1. The BSOD states DRIVER_POWER_STATE_FAILURE in ntoskrnl.exe, appears completely randomly, including when the pc is idle. I already tried disabling the bluetooth device according to some suggestion, did not help. I attached the bsod dump and the system health report, would be grateful if someone could point me at which driver is causing the problem.

-CPU i7-4720HQ
-VGA Geforce GTX960M
-Motherboard/PSU Laptop
 

Attachments

re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

Code: 
4: kd> !irp ffffe001a9447670
Irp is active with 6 stacks 4 is current (= 0xffffe001a9447818)
 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
>[ 16, 2]   0 e1 ffffe001a9404350 00000000 fffff80143ba7b30-ffffe001a9456cf0 Success Error Cancel pending
	       \Driver\ACPI	pci!PciBusPowerUpCompletion
			Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 ffffe001a9456ba0 00000000 fffff8038131f1cc-ffffe001a9446338 Success Error Cancel pending
	       \Driver\pci	nt!PopRequestCompletion
			Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-ffffe001a9446338    

			Args: 00000000 00000000 00000000 00000000

4: kd> !devstack ffffe001a93bd880
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffffe001a9456ba0  \Driver\pci        ffffe001a9456cf0  InfoMask field not found for _OBJECT_HEADER at ffffe001a9456b70

  ffffe001a9404350  \Driver\ACPI       ffffe001a930a7f0  InfoMask field not found for _OBJECT_HEADER at ffffe001a9404320

> ffffe001a93bd880  \Driver\pci        ffffe001a93bd9d0  Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode ffffe001a9402d30 :
  DeviceInst is "PCI\VEN_8086&DEV_0C01&SUBSYS_186D1043&REV_06\3&11583659&1&08"
  ServiceName is "pci"

Can we have a Kernel memory dump, it seems a lot wasn't saved, as usual, in this minidump.
There's some PCI device holding up IRPs, but it isn't being recognised.

Go the Start
Right click My Computer
Select Properties
Click Advanced system settings
Click on the Advanced tab
Select Settings under Startup and Recovery
Then under Write debugging information select Kernel memory dump.

Once a dump is created go to:
C:/Windows/memory.dmp
Copy the file to the desktop, zip it up and upload it to a file sharing site like Onedrive. After the upload is done post the download link in your next reply.
 
re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

Code: 
4: kd> [COLOR=#008000].dumpdebug[/COLOR]
----- 64 bit Kernel Mini Dump Analysis

DUMP_HEADER64:
MajorVersion        0000000f
MinorVersion        00002580
KdSecondaryVersion  00000000
DirectoryTableBase  00000000`001ab000
PfnDataBase         fffff803`815630f0
PsLoadedModuleList  fffff803`814d9850
PsActiveProcessHead fffff803`814bf580
MachineImageType    00008664
NumberProcessors    00000008
BugCheckCode        [COLOR=#ff0000]0000009f[/COLOR]
BugCheckParameter1  00000000`00000003
BugCheckParameter2  ffffe001`a93bd880
BugCheckParameter3  ffffd000`f9079960
BugCheckParameter4  [COLOR=#008000]ffffe001`a9447670[/COLOR]
KdDebuggerDataBlock fffff803`814a6530
ProductType         00000001
SuiteMask           00000310
WriterStatus        00000000
MiniDumpFields      00000cff

[...]

Code: 
4: kd> [COLOR=#008000]!irp ffffe001`a9447670[/COLOR]
Irp is active with 6 stacks 4 is current (= 0xffffe001a9447818)
 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
>[ [COLOR=#0000ff]16[/COLOR], [COLOR=#800080]2[/COLOR]]   0 e1 ffffe001a9404350 00000000 fffff80143ba7b30-ffffe001a9456cf0 Success Error Cancel [COLOR=#ff0000]pending[/COLOR]
           \Driver\ACPI    pci!PciBusPowerUpCompletion
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 ffffe001a9456ba0 00000000 fffff8038131f1cc-ffffe001a9446338 Success Error Cancel pending
           \Driver\pci    nt!PopRequestCompletion
            Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-ffffe001a9446338    

            Args: 00000000 00000000 00000000 00000000

As we can see, the IRP which has been stuck is the Power IRP which is used to set the power state of the device. This is common among power state transitions.

Code: 
4: kd> [COLOR=#008000]knL[/COLOR]
 # Child-SP          RetAddr           Call Site
00 ffffd000`f9079928 fffff803`81408782 nt!KeBugCheckEx
01 ffffd000`f9079930 fffff803`814086a2 nt!PopIrpWatchdogBugcheck+0xde
02 ffffd000`f9079990 fffff803`812a62d8 [COLOR=#ff0000]nt!PopIrpWatchdog+0x32[/COLOR] <-- Crash Dump begins here
03 ffffd000`f90799e0 fffff803`813547ea nt!KiRetireDpcList+0x4f8
04 ffffd000`f9079c60 00000000`00000000 nt!KiIdleLoop+0x5a

Code: 
4: kd> [COLOR=#008000]!devstack ffffe001a93bd880[/COLOR]
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffffe001a9456ba0  \Driver\pci        ffffe001a9456cf0  InfoMask field not found for _OBJECT_HEADER at ffffe001a9456b70

  ffffe001a9404350  \Driver\ACPI       ffffe001a930a7f0  InfoMask field not found for _OBJECT_HEADER at ffffe001a9404320

> [COLOR=#ff8c00]ffffe001a93bd880[/COLOR]  \Driver\pci        ffffe001a93bd9d0  Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode ffffe001a9402d30 :
  DeviceInst is "PCI\VEN_[COLOR=#ff0000]8086[/COLOR]&DEV_[COLOR=#0000ff]0C01[/COLOR]&SUBSYS_186D1043&REV_06\3&11583659&1&08"
  ServiceName is "pci"

I've examined the Vendor ID and Device ID, and it appears that the Vendor ID belongs to an Intel device. I couldn't find any mention of your Device ID. I have a feeling it may be related to your chipset drivers.

Could you please run Driver Verifier as per these instructions?

https://www.sysnative.com/forums/bs...er-bsod-related-windows-10-8-1-8-7-vista.html
 
re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

x BlueRobot said:
Code: 
4: kd> [COLOR=#008000].dumpdebug[/COLOR]
----- 64 bit Kernel Mini Dump Analysis

DUMP_HEADER64:
MajorVersion        0000000f
MinorVersion        00002580
KdSecondaryVersion  00000000
DirectoryTableBase  00000000`001ab000
PfnDataBase         fffff803`815630f0
PsLoadedModuleList  fffff803`814d9850
PsActiveProcessHead fffff803`814bf580
MachineImageType    00008664
NumberProcessors    00000008
BugCheckCode        [COLOR=#ff0000]0000009f[/COLOR]
BugCheckParameter1  00000000`00000003
BugCheckParameter2  ffffe001`a93bd880
BugCheckParameter3  ffffd000`f9079960
BugCheckParameter4  [COLOR=#008000]ffffe001`a9447670[/COLOR]
KdDebuggerDataBlock fffff803`814a6530
ProductType         00000001
SuiteMask           00000310
WriterStatus        00000000
MiniDumpFields      00000cff

[...]

Code: 
4: kd> [COLOR=#008000]!irp ffffe001`a9447670[/COLOR]
Irp is active with 6 stacks 4 is current (= 0xffffe001a9447818)
 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
>[ [COLOR=#0000ff]16[/COLOR], [COLOR=#800080]2[/COLOR]]   0 e1 ffffe001a9404350 00000000 fffff80143ba7b30-ffffe001a9456cf0 Success Error Cancel [COLOR=#ff0000]pending[/COLOR]
           \Driver\ACPI    pci!PciBusPowerUpCompletion
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 ffffe001a9456ba0 00000000 fffff8038131f1cc-ffffe001a9446338 Success Error Cancel pending
           \Driver\pci    nt!PopRequestCompletion
            Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-ffffe001a9446338    

            Args: 00000000 00000000 00000000 00000000

As we can see, the IRP which has been stuck is the Power IRP which is used to set the power state of the device. This is common among power state transitions.

Code: 
4: kd> [COLOR=#008000]knL[/COLOR]
 # Child-SP          RetAddr           Call Site
00 ffffd000`f9079928 fffff803`81408782 nt!KeBugCheckEx
01 ffffd000`f9079930 fffff803`814086a2 nt!PopIrpWatchdogBugcheck+0xde
02 ffffd000`f9079990 fffff803`812a62d8 [COLOR=#ff0000]nt!PopIrpWatchdog+0x32[/COLOR] <-- Crash Dump begins here
03 ffffd000`f90799e0 fffff803`813547ea nt!KiRetireDpcList+0x4f8
04 ffffd000`f9079c60 00000000`00000000 nt!KiIdleLoop+0x5a

Code: 
4: kd> [COLOR=#008000]!devstack ffffe001a93bd880[/COLOR]
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffffe001a9456ba0  \Driver\pci        ffffe001a9456cf0  InfoMask field not found for _OBJECT_HEADER at ffffe001a9456b70

  ffffe001a9404350  \Driver\ACPI       ffffe001a930a7f0  InfoMask field not found for _OBJECT_HEADER at ffffe001a9404320

> [COLOR=#ff8c00]ffffe001a93bd880[/COLOR]  \Driver\pci        ffffe001a93bd9d0  Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode ffffe001a9402d30 :
  DeviceInst is "PCI\VEN_[COLOR=#ff0000]8086[/COLOR]&DEV_[COLOR=#0000ff]0C01[/COLOR]&SUBSYS_186D1043&REV_06\3&11583659&1&08"
  ServiceName is "pci"

I've examined the Vendor ID and Device ID, and it appears that the Vendor ID belongs to an Intel device. I couldn't find any mention of your Device ID. I have a feeling it may be related to your chipset drivers.

Could you please run Driver Verifier as per these instructions?

https://www.sysnative.com/forums/bs...er-bsod-related-windows-10-8-1-8-7-vista.html
Click to expand...

It's quite rare that you can find anything on the device ID in my experience.
 
re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

It sometimes works, but otherwise, like you stated it isn't really worth anything.
 
re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

Thanks for the reply.
I have enabled the full kernel dump and the driver verifier and tried to reboot my PC. It got stuck rebooting for a few minutes with a black screen and after finally rebooting displayed the error reporting message and stated that it made a dump. Now it has displayed the BSOD already twice in a 15 minutes period (normally it happens once per day), although it is still DRIVER_POWER_STATE_FAILURE instead of DRIVER_VERIFIER_BSOD. I have uploaded the full dump files, and rerun the bsod collection app after the new crashes. The information is in the links:
https://dl.dropboxusercontent.com/u/3319605/MEMORY.ZIP
https://dl.dropboxusercontent.com/u/3319605/MEMORY2.ZIP
https://dl.dropboxusercontent.com/u/3319605/SysnativeFileCollectionApp.zip

Please tell if you need any other information
 
re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

Have you disabled Driver Verifier now?

I'll examine the dump files and see what I can find.
 
I found a possibly outdated Intel Wireless driver in the raw stack of the processor where the crash was produced:

Code: 
6: kd> [COLOR=#008000]lmvm Netwbw02[/COLOR]

start             end                 module name
fffff800`3e0ff000 fffff800`3e47e000   Netwbw02   (no symbols)           
    Loaded symbol image file: Netwbw02.sys
    Image path: \SystemRoot\system32\DRIVERS\Netwbw02.sys
    Image name: Netwbw02.sys
    Timestamp:        [COLOR=#ff0000]Mon Nov 17 09:17:19 2014[/COLOR] (5469BD1F)
    CheckSum:         0035CFDD
    ImageSize:        0037F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Download Page - https://downloadcenter.intel.com/

I've been doing a little more investigation, I just been looking into the Power Management of the Intel adapter:

Code: 
6: kd> [COLOR=#008000]!ndiskd.miniport ffffe001b737c1a0 -pm[/COLOR]


POWER MANAGEMENT

    Bus Capabilities (IRP_MN_QUERY_CAPABILITIES):
    SystemWake         PowerSystemSleeping3
    DeviceWake         D3

    System state       Device state                     
    Working            D0
    S1                 PowerDeviceUnspecified
    S2                 PowerDeviceUnspecified
    S3                 D3
    S4 (Hibernate)     D3
    S5 (Shutdown)      D3

I know most device stacks will lead to the PCI Bus, but at least it shows some similarities with the crash dump:

Code: 
6: kd> [COLOR=#008000]!devstack ffffe001b737c050[/COLOR]
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffffe001b6e40630  \Driver\vwifibus   ffffe001b6e35ff0  
> ffffe001b737c050  \Driver\NETwNb64   ffffe001b737c1a0  NDMP1
  ffffe001b439d460  \Driver\ACPI       ffffe001b3163910  
  ffffe001b439d810  \Driver\ACPI       ffffe001b3163c90  
  ffffe001b43a0060  \Driver\pci        ffffe001b43a01b0  NTPNP_PCI0016
!DevNode ffffe001b439c010 :
  DeviceInst is "PCI\VEN_[COLOR=#0000cd]8086[/COLOR]&DEV_[COLOR=#800080]08B1[/COLOR]&SUBSYS_41708086&REV_BB\4851B7FFFF6AB68E00"
  ServiceName is "[COLOR=#ff0000]NETwNb64[/COLOR]"

Here's some power state history:

Code: 
6: kd> [COLOR=#008000]!ndiskd.miniport ffffe001b737c1a0 -log
[/COLOR]

MINIPORT PM & PNP EVENTS

    Event              Timestamp           (most recent event at bottom)        
    DeviceAdded
                       312 ms later
    DeviceStart
                       78 ms later
    MiniportInitialized
                       3230 ms later
    MiniportRestarted
                       16 minutes later
    Dx_SystemSleep
                       81 ms later
    Dx_Complete
                       2 hours later
    D0_SystemResume
                       129 ms later
    D0_Complete
                       15 minutes later
    Dx_SystemSleep
                       84 ms later
    Dx_Complete
                       2 hours later
    D0_SystemResume
                       128 ms later
    D0_Complete
                       40 seconds later
    Dx_SystemSleep
                       118 ms later
    Dx_Complete
    D0_SystemResume
                       122 ms later
    D0_Complete
                       3 hours later
    Dx_SystemSleep
                       112 ms later
    Dx_Complete
    D0_SystemResume
                       124 ms later
    D0_Complete
                       Sat May 30 13:38:26.944 2015 (UTC + 1:00)
 
Last edited:
re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

Furthermore, judging from the IoCompletionRoutine for the current IRP, it appears to be a Power Up request, and thus usually leads to the the Device State being changed to D0.
 
re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

Since enabling the driver verifier it produces the failure each time I try to shutdown/restart the PC. Verifier is running, though its status is still "no drivers verified". Analyzing the logs all the errors are the same - DRIVER_POWER_STATE_FAILURE. I will try updating the Intel wireless driver now and see if it helps

Edit: After updating I managed to at least restart the PC without a crash with verifier enabled. Let's see if it really helps.
Edit2: verifier /query now displays some information about a number of verified drivers
 
re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

Good, please keep us updated. Hopefully you won't experience any more crashes.
 
re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

Unfortunately I got one more crash today. I will enable the verifier again. Anything else I could do to help identify the problem?
 
re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

After enabling verifier once again the PC won't even boot now. After displaying the manufacterer logo it is just stuck with a black screen.
Edit: Managed to run system recovery. Looks like it boots now
 
re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

Was the crash a BSOD?

If so, could you please upload the dump file.
 
re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

I can't really tell right now since I had to run system restore after turning on driver verifier and apparently the latest dump and latest error logs are gone. It had the same behaviour - when rebooting the PC it got stuck with a black screen for a minute or so and upon the next system startup it displayed the message that the "system had a problem, let's send an error report to microsoft". I enabled verifier an had to do a system restore after that.

If (likely when) I get another crash, I'll upload the dump immediately
 
re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

Within the very first Dump 052815-5484-01.dmp, a small one i discovered

> BugCheck 9F, {3, ffffe001a93bd880, ffffd000f9079960, ffffe001a9447670}

> Probably caused by : pci.sys

Sounds OK

4: kd> !devnode ffffe001a9402a50
DevNode 0xffffe001a9402a50 for PDO 0xffffe001a93bc060
Parent 0xffffe001a93a0b20 Sibling 0xffffe001a9402490 Child 0xffffe001af6c7d30
InstancePath is "PCI\VEN_8086&DEV_0416&SUBSYS_186D1043&REV_06\3&11583659&1&10"
ServiceName is "igfx"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[10] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[09] = DeviceNodeEnumeratePending (0x30c)
StateHistory[08] = DeviceNodeStarted (0x308)
StateHistory[07] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[06] = DeviceNodeEnumeratePending (0x30c)
StateHistory[05] = DeviceNodeStarted (0x308)
StateHistory[04] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[03] = DeviceNodeEnumeratePending (0x30c)
StateHistory[02] = DeviceNodeStarted (0x308)
StateHistory[01] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[00] = DeviceNodeEnumeratePending (0x30c)
StateHistory[19] = DeviceNodeStarted (0x308)
StateHistory[18] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[17] = DeviceNodeEnumeratePending (0x30c)
StateHistory[16] = DeviceNodeStarted (0x308)
StateHistory[15] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[14] = DeviceNodeEnumeratePending (0x30c)
StateHistory[13] = DeviceNodeStarted (0x308)
StateHistory[12] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[11] = DeviceNodeEnumeratePending (0x30c)
Flags (0x6c0000f0) DNF_ENUMERATED, DNF_IDS_QUERIED,
DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED,
DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_LOWER_CLASS_FILTERS,
DNF_NO_UPPER_DEVICE_FILTERS, DNF_NO_UPPER_CLASS_FILTERS
Click to expand...
While CPU is identifyed as
> ProcessorNameString = REG_SZ Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz

what matches OP's Discription

the later revealed Chipset Bluerobot stumbled upon & myself got the same result:

> !DevNode ffffe001a9402d30 :
> DeviceInst is "PCI\VEN_8086&DEV_0C01&SUBSYS_186D1043&REV_06\3&11583659&1&08"

which decodes to an
Intel Xenon(R) CPU E3-1200 v3/4th Gen Core CPU PCI Express Controller x16 = 0C01

i would likely declare that Mainboard / CPU as the failure, unusual a cpu changes it's ID in that way?

Other possibility is memory, so a memtest might clear up that myteriousity, if not L2 itself is the Problem?

Just an Idea from my findings.

regards
Michael
 
re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

Have you tried booting to Safe Mode and seeing if crashes there?
 
Re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

So far after restoring the system and updating the drivers once more it haven't crashed for 3 days. This is with driver verifier disabled. If it crashes again I will post all the information I can get.
 
Re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

Got one more crash today. Once again DRIVER_POWER_STATE_FAILURE. I am attaching the latest memory dump.
https://dl.dropboxusercontent.com/u/3319605/MEMORY3.ZIP

BlueRobot, I could boot into safe mode and check but this would not be a sure way - the crashes are absolutely random and seemingly a few days may pass without a crash. Since I use the laptop for work, I don't think I could use it for a week exclusively in safe mode. Would there be some other way of determining the faulty driver from the dump or with some testing utility? I could try enabling the driver verifier once again and maybe going over the drivers one by one...
 
Re: BSOD DRIVER_POWER_STATE_FAILURE Windows 8.1 x64

I've enabled the driver verifier again and got a crash in 30 minutes. Seemingly it still fails to capture the error - it's DRIVER_POWER_STATE_FAILURE instead of the verifier flagged BSOD. Should I upload one more dump?..
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top