| Previous | Next |
| FATAL_ABNORMAL_RESET_ERROR | SOC_CRITICAL_DEVICE_REMOVED |
EXCEPTION_SCOPE_INVALID
EXCEPTION_SCOPE_INVALID is bug check 0x14D. Microsoft defines it as detection of an internal inconsistency in exception dispatching. The public parameter table marks all four arguments as reserved, so there is no documented argument that can be treated as an exception code, fault address, exception record, or context record.
Do not borrow the 0x7E parameter layout
Several better-known exception bug checks expose an exception code and faulting address. EXCEPTION_SCOPE_INVALID does not publish that contract. Decoding parameter 1 as an NTSTATUS or parameter 2 as an instruction pointer simply because another exception stop uses those positions can misdirect the investigation.
Diagnostic focus
- Use
!analyze -vand matching symbols to inspect the exception-dispatch path visible in the dump. - Keep the raw reserved arguments for comparison across identical builds, but do not give them portable labels.
- Look for the first non-kernel component or corrupted control state supported by the stack and context, rather than inferring a user-mode exception from the name.
References
- Microsoft: Bug Check 0x14D EXCEPTION_SCOPE_INVALID
- Microsoft: analyze bug check data
- Microsoft: !analyze extension
Looking for a different code? Search another status or error code.