DRIVER_POWER_STATE_FAILURE is a Windows Blue Screen of Death (BSOD) stop error associated with device drivers and power-management operations.

The corresponding Windows bug check is:

Bug Check: 0x0000009F
Stop Code: DRIVER_POWER_STATE_FAILURE

According to Microsoft, Bug Check 0x9F indicates that a driver is in an inconsistent or invalid power state. A common scenario occurs when Windows is changing the power state of a device or the computer, but a driver does not complete the required power request within the expected time.

You may see a blue screen containing a message similar to:

Your device ran into a problem and needs to restart.

Stop code: DRIVER_POWER_STATE_FAILURE

The computer normally restarts automatically after Windows collects crash information.

Although the error can appear randomly, it is particularly common during:

• Windows startup or shutdown
• Restarting the computer
• Entering Sleep mode
• Waking from Sleep
• Entering or leaving Hibernate
• Connecting or disconnecting hardware
• Switching between AC power and battery
• Installing or updating drivers
• Installing Windows updates
• Connecting USB, Bluetooth, Wi-Fi or other peripheral devices

What Does Stop Code 0x0000009F Actually Mean?

Windows communicates with hardware through device drivers.

Modern devices also support multiple power states. For example, Windows may ask a Wi-Fi adapter, graphics card, USB controller or storage device to transition from an active state into a lower-power state when the computer enters Sleep.

When Windows initiates such a transition, drivers must correctly process power-related I/O requests.

If a driver becomes stuck, fails to complete the request, or leaves the device in an invalid state, Windows may eventually stop the operating system with:

DRIVER_POWER_STATE_FAILURE (0x9F)

Microsoft documents several forms of Bug Check 0x9F. One common form uses Parameter 1 (Arg1) value 0x3, indicating that a device object has been blocking a power IRP for too long. Another uses 0x4, indicating that a power transition timed out while Windows was waiting for synchronization with the Plug-and-Play subsystem.

This is important because DRIVER_POWER_STATE_FAILURE is generally not simply a "Windows power setting problem." The power transition often exposes an underlying driver, device, firmware or compatibility problem.

Common Symptoms

A computer experiencing DRIVER_POWER_STATE_FAILURE may show several different symptoms.

1. Blue screen during shutdown

Windows displays Shutting down for an unusually long time and eventually crashes with DRIVER_POWER_STATE_FAILURE.

2. Blue screen during restart

The system hangs at:

Restarting...

and eventually generates the 0x9F BSOD.

3. Crash after waking from Sleep

The computer appears to wake, but then freezes or displays a blue screen.

4. Laptop hangs when closing or opening the lid

Closing the laptop lid normally triggers Sleep or another configured power action. A problematic driver may fail during that transition.

5. Very slow shutdown followed by BSOD

This is an important clue because Windows may be waiting for a device driver to complete its power request.

6. Random BSOD while using a laptop

Power-management transitions happen continuously on modern laptops, not only during Sleep. Individual devices can dynamically enter lower-power states.

Most Common Causes of DRIVER_POWER_STATE_FAILURE

1. Faulty or Outdated Device Drivers

The most frequent cause is a driver that does not correctly handle Windows power-management requests.

Potentially problematic drivers include:

• Wi-Fi adapters
• Ethernet controllers
• Bluetooth devices
• Graphics cards
• USB controllers
• USB devices
• Storage controllers
• NVMe controllers
• SATA/AHCI controllers
• Thunderbolt devices
• Docking stations
• Audio devices
• Webcam drivers
• Card readers
• Chipset components

2. Recently Updated Driver

Sometimes the newest driver is not necessarily the most stable driver for a particular computer.

For example:

Old driver → working normally

then:

Driver update → Sleep/Restart BSOD begins

In this situation, rolling back the driver may be more effective than repeatedly installing the same newer version.

3. Incorrect or Generic Windows Driver

Windows Update can automatically install drivers.

