| Previous | Next |
| IRQL_NOT_LESS_OR_EQUAL | MAXIMUM_WAIT_OBJECTS_EXCEEDED |
NO_EXCEPTION_HANDLING_SUPPORT
NO_EXCEPTION_HANDLING_SUPPORT is bug check 0x0B. Microsoft marks the code very infrequent and does not publish meanings for parameters 1 through 4. The symbolic name does not identify an exception code, exception record, or fault address in any documented parameter position.
Do not import fields from another exception stop
Codes such as SYSTEM_THREAD_EXCEPTION_NOT_HANDLED expose a detailed four-argument exception contract. The 0x0B reference does not. If WinDbg identifies exception state in a specific dump, use that debugger-derived context, but do not present the raw bug-check arguments as universally equivalent to the 0x7E fields.
Useful evidence
- Run
!analyze -show 0x0Bto display any stop information known to the installed debugger. - Use
!analyze -vand the symbolized stack to identify the execution path at the stop. - Retain the original dump and matching symbols; changing exception-handling settings without a responsible component in evidence is not a code-defined remedy.
References
- Microsoft: Bug Check 0x0B NO_EXCEPTION_HANDLING_SUPPORT
- Microsoft: !analyze -show for stop-code information
- Microsoft: analyze bug check data
Looking for a different code? Search another status or error code.
