What 0x0000009F actually means
When Windows goes to sleep or wakes, it sends every device a power request (an IRP) and expects an answer within a timeout. A buggy or outdated driver can hold that request and never complete the transition; once the timeout expires, the kernel bug-checks with 0x0000009F and names the stuck driver in the crash data. The crash almost always happens at a specific moment: right after waking the laptop, at shutdown, or when the screen turns off — that timing is the biggest clue to which subsystem is stuck.
The usual suspects are graphics drivers (NVIDIA and AMD alike), wireless and Bluetooth adapters, NVMe and SATA storage drivers, and the tangle of USB and Thunderbolt docks that proxy several devices through one controller. A Windows feature update or a vendor driver update right before the crashes started is the strongest hint of all. On laptops, an outdated chipset driver that does not understand the platform's modern standby is a frequent root cause.
- GPU driver stuck on resume — black screen or crash seconds after opening the laptop lid
- Wi-Fi or Bluetooth adapter not answering sleep requests after a driver update
- USB-C or Thunderbolt dock — crashes around sleep and undocking are classic dock behaviour
- NVMe/SATA storage driver failing the transition, sometimes after firmware updates
- Outdated AMD/Intel chipset drivers breaking modern standby on laptops
- Fast startup — a hybrid shutdown that exercises the same power path as sleep on every boot
The fixes, in the order worth trying
Start with the driver that changed most recently: Device Manager → device Properties → Driver tab shows the Driver Date; if a recently updated driver matches the timing, click Roll Back Driver, otherwise update it from the vendor's site — for GPUs that means the NVIDIA or AMD package, not Windows Update. Then update the platform set: chipset drivers from AMD or Intel, plus the laptop maker's power management drivers. Unplug every dock and USB peripheral for a few days; if the crashes stop, the dock or its driver is your answer.
Next, disable fast startup: Control Panel → Power Options → Choose what the power buttons do → Change settings that are currently unavailable → uncheck Turn on fast startup. Fast startup turns every shutdown into a partial hibernate and is a well-known amplifier of power-transition bugs. If you never use hibernation at all, powercfg /h off in an elevated prompt removes hibernation and fast startup in one stroke.
If the crash keeps coming back
Open Event Viewer → Windows Logs → System and look for BugCheck (Event ID 1001) around the crash times; the entry names the driver faulted in the minidump. The dump itself sits in C:\Windows\Minidump and opens in WinDbg, which usually names the responsible module in its probably caused by line. Run powercfg /energy too — the power management errors it reports often overlap with 0x9F causes, like a device that never enters its low-power state.
Driver Verifier can force the flaky driver to surface, but treat it as a diagnostic of last resort: it deliberately stresses drivers, will crash the PC on purpose when it catches the culprit, and must be switched off with verifier /reset afterwards. Persistent 0x0000009F on a machine with fully updated drivers, no dock and no fast startup points to firmware — update BIOS/UEFI and the SSD firmware — or to a hardware fault in the sleep circuitry, which is a service diagnosis rather than a settings fix.
Questions and Answers
Is DRIVER POWER STATE FAILURE dangerous for my data?
The crash itself is a controlled bug check, so the filesystem normally survives — but unsaved work is lost, and repeated crashes during writes are never healthy. Fix the cause rather than tolerating it.
Why does the BSOD happen only after sleep or shutdown?
Because the failing code path is the power transition itself: the driver gets a sleep or wake request it cannot complete. The timing — crash on wake, at shutdown or when the screen blanks — tells you which device to suspect.
Does disabling fast startup really help?
In many cases, yes. Fast startup routes every shutdown through the same power-transition path as sleep, so a driver that hangs there crashes boot and shutdown as well. Disabling it removes that path entirely.
Know what is included before you buy.
The one-time 30-minute trial covers core tools. PRO-labelled features stay locked until a paid license is activated.
Read next
Write to us: [email protected]