| Previous | Next |
| STATUS_IMAGE_AT_DIFFERENT_BASE | STATUS_DS_SHUTTING_DOWN |
STATUS_WAKE_SYSTEM
This is a wake-transition status, not the identity of the wake source
STATUS_WAKE_SYSTEM records that the system has returned from a sleeping state. It does not by itself say whether the wake was caused by a keyboard, network adapter, timer, lid, GPIO event, firmware signal, or another wake-capable device. ACPI describes wake sources through platform resources and power methods, while Windows records the observed wake path separately.
The practical diagnostic mistake is to treat this status as the cause. It is a transition marker. To explain an unwanted wake, collect the wake source and power timeline around it. powercfg /lastwake reports information about the last wake transition when available; powercfg /waketimers and /devicequery wake_armed help identify timers and devices currently able to request wake.
What to correlate
- The sleep state entered and the timestamp at which the machine resumed.
- The last-wake report, armed wake devices, active wake timers, and Kernel-Power events.
- For firmware-defined devices, the ACPI resources and methods that describe wake capability.
- Whether the event is a real platform resume or only a display/session activation; those are different diagnostic paths.
Disabling every wake-capable device may hide the symptom but can remove intended functionality. Identify the actual source before changing wake policy.
References
- Microsoft: System sleeping states
- Microsoft: powercfg command-line options
- UEFI Forum: ACPI software programming model
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.