DRIVER_POWER_STATE_FAILURE: Sleep/Hibernate Driver Conflicts And Solutions

Contents show

Introduction

The Windows stop code DRIVER_POWER_STATE_FAILURE (0x9F) is a Blue Screen of Death that commonly appears when a system is entering, exiting, or resuming from Sleep or Hibernate. In plain terms, a device driver didn’t handle a power transition correctly or timed out, leaving Windows stuck in an unsafe power state. This error can happen during shutdown, sleep, hibernate, or resume, and it’s critical to fix because repeated crashes can corrupt data, shorten SSD lifespan, and mask deeper driver, firmware, or hardware issues.

This guide goes beyond generic advice. You’ll find step-by-step troubleshooting, minidump analysis with WinDbg or BlueScreenView, Driver Verifier, and powercfg diagnostics to pinpoint the exact cause of DRIVER_POWER_STATE_FAILURE after sleep or hibernate—and the proven fixes that work.

Understanding the Error

The bug check DRIVER_POWER_STATE_FAILURE (Stop Code: 0x0000009F) indicates a driver failed to transition to a required power state (S0/S3/S4) or didn’t complete a power IRP (I/O Request Packet) within the expected time. Windows detects the hold-up and crashes to protect data.

Typical, plain-language scenario: Windows asks all devices to sleep. One driver (for example, a Wi‑Fi adapter, GPU, storage controller, or USB device) doesn’t respond or gets stuck. Windows waits, then gives up and triggers the BSOD.

Common when:

Closing the laptop lid (Sleep/S3), using Hibernate/S4, or waking from either.
Shutdown/restart hangs and then BSODs.
Docking/undocking, hot-plugging USB devices, or using Thunderbolt gear.
After a driver update, BIOS/UEFI change, or Windows Update.
Switching power plans, using Fast Startup, or on Modern Standby systems (S0 Low Power Idle).

The root cause is almost always a misbehaving driver or firmware, though hardware faults can also manifest as 0x9F.

Common Causes

Below are the most likely causes of DRIVER_POWER_STATE_FAILURE, especially related to sleep/hibernate transitions.

Outdated, buggy, or conflicting device drivers (GPU, Wi‑Fi/Bluetooth, storage/SATA/NVMe, USB, Thunderbolt, chipset, Intel MEI/AMT).
Fast Startup or Hibernate conflicts.
USB devices and hubs not handling power transitions.
Docking station or Thunderbolt firmware/driver issues.
Storage driver conflicts (e.g., Intel RST, NVMe, RAID, controller firmware).
BIOS/UEFI settings or outdated firmware (ACPI/Modern Standby bugs).
Windows updates introducing driver regressions.
Power plan misconfigurations and selective suspend problems.
Third-party software (VPNs, antivirus, overclocking/RGB tools, virtualization).
Faulty RAM, marginal PSU, or failing SSD/HDD.
Malware that hooks drivers or disrupts system services.

Skimmable table of causes and signals:

Likely Cause	Typical Triggers	Clues/Symptoms
GPU driver (NVIDIA/AMD/Intel)	Sleep/resume, multi-monitor	nvlddmkm.sys, amdkmdag.sys references in dumps
Wi‑Fi/Bluetooth NIC	Wake from sleep, VPN, tethering	netwtwxx.sys, bt*.sys in dumps, disconnects
Storage/NVMe/RAID	Shutdown/hibernate, wake	iaStorAC.sys, storport.sys, nvme.sys delays
USB/Thunderbolt device	Dock/undock, USB hubs	usbhub.sys, USBXHCI.sys, tbtxxx.sys activity
Chipset/MEI	After BIOS update or Windows upgrade	ACPI.sys timeouts, random hangs
Fast Startup/Hibernate	First boot of the day	Works after reboot; fails after shutdown
Firmware/BIOS bugs	New BIOS or very old BIOS	ACPI errors in Event Viewer
Power plan settings	Selective suspend	Resumes sluggishly, devices missing
Bad RAM/disk	Random BSOD variety	Memory errors, SMART warnings
Malware	Persistent driver hooks	Unknown drivers, suspicious services

Preliminary Checks

Before deep diagnostics, do quick safety and health steps.

Boot into Safe Mode

If you’re stuck in a crash loop, use Safe Mode:

