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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80027eae07c, The address that the exception occurred at
Arg3: ffffd0002a0c68d8, Exception Record Address
Arg4: ffffd0002a0c60e0, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!CmpDelayDerefKCBWorker+110
fffff800`27eae07c 4438be380b0000  cmp     byte ptr [rsi+0B38h],r15b

EXCEPTION_RECORD:  ffffd0002a0c68d8 -- (.exr 0xffffd0002a0c68d8)
ExceptionAddress: fffff80027eae07c (nt!CmpDelayDerefKCBWorker+0x0000000000000110)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000b3a
Attempt to read from address 0000000000000b3a

CONTEXT:  ffffd0002a0c60e0 -- (.cxr 0xffffd0002a0c60e0)
rax=0000000000000000 rbx=0000000000000000 rcx=ffffe0001a79e57f
rdx=00000000ffffffff rsi=0000000000000002 rdi=ffffc0000cc16008
rip=fffff80027eae07c rsp=ffffd0002a0c6b10 rbp=fffff80027d53280
 r8=0000000000000000  r9=7ffff80027d53280 r10=fffff80027d53280
r11=7ffffffffffffffc r12=fffff80027d53270 r13=fffff80027d201c0
r14=fffff80027d532c0 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!CmpDelayDerefKCBWorker+0x110:
fffff800`27eae07c 4438be380b0000  cmp     byte ptr [rsi+0B38h],r15b ds:002b:00000000`00000b3a=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000b3a

READ_ADDRESS: fffff80027d33340: Unable to get special pool info
fffff80027d33340: Unable to get special pool info
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 0000000000000b3a 

FOLLOWUP_IP: 
nt!CmpDelayDerefKCBWorker+110
fffff800`27eae07c 4438be380b0000  cmp     byte ptr [rsi+0B38h],r15b

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80027eae07c

STACK_TEXT:  
ffffd000`2a0c6b10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpDelayDerefKCBWorker+0x110


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!CmpDelayDerefKCBWorker+110

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  52718d9c

STACK_COMMAND:  .cxr 0xffffd0002a0c60e0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nt!CmpDelayDerefKCBWorker+110

BUCKET_ID:  X64_0x7E_nt!CmpDelayDerefKCBWorker+110

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

