DRIVER_POWER_STATE_FAILURE (bug check 0x9F, shown as 0x0000009F on older blue screens) most often means a driver didn’t finish a power change in time; less often, a driver handled a power request incorrectly. When Windows sleeps, wakes, hibernates or shuts down, it asks each device’s driver to power down or back up; docking or undocking adds or removes several devices at once. If one driver sits on a power request, Windows waits, sometimes long enough that the PC looks stuck on a black screen with the fans running, and then stops with 0x9F.
That makes driver power state failure on Windows 11 and 10 unusual among stop codes: the moment it happens is the best clue. A crash when you close the lid points at different drivers than one when you pull a laptop off its dock or press Shut down. Note that moment, plus any .sys file the stop screen shows under What failed, and you can usually narrow the field to one or two devices.
Try these first
- Note exactly when it crashed: closing the lid, waking, undocking, shutting down or plugging in a charger.
- Write down any .sys file shown under What failed on the stop screen.
- If it started after an update, roll back the driver that changed that day in Device Manager.
- Unplug the dock, USB hubs and other USB devices, then test sleep and wake for a day.
- Install the PC maker’s current chipset, Wi-Fi, Bluetooth, graphics and dock drivers for your model.
- Use the laptop’s original charger, and test with Restart instead of Shut down, which bypasses Fast Startup.
Match the moment to the cause
| When it crashes | What’s going on | Usual suspects | First fix |
|---|---|---|---|
| Closing the lid or selecting Sleep | A device won’t power down | Wi-Fi, Bluetooth, USB devices, graphics | Update those drivers; unplug USB devices and test |
| Opening the lid or waking from sleep | A device won’t power back up | Network adapter, graphics with external monitors, USB hubs | Update drivers; wake with monitors and hubs unplugged to test |
| Undocking, or docking a sleeping laptop | Devices vanishing or arriving mid-transition | Dock firmware, Thunderbolt or USB4, DisplayLink, the dock’s network adapter | Update dock firmware and drivers; dock and undock only while awake |
| Pressing Shut down, or at the next power-on | A driver carried over by Fast Startup, or one that won’t stop | Storage, chipset and network drivers | Test with Restart; turn Fast Startup off |
| Hibernating or resuming from hibernate | A device won’t power down for hibernation, or back up on resume | Storage controller driver, SSD firmware | Update storage drivers and firmware |
| Plugging in or unplugging the charger | The laptop renegotiating power | An undersized USB-C charger, dock power delivery, BIOS | Use the original adapter; update BIOS |
| While you’re working, screen on (less common) | Possibly a device idling down to save power | Power management in network, USB or storage drivers | Driver updates, then the power settings below |
Check the stop code first: a crash on docking or waking can also be DPC_WATCHDOG_VIOLATION (0x133), a driver holding up a processor, or VIDEO_TDR_FAILURE (0x116), a graphics driver that stopped responding. They need different fixes: our DPC watchdog violation guide covers 0x133, including crashes that follow only a Fast Startup power-on, and the stop-code table in our blue screen of death guide links the rest.
To confirm which transition failed, match the crash time in Reliability Monitor against Event Viewer’s System log filtered to the Kernel-Power and Power-Troubleshooter sources, which record sleeps, wakes and the wake source.
What parameter 1 tells you
The first parameter of a 0x9F says what kind of power failure Windows caught. Read it from Reliability Monitor or a minidump, as the blue screen guide linked above shows; this table is what the value means.
| Parameter 1 | Microsoft’s description, simplified | What it usually means for you |
|---|---|---|
| 0x3 | A device object has been blocking a power request too long | One device’s driver didn’t finish powering down or up. Parameter 2 identifies the device, which makes this the easiest case to trace. |
| 0x4 | The power transition timed out waiting to synchronize with Plug and Play | Plug and Play was still adding or removing a device. Parameter 2 is the timeout in seconds. Docking and undocking are classic triggers. |
| 0x5 or 0x6 | A device didn’t complete a directed power transition in time (0x5) or successfully (0x6) | Modern Standby PCs only. While the PC sat in standby with the screen off, Windows told one device to power down or back up on its own, and its driver didn’t finish the job. |
| 0x1 | A device object being freed still had an outstanding power request | A device or driver was removed mid-transition |
| 0x2 or 0x500 | A power request was completed improperly | A driver bug; update or roll back the driver named |
Turning parameter 2 into a device name
Skip this unless crashes continue after the updates below.
For a 0x3 crash, open the dump in WinDbg, run !analyze -v, then !devstack followed by the address in Arg2. The output lists the drivers stacked on that device and a DeviceInst line such as USB\VID_...&PID_.... If the PC restarted before you could read the stop screen, dx KiBugCheckDriver shows the driver name Windows printed there, if it identified one.
In Device Manager, compare the DeviceInst value with each candidate’s Device instance path (Properties > Details tab) to find the suspect.
Know which sleep your PC uses
Run powercfg /a in a terminal. If it lists Standby (S0 Low Power Idle), the PC uses Modern Standby, which most current laptops do. If it lists Standby (S3), it uses traditional sleep.
- Modern Standby keeps parts of the system running with the screen off, waking network devices briefly for email and updates, so network and Wi-Fi drivers deserve the first look on these laptops. In an administrator terminal,
powercfg /sleepstudysaves an HTML report of the last three days of standby sessions, showing which components kept the system active. - S3 sleep powers almost everything off, so the usual trouble is a device that won’t come back on wake.
Skip registry tweaks that claim to switch a Modern Standby laptop back to S3 sleep. Microsoft says switching between the two isn’t supported without a complete reinstall of Windows, so the tweak leaves you on a sleep mode the PC maker never tested.
Find what keeps waking it
powercfg /lastwake reports what woke the PC last time, and powercfg /devicequery wake_armed lists the devices allowed to wake it. If a crash follows unexpected wakes, open that device in Device Manager and, on its Power Management tab, clear Allow this device to wake the computer as a test. Leave it on for the keyboard and touchpad so you can still wake the laptop.
Update drivers and firmware in the right order
First, check what changed
In Reliability Monitor (perfmon /rel), check the day the crashes began for a driver, Windows update or program installed just before. In Device Manager, a device’s Properties > Events tab shows when its driver last changed. If one did, roll it back (Driver > Roll Back Driver) before you update anything else.
Software counts too. VPN clients, antivirus and endpoint security tools, and virtualization apps add their own network and filter drivers, which also have to handle sleep and wake. Update one that was installed recently, or uninstall it as a test, because quitting the app leaves its drivers loaded. On a work PC, ask whoever manages your security software first.
If a Windows update is the trigger, remove it in Windows 11 under Settings > Windows Update > Update history > Uninstall updates, and pause updates for a week while a fix arrives.
Then update in this order
Power transitions involve the whole platform, so a single driver update often isn’t enough. Use the PC maker’s support page or tool for your exact model (Dell SupportAssist, or Dell Command Update on business models; HP Support Assistant; Lenovo Vantage, for example) and work through this order:
- BIOS or UEFI firmware. Power-management fixes often arrive here, especially for Modern Standby laptops. Back up first, keep the laptop on its charger and never interrupt the update, because a failed firmware flash can leave the PC unable to start. Suspend BitLocker before you begin, have your BitLocker recovery key available in case it’s requested at the next start, and check afterward that protection is on again.
- Chipset and platform drivers, which manage how the processor and its connections change power state.
- Network, Wi-Fi and Bluetooth drivers. They’re often the driver named on a sleep-related 0x9F.
- Graphics drivers, particularly if crashes happen when waking with external monitors attached.
- Thunderbolt or USB4 drivers and dock firmware. If your PC maker publishes an update order for its docks, follow it instead of this list; our second monitor guide covers Dell’s.
Rather have a technician sort it out?
With your approval, a technician can trace which device held up the power change, update the chipset, network, dock and graphics drivers your PC maker supports, and tidy the power settings with you in a remote session. A GoProIT technician can connect remotely, with your permission, and fix it while you watch. $59 per fix, Mon–Fri 8am–8pm ET.
Power settings to test, then put back
These settings control when devices may power down. Turning them off can stop the crashes until a fixed driver arrives, at some cost in battery life. Change one at a time and note each change.
- Device power saving. In Device Manager, open the suspected network adapter or Bluetooth radio and, on the Power Management tab, clear Allow the computer to turn off this device to save power. Not every device shows the tab. For USB hubs and USB selective suspend, use the steps in our USB device not recognized guide.
- Wireless adapter power saving. In Control Panel, open Power Options > Change plan settings > Change advanced power settings. If Wireless Adapter Settings is listed, set Power Saving Mode to Maximum Performance for both battery and plugged in. Some laptops don’t show it.
- PCI Express power saving. In the same dialog, if it’s listed, set PCI Express > Link State Power Management to Off. This affects Wi-Fi cards, NVMe drives and graphics on many PCs.
- Fast Startup. With it on, Shut down saves the Windows kernel session and drivers to the hibernation file and restores them at power-on; Restart always does a full start. For driver power state failure on shutdown or at the next power-on, use Restart (or
shutdown /s /t 0for a full shutdown) for a few days. If that’s clean, turn it off: in Control Panel > Power Options, open Choose what the power buttons do, then Change settings that are currently unavailable, and clear Turn on fast startup (recommended). No such box means it’s already off. Microsoft doesn’t recommend leaving it off, so turn it back on once updated drivers have proved stable.
Once updated drivers have run cleanly for a week or two, turn the settings back on one at a time; if one brings the crash back, leave it off and report the device and setting to the PC maker.
Docks and chargers
A dock connection is a power event, which is why driver power state failure when undocking is a classic case: undocking removes a network adapter, USB hub, audio device and sometimes a display controller in one go, and each of those drivers has to let go of its device without leaving a power request unfinished. Docking a laptop while it’s asleep adds those same devices in the middle of a wake. Until the dock firmware and drivers are current, dock and undock only while the laptop is awake.
Dell documents 0x9F appearing on certain Inspiron, Latitude and Vostro laptops when they’re connected to a 45 W adapter, which supplies too little power; its fix is to use the higher-wattage adapter that shipped with the laptop (the article names 130 W). Undersized USB-C chargers and docks can cause trouble on other brands too, so test with the original adapter before chasing drivers.
In an office, the riskiest habit is closing the lid and lifting the laptop off the dock, which undocks it while it’s asleep or going to sleep. Ask people to open the lid and wait for the desktop before undocking. For laptops used closed on a dock, set When I close the lid to Do nothing under Plugged in (Control Panel > Power Options > Choose what closing the lid does) so they stay awake there; to set this on every PC, use the Group Policy setting Select the lid switch action (plugged in) under Computer Configuration > Administrative Templates > System > Power Management > Button Settings, or the matching lid-close setting under Power in Intune’s settings catalog. Test dock firmware on one desk before rolling it out, and label chargers by laptop model.
When it’s hardware, and when to stop
0x9F is mostly a driver and firmware problem, but a few patterns point at hardware:
- One USB device, headset or dock causes it on every PC it’s connected to: replace that device.
- Crashes continue with nothing attached, after BIOS, chipset and network updates, and with the power settings above turned off: suspect the Wi-Fi card, the drive or the motherboard, and run the PC maker’s hardware diagnostics.
- Parameter 2 traces to the storage controller and hibernate or resume crashes keep coming: check the drive’s health and back up now.
Stop before a BIOS update if you don’t have a current backup and your BitLocker recovery key, or if the laptop can’t stay on its charger. If you’d rather not work through the drivers and settings yourself, this is a typical $59 remote fix as long as the PC stays up long enough to connect; replacing a faulty card, dock or charger is hands-on work. See how our remote support works; every session needs your approval, and you can end it at any time.
Common questions
Is driver power state failure serious?
The crash itself rarely harms the hardware, and a single crash after a driver update may never repeat. Repeated crashes matter more: you lose unsaved work each time, and a laptop that fails to sleep can keep running in a bag and get hot. If it happens more than once, note when it happens and update the drivers involved rather than waiting for it to clear up.
Can a USB device cause DRIVER_POWER_STATE_FAILURE?
Yes. Every USB device has a driver that must respond when the PC sleeps or wakes, and some cheap hubs, adapters and older peripherals don’t. If crashes stop when you unplug everything, reconnect devices one at a time over a few days. Microsoft’s own debugging example traces a 0x9F to a USB HID-class device sitting under the USB hub driver.
Why does my laptop crash when waking from sleep?
On wake, every device has to power back up in a set order. If one driver, often Wi-Fi, graphics or a USB hub, doesn’t come back in time, Windows stops with 0x9F. External monitors and docks add more devices to that list. Update the PC maker’s BIOS, chipset, network and graphics drivers, and test waking with nothing attached.
Should I turn off sleep to stop the crashes?
Only as a stopgap. Setting the lid and power button to hibernate avoids the failing transition while you sort out drivers, but leaving sleep off hides the cause and costs you quick resume. Hibernate is also a useful test: if it works and sleep doesn’t, suspect devices that stay partly powered in sleep. To add Hibernate to the Start menu’s power options, select its box under Power Options > Choose what the power buttons do > Change settings that are currently unavailable.
Can bad RAM or a failing SSD cause driver power state failure?
Faulty RAM is an unlikely cause. 0x9F records a driver that didn’t finish or mishandled a power change, not a memory error, and failing memory more often shows up as MEMORY_MANAGEMENT or a different stop code each time. A struggling SSD is more plausible, because its driver has to flush and power down the drive for sleep and hibernate. If crashes cluster around hibernate or resume, check the drive’s health and back up before updating its firmware.
Why does the screen stay black for minutes before the blue screen?
While a driver holds up a power change, Windows can wait several minutes before giving up; Microsoft’s debugger text puts the limit at usually 10 minutes. Meanwhile the screen often stays black, with the fans running and the power light on. That long pause is typical of 0x9F. Holding the power button during it loses the crash dump, so if you can, wait for the stop screen. If it never comes, note the time and check Reliability Monitor afterward.