Windows 10/11:
- Hold Shift and click Restart (from Start > Power).
- Troubleshoot > Advanced options > Startup Settings > Restart.
- Press 4 (Enable Safe Mode) or 5 (Safe Mode with Networking).

If you cannot reach the login screen, interrupt boot 3 times (power off during spinning dots) to trigger Automatic Repair, then navigate the same path to Startup Settings.

Back Up Important Data

Protect data before making changes:

Copy files to an external drive or cloud.
Use a quick command for a user profile backup (replace UserName and drive):

robocopy “C:\Users\UserName” “E:\Backup\UserName” /MIR /XJ /R:1 /W:1

Run Basic Health Checks

Open an elevated Command Prompt (Run as Administrator):

System File Checker:

sfc /scannow

DISM to repair component store:

dism /online /cleanup-image /restorehealth

Check disk on reboot (system volume):

chkdsk C: /scan

If it reports errors needing a reboot:

chkdsk C: /f

These checks fix system file or file-system corruption that can exacerbate power transitions.

Step-by-Step Troubleshooting

Work from simplest to advanced. Test sleep, hibernate, and shutdown after each change.

Physically Simplify and Test

Disconnect non-essential USB devices, docks, external drives, and hubs.
Remove SD cards, disable external displays, and undock laptops.
Change only one variable at a time; try Sleep and Hibernate.
If stable, reconnect peripherals one-by-one to identify the offender.

Disable Fast Startup and Test Hibernate
Fast Startup can cause DRIVER_POWER_STATE_FAILURE by mixing hibernation with shutdown.

Disable hibernation (also disables Fast Startup):

powercfg -h off

Reboot and test. If stability returns, re-enable hibernation then disable only Fast Startup:

Re-enable hibernation:

powercfg -h on

Disable Fast Startup via Control Panel:
- Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable > Uncheck Turn on fast startup > Save.
  Test again.

Update or Roll Back Problematic Drivers
Focus on devices heavily involved in power transitions:

Chipset drivers (Intel/AMD), Management Engine Interface, SATA/NVMe/RAID, GPU, Wi‑Fi/Bluetooth, Thunderbolt, USB 3.x controller.
Prefer the OEM laptop/desktop support page over generic drivers, especially for laptops (custom ACPI tables).
If the issue began after an update, roll back:
- Device Manager > device > Properties > Driver tab > Roll Back Driver.
For GPUs, use DDU (Display Driver Uninstaller) in Safe Mode to cleanly reinstall the latest stable driver.

Adjust Power Management Settings

USB selective suspend:
- Control Panel > Power Options > Change plan settings > Change advanced power settings > USB settings > USB selective suspend setting = Disabled (test; you can re-enable later).
Network adapter power:
- Device Manager > Network adapters > your Wi‑Fi/Ethernet > Properties > Power Management > Uncheck Allow the computer to turn off this device.
PCI Express Link State Power Management:
- Advanced power settings > PCI Express > Link State Power Management = Off (test).
Intel Rapid Storage Technology (if used):
- Update RST driver, or switch to Microsoft Standard NVMe driver if applicable (and supported by your platform).

Update BIOS/UEFI and Firmware

Check BIOS/UEFI version:
- Press Win+R > type:

msinfo32

Note BIOS Version/Date and compare with your OEM’s website.
Update BIOS/UEFI following vendor instructions.
Update SSD firmware, Thunderbolt NVM, and dock firmware.
Update Intel ME firmware/software on Intel systems.

Windows Update and Known Bad Patches

Install all pending Windows Updates and optional driver/firmware updates that match your OEM hardware.
If 0x9F started after a specific update, uninstall it:
- Settings > Windows Update > Update history > Uninstall updates.
Pause updates temporarily while troubleshooting.

Clean Boot to Rule Out Software Conflicts

Press Win+R > type:

msconfig

On Services tab: check Hide all Microsoft services, then click Disable all.
On Startup tab: open Task Manager and Disable all startup items.
Reboot and test sleep/hibernate. If stable, re-enable services/startups in batches to isolate the culprit (VPN clients, third-party antivirus, RGB/overclock tools, and virtualization software are common offenders).

Storage and Memory Diagnostics

Run Windows Memory Diagnostic:
- Press Win+R > type:

mdsched.exe

