ERROR_WAKE_SYSTEM_DEBUGGER - 675 (0x2A3)
{Kernel Debugger Awakened} the system debugger was awakened by an interrupt.
Updated: Feb 21, 2026
Technical Meaning
This error code indicates that the system debugger was awakened by an interrupt. This typically occurs during kernel operation and is not a user-level event.
Error Details
The error message {Kernel Debugger Awakened} suggests that a specific debug event has occurred, which may be related to hardware or software interrupts. The system debugger being awakened implies that the operating environment was paused for debugging purposes, possibly due to an unexpected condition or a breakpoint being hit.
Usage Context
This error code is relevant in scenarios where kernel-level operations are being monitored or debugged. It can occur during normal operation if the system is configured with a kernel debugger attached, or it may indicate an issue that requires further investigation.
Developer Interpretation
Developers should interpret this error as a signal that the system was paused for debugging purposes. This could be due to a variety of reasons, such as hitting a breakpoint, encountering an unexpected condition, or receiving a specific interrupt that triggered the debugger.
Related Errors
- ERROR_DEBUGGER_ATTACHED (674, 0x2A2): Indicates that a debugger is attached to the system but not necessarily awakened.
- ERROR_DEBUGGER_NOT_ATTACHED (673, 0x2A1): Indicates that no debugger is currently attached.
FAQ
Q: What does ERROR_WAKE_SYSTEM_DEBUGGER mean?
A: It indicates that the system debugger was awakened by an interrupt. This can occur during normal operation or due to a specific condition requiring debugging.
Q: How should I handle this error in my application?
A: Typically, this is not an error that needs direct handling by your application. However, if you are developing kernel-mode drivers or applications that interact with the kernel, understanding when and why the debugger was awakened can be crucial for troubleshooting.
Summary
ERROR_WAKE_SYSTEM_DEBUGGER - 675 (0x2A3) is a specific error code indicating that the system debugger was awakened by an interrupt. This event is typically observed during kernel debugging sessions and does not necessarily indicate a failure in the operating system. Developers should be aware of this error to understand when and why the system might pause for debugging purposes.