| Previous | Next |
| ERROR_TIMER_NOT_CANCELED | ERROR_BAD_STACK |
ERROR_UNWIND
What this result means
ERROR_UNWIND is a Windows system result. Stack unwinding is the process of walking back through active call frames during exception handling, cancellation, or nonlocal control transfer. This code signals that Windows is in or reporting an unwind condition.
Why it can appear
- an exception handler is being invoked during normal stack unwind
- code incorrectly treats an unwind notification as a new independent exception
- a language runtime, injected hook, or manual exception frame violates unwind rules
- corrupted stack metadata causes the unwinder to enter an abnormal path
Diagnostic workflow
- capture the original exception code, exception flags, instruction pointer, stack pointer, and full stack
- inspect whether the exception record has unwind flags set
- verify compiler, runtime, and module architecture consistency
- enable page heap, application verifier, or control-flow diagnostics when stack corruption is suspected
Correct recovery and handling
Do not swallow unwind notifications or resume execution from an invalid frame. Let the language runtime complete cleanup. If custom exception handling is present, follow the platform ABI and keep handlers minimal.
Administrator and support checklist
- confirm whether the condition is isolated to one machine, one user, one file, or one application build.
- Compare the host reporting this result with a known-good system using the same Windows edition and policy.
- Review updates, drivers, security-policy changes, restores, and infrastructure incidents that preceded this result.
- Preserve logs and dumps associated with this result before rebooting when the failure may be intermittent or destructive.
- Use vendor-supported repair or rollback steps for it instead of copying system files or disabling protections ad hoc.
Developer guidance
When handling it, log the API or subsystem that returned it, the first lower-level failure, relevant object identifiers, process and thread context, and safe operation parameters. Preserve the original numeric Value rather than converting it to an unrelated HRESULT or NTSTATUS. Retry it only when the evidence shows a transient dependency; deterministic it cases involving policy, format, compatibility, or integrity should fail fast.
What to record in telemetry
- Windows build, architecture, and component version for the result event
- the first result timestamp and the operation then in progress
- process, thread, session, and target object associated with it
- warnings or lower-layer status values immediately preceding it
- whether retry, restart, rollback, or repair changed the result outcome
Example investigation pattern
Investigate it by reproducing the operation once with detailed logging, then correlate that timestamp with Windows events and lower-layer traces. Compare the affected object or process with a known-good one, change one variable at a time, and stop retrying When it is deterministic. That method keeps the first relevant failure from being hidden by secondary cleanup messages.
Related and easily confused conditions
This is not itself proof of a crash. It may be an intermediate state during legitimate exception processing. The original exception and the handler that mishandled it are usually more important.
Operational note
Do not diagnose it from its text alone. The result can cross subsystem boundaries and may summarize an earlier, more specific event. The first failure in time is normally more useful than the last message printed during cleanup.
References
Looking for a different code? Search another status or error code.