| Previous | Next |
| STATUS_DS_ADMIN_LIMIT_EXCEEDED | STATUS_MUTUAL_AUTHENTICATION_FAILED |
STATUS_DRIVER_FAILED_SLEEP
The driver rejected or failed the sleep path
Before a system enters a sleeping state, device stacks must quiesce I/O and place hardware in compatible D-states. This status means a driver reported that it cannot complete the required standby operation. The limitation can be in the driver’s power implementation, a dependent device, or a hardware capability it advertised incorrectly.
Updating the driver can be appropriate, but first identify the exact stack and power request. Disabling the device may confirm ownership of the failure. Do not assume every sleep failure is the display driver or battery; storage and network devices can block the transition because they hold paging, crash-dump or wake responsibilities.
What to inspect
- Trace the failed power IRP through the full device stack and record the rejecting driver.
- Compare DEVICE_CAPABILITIES with the selected system and device power states.
- Check pending I/O, wake requests and special paging or hibernation-file usage.
References
- Microsoft: Kernel-mode power manager
- Microsoft: Selecting a device power state
- Microsoft: Handling query-remove requests
- Microsoft: Device power states
- Microsoft Open Specifications: NTSTATUS values
- ReactOS source: kernel power manager
Looking for a different code? Search another status or error code.