Question
1492 views

Windows 8 Blue Screen - DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe

wiclee asked on

I have a new Sony Vaio Pro and have experienced system crashes on 3 occasions.  All the crashes happened after I resumed from Hibernate mode and were related to Bug Check DRIVER_POWER_STATE_FAILURE.  After the first two crashes, I ran the Sony diagnostics on both Memory and SSD and they passed the test.  I even sent my Vaio Pro to Sony Repair Depot for a stress test on Memory, Hard Drive and other hardware and they all passed.

I got my Vaio Pro back last Wednesday and refreshed the Windows 8 from scratch.  This morning, after resumed from Hibernate mode, I realised my Bluetooth mouse was not functioning.  So I shutdown the Laptop hoping a restart would fix the issue.  However, it took close to 5 minutes before it would shutdown and on Restart Windows gave a warning:

"Windows experienced problem with the shutdown.  Your PC ran into problem.  This problem case your PC to restart".

 

Bluescreen Viewer pointing it towards DRIVER_POWER_STATE_FAILURE caused by driver ntoskrnl.exe.

 

Bluescreen details as follows:

 

A problem has been detected and Windows has been shut down to prevent damage to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

DRIVER_POWER_STATE_FAILURE

If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed.

If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing.

If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then

select Safe Mode.

Technical Information:

*** STOP: 0x0000009f (0x0000000000000004, 0x000000000000012c, 0xfffffa80196707c0, 0xfffff880009ec810)

*** ntoskrnl.exe - Address 0xfffff80189072106 base at 0xfffff8018901e000 DateStamp

0x51a966cd

 

Here is my minidump file:

https://dl.dropboxusercontent.com/u/1928780/093013-7531-01.dmp

 

MSINFO32.nfo file:

https://dl.dropboxusercontent.com/u/1928780/MSINFO32.nfo

 

