| Previous | Next |
| STATUS_OBJECT_TYPE_MISMATCH | STATUS_INVALID_DISPOSITION |
STATUS_NONCONTINUABLE_EXCEPTION
Exception handling attempted an invalid continuation
EXCEPTION_RECORD flags can mark an exception as noncontinuable. If a filter or vectored handler returns a continue-execution result for such an exception, Windows raises this second exception instead of restoring the original context. The important diagnostic object is therefore usually the earlier exception record and the handler decision that attempted to continue.
Do not treat this code as the root defect or add another handler that consumes it. Follow the chained ExceptionRecord pointer, inspect the original flags, and identify which filter returned EXCEPTION_CONTINUE_EXECUTION. Fail-fast events, corrupted process states, and explicitly raised noncontinuable exceptions are designed to terminate or transfer control, not to resume at the faulting instruction.
What to inspect
- Inspect the chained original exception record and its flags.
- Identify the filter or vectored handler that requested continuation.
- Verify that exception translation preserves the noncontinuable property.
- Remove “catch everything and continue” logic from corrupted-state paths.
References
- Microsoft Learn: EXCEPTION_RECORD
- Microsoft Learn: Exception Dispatching
- ReactOS source: AMD64 unwind implementation
- Microsoft Learn: __fastfail
Looking for a different code? Search another status or error code.