BSOD: DRIVER_POWER_STATE_FAILURE (9f) on shutdown/sleep
Hello.
I just did a clean re-install of Windows 7 on a laptop.
I got all the latest drivers from the respective manufacturers' websites and everything seemed to be working fine (also no unknown/driverless devices in device manager).
However, a day (or so) after finishing the installation I received a BSOD when I tried to reboot the computer.
It was stuck at the "Shutting down" screen for a long time and then the BSOD showed up (I suppose after running into some sort of timeout).
The next day I got another BSOD (same kind), this time when putting the machine into sleep mode.
I have looked at the respective minidumps (they are pretty much identical) with WinDbg, this is the bugcheck analysis output:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000009F, 4, 258, fffffa80042ccb50, fffff80000b9c3d0
Implicit thread is now fffffa80`042ccb50
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
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.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa80042ccb50, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c3d0, nt!TRIAGE_9F_PNP on Win7 and higher
Debugging Details:
------------------
Implicit thread is now fffffa80`042ccb50
DRVPOWERSTATE_SUBCODE: 4
FAULTING_THREAD: fffffa80042ccb50
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff80002ec35f2 to fffff80002ed0a8a
STACK_TEXT:
fffff880`03708620 fffff800`02ec35f2 : fffffa80`042ccb50 fffffa80`042ccb50 00000000`00000039 00000000`00000001 : nt!KiSwapContext+0x7a
fffff880`03708760 fffff800`02ed499f : fffffa80`042cd040 fffff880`033e4180 fffff880`0000009c 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff880`037087f0 fffff800`02eadb4e : 00000000`00000000 fffff800`0000001b 00000000`00000000 fffff880`033e4100 : nt!KeWaitForSingleObject+0x19f
fffff880`03708890 fffff800`02ed2dbc : ffffffff`fd9da600 fffffa80`04de1100 fffff800`030d1da0 00000000`00000000 : nt!ExpWaitForResource+0xae
fffff880`03708900 fffff800`0320a602 : fffff880`03708b78 00000000`00000000 00000000`00000001 00000000`00000000 : nt!ExAcquireResourceExclusiveLite+0x14f
fffff880`03708970 fffff800`0334a327 : 00000000`00000000 fffffa80`042f8b60 fffff8a0`00eb0010 fffff880`03708b78 : nt! ?? ::NNGAKEGL::`string'+0x1b83c
fffff880`037089a0 fffff800`0334b53c : fffff880`03708b78 fffffa80`07bdfb00 fffffa80`042ccb50 fffffa80`07bdfb80 : nt!PnpProcessQueryRemoveAndEject+0x77
fffff880`03708ae0 fffff800`0323473e : 00000000`00000000 fffffa80`07bdfb80 fffff8a0`00eb0010 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`03708b10 fffff800`02ed7261 : fffff800`031383d8 fffff8a0`00eb0010 fffff800`030732d8 fffffa80`00000299 : nt! ?? ::NNGAKEGL::`string'+0x54d9b
fffff880`03708b70 fffff800`0316973a : 00000000`00000000 fffffa80`042ccb50 00000000`00000080 fffffa80`042b9040 : nt!ExpWorkerThread+0x111
fffff880`03708c00 fffff800`02ebe8e6 : fffff880`033e4180 fffffa80`042ccb50 fffff880`033eefc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03708c40 00000000`00000000 : fffff880`03709000 fffff880`03703000 fffff880`037088a0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .thread 0xfffffa80042ccb50 ; kb
FOLLOWUP_IP:
nt!KiSwapContext+7a
fffff800`02ed0a8a 488d8c2400010000 lea rcx,[rsp+100h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSwapContext+7a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb
IMAGE_VERSION: 6.1.7601.18409
FAILURE_BUCKET_ID: X64_0x9F_4_nt!KiSwapContext+7a
BUCKET_ID: X64_0x9F_4_nt!KiSwapContext+7a
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x9f_4_nt!kiswapcontext+7a
FAILURE_ID_HASH: 988e0922-fc98-5cf6-5921-ee45c15cab37
Followup: MachineOwner
---------
So it says that ntkrnlmp.exe probably caused the BSOD, but since that is part of the system something else (a misbehaving driver, I presume?) must be responsible for the BSOD.
This is where I'm at my wits' end.
I suppose further inspection of the dumps (I also have a kernel dump (MEMORY.DMP) of the 2nd BSOD) could reveal the faulty driver/component, but I have no experience in doing that.
Could someone of the experts please give me directions or would it be more sensible to just upload the kernel dump and have you look at it?
Thanks in advance either way!
Anwsers to the Problem BSOD: DRIVER_POWER_STATE_FAILURE (9f) on shutdown/sleep
Download SmartPCFixer for Free Now
This particular error can easily be resolved with a few simple steps. However, if you are not confident in your ability to use the methods below or they do not fully remove the issue on your computer, you may want to seek the assistance of a qualified repair technician who is well versed in fixing BSOD: DRIVER_POWER_STATE_FAILURE (9f) on shutdown/sleep.
- Back-up the Registry of your operating system.
- Find the Registry Key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade]
- Note: this Registry Key should already exist, if it does not exist, create it.
- Create a brand new DWORD Value that is named AllowOsUpdate
- Set the Value to 0x00000001.
- Close and reopen your Control Panel.
- Restart the Microsoft Windows.
Another Safe way to Repair the Problem: BSOD: DRIVER_POWER_STATE_FAILURE (9f) on shutdown/sleep:
How to Fix BSOD: DRIVER_POWER_STATE_FAILURE (9f) on shutdown/sleep with SmartPCFixer?
1. Download Error Fixer. Install it on your system.
2. After the scan is done, you can see the errors and problems which need to be repaired.
3. When the Fixing part is done, your computer has been speeded up and the errors have been fixed
Related: How to Download Toshiba Portege R500 HDD/SSD Alert Utility v.2.2.0.0 driver,Way to Update & Download Toshiba Satellite A355-S69403 Motorola Modem Region Select Utility v.2.2.3.0 driver,Where to Download Toshiba Satellite L305-S5926 HW Setup Utility v.2.00.11 driver,[Solved] Download Toshiba Satellite L675-S7115 Laptop Checkup v.2.0.6.22 driver,Method to Download Toshiba Satellite M645-S4080 Media Controller v.1.1.88.1 driver,Best Way to Download NVidia GeForce 6100 VGA Driver v.304.51 Certified,How Can You Update & Download NVidia GeForce 9300/nForce 730i VGA Driver v.310.19 Certified,Method to Download NVidia GeForce GT 330M Driver v.340.65,How Can I Update & Download NVidia GeForce GTX 590 Driver v.280.26 WHQL,Method to Download NVidia Tesla C2050 Driver v.319.17
Read More: How to Fix - bug in Content Advisor constant pop ups Ratings Pol file?,How to Fix Error - Calculated formula in a pivot table?,All diagnostic tools give 0x800700C1, troubleshooting wizard can't continue,all files try to open with adobe,all icons on desktop have changed to Adobe icon and won't open,All functions of my outlook are working except it will not let me "REPLY" or start a "NEW" email,all f1-f12 shortcuts not work
No comments:
Post a Comment