UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000006f8
Arg4: fffffa6006fbf8dd
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
PROCESS_NAME: mmc.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800020a31ae to fffff800020a3410
Stop 7F, 0x00000008 (double-fault) error occurs because of a single-bit error in the ESP register
http://support.microsoft.com/kb/842465/en-us
http://support.microsoft.com/kb/842465/zh-tw
http://support.microsoft.com/kb/842465/zh-cn
其实里面就俩个命令,检查esp超出范围不。
Part 1: Got Stack? No. We ran out of Kernel Mode Stack and kv won’t tell me why!
http://blogs.msdn.com/b/ntdebugging/archive/2009/11/25/got-stack-no-we-ran-out-of-kernel-mode-stack-and-kv-won-t-tell-me-why-part-1.aspx