| Previous | Next |
| STATUS_PARAMETER_QUOTA_EXCEEDED | STATUS_DELAY_LOAD_FAILED |
STATUS_HIBERNATION_FAILURE
The hibernation image or S4 transition failed
Hibernation requires a usable hibernation file, sufficient storage, a supported platform state and device stacks that can quiesce correctly. A failure can occur before the image is committed, while firmware enters S4, or during validation of the saved state. Windows can disable hibernation until restart to avoid repeating an unsafe path.
Do not delete diagnostic evidence before identifying the phase. Check storage and file-system errors, power-manager events and the device stack named by any accompanying status. Recreating the hibernation file can repair file configuration, but it will not fix a driver or firmware transition failure.
What to inspect
- Record the accompanying status, Kernel-Power events and available sleep states from powercfg.
- Check free space, storage health and hibernation-file configuration.
- Run a power trace to identify the last device or firmware phase completed before failure.
References
- Microsoft: System sleeping states
- Microsoft: powercfg command-line options
- Microsoft: Kernel-mode power manager
- Microsoft Open Specifications: NTSTATUS values
- ReactOS source: kernel power manager
Looking for a different code? Search another status or error code.