Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
General causes of "STOP 0x0000007F" errors
Article ID: 137539 - View products that this article applies to.
This article was previously published under Q137539
You may receive the following error message while running Windows:
STOP 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP)
This error message can occur if either of the following conditions exists:
**STOP 0x0000007F (0x000000XX, 0x00000000, 0x00000000, 0x00000000)The most important parameter is the first one (0x0000000X) which may have several different values. The cause of this trap can vary, depending on the value of this parameter. All traps that cause a STOP 0x7F can be found in any Intel x86 microprocessor reference manual as they are specific to the x86 platform. Here are some of the most common ones:
Values Meaning ---------- -------------------- 0x00000000 Divide by Zero Error 0x00000004 Overflow 0x00000005 Bounds Check Fault 0x00000006 Invalid Opcode 0x00000008 Double Fault
Divide by zero errorA divide by zero is caused when a DIV instruction is executed and the divisor is 0. Memory corruption (or other hardware problems) or software failures can cause this.
OverflowThe overflow instruction occurs when the processor executes a call to an interrupt handler when the overflow (OF) flag is set.
Bounds check faultThis fault is generated when the processor, while executing a BOUND instruction, finds the operand exceeds the specified limits. A BOUND instruction is used to ensure that a signed array index is within a certain range.
Invalid opcodeThis fault is generated when the processor attempts to execute an invalid instruction. This is generally caused when the instruction pointer has become corrupted and is pointing to the wrong location. The most common cause of this is hardware memory corruption.
Double faultA double fault occurs when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially, however there are several exceptions that cannot be handled serially and in this situation the processor signals a double fault. The two primary causes for this are hardware and kernel stack overflows. Hardware problems are usually related to CPU, RAM, or bus. Kernel stack overflows are almost always caused by faulty kernel-mode drivers.
To resolve this issue, use the appropriate method:
Article ID: 137539 - Last Review: September 11, 2011 - Revision: 6.0