Few things ruin a workday faster than a blue screen that appears every time a laptop lid closes. The DRIVER_POWER_STATE_FAILURE stop code, also known as 0x0000009F, is one of the most common Blue Screen of Death errors on Windows machines, and it almost always strikes at the worst possible moment: during sleep, wake, shutdown, or restart. According to Microsoft’s bug check documentation, the error means a driver failed to complete a power state transition within the time Windows allows, leaving the system in an inconsistent state. In plain terms, a piece of software that talks to your hardware got stuck while the PC was trying to nap or wake up.
The good news is that this error is usually fixable, and you do not need to reinstall Windows to do it. The bad news is that most online guides throw twenty random “fixes” at you with no order or logic. This guide takes a different route: it explains what the stop code actually means, then walks through diagnostics and repairs in the order a technician would use them, from the fastest checks to the deeper ones.
What DRIVER_POWER_STATE_FAILURE Actually Means
Windows moves devices through power states constantly. When you close a laptop lid, the operating system asks every driver to power down its device, wait for confirmation, and then proceed. If one driver fails to respond in time, Windows panics and crashes deliberately, because continuing could corrupt data or damage hardware.
Microsoft’s official bug check reference describes 0x9F as occurring when a driver is “in an inconsistent power state.” That phrasing matters. The culprit is not always the device you were using when the crash happened. A Bluetooth adapter, a network card, a storage controller, or even a virtual adapter installed by VPN software can be the one that hangs.
Three details separate a quick fix from a long ordeal:
- The crash usually happens during a transition, not during active use. If your PC blue-screens while idle or on wake, this stop code is a strong suspect.
- The faulting driver is often unnamed on the blue screen itself. You usually need the crash dump to identify it.
- Fast Startup and hybrid sleep amplify the problem. These features save a hibernation image during shutdown, which forces drivers through an extra power cycle that some of them handle badly.
Start With the Fastest, Safest Fixes
Before touching drivers, rule out the cheap stuff. These steps take minutes and resolve a surprising share of cases.
1. Disable Fast Startup
Fast Startup is enabled by default on most Windows 10 and 11 PCs. It makes shutdowns feel instant, but it also means your drivers never get a clean, full power cycle. Turning it off is the single most recommended first step for this bug check.
- Open Control Panel and go to Power Options.
- Click Choose what the power buttons do.
- Click Change settings that are currently unavailable.
- Uncheck Turn on fast startup (recommended) and save.
Reboot normally afterward. If the blue screens stop, you have found your trigger, though the underlying driver may still deserve an update. (Blue Screen of Death)
2. Run the Built-In Power Troubleshooter
Windows ships with a power troubleshooter that resets power plans and flags misconfigured sleep settings. It is not magic, but it is free and takes one click. Go to Settings > System > Troubleshoot > Other troubleshooters and run Power. On older builds, the same tool lives under Control Panel > Troubleshooting.
3. Check for Pending Updates
A meaningful number of 0x9F crashes are fixed by cumulative Windows updates that patch driver compatibility. Install all pending updates, including optional driver updates, then test sleep and wake again. If your network stack is misbehaving during these tests and pages refuse to load, the same troubleshooting mindset applies to fixing a website that will not load, because connectivity problems and driver problems often share symptoms.
Identify the Real Culprit With Driver Verifier and Crash Dumps
If the quick fixes fail, stop guessing and get evidence. This is where most guides get vague, and where a technician earns their fee.
Read the Minidump
Windows writes a small memory dump after each crash, usually to `C:WindowsMinidump`. You can open these files with WinDbg, Microsoft’s free debugging tool, and run the `!analyze -v` command. The output names the driver that failed the power transition. Look for lines labeled MODULE_NAME and IMAGE_NAME.
You do not need to be a programmer to read the key lines. If the dump points to `nvlddmkm.sys`, you have a graphics driver problem. If it points to `rtwlane.sys`, you have a Wi-Fi driver problem. If it points to a file with a third-party vendor name, you have found your suspect.
Turn On Driver Verifier
Driver Verifier is Microsoft’s dedicated tool for catching misbehaving drivers. It stresses drivers with extreme conditions so that a faulty one fails predictably instead of intermittently. Enable it carefully:
- Open Command Prompt as administrator and type `verifier`.
- Choose Create custom settings and select Special pool, Force IRQL checking, and Power framework stress.
- Select drivers from a list, or choose all drivers if you can tolerate repeated crashes.
- Reboot and use the PC normally until it blue-screens again.
The resulting crash will name the offending driver directly. Once you have your answer, disable Driver Verifier with `verifier /reset`, because leaving it on slows the system and causes false crashes. Never leave Driver Verifier running indefinitely; it is a diagnostic tool, not a repair.
Repair the Driver You Found
With a driver name in hand, the repair path becomes obvious. The table below maps common culprits to their usual fixes.
| Driver type | Typical file names | Usual fix |
|---|---|---|
| Graphics | nvlddmkm.sys, atikmdag.sys | Clean install of the latest GPU driver, or roll back to a stable version |
| Wi-Fi / Bluetooth | rtwlane.sys, netwtw.sys, bth.sys | Update from the laptop maker’s site, not the chip vendor’s |
| Storage controller | storahci.sys, iaStor.sys | Update chipset and storage drivers, check BIOS/UEFI version |
| Virtual adapters | tap.sys, vpn filter drivers | Update or remove VPN and virtual machine software |
| Antivirus filter drivers | Third-party security drivers | Update the security suite or temporarily uninstall to test |
A few practical rules make this stage far less frustrating:
- Prefer the laptop manufacturer’s drivers over generic ones. On a Dell, Lenovo, or HP machine, the vendor-tuned driver often handles sleep states better than the chipmaker’s latest release.
- Use a clean install for graphics drivers. Standard “update” installs can leave conflicting files behind.
- Update BIOS and chipset firmware. Power management lives partly in firmware, and vendors regularly patch sleep bugs.
- Roll back rather than update when the timing fits. If crashes began right after an update, the previous driver version is often the fix.
The same “identify, then replace” discipline applies to software problems elsewhere on your PC. If a background service is eating your CPU, the approach in this guide to fixing antimalware service executable high CPU usage follows the same logic: find the process, understand why it misbehaves, then address the cause rather than the symptom.
Inspect Power Behavior With Built-In Commands
Windows includes command-line tools that reveal what your hardware is doing during sleep and wake. Two are especially useful here.
`powercfg /energy` runs a 60-second scan and produces an HTML report listing devices and settings that waste power or violate sleep requirements. Look for entries flagged as errors, particularly drivers that block sleep transitions.
`powercfg /lastwake` tells you which device woke the machine last. If a USB device or network adapter keeps waking the PC and then crashing it, you can disable wake permissions for that device in Device Manager > [device] > Properties > Power Management.
`powercfg /devicequery wake_armed` lists every device currently allowed to wake the system. Trimming that list to the keyboard and power button is a sensible hardening step for laptops that crash on wake.
One more setting deserves attention: hybrid sleep. On desktops, hybrid sleep writes a hibernation file while also keeping memory powered. Disabling it under Power Options > Advanced settings > Sleep eliminates one more transition that drivers can fail.
When Hardware, Not Software, Is the Problem
Occasionally the driver is fine and the hardware is failing. A network card with a dying capacitor or a RAM stick with a bad cell can produce power-state errors that no driver update will fix. Signs that hardware is involved include:
- Crashes that persist in Safe Mode.
- Errors that appear on a fresh Windows installation.
- Multiple different bug checks, with 0x9F as one example.
- Physical symptoms such as fans running constantly or devices disappearing from Device Manager.
In these cases, run the built-in Windows Memory Diagnostic, reseat expansion cards and RAM, and test with minimal peripherals attached. If you are planning hardware changes anyway, the practical advice in this guide to cloning a hard drive to an SSD is worth reading first, because a clean migration to new storage sometimes eliminates storage-controller power errors as a side effect.
A Sensible Order of Operations
If you want a single checklist to follow, use this sequence. It moves from least invasive to most, so you never waste an afternoon reinstalling Windows for a problem a checkbox would have solved.
- Disable Fast Startup and hybrid sleep.
- Install all Windows updates, including optional driver updates.
- Update BIOS, chipset, and the drivers for network, graphics, and storage devices.
- Run `powercfg /energy` and review the report for flagged devices.
- Analyze the latest minidump with WinDbg to name the faulting driver.
- Enable Driver Verifier to confirm the suspect under stress.
- Clean-install or roll back the confirmed driver.
- Remove or update third-party filter drivers such as VPN clients and old antivirus suites.
- Test hardware if software fixes fail repeatedly.
Most people solve the problem somewhere in steps one through four. The rest need the diagnostic tools, but the tools reward patience with a definitive answer instead of another guess.
Conclusion
DRIVER_POWER_STATE_FAILURE looks intimidating because it arrives as a full-screen crash with a cryptic code. Underneath, it is a timing problem: a driver could not finish a power transition, so Windows protected itself by stopping. That framing turns a scary error into a solvable puzzle. Disable Fast Startup first, update the drivers that handle sleep and networking, then use minidumps and Driver Verifier to name the culprit if the easy fixes fall short. Patience beats brute force here; a methodical hour with the built-in tools will outperform a weekend of reinstalling Windows. And once the crashes stop, keep your drivers current, because the same power transitions happen every single time the lid closes.
Frequently Asked Questions
What causes DRIVER_POWER_STATE_FAILURE?
It is caused by a driver that fails to complete a power state transition, such as entering sleep or resuming from it, within the time Windows allows. Microsoft’s bug check documentation describes the driver as being in an inconsistent power state. Common triggers include outdated network, graphics, and storage drivers, incompatible USB or Bluetooth devices, and Fast Startup interactions. (Windows drivers documentation)
Is DRIVER_POWER_STATE_FAILURE dangerous to my PC?
The crash itself is a protective measure, not damage. Windows stops deliberately to prevent data corruption when a driver hangs mid-transition. The real risks are lost unsaved work and repeated crashes that make the machine unusable. Persistent errors can, however, point to failing hardware, which is worth investigating if software fixes do not help.
Can I fix it without reinstalling Windows?
In most cases, yes. Disabling Fast Startup, updating the relevant drivers, and removing conflicting third-party filter drivers resolve the majority of cases. Reinstalling Windows is a last resort, and even then the problem can return if the underlying driver or hardware issue is not addressed first.
How do I find out which driver is failing?
Enable Driver Verifier and let the PC crash, or open the latest minidump in WinDbg and run `!analyze -v`. Both methods name the faulting driver. Driver Verifier is more aggressive and produces a crash faster, while dump analysis works with crashes that have already happened.
Does Safe Mode stop the crashes?
Safe Mode loads a minimal set of drivers, so if the blue screens disappear there, a third-party driver is almost certainly involved. If crashes continue in Safe Mode, hardware or a core system component is more likely to blame, and you should test memory and storage.
Will a BIOS update fix this error?
Sometimes. Power management depends partly on firmware, and manufacturers regularly patch sleep and wake behavior. A BIOS update is worth trying after driver updates, especially on laptops, but it should be done carefully with the machine plugged in and stable.
