*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {d, 0, 0, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
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: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 9ae338b2 to 8304a99e
STACK_TEXT:
8df5cc30 9ae338b2 8794d470 000000e1 83134d20 nt!KiTrap0E+0x12
8df5ccc8 9ad7d3ea 00000004 01abfd20 9ae44625 win32k!TimersProc+0x189
8df5cd04 9ad8dfa7 00000004 00000002 8df54400 win32k!RawInputThread+0x61a
8df5cd18 9ae44640 00000004 01abfd20 8df5cd34 win32k!xxxCreateSystemThreads+0x4a
8df5cd28 8304787a 00000004 01abfd60 77457094 win32k!NtUserCallNoParam+0x1b
8df5cd28 77457094 00000004 01abfd60 77457094 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01abfd60 00000000 00000000 00000000 00000000 0x77457094
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
9 errors : !nt (8304a598-8304aab8)
8304a590 04 3c 32 75 1b f7 45 71 *00 00 00 00 74 01 fb 8b .<2u..Eq....t...
...
8304a5b0 66 83 7d 38 23 74 03 cc *e9 12 66 83 7d 34 23 0f f.}8#t....f.}4#.
...
8304a7a0 0f 84 a0 00 00 00 3c 30 *0d 84 98 00 00 00 e9 aa ......<0........
...
8304a820 1e 8b 55 3c 8b ca 83 e1 *05 c1 ea 03 8b 7f 40 0f ..U<..........@.
8304a830 *b5 47 66 03 d0 3b d3 77 0d 03 fa ba 01 00 00 00 .Gf..;.w........
...
8304a890 6a 0d e8 ad 81 23 00 a8 *0d 75 09 59 ff 15 58 31 j....#...u.Y..X1
...
8304a9a0 *e1 64 8b 1d 00 00 00 00 53 83 ec 04 50 51 52 1e .d......S...PQR.
8304a9b0 *04 0f a8 66 b8 23 00 83 ec 30 66 8e d8 66 8e c0 ...f.#...0f..f..
...
8304aab0 ff 15 58 31 01 83 e9 cd *d5 ff ff b9 ad b4 04 83 ..X1............
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE
Followup: memory_corruption
---------
