| Previous | Next |
| STATUS_ALPC_CHECK_COMPLETION_LIST | STATUS_ACCESS_AUDIT_BY_POLICY |
STATUS_SYSTEM_POWERSTATE_COMPLEX_TRANSITION
The system power path has an intermediate state
Some actions are not a single S-state edge. Hybrid sleep, shutdown variants and firmware-directed sequences can prepare one state while retaining the possibility of entering another. This informational result records that the current transition includes such an intermediate or alternative stage.
Event consumers should preserve all state parameters rather than flattening the event to sleep or shutdown. During diagnosis, identify which phase owns the failure: writing the hibernation image, quiescing devices, entering firmware, or restoring the working state. The same final symptom can originate in different phases.
What to inspect
- Capture every reported source, intermediate and target state.
- Correlate the event with hibernation-file writes and device D-state changes.
- Use power traces to locate the last completed phase before timeout, reset or rollback.
References
- Microsoft: System and device power states
- Microsoft: System sleeping states
- 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.