DRIVER_POWER_STATE_FAILURE Random BSOD at sleep/hibernate

A

ariftwister

New Member
Messages
37
Hello Guys I am getting Random BSOD in my Lenovo y500 at mostly sleep/hibernate/shutdown. I Know this is caused by Some driver but dont know which driver. I have attached SF tool files. Please take a look and say which driver is causing BSOD.
 
Hi Ariftwister,

I have analyzed your DUMP files and they are pointing towards = "BTFILTER.SYS" which is the Atheros Bluetooth Driver Package. In the driver list, there is mention of Microsoft Bluetooth package as well, hence I would suggest you to Uninstall the Atheros Bluetooth Driver Package.

============== MORE INFO =============

The Dump files have an error DRIVER_POWER_STATE_FAILURE (9f) with a bug check code of 9F. This means that an Input/Output Request packet has been blocked due to some faulty driver. The IRP packet was sent but was not returned with proper output and hence the bugcheck.

0: kd> !analyze -v*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************


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: ffffe00005253060, Physical Device Object of the stack
Arg3: fffff80081d36840, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe000064afbd0, The blocked IRP


Debugging Details:
------------------




DRVPOWERSTATE_SUBCODE: 3


IMAGE_NAME: usbhub.sys


DEBUG_FLR_IMAGE_TIMESTAMP: 5215f839


MODULE_NAME: usbhub


FAULTING_MODULE: fffff80001ecf000 usbhub


CUSTOMER_CRASH_COUNT: 1


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT


BUGCHECK_STR: 0x9F


PROCESS_NAME: System


CURRENT_IRQL: 2


ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre


DPC_STACK_BASE: FFFFF80081D3DFB0


STACK_TEXT:
fffff800`81d36808 fffff800`802081a6 : 00000000`0000009f 00000000`00000003 ffffe000`05253060 fffff800`81d36840 : nt!KeBugCheckEx
fffff800`81d36810 fffff800`802080c6 : ffffe000`06dd36e0 fffff131`5ebc6501 00000000`00000002 fffff800`8006da04 : nt!PopIrpWatchdogBugcheck+0xde
fffff800`81d36870 fffff800`800bef64 : ffffe000`06dd3718 fffff800`81d36939 ffffe000`06dd3758 00000000`00000002 : nt!PopIrpWatchdog+0x32
fffff800`81d368c0 fffff800`800bf478 : 00000000`00000001 ffffe000`0a4f7328 fffff800`802ff180 fffff800`80303760 : nt!KiProcessExpiredTimerList+0x1d8
fffff800`81d369a0 fffff800`8011b478 : fffff800`802ff180 00000000`0020b55a 00000000`006ef797 00000000`006ef7af : nt!KiExpireTimerTable+0x218
fffff800`81d36a40 fffff800`8006babc : ffffe000`00000000 00001f80`00000001 000001bb`de5fb8f6 00000000`00000002 : nt!KiTimerExpiration+0x148
fffff800`81d36af0 fffff800`801627ea : fffff800`802ff180 fffff800`802ff180 00000000`001a3fc0 fffff800`80357a80 : nt!KiRetireDpcList+0x19c
fffff800`81d36c60 00000000`00000000 : fffff800`81d37000 fffff800`81d31000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a




STACK_COMMAND: kb


FOLLOWUP_NAME: MachineOwner


IMAGE_VERSION: 6.3.9600.16384


FAILURE_BUCKET_ID: 0x9F_3_btfilter_IMAGE_usbhub.sys


BUCKET_ID: 0x9F_3_btfilter_IMAGE_usbhub.sys


ANALYSIS_SOURCE: KM


FAILURE_ID_HASH_STRING: km:0x9f_3_btfilter_image_usbhub.sys


FAILURE_ID_HASH: {e32271a1-eb13-6913-1626-4c8d704b5d5a}


Followup: MachineOwner
---------


0: kd> !irp ffffe000064afbd0
Irp is active with 12 stacks 11 is current (= 0xffffe000064aff70)
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
[ 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
[ 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
[ 0, 0] 0 0 00000000 00000000 00000000-00000000


Args: 00000000 00000000 00000000 00000000
>[ 16, 2] 0 e1 ffffe000051da030 00000000 fffff80080126d80-ffffe00006dd36e0 Success Error Cancel pending
Unable to load image \SystemRoot\system32\DRIVERS\btfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for btfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for btfilter.sys
\Driver\BtFilter nt!PopRequestCompletion
Args: 00000000 00000001 00000001 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-ffffe00006dd36e0


Args: 00000000 00000000 00000000 00000000
Click to expand...
I would also advice you on updating the Huawei Datacard Drivers as they are from 2010 and also could cause BSOD in the future due to compatibility issues.

Let me know in case the issue is not solved and I would be glad to assist you further.
 
Thanks for the Quick Help. I un installed Bluetooth driver and I wil report if BSOD happens again. Also Can you analyze other dump files and assure me that all the previous BSOD were happened due to this same Bluetooth driver??
 
Yups, I can confirm that all the DUMP files point towards this driver file only. All of the DUMP files have the same Bugcheck Error and Code and also the same ntoskrnl.exe address in the stack.

Test it out and let me know in case of any problems :)
 
ariftwister said:
I am Sorry to say this, The same BSOD happened again. I have attached latest dump files also.
Click to expand...

Hi Ariftwister,

I have analyzed your latest dump file and it is still returning the same error and the blocked IRP which is responsible for the BSOD. Have you removed your Bluetooth drivers mate? Because I can see that the same drivers for the bluetooth have been loaded and are present in there.

Try following this guide to completely remove your Bluetooth Adapters :-
Uninstall bluetooth driver - Microsoft Community

Let me know the results. In the meanwhile I will see if there is some more information available in the DUMP file and report back in case I find something odd.
 
Hi blueelvis,

At first I un installed atheros bluetooth using Control panel's Add/Remove programs option, then after visiting your link, I went to device manager and un installed Atheros driver. After restarting the driver is there automatically. So I again did that, the same happened. I have attached a screenshot which shows, how the driver and its services are automatically created.View attachment 41660
 
Try disabling the bluetooth devices from the Device Manager. Use your computer normally and see if it is still unstable.
 
You must log in or register to reply here.

Similar threads

Bagel Bob
BSOD/POWER STATE DRIVER FAILURE After Coming Out of Sleep
Replies
1
Views
3K
softwaremaniac
S
S
BSOD of Driver Power State Failure
Replies
0
Views
2K
sosores
S
G
Driver Power State Failure
Replies
1
Views
2K
axe0
axe0
R
Solved ASUS Laptop Constant BSOD Power Driver State Failure
Replies
7
Views
5K
axe0
axe0
T
Driver power state failure BSOD - ntoskrnl.exe
Replies
1
Views
2K
axe0
axe0
Back
Top