DRIVER_POWER_STATE_FAILURE

[curtixman]

I have been experiencing this issue intermittently for a long time. Sometimes it will happen several times in a day and then not happen for a week or more.
WhoCrashed finds no offending drivers and so I am at a loss.

System Information (local)
Computer name: XXXXXXXX
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\Windows
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., X99-DELUXE
CPU: GenuineIntel Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 34267729920 bytes (31.9GB)

On Tue 1/8/2019 12:55:27 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010819-18500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0x9F (0x3, 0xFFFFBE01DCBA3E20, 0xFFFF9208AD0538D0, 0xFFFFBE01E59E7AB0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Trouble]

I don't see anything definitive.
There is a mention of a Broadcom chipset Bluetooth device driver
Unable to load image bcbtums.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bcbtums.sys
bcbtums.sys 1/21/2016
AND
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: UsbHub3.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 62126b5b
MODULE_NAME: UsbHub3
FAULTING_MODULE: fffff80897270000 UsbHub3
AND
A somewhat weird mention of your CD-ROM way down in the stack
ffff9208`ad0532c8 fffff808`91900120 cdrom!WPP_1850a6d149bc32702d01ac09fb945719_Traceguids

Which I wouldn't normally mention unless you have an external optical drive attached to a USB port and or you are using some software package that supports the CD device which has its' own driver.

 

[curtixman]

No, I don't have either of those things.
A couple days ago I had the restart with the BSOD 5 times in a matter of a couple hours. Now it has been two days and not once.
Seems to be no pattern of consistency. Sometimes I am using it and doing something and sometimes not.

 

[Trouble]

No, I don't have either of those things.

Actually you do....
When I enumerate your drivers I can see something called
vclone.sys which appears to be a software driver installed by CloneDVD

I'm not saying that, that is producing your problem, I'm just suggesting that sometime if not often software that installs drivers so that they can pretend to be hardware do not always behave well.
That particular one is from 2014 so it's going on five years old, just saying that maybe they might have an updated version and that, that's the kind of thing you need to look for …..
IF, all your crashes are pointing towards a DRIVER_POWER_STATE_FAILURE

 

[curtixman]

Actually you do....
When I enumerate your drivers I can see something called
vclone.sys which appears to be a software driver installed by CloneDVD

I'm not saying that, that is producing your problem, I'm just suggesting that sometime if not often software that installs drivers so that they can pretend to be hardware do not always behave well.
That particular one is from 2014 so it's going on five years old, just saying that maybe they might have an updated version and that, that's the kind of thing you need to look for …..
IF, all your crashes are pointing towards a DRIVER_POWER_STATE_FAILURE

Virtual CloneDrive. I just checked. I have 5.5.0.0 and that seems to be the latest version.

 

[curtixman]

Just happened again. It hasn't happened between my last message and now and then twice in the last hour.

 

[curtixman]

So a couple hours later now it has happened 3 more times

 

[curtixman]

Is no one able to help diagnose this?