*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002e1f41d, fffff8800637f7a8, fffff8800637f000}
Unable to load image \SystemRoot\System32\Drivers\PCTSD64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PCTSD64.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTSD64.sys
Probably caused by : PCTSD64.sys ( PCTSD64+3fede )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff80002e1f41d, The address that the exception occurred at
Arg3: fffff8800637f7a8, Exception Record Address
Arg4: fffff8800637f000, 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!RtlRealSuccessor+39
fffff800`02e1f41d 488b4908        mov     rcx,qword ptr [rcx+8]
EXCEPTION_RECORD:  fffff8800637f7a8 -- (.exr 0xfffff8800637f7a8)
ExceptionAddress: fffff80002e1f41d (nt!RtlRealSuccessor+0x0000000000000039)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000460009
Attempt to read from address 0000000000460009
CONTEXT:  fffff8800637f000 -- (.cxr 0xfffff8800637f000)
rax=0000000000460001 rbx=fffff8a00b2879c0 rcx=0000000000460001
rdx=fffff8800637fa70 rsi=0000000000000238 rdi=fffff880012aa148
rip=fffff80002e1f41d rsp=fffff8800637f9e8 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=fffff8800637fa70
r11=fffff8800637fa00 r12=fffff8a004c06e08 r13=fffff880012a8000
r14=fffff8a0188c8030 r15=fffffa800b74c070
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!RtlRealSuccessor+0x39:
fffff800`02e1f41d 488b4908        mov     rcx,qword ptr [rcx+8] ds:002b:00000000`00460009=????????????????
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:  0000000000460009
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030af100
 0000000000460009 
FOLLOWUP_IP: 
PCTSD64+3fede
fffff880`012bcede ??              ???
BUGCHECK_STR:  0x7E
LAST_CONTROL_TRANSFER:  from fffff80002f1088f to fffff80002e1f41d
STACK_TEXT:  
fffff880`0637f9e8 fffff800`02f1088f : fffff8a0`0345e6e8 00000000`00000238 fffff8a0`04c06e08 fffff880`012aa148 : nt!RtlRealSuccessor+0x39
fffff880`0637f9f0 fffff880`012bcede : fffff8a0`0b2879c0 fffff8a0`04c06e30 00000000`00000000 00000000`000007ff : nt!RtlEnumerateGenericTableWithoutSplaying+0x3f
fffff880`0637fa20 fffff8a0`0b2879c0 : fffff8a0`04c06e30 00000000`00000000 00000000`000007ff ffffffff`80001598 : PCTSD64+0x3fede
fffff880`0637fa28 fffff8a0`04c06e30 : 00000000`00000000 00000000`000007ff ffffffff`80001598 00000000`00000000 : 0xfffff8a0`0b2879c0
fffff880`0637fa30 00000000`00000000 : 00000000`000007ff ffffffff`80001598 00000000`00000000 fffff880`0637fa68 : 0xfffff8a0`04c06e30
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  PCTSD64+3fede
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: PCTSD64
IMAGE_NAME:  PCTSD64.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4d77fdcc
STACK_COMMAND:  .cxr 0xfffff8800637f000 ; kb
FAILURE_BUCKET_ID:  X64_0x7E_PCTSD64+3fede
BUCKET_ID:  X64_0x7E_PCTSD64+3fede
Followup: MachineOwner