dump
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf8ed7f7, The address that the exception occurred at
Arg3: a8e824f8, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"
FAULTING_IP:
win32k!XLATE:fnXlateBetweenBitfields+6
bf8ed7f7 8b4910 mov ecx,dword ptr [ecx+10h]
TRAP_FRAME: a8e824f8 -- (.trap 0xffffffffa8e824f8)
ErrCode = 00000000
eax=ffffffc2 ebx=04580140 ecx=00000000 edx=00000000 esi=001a00a8 edi=0000000a
eip=bf8ed7f7 esp=a8e8256c ebp=a8e825a0 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
win32k!XLATE:fnXlateBetweenBitfields+0x6:
bf8ed7f7 8b4910 mov ecx,dword ptr [ecx+10h] ds:0023:00000010=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: LinkMain.exe
LAST_CONTROL_TRANSFER: from bf966c5a to bf8ed7f7
STACK_TEXT:
a8e82568 bf966c5a 00000000 00000011 e266c018 win32k!XLATE:fnXlateBetweenBitfields+0x6
a8e825a0 bf836b4e bf9a5ea8 00000000 0019fea8 win32k!vSrcCopyS16D24+0x4e
a8e827b4 bf844f5f e3397b50 00000000 00000000 win32k!EngCopyBits+0x51a
a8e82870 bf8455d9 00000018 00000000 00000011 win32k!GreGetDIBitsInternal+0x79f
a8e82908 8054161c 05010161 0605027f 00000000 win32k!NtGdiGetDIBitsInternal+0x27e
a8e82908 7c90e4f4 05010161 0605027f 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00115274 00000000 00000000 00000000 00000000 0x7c90e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!XLATE:fnXlateBetweenBitfields+6
bf8ed7f7 8b4910 mov ecx,dword ptr [ecx+10h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!XLATE:fnXlateBetweenBitfields+6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48025f2a
FAILURE_BUCKET_ID: 0x8E_win32k!XLATE:fnXlateBetweenBitfields+6
BUCKET_ID: 0x8E_win32k!XLATE:fnXlateBetweenBitfields+6
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf8ed7f7, The address that the exception occurred at
Arg3: a8e824f8, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"
FAULTING_IP:
win32k!XLATE:fnXlateBetweenBitfields+6
bf8ed7f7 8b4910 mov ecx,dword ptr [ecx+10h]
TRAP_FRAME: a8e824f8 -- (.trap 0xffffffffa8e824f8)
ErrCode = 00000000
eax=ffffffc2 ebx=04580140 ecx=00000000 edx=00000000 esi=001a00a8 edi=0000000a
eip=bf8ed7f7 esp=a8e8256c ebp=a8e825a0 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
win32k!XLATE:fnXlateBetweenBitfields+0x6:
bf8ed7f7 8b4910 mov ecx,dword ptr [ecx+10h] ds:0023:00000010=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: LinkMain.exe
LAST_CONTROL_TRANSFER: from bf966c5a to bf8ed7f7
STACK_TEXT:
a8e82568 bf966c5a 00000000 00000011 e266c018 win32k!XLATE:fnXlateBetweenBitfields+0x6
a8e825a0 bf836b4e bf9a5ea8 00000000 0019fea8 win32k!vSrcCopyS16D24+0x4e
a8e827b4 bf844f5f e3397b50 00000000 00000000 win32k!EngCopyBits+0x51a
a8e82870 bf8455d9 00000018 00000000 00000011 win32k!GreGetDIBitsInternal+0x79f
a8e82908 8054161c 05010161 0605027f 00000000 win32k!NtGdiGetDIBitsInternal+0x27e
a8e82908 7c90e4f4 05010161 0605027f 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00115274 00000000 00000000 00000000 00000000 0x7c90e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!XLATE:fnXlateBetweenBitfields+6
bf8ed7f7 8b4910 mov ecx,dword ptr [ecx+10h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!XLATE:fnXlateBetweenBitfields+6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48025f2a
FAILURE_BUCKET_ID: 0x8E_win32k!XLATE:fnXlateBetweenBitfields+6
BUCKET_ID: 0x8E_win32k!XLATE:fnXlateBetweenBitfields+6
Followup: MachineOwner
---------