Usually these drivers work correctly, but laptops and OEM desktops sometimes require manufacturer-specific drivers for components such as:

• Chipset
• Intel Management Engine
• AMD chipset
• Graphics
• Wi-Fi
• Bluetooth
• Storage
• Thunderbolt
• Serial I/O

If the problem started after Windows automatically changed a driver, check the computer manufacturer's support page.

4. Wi-Fi or Network Adapter Driver

Network adapters are common suspects because Windows frequently changes their power state.

A problematic wireless adapter driver may cause the computer to crash when:

• entering Sleep,
• waking from Sleep,
• shutting down,
• restarting,
• switching networks,
• or changing power mode.

5. Graphics Driver Problems

Graphics hardware undergoes significant power-state changes, particularly on laptops using hybrid graphics.

Systems containing combinations such as:

Intel integrated graphics + NVIDIA GPU

or

AMD integrated graphics + discrete GPU

can encounter DRIVER_POWER_STATE_FAILURE if one graphics driver does not correctly coordinate a power transition.

6. USB Devices and USB Drivers

External hardware can also cause Bug Check 0x9F.

Examples include:

• External hard disks
• USB Wi-Fi adapters
• USB Bluetooth adapters
• Printers
• Scanners
• Webcams
• USB hubs
• Docking stations
• Card readers
• USB audio interfaces

If the error began after connecting new hardware, disconnecting that device is an important diagnostic test.

7. Storage Controller or NVMe Driver

Storage drivers can also participate in power-management transitions.

Potential components include:

• NVMe SSD drivers
• Intel Rapid Storage Technology
• SATA/AHCI controllers
• RAID controllers
• Third-party storage filter drivers

Be especially cautious when changing storage-controller drivers because an incorrect driver can make Windows unbootable.

8. BIOS/UEFI or Firmware Problems

Power management is coordinated between Windows, device drivers and system firmware.

An outdated BIOS/UEFI may therefore contribute to problems involving:

• ACPI
• PCI Express power states
• Sleep
• Modern Standby
• CPU power management
• USB power
• Thunderbolt
• integrated/discrete graphics

Microsoft specifically recommends checking with the computer manufacturer for updated ACPI/BIOS or other firmware when troubleshooting Bug Check 0x9F.

9. Recently Installed Hardware

If DRIVER_POWER_STATE_FAILURE appeared immediately after installing:

• Graphics card
• Wi-Fi card
• Bluetooth adapter
• NVMe SSD
• USB device
• Docking station
• PCIe expansion card

temporarily remove the device and test Windows again.

Microsoft also recommends considering recently added hardware when troubleshooting blue-screen errors.

How to Fix DRIVER_POWER_STATE_FAILURE

Step 1 – Identify When the BSOD Occurs

Before changing anything, determine the trigger.

Ask:

Does it happen during shutdown?

Does it happen during restart?

Does it happen entering Sleep?

Does it happen waking from Sleep?

Does it happen only when a USB device is connected?

Did it begin after a Windows Update?

Did it begin after installing a driver?

This information can significantly narrow down the responsible component.

Step 2 – Disconnect Unnecessary External Devices

Shut down the computer and temporarily disconnect nonessential peripherals.

Leave only essential hardware such as:

• Keyboard
• Mouse
• Monitor

Disconnect devices such as:

• USB drives
• External HDD/SSD
• Printer
• Scanner
• Webcam
• USB hub
• Docking station
• USB Wi-Fi/Bluetooth adapters

Restart and test the computer.

If the BSOD disappears, reconnect devices one at a time until the problematic device is identified.

Step 3 – Check Device Manager

Press:

Windows + X

and select:

Device Manager

Look for devices displaying:

• Yellow warning triangle
• Unknown Device
• Error status
• Disabled hardware
• Driver-related warnings

Pay particular attention to:

Display adapters

Network adapters

Bluetooth

Storage controllers

Universal Serial Bus controllers

System devices

