| Previous | Next |
| ERROR_DBG_RIPEXCEPTION | ERROR_DBG_COMMAND_EXCEPTION |
ERROR_DBG_CONTROL_BREAK
What ERROR_DBG_CONTROL_BREAK means
The debugger received a Ctrl+Break control event. In practical terms, this status belongs to console break handling: a stronger console break signal reaches the debugger and may bypass ordinary Ctrl+C expectations.
Typical causes
- A user pressed Ctrl+Break
- A management tool generated CTRL_BREAK_EVENT for the process group
- The debugger is configured to stop on console break notifications
How to investigate
- Record the target process group and event timestamp
- Inspect debugger policy for passing or swallowing Ctrl+Break
- Verify whether the program has a console control handler for graceful shutdown
Developer guidance
Ctrl+Break often indicates an operator request for interruption, but the final behavior depends on debugger continuation and the application handler.
Operational interpretation
When ERROR_DBG_CONTROL_BREAK appears, first determine whether the operation actually failed, completed with an informational condition, or transferred work to another component. Record the API name, returned value, affected process or object, and the immediately preceding event. For this code, the most useful boundary is the console break handling boundary; broad machine-wide remediation before that boundary is identified can hide the original evidence.
Example scenario
An incident begins when a user pressed Ctrl+Break. A responder investigating this result should not begin with a generic reboot that destroys the original context. A better first step is to record the target process group and event timestamp. That evidence connects it to its producing operation and reveals whether this particular result is repeatable, expected, or merely secondary.
Logging and telemetry
Telemetry for this Win32 error should preserve its numeric value, component version, process and thread identifiers, operation name, affected object or endpoint, elapsed time, and the first earlier failure in the same activity. Keep the result correlation identifier stable across callbacks so the status can be joined to the request that initiated this exact operation.
Recovery and validation
Apply recovery only after the responsible state has demonstrably changed. After changing that state, repeat one controlled this result scenario and verify both the returned status and the resulting system state. Absence of another log line is not sufficient: confirm that the intended console break handling action completed, that no resource remains pending, and that later cleanup does not produce a different secondary error.
Escalation notes
Escalate this result with a minimal reproduction, the exact binary architecture, operating-system build, and a timestamped trace covering initialization through cleanup. Include whether the result changes after the affected object is recreated. These details allow the owner of the console break handling component to distinguish a contract violation from environmental state.
References
Looking for a different code? Search another status or error code.