| Previous | Next |
| STATUS_DEVICE_NOT_CONNECTED | STATUS_FREE_VM_NOT_AT_BASE |
STATUS_DEVICE_POWER_FAILURE
The hardware did not complete its power transition
Power transitions require coordination between the power policy owner, lower bus drivers and the device itself. The failure may involve an unacknowledged command, lost register context, a rail or clock that did not become available, or firmware that reports an invalid state. It is more specific than a generic I/O failure because the failing operation is power management.
Capture the requested system and device states and whether the device was moving up to D0 or down to a low-power state. Repeatedly disabling sleep can hide the trigger but does not show whether the defect lies in the function driver, bus, ACPI firmware or hardware.
What to inspect
- Record the power IRP minor function, old and new D-states, and completion status from each stack layer.
- Check ACPI, bus and device firmware logs for failed power resources or reset sequences.
- Test cold boot, warm reboot and runtime idle separately to isolate the transition that fails.
References
- Microsoft: Device power states
- Microsoft: Kernel-mode power manager
- Microsoft: Selecting a device power state
- Microsoft Open Specifications: NTSTATUS values
- ReactOS source: kernel power manager
Looking for a different code? Search another status or error code.