Microsoft recommends checking Device Manager for devices marked with an exclamation point and updating, disabling or uninstalling the problematic device where appropriate.

Step 4 – Update the Suspected Driver

For laptops and branded desktops, preferably obtain important drivers from the computer manufacturer's support website.

Examples include:

• Dell
• HP
• Lenovo
• ASUS
• Acer
• MSI
• Microsoft Surface

For custom-built computers, obtain drivers from the motherboard or hardware manufacturer.

Prioritize:

1. Chipset
2. BIOS/UEFI
3. Graphics
4. Wi-Fi
5. Bluetooth
6. Ethernet
7. Storage/NVMe
8. Thunderbolt/USB controllers

Avoid downloading drivers from unknown third-party "driver download" websites.

Step 5 – Roll Back a Recently Updated Driver

If the problem started immediately after a driver update:

Open:

Device Manager → Device → Properties → Driver

Select:

Roll Back Driver

Restart Windows and test again.

This is especially useful for:

• Graphics drivers
• Wi-Fi drivers
• Bluetooth drivers
• Storage drivers

Step 6 – Reinstall the Problematic Driver

If updating does not solve the problem, reinstalling may help.

Open:

Device Manager

Right-click the suspected device and select:

Uninstall device

Restart Windows.

Then install the correct driver from the computer or hardware manufacturer's support source.

Step 7 – Install Windows Updates

Open:

Settings → Windows Update

Click:

Check for updates

Install applicable Windows updates and restart the computer.

Microsoft includes Windows Update among its recommended basic troubleshooting steps for blue-screen errors.

Step 8 – Test with Fast Startup Disabled

Fast Startup combines aspects of shutdown and hibernation. In some driver-related cases, disabling it is a useful diagnostic step.

Open:

Control Panel → Hardware and Sound → Power Options → Choose what the power buttons do

Click:

Change settings that are currently unavailable

Temporarily clear:

Turn on fast startup

Save the changes and restart the computer.

If the BSOD disappears, investigate chipset, graphics, storage and network drivers rather than assuming Fast Startup itself is defective.

Step 9 – Check Network Adapter Power Management

Open:

Device Manager → Network adapters

Open the properties of the Wi-Fi or Ethernet adapter.

If a Power Management tab is available, review:

Allow the computer to turn off this device to save power

As a troubleshooting test, you can temporarily disable this option and observe whether Sleep/Wake behavior improves.

Do not treat this as a universal permanent fix. If changing the setting solves the problem, update the adapter driver and BIOS/firmware and investigate the underlying compatibility issue.

Step 10 – Check Windows Event Viewer

Press:

Windows + R

Enter:

eventvwr.msc

Navigate to:

Windows Logs → System

Check events around the exact time of the crash.

Look for:

• Critical events
• Driver errors
• Kernel-Power events
• Device initialization failures
• Disk/controller errors
• ACPI warnings
• Plug-and-Play errors

Microsoft specifically recommends reviewing the System log for errors occurring in the same time window as Bug Check 0x9F.

Remember that Kernel-Power Event ID 41 does not necessarily identify the cause. It commonly records that Windows restarted without a clean shutdown.

Step 11 – Repair Windows System Files

Open Command Prompt or Terminal as Administrator.

Run:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, run:

sfc /scannow

Restart Windows.

These commands are useful when Windows component or system-file corruption is suspected, although a true 0x9F problem often ultimately requires identifying the problematic driver or device.

Step 12 – Check the Minidump Files

For recurring DRIVER_POWER_STATE_FAILURE errors, crash-dump analysis is one of the most useful diagnostic methods.

Windows commonly stores small crash dumps in:

C:\Windows\Minidump

Files normally have the .dmp extension.

Example:

082926-15468-01.dmp

The dump can reveal information about the driver and device stack involved in the crash.

Advanced Diagnosis with WinDbg

Microsoft's WinDbg debugger can analyze Windows crash dumps.

Open the dump file and execute:

!analyze -v

