*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {d, 0, 0, 0}

Probably caused by : win32k.sys ( win32k!RawInputThread+4f3 )

Followup: MachineOwner
---------

1: 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

DEFAULT_BUCKET_ID:  DRIVER_FAULT

LAST_CONTROL_TRANSFER:  from 804dc84d to 804dc9ff

STACK_TEXT:  
f6e5ca5c 804dc84d f6e5cab4 8970a020 f771f120 nt!SwapContext+0xbe
f6e5ca70 804e1bd2 00000000 8970a020 804e1b83 nt!KiSwapContext+0x2f
f6e5ca7c 804e1b83 804e37aa 00000001 00000000 nt!KiSwapThread+0x8a
f6e5cab4 bf88db63 00000007 895f7270 00000001 nt!KeWaitForMultipleObjects+0x284
f6e5cd30 bf8725df f6e3c490 00000002 f6e5cd54 win32k!RawInputThread+0x4f3
f6e5cd40 bf80109a f6e3c490 f6e5cd64 006dfff4 win32k!xxxCreateSystemThreads+0x60
f6e5cd54 804dd99f 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23
f6e5cd54 7c90eb94 00000000 00000022 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!RawInputThread+4f3
bf88db63 391d10aa9abf    cmp     dword ptr [win32k!gdwUpdateKeyboard (bf9aaa10)],ebx

SYMBOL_STACK_INDEX:  4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45f013f6

SYMBOL_NAME:  win32k!RawInputThread+4f3

FAILURE_BUCKET_ID:  0x7f_d_win32k!RawInputThread+4f3

BUCKET_ID:  0x7f_d_win32k!RawInputThread+4f3

Followup: MachineOwner