Restart now and check for problems.
Consider MemTest86 (USB boot) for deeper memory testing.
Check disk health (SMART):
- For a quick look:

wmic diskdrive get status, model

Use vendor-specific SSD tools (Samsung Magician, Crucial Storage Executive) for detailed health and firmware updates.

Powercfg Diagnostics for Sleep/Hibernate
Run these in an elevated Command Prompt:

Show available sleep states:

powercfg -a

Detect what is blocking sleep:

powercfg -requests

Energy report (generates HTML):

powercfg -energy -output “%USERPROFILE%\Desktop\energy-report.html” -duration 60

For Modern Standby (S0 Low Power Idle) systems, Sleep Study:

powercfg /sleepstudy

Review the reports for drivers or devices preventing or delaying transitions.

Minidump Analysis: Find the Faulty Driver

Enable and locate minidumps:

Press Win+R > type:

sysdm.cpl

Advanced tab > Startup and Recovery > Settings > Under Write debugging information, choose Small memory dump (256 KB). Ensure dump directory is:

%SystemRoot%\Minidump

After the next crash, find files in:

C:\Windows\Minidump

Option A: Quick view with BlueScreenView (NirSoft)

Download and run BlueScreenView.
Open the latest dump; note Caused By Driver (e.g., nvlddmkm.sys, netwtw10.sys, iaStorAC.sys).
Cross-reference the driver with Device Manager and update/rollback/reinstall accordingly.

Option B: Deep analysis with WinDbg (Preview)

Install WinDbg Preview from Microsoft Store (or WinDbg via Windows SDK).
Launch WinDbg > File > Open dump file > select latest .dmp in C:\Windows\Minidump.
Set symbols and analyze:

.symfix
.reload
!analyze -v

Look for:
- Probably caused by: driver.sys
- Failure Bucket ID referencing a driver
- IRP timeouts and blocked threads
For power IRPs, advanced users can inspect:

!irpfind
!poaction
!devnode 0 1

Once a suspect driver is identified, update from OEM, roll back, or uninstall related software.

Driver Verifier to Stress-Test Drivers (use with caution)

Driver Verifier forces drivers to behave; misbehaving ones will crash quickly and reveal themselves in dumps.
Start it:

verifier.exe

Choose Create standard settings > Automatically select unsigned drivers and/or Automatically select drivers built for older versions of Windows. Alternatively, Select driver names from a list and include non-Microsoft drivers.
Reboot and use the PC normally. Expect more BSODs—this is normal during the test.
After a crash, analyze the new dump with WinDbg/BlueScreenView to see the exact driver name.
Turn off Driver Verifier when finished:

verifier /reset

Reboot.

System Restore or Rollback
If 0x9F started recently:

Press Win+R > type:

rstrui

Choose a restore point from before the issue and follow prompts.

In-Place Repair (Windows 10/11)
If corruption persists:

Download the Media Creation Tool (Windows 10) or use the Windows 11 Installation Assistant.
Run setup from within Windows and choose Keep personal files and apps.
This refreshes Windows while preserving data and programs.

Last-Resort Hardware Checks

Reseat RAM and storage drives (desktops).
Try different RAM sticks/slots or run with one module at a time.
Swap PSU (desktop) or test on battery vs. AC (laptop).
Replace failing SSD/HDD if SMART indicates issues.

Advanced Diagnostics

Driver Verifier Strategy

Enable Driver Verifier only for non-Microsoft drivers to reduce noise.
Start with network, storage, video, and USB stack drivers.
If crashes point to a core component (e.g., ntoskrnl.exe) without naming a third-party driver, examine the call stack and loaded modules in WinDbg to find the third-party code path.
Always disable when done:

verifier /reset

Warning: Driver Verifier can cause boot loops if the offending driver loads early. If you can’t boot, use Safe Mode to run verifier /reset or boot to Recovery > Command Prompt.

Event Viewer Clues

Open Event Viewer:

Press Win+X > Event Viewer.
Check under Windows Logs > System:
- Kernel-Power events
- Kernel-Boot and Kernel-General
- BugCheck entries with codes
- ACPI warnings/errors
- Disk, storahci, iaStorAC, nvme
- Netwtw (Intel Wi‑Fi), rtwlane (Realtek), bt (Bluetooth)
Correlate timestamps with BSODs and sleep/wake cycles.

