Edit

Bug Check 0x12: TRAP_CAUSE_UNKNOWN

  • Article

The TRAP_CAUSE_UNKNOWN bug check has a value of 0x00000012. This indicates that an unknown exception has occurred.

Important

This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

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).

If you are not equipped to use the Windows debugger to work on this problem, you can use some basic troubleshooting techniques.

  • Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing this bug check.

  • If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.

  • Confirm that any new hardware that is installed is compatible with the installed version of Windows. For example, you can get information about required hardware at Windows 10 Specifications.

  • For additional general troubleshooting information, see Blue Screen Data.