For Bug Check 0x9F, this may display information such as:

DRIVER_POWER_STATE_FAILURE (9f)

and the four bug-check arguments.

Microsoft recommends !analyze -v as an initial debugging command for this stop code.

Important fields can include:

MODULE_NAME

IMAGE_NAME

FAILURE_BUCKET_ID

STACK_TEXT

BUGCHECK_CODE

BUGCHECK_P1

BUGCHECK_P2

BUGCHECK_P3

BUGCHECK_P4

Do not automatically assume that every Microsoft component appearing in the stack is defective.

For example, seeing:

ntoskrnl.exe

pci.sys

or

ACPI.sys

does not automatically prove that the Windows kernel, PCI driver or ACPI component is the actual cause.

A third-party device driver interacting with those Windows components may be responsible.

Understanding 0x9F Parameter 1

For advanced technicians, the first bug-check parameter is particularly useful.

Microsoft documents several possible values.

Arg1 = 0x3

A device object has been blocking an IRP for too long.

This is a commonly encountered DRIVER_POWER_STATE_FAILURE scenario.

In this case, the fourth parameter points to the blocked IRP.

A debugger can inspect it further.

Arg1 = 0x4

The power transition timed out while Windows was waiting to synchronize with the Plug-and-Play subsystem.

This can help direct investigation toward PnP/device initialization and power-management activity.

Other parameter values exist, so technicians should interpret the dump according to Microsoft's Bug Check 0x9F documentation rather than assuming every 0x9F crash has the same internal cause.

Using Driver Verifier – Advanced Users Only

Windows includes Driver Verifier, which monitors kernel-mode and graphics drivers for improper behavior.

Run:

verifier

However, Driver Verifier should not be treated as a routine first troubleshooting step.

Microsoft explicitly warns that Driver Verifier can cause the computer to crash and recommends it primarily for systems used for testing and debugging.

If Driver Verifier is used incorrectly, Windows may repeatedly crash during startup.

To reset Driver Verifier from an elevated command prompt:

verifier /reset

Then restart the computer.

For business-critical or production computers, analyzing existing crash dumps is generally preferable before intentionally stressing drivers with Driver Verifier.

Step 13 – Update BIOS/UEFI

Check the computer or motherboard manufacturer's support page for a newer BIOS/UEFI version.

BIOS updates may include fixes involving:

• Power management
• ACPI
• CPU microcode
• PCIe
• USB
• Thunderbolt
• Sleep/Wake
• Memory compatibility
• Graphics initialization

Warning: BIOS updates should only be performed using the manufacturer's official instructions. Interrupting a firmware update can render a system unbootable.

Step 14 – Update Chipset Drivers

Chipset drivers are particularly important because they affect communication among Windows, the motherboard and attached hardware.

For Intel systems, check the PC/motherboard manufacturer's recommended:

• Chipset drivers
• Management Engine components
• Serial IO components

For AMD systems, check the applicable:

• AMD chipset package
• GPIO components
• PCI components
• power-management-related platform drivers

For laptops, OEM-provided packages are often preferable when they have been customized for that model.

Step 15 – Use Safe Mode

If Windows repeatedly crashes before you can troubleshoot normally, start the computer in Safe Mode.

Safe Mode loads a reduced set of drivers and services.

If DRIVER_POWER_STATE_FAILURE disappears in Safe Mode, a third-party driver, service or device becomes a stronger suspect.

Microsoft also recommends Safe Mode as one of the basic troubleshooting approaches when Windows has difficulty restarting after blue-screen errors.

Step 16 – Perform a Clean Boot

If you suspect third-party software rather than hardware, perform a Windows clean boot.

This temporarily removes many third-party startup services and applications from the test environment.

Programs that install low-level drivers deserve particular attention, including:

• VPN software
• Antivirus/security products
• Hardware monitoring utilities
• RGB/control utilities
• Virtualization software
• Backup software
• Disk encryption products
• OEM hardware-management utilities