Power and Sleep Capabilities

Verify supported sleep states:

powercfg -a

On systems with Modern Standby (S0), misbehaving devices can drain or crash resumes. Use:

powercfg /sleepstudy

Identify devices that can wake or are armed to wake the computer:

powercfg /devicequery wake_armed
powercfg /devicequery wake_programmable

Temporarily disallow problematic wake-capable devices (Device Manager > device > Power Management).

ACPI and BIOS/UEFI Settings

Check BIOS for:
- Sleep state preferences (S3 vs. S0). Some OEMs expose a toggle between Modern Standby and Legacy S3.
- ErP settings (can affect USB power during S5).
- Wake on LAN and USB wake options.
If you changed BIOS settings recently, revert to defaults and test.
Ensure BIOS is up-to-date, especially on mobile platforms with newer ACPI tables.

When to Seek Professional Help

Consider professional repair or hardware replacement if:

Driver Verifier and minidump analysis implicate storage or memory but updates don’t resolve it.
You see SMART errors, frequent disk timeouts, or growing bad sectors.
MemTest86 shows memory errors, or the system is unstable even in a clean environment.
BSODs persist after a clean Windows install with only OEM drivers.
The device is under warranty—contact the OEM for motherboard, battery, or device-level diagnostics.

Prevention Tips

Keep OEM-provided drivers up to date (especially chipset, MEI, storage, GPU, Wi‑Fi/Bluetooth).
Update BIOS/UEFI and device firmware (SSD, Thunderbolt, docks) periodically.
Avoid installing drivers from untrusted sources; prefer the OEM support page over third-party driver utilities.
Create System Restore points or full-disk images before major updates.
Be cautious with Fast Startup on systems with persistent sleep/hibernate BSODs.
Limit the number of chained USB hubs; use powered hubs for peripherals.
Keep Windows fully patched; if a new patch causes issues, roll back promptly and report to the OEM.
After adding new hardware/software, test sleep/hibernate immediately to catch problems early.
Run periodic SFC/DISM and monitor SMART health of drives.

Conclusion

Most DRIVER_POWER_STATE_FAILURE crashes boil down to a single misbehaving driver or firmware that fails during sleep/hibernate or shutdown transitions. By methodically updating drivers and firmware, adjusting power settings, analyzing minidumps with BlueScreenView or WinDbg, and using Driver Verifier and powercfg reports, you can reliably identify and fix the root cause.

Follow the steps in order—starting with simple power tweaks and driver updates, then moving to diagnostics and, if needed, repair installs. With patience and a structured approach, the vast majority of sleep/hibernate BSODs are fixable.

FAQ

Can I ignore the DRIVER_POWER_STATE_FAILURE BSOD if it only happens sometimes?

No. Even intermittent 0x9F crashes indicate underlying driver/firmware issues that can worsen, cause data loss, and create instability. Address it by updating drivers, disabling Fast Startup, and reviewing minidumps to prevent future crashes.

Does this BSOD mean my hardware is failing?

Not necessarily. Most 0x9F cases are driver- or firmware-related. However, if minidumps implicate storage or memory, or diagnostics show SMART or memory errors, hardware could be at fault.

Turning off hibernation fixed the issue—should I leave it off?

If disabling hibernation (and Fast Startup) resolves the BSOD, it’s a strong signal of a driver that mishandles power transitions. You can leave it off as a workaround, but the best solution is to identify and fix the problematic driver or firmware so you can use all power features reliably.

Will a clean install of Windows fix DRIVER_POWER_STATE_FAILURE?

A clean install removes software conflicts and bad drivers, often resolving the issue. But if the root cause is firmware or hardware, the problem may persist until those are updated or replaced. Try an in-place repair first—it’s less disruptive.

Is Driver Verifier safe to use?

Yes, but use it carefully. Driver Verifier deliberately stresses drivers and can trigger additional BSODs to reveal the culprit. Enable it only for non-Microsoft drivers, collect dump data, and then disable it with:

verifier /reset

If you get stuck in a boot loop, use Safe Mode to turn it off.

DRIVER_POWER_STATE_FAILURE: Sleep/Hibernate Driver Conflicts and Solutions

Introduction

Understanding the Error

Common Causes