BSOD DRIVER-POWER_STATE-FAILURE after getting DRIVER_IRQL_NOT_LESS_OR_

[surf1000]

My HP dv6t Quad Windows 7 Professional 64-bit laptop is less than 1 year old and is usually stable but it became unresponsive and my son did a hard reset on Saturday. I have entered in the System Info in my Profile. After rebooting, I began getting DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen with iastor.sys. After researching on your site, I went to the HP.Com site and downloaded new drivers for Bios, Intel Storage, and Wireless. I also downloaded the latest Wireless drivers from intel.com. Today, my laptop would not respond from Hibernate and I got a different blue screen which was DRIVER_POWER_STATE_FAILURE. I was unable to use System Restore initially but used a different restore point and was able to log in.

Here is the dump file from today and I've attached the screen shot of the blue screens:
Loading Dump File [C:\Users\Susan\Documents\Susan\HP PC Rltd\New folder\060412-56846-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e5b000 PsLoadedModuleList = 0xfffff800`030a0670
Debug session time: Mon Jun 4 18:18:27.077 2012 (UTC - 5:00)
System Uptime: 1 days 4:23:19.897
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa8007336b60, fffff8000493c3d0}

*** WARNING: Unable to verify timestamp for btwampfl.sys
*** ERROR: Module load completed but symbols could not be loaded for btwampfl.sys
Implicit thread is now fffffa80`07336b60
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : btwampfl.sys ( btwampfl+30a2a )

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8007336b60, The thread currently holding on to the Pnp lock.
Arg4: fffff8000493c3d0, nt!TRIAGE_9F_PNP on Win7

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

Implicit thread is now fffffa80`07336b60

DRVPOWERSTATE_SUBCODE: 4

FAULTING_THREAD: fffffa8007336b60

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002edcf32 to fffff80002eda4da

STACK_TEXT:
fffff880`03969240 fffff800`02edcf32 : fffffa80`07336b60 fffffa80`07336b60 00000000`00000000 00000000`00000002 : nt!KiSwapContext+0x7a
fffff880`03969380 fffff800`02ede742 : 00000001`03060001 00000000`00000018 00000000`000000c1 fffff800`02ede5c8 : nt!KiCommitThreadWait+0x1d2
fffff880`03969410 fffff880`02ac0a2a : fffffa80`0cf45b70 00000000`00000000 fffffa80`41777400 fffff880`000000c1 : nt!KeDelayExecutionThread+0x186
fffff880`03969480 fffffa80`0cf45b70 : 00000000`00000000 fffffa80`41777400 fffff880`000000c1 fffff880`02d90da0 : btwampfl+0x30a2a
fffff880`03969488 00000000`00000000 : fffffa80`41777400 fffff880`000000c1 fffff880`02d90da0 fffff880`02ac9682 : 0xfffffa80`0cf45b70


STACK_COMMAND: .thread 0xfffffa8007336b60 ; kb

FOLLOWUP_IP:
btwampfl+30a2a
fffff880`02ac0a2a ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: btwampfl+30a2a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: btwampfl

IMAGE_NAME: btwampfl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c3bc43e

FAILURE_BUCKET_ID: X64_0x9F_4_btwampfl+30a2a

BUCKET_ID: X64_0x9F_4_btwampfl+30a2a

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8007336b60, The thread currently holding on to the Pnp lock.
Arg4: fffff8000493c3d0, nt!TRIAGE_9F_PNP on Win7

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

Implicit thread is now fffffa80`07336b60

DRVPOWERSTATE_SUBCODE: 4

FAULTING_THREAD: fffffa8007336b60

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002edcf32 to fffff80002eda4da

STACK_TEXT:
fffff880`03969240 fffff800`02edcf32 : fffffa80`07336b60 fffffa80`07336b60 00000000`00000000 00000000`00000002 : nt!KiSwapContext+0x7a
fffff880`03969380 fffff800`02ede742 : 00000001`03060001 00000000`00000018 00000000`000000c1 fffff800`02ede5c8 : nt!KiCommitThreadWait+0x1d2
fffff880`03969410 fffff880`02ac0a2a : fffffa80`0cf45b70 00000000`00000000 fffffa80`41777400 fffff880`000000c1 : nt!KeDelayExecutionThread+0x186
fffff880`03969480 fffffa80`0cf45b70 : 00000000`00000000 fffffa80`41777400 fffff880`000000c1 fffff880`02d90da0 : btwampfl+0x30a2a
fffff880`03969488 00000000`00000000 : fffffa80`41777400 fffff880`000000c1 fffff880`02d90da0 fffff880`02ac9682 : 0xfffffa80`0cf45b70


STACK_COMMAND: .thread 0xfffffa8007336b60 ; kb

FOLLOWUP_IP:
btwampfl+30a2a
fffff880`02ac0a2a ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: btwampfl+30a2a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: btwampfl

IMAGE_NAME: btwampfl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c3bc43e

FAILURE_BUCKET_ID: X64_0x9F_4_btwampfl+30a2a

BUCKET_ID: X64_0x9F_4_btwampfl+30a2a

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

Thank you for your help

 

[usasma]

Since you've updated the storage drivers, that should take care of the iastor.sys error
The other error blames btwampfl - your Broadcom Bluetooth drivers. You should be able to download these from the HP website also.

Should the BSOD's continue after that, we'll have to take a different approach. If the BSOD's recur, please provide this info: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html