Step 17 – Use System Restore

If the computer worked correctly before a recent driver or software installation, System Restore may return Windows system configuration to an earlier state.

Search Windows for:

Create a restore point

Then select:

System Restore

Choose a restore point created before the DRIVER_POWER_STATE_FAILURE problem started.

Troubleshooting Based on When the Error Happens

DRIVER_POWER_STATE_FAILURE During Sleep

Concentrate on:

• Wi-Fi driver
• Bluetooth driver
• Graphics driver
• Chipset
• USB devices
• BIOS/UEFI
• power-management settings

DRIVER_POWER_STATE_FAILURE After Wake

Prioritize:

• Graphics
• Wi-Fi
• Bluetooth
• USB controllers
• docking station
• chipset
• BIOS/firmware

DRIVER_POWER_STATE_FAILURE During Shutdown

Investigate:

• recently installed drivers
• USB devices
• network drivers
• storage drivers
• third-party filter drivers
• Fast Startup
• dump files

DRIVER_POWER_STATE_FAILURE During Restart

Look for a driver that cannot correctly stop or reinitialize its device.

Dump analysis becomes particularly useful if the system consistently waits for several minutes before crashing.

Should You Reinstall Windows?

Usually, not initially.

A Windows reinstall may temporarily appear to solve the issue because drivers are replaced, but the problem may return once the problematic driver is installed again.

Before reinstalling Windows, investigate:

1. Crash dump
2. Recently installed drivers
3. Device Manager
4. Windows updates
5. OEM drivers
6. BIOS/UEFI
7. Chipset
8. Graphics
9. Wi-Fi/Bluetooth
10. External devices

Consider Windows repair/reinstallation only after reasonable driver and hardware troubleshooting has failed.

How to Prevent DRIVER_POWER_STATE_FAILURE

Good preventive practices include:

• Keep Windows updated.
• Use drivers appropriate for the exact hardware model.
• Prefer official OEM/hardware manufacturer driver sources.
• Keep BIOS/UEFI reasonably current when updates address stability or compatibility.
• Avoid random third-party driver-update utilities.
• Remove obsolete device-management software.
• Investigate repeated Sleep/Wake failures rather than ignoring them.
• Keep chipset, graphics, Wi-Fi and Bluetooth drivers maintained.
• Create restore points before major driver changes.
• Keep backups of important data.

Frequently Asked Questions (FAQ)

1. What is DRIVER_POWER_STATE_FAILURE?

It is a Windows BSOD indicating that a driver entered or remained in an invalid or inconsistent power state.

2. What is the error code for DRIVER_POWER_STATE_FAILURE?

The bug-check value is:

0x0000009F

3. Is DRIVER_POWER_STATE_FAILURE a hardware problem?

It can be, but a device driver is often directly involved. Hardware, firmware, BIOS and driver compatibility can all contribute to the problem.

4. Why does it happen when my laptop goes to Sleep?

Sleep requires Windows to change the power states of multiple devices. If a driver fails to correctly complete that transition, Windows can generate Bug Check 0x9F.

5. Why does my computer crash when waking from Sleep?

A device may fail to resume correctly. Wi-Fi, Bluetooth, graphics, USB and chipset components are common areas to investigate.

6. Can a graphics driver cause DRIVER_POWER_STATE_FAILURE?

Yes. Graphics devices perform complex power-state transitions, especially on laptops with integrated and discrete GPUs.

7. Can a Wi-Fi driver cause this BSOD?

Yes. Network adapters frequently participate in Windows power-management transitions and can be involved in 0x9F crashes.

8. Can USB devices cause DRIVER_POWER_STATE_FAILURE?

Yes. USB controllers, hubs, external storage devices, docking stations and other peripherals can be involved.

9. Does ntoskrnl.exe mean Windows itself is corrupted?

Not necessarily. ntoskrnl.exe is the Windows kernel and appears in many crash stacks. The underlying cause can still be another driver or device.

