| Previous | Next |
| THREAD_NOT_MUTEX_OWNER | EMPTY_THREAD_REAPER_LIST |
TRAP_CAUSE_UNKNOWN
The TRAP_CAUSE_UNKNOWN bug check has a value of 0x00000012. This indicates that an unknown exception has occurred.
Important
TRAP_CAUSE_UNKNOWN Parameters
| Parameter | Description |
|---|---|
1 |
Type of TRAP_CAUSE_UNKNOWN VALUES 1 - Unexpected interrupt. (Parameter 2 – Interrupt Vector) 2 - Unknown floating point exception. 3 - The enabled and asserted status bits (see processor definition). |
2 |
Dependent on Arg1 |
3 |
Reserved |
4 |
Reserved |
Resolution
The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause.
To start, examine the stack trace using the k, kb, kc, kd, kp, kP, kv (Display Stack Backtrace) command. You can specify the processor number to examine the stacks on all processors.
You can also set a breakpoint in the code leading up to this stop code and attempt to single step forward into the faulting code.
The !idt extension can be used to display the interrupt service routines (ISRs) for a specified interrupt dispatch table (IDT).
Some of the techniques described in Debugging an Interrupt Storm can be used with the unexpected interrupts.
For general information about working with crash dumps, see Crash dump analysis using the Windows debuggers (WinDbg).
Looking for a different code? Search another status or error code.