| Previous | Next |
| STATUS_NO_MORE_FILES | STATUS_HANDLES_CLOSED |
STATUS_WAKE_SYSTEM_DEBUGGER
The debugger was awakened; this is not a normal sleep-resume report
STATUS_WAKE_SYSTEM_DEBUGGER belongs to the kernel-debugging path. The public NTSTATUS definition says an interrupt awakened the system debugger. Despite the word wake, this should not be interpreted as evidence that the whole computer resumed from ACPI sleep. STATUS_WAKE_SYSTEM is the separate status associated with a system wake transition.
Kernel debugging depends on a debugger transport and on target-side debugger state. When this status appears in a trace or dump, preserve the debugging context: transport type, whether the target was broken in or running, and what interrupt or debugger action immediately preceded the event. A network debugger transport also has a different failure surface from USB or serial debugging, so transport resets and target reboots matter.
Diagnostic focus
- Confirm that kernel debugging was enabled for the target boot and record the active transport.
- Correlate the status with break-in activity and debugger output rather than with ordinary wake-device policy.
- If the event is unexpected, distinguish a debugger interrupt from a platform power interrupt before changing ACPI settings.
- Preserve the target boot configuration and transport logs; reconnecting without them can erase the sequence that triggered the event.
References
- Microsoft: Kernel-mode debugging
- Microsoft: KDNET extensibility and debugger transport
- Microsoft WDK: Wdm.h DDI index
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.