10. Does pci.sys mean the PCI driver is defective?

Not automatically. pci.sys can appear because the affected hardware is attached through the PCI/PCIe subsystem. Dump analysis is required to identify the actual device stack and responsible driver.

11. Where are Windows BSOD minidumps stored?

Usually:

C:\Windows\Minidump

12. How can I analyze DRIVER_POWER_STATE_FAILURE?

Use WinDbg to open the .dmp file and begin with:

!analyze -v

Microsoft documents this as a key debugging method for Bug Check 0x9F.

13. Should I use Driver Verifier?

Only when advanced driver debugging is appropriate. Driver Verifier intentionally stresses drivers and can cause additional crashes. Microsoft warns that it should generally be used on systems intended for testing/debugging.

14. How do I disable Driver Verifier?

Open an elevated Command Prompt and run:

verifier /reset

Then restart Windows.

15. Can Windows Update cause this problem?

A DRIVER_POWER_STATE_FAILURE can begin after a driver or Windows update if a newly installed driver is incompatible with the hardware or firmware. In that situation, updating again, reinstalling the OEM driver or rolling back the affected driver may help.

16. Can outdated BIOS cause DRIVER_POWER_STATE_FAILURE?

It can contribute. BIOS/UEFI firmware participates in ACPI and hardware power management, so firmware updates are worth checking when Sleep/Wake or device power transitions consistently fail.

17. Will disabling Fast Startup fix the problem?

It may stop the symptom in some configurations, but it should initially be treated as a diagnostic test. If disabling Fast Startup resolves the BSOD, investigate the relevant device drivers, chipset and firmware.

18. Should I reinstall Windows immediately?

No. DRIVER_POWER_STATE_FAILURE is commonly diagnosable through drivers, devices and crash dumps. Reinstalling Windows should generally come later in the troubleshooting process.

19. Can antivirus software cause this BSOD?

Potentially. Security products can install kernel-level drivers and filter drivers. If the problem started immediately after installing or updating such software, it should be considered during troubleshooting.

20. What should I do if DRIVER_POWER_STATE_FAILURE keeps returning?

Analyze the newest crash dump, identify the affected device/driver stack, update or roll back that driver, update relevant chipset and firmware, and test the associated hardware. Repeated 0x9F crashes should be diagnosed rather than repeatedly suppressed by changing power settings.

Conclusion

DRIVER_POWER_STATE_FAILURE (0x0000009F) is primarily associated with a driver or device that does not correctly complete a Windows power-state transition.

The most important troubleshooting principle is therefore:

Do not focus only on hiding the BSOD—identify which driver or device is failing the power transition.

Start with recently changed drivers and hardware, inspect Device Manager and Event Viewer, update OEM drivers and firmware, and analyze the Windows minidump when the error continues.

For advanced troubleshooting, WinDbg can reveal the bug-check parameters, blocked power request and associated device stack. Microsoft specifically documents dump analysis as an important method of diagnosing Bug Check 0x9F.

#tags

#DRIVER_POWER_STATE_FAILURE #DriverPowerStateFailure #BSOD #WindowsBSOD #BlueScreen #Windows11 #Windows10 #StopCode #Error0x9F #0x0000009F #WindowsError #DriverError #WindowsDrivers #DeviceDriver #PowerStateFailure #PowerManagement #WindowsTroubleshooting #BSODFix #Windows11Fix #Windows10Fix #DriverTroubleshooting #DriverUpdate #DriverRollback #DeviceManager #WinDbg #CrashDump #Minidump #DumpAnalysis #WindowsDebugging #DriverVerifier #WindowsSleep #SleepMode #Hibernate #WakeFromSleep #WindowsShutdown #WindowsRestart #WiFiDriver #GraphicsDriver #BluetoothDriver #USBDriver #ChipsetDriver #NVIDIADriver #AMDDriver #IntelDriver #BIOSUpdate #UEFI #ACPI #WindowsRepair #TechSupport #WindowsTips