Memory dump file (don't know why this file is close to 550MB big):

https://dl.dropboxusercontent.com/u/1928780/MEMORY.DMP

 

 

p.s.  I suspect this may have something to do with my Bluetooth driver as I had experienced many occasions that Bluetooth driver had been disabled by Windows and the Event Viewer reported "The Local Bluetooth has failed in an undetermined manner and will not be used.  The driver has been unloaded".

 

Thanks in advance,

William

 

 

1 person had this question

Abuse history


The answered status icon Answer
Patrick Barker replied on
Hi William,

The attached DMP file is of the DRIVER_POWER_STATE_FAILURE (9f) bugcheck.

This bug check indicates that the driver is in an inconsistent or invalid power state.

BugCheck 9F, {4, 12c, fffffa80196707c0, fffff880009ec810}

The 1st parameter of the bugcheck is 4 which indicates that the power transition timed out waiting to synchronize with the Pnp subsystem.

The 2nd parameter is 12c which indicates that it timed out for a total of 12 seconds.

By default the crash dump is faulting UsbHub3.sys which is the USB3 HUB Driver (system driver and not the true cause and is being driven to fault by something else).

If we look further into the dump:

*** ERROR: Module load completed but symbols could not be loaded for btmhsf.sys

FAILURE_BUCKET_ID:  0x9F_4_btmhsf_IMAGE_UsbHub3.sys

Implicit thread is now fffffa80`196707c0

^^ If we run a !thread on address fffffa80`196707c0:

Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`20b42f20 fffff801`890bb7cb : fffffa80`00000001 00000000`00000000 00000000`00000003 00000000`00000000 : nt!KiSwapContext+0x76
fffff880`20b43060 fffff801`890ba60f : fffffa80`18b23ef8 fffff880`0115a178 00000000`00000000 fffff880`0622a202 : nt!KiCommitThreadWait+0x23b
fffff880`20b43120 fffff880`06114700 : fffffa80`16115fd8 fffff880`00000000 00000001`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x1cf
fffff880`20b431b0 fffff880`06117ef0 : 00000000`00000018 fffff880`0622a2f8 00000000`00000000 00000000`00000018 : btmhsf+0x33700
fffff880`20b431f0 fffff880`060fb1e4 : fffffa80`17a00030 fffff880`20b433b0 fffff880`0622a2f8 00000000`00000000 : btmhsf+0x36ef0
fffff880`20b43260 fffff880`060e2b84 : 0000057f`e9eaddd8 00000000`00000127 fffff880`0622a2f8 fffff880`0115a178 : btmhsf+0x1a1e4
fffff880`20b432b0 fffff880`060e2cce : 00000000`00000008 fffff880`20b43370 00000000`00000008 fffff880`20b43378 : btmhsf+0x1b84
fffff880`20b432e0 fffff880`0114ecb0 : fffffa80`16153860 00000000`00000000 fffff8a0`04c3a748 fffff801`89403cfe : btmhsf+0x1cce
fffff880`20b43310 fffff880`010e881d : 00000000`00000127 fffff880`20b433b0 00000000`00000119 fffffa80`16153860 : Wdf01000!FxPkgPnp::PnpEventSurpriseRemoveIoStarted+0x2c
fffff880`20b43340 fffff880`010e9032 : fffffa80`16153980 fffffa80`16153988 fffffa80`16153860 fffff880`20b434c0 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a1
fffff880`20b433e0 fffff880`010e8cdd : 00000000`00000000 fffff880`20b434c0 fffffa80`16153970 fffffa80`16153860 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff880`20b43450 fffff880`0114d701 : 00000000`00000000 fffffa80`16153860 fffff880`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x18d
fffff880`20b434f0 fffff880`010d1ecf : fffffa80`16141b30 fffff880`20b43570 00000000`00000000 fffffa80`1615d1d0 : Wdf01000!FxPkgFdo::_PnpSurpriseRemoval+0x25
fffff880`20b43520 fffff880`010c99da : fffffa80`197b9010 fffffa80`197b9010 fffffa80`197b9010 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x18f
fffff880`20b43580 fffff880`010c9aa6 : fffffa80`197b9010 00000000`00000005 fffffa80`161531c0 fffff880`062fca20 : Wdf01000!FxDevice::Dispatch+0x19a
fffff880`20b435c0 fffff880`062e3cbe : fffffa80`197b9010 00000000`00000005 fffffa80`1615e190 00000000`00000000 : Wdf01000!FxDevice::DispatchWithLock+0xa6
fffff880`20b43600 fffff880`062e3484 : fffffa80`197b9010 00000000`00000000 fffffa80`1615e190 00000000`00000000 : bthport!BthDefaultPnpHandler+0x2a
fffff880`20b43630 fffff880`062e2cc1 : fffffa80`1615e190 fffff880`062fca17 fffffa80`1615e190 fffffa80`197b9010 : bthport!BthHandleSurpriseRemoval+0xc4
fffff880`20b436b0 fffff880`062e2b04 : fffffa80`197b9010 00000000`00000701 fffff880`062fca20 fffff880`20b43800 : bthport!BthHandlePnp+0x16d
fffff880`20b43700 fffff801`8940a8f7 : fffffa80`1615e040 00000000`c00000bb 00000000`00000000 fffff880`00a82180 : bthport!BthDispatchPnp+0x68
fffff880`20b43750 fffff801`89526d39 : 00000000`00000017 fffff880`20b43819 fffffa80`16137710 fffffa80`16137060 : nt!IopSynchronousCall+0xc7
fffff880`20b437c0 fffff801`895265e6 : fffff8a0`04069710 00000000`00000308 fffffa80`16137060 00000000`00000000 : nt!IopRemoveDevice+0xd9
fffff880`20b43880 fffff801`89526501 : fffffa80`16137710 00000000`00000000 fffff8a0`0c432a01 fffff880`20b43930 : nt!PnpSurpriseRemoveLockedDeviceNode+0xaa
fffff880`20b438d0 fffff801`89526468 : 00000000`00000000 00000000`00000000 fffff8a0`0c432a70 fffffa80`16137710 : nt!PnpDeleteLockedDeviceNode+0x5d
fffff880`20b43910 fffff801`89525bcb : 00000000`00000000 fffff880`20b43a70 fffff8a0`0b89e6f0 00000000`00000005 : nt!PnpDeleteLockedDeviceNodes+0x98
fffff880`20b43970 fffff801`893b52e5 : fffff880`20b43b88 00000000`00000000 fffff8a0`05764100 fffff8a0`00000000 : nt!PnpProcessQueryRemoveAndEject+0x2c3
fffff880`20b43ae0 fffff801`89418346 : fffff8a0`04069710 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x9d
fffff880`20b43b20 fffff801`890b62a1 : fffffa80`196707c0 fffff8a0`0b89e6f0 fffff801`8941805c fffffa80`16748130 : nt!PnpDeviceEventWorker+0x2ea
fffff880`20b43b80 fffff801`8904afd9 : fffffa80`00180000 00000000`00000080 fffff801`890b6160 fffffa80`196707c0 : nt!ExpWorkerThread+0x142
fffff880`20b43c10 fffff801`890ff7e6 : fffff880`00a82180 fffffa80`196707c0 fffffa80`06741b00 fffffa80`06765940 : nt!PspSystemThreadStartup+0x59
fffff880`20b43c60 00000000`00000000 : fffff880`20b44000 fffff880`20b3e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

We can see various bthport.sys (Bluetooth Bus Driver) routine calls which then eventually go into various btmhsf.sys before the bugcheck.

btmhsf.sys is the Intel Proset Bluetooth HighSpeed Filter Driver and is likely the overall culprit here. Update this driver ASAP - http://downloadcenter.intel.com/default.aspx?iid=gg_support-EN_01+home_downloadctr

or uninstall it if you don't plan on using BlueTooth.

---------------------------------------------------------------------

If after performing the above you're still crashing, remove and replace AVG with Windows 8's built-in Windows Defender for temporary troubleshooting purposes:

AVG removal tool - http://www.avg.com/us-en/utilities

Also, to answer your question as to why the MEMORY.DMP is so large is because it's a Kernel memory dump as opposed to a Small. Kernel memory dumps contain all of the memory the kernel was working with and that was in use at the time of the crash, therefore it's larger and provides much more information.

Regards,

Patrick
Debugger/Reverse Engineer.
1 person found this helpful

Abuse history


The answered status icon Answer
wiclee

This one was caused by 2 factors
Related to USBHUB3.SYS USB3 HUB Driver from Microsoft Corporation
Related to btmhsf.sys Bluetooth HighSpeed Filter Driver from Intel Corporation
0x9F_4_btmhsf_IMAGE_UsbHub3.sys

I would re-install the newest Intel BT driver and run a system file check to verify the OS. 
Learn how to run the SFC here


Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/
1 person found this helpful

Abuse history


progress