Solved why did i get Windows 10 BSOD Driver Power State Failure

Razor2.3 August 3, 2015 at 13:58:24

You'll have to find out which driver is causing the fault, and update it. Unfortunately, that requires both the Windows debugger, and possibly modifying your memory dump settings. The other option is to update all of your drivers, and hope you got the buggy one in the process. How To Ask Questions The Smart Way

Hi, thank you for the reply (Razor 2.3) but I need more specific guidance - not a lot of tech knowledge I'm afraid.... I downloaded the blue screen view and after a second BSOD driver power state failure and a second minidump log (?) I am still none the wiser as to how to sort this. This is the second minidump info: 080415-20703-01.dmp 04/08/2015 22:22:54 DRIVER_POWER_STATE_FAILURE 0x0000009f 00000000`00000003 ffffe001`f32e4060 ffffd001`0fe06990 ffffe001`f8f61b80 ntoskrnl.exe ntoskrnl.exe+14d220 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.10240.16393 (th1_st1.150717-1719) x64 ntoskrnl.exe+14d220 C:\WINDOWS\Minidump\080415-20703-01.dmp 4 15 10240 1,292,992 04/08/2015 22:24:26 When attempting to google what to do I read about updating the BIOS but not sure where to go with this....

Razor2.3 August 5, 2015 at 12:23:04

If you zip up your c:\windows\memory.dmp file, and upload it somewhere I can get access to it, I can see if I can pinpoint the buggy driver. Other option is just to update all of your drivers, and see if the problem goes away. How To Ask Questions The Smart Way

Hi. Here is the link: https://onedrive.live.com/redir?res...

Razor2.3 August 10, 2015 at 10:33:12

✔ Best Answer

Okay, ran it through Windbg, and this is what I got. Try updating your Bluetooth drivers. I've only dealt with two PCs with both Win10 and Bluetooth, but they both needed their drivers updated to fix something, so this doesn't come as a surprise to me. DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: ffffe0016ed4b060, Physical Device Object of the stack Arg3: ffffd001279ec990, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffe0016bc56a80, The blocked IRP The actual crash is some driver is taking too long to do its job. As of Win8+, this is now a crash-able offense. 2: kd> !devobj ffffe0016ed4b060 Device object (ffffe0016ed4b060) is for: Cannot read info offset from nt!ObpInfoMaskToOffset \Driver\usbhub DriverObject ffffe0016f58fbb0 Current Irp 00000000 RefCount 2 Type 00000022 Flags 00003040 DevExt ffffe0016ed4b1b0 DevObjExt ffffe0016ed4bd80 DevNode ffffe0016ed46800 ExtensionFlags (0x00000800) DOE_DEFAULT_SD_PRESENT Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN AttachedDevice (Upper) ffffe0016d39b570 \Driver\ACPI Device queue is not busy. It's just a generic USB hub, so let's look at a different view. 2: kd> !devnode ffffe0016ed46800 DevNode 0xffffe0016ed46800 for PDO 0xffffe0016ed4b060 Parent 0xffffe0016f2db010 Sibling 0xffffe0016f29db30 Child 0xffffe0016f30b8a0 InstancePath is "USB\VID_0CF3&PID_0036\6&2f43bf89&0&5" ServiceName is "BTHUSB" TargetDeviceNotify List - f 0xffffc00189e37ad0 b 0xffffc00189e37ad0 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 (0x48000130) DNF_ENUMERATED, DNF_IDS_QUERIED, DNF_NO_RESOURCE_REQUIRED, DNF_NO_LOWER_CLASS_FILTERS, DNF_NO_UPPER_CLASS_FILTERS CapabilityFlags (0x00041e03) DeviceD1, DeviceD2, SurpriseRemovalOK, WakeFromD0, WakeFromD1, WakeFromD2 Unknown flags 0x00040000 This is more interesting, and references bthusb.sys, which is why I'm pointing the finger at the Bluetooth drivers. How To Ask Questions The Smart Way