System Uptime: 0 days 9:18:42.959
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffff8ad90000, 0, fffff80002c9db38, 5}
*** WARNING: Unable to verify timestamp for ctoss2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ctoss2k.sys
Could not read faulting driver name
Probably caused by : ctoss2k.sys ( ctoss2k+5cea )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffff8ad90000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002c9db38, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb1100
GetUlongFromAddress: unable to read from fffff80002eb11c0
ffffffff8ad90000
FAULTING_IP:
nt!MmProbeAndLockPages+118
fffff800`02c9db38 410fb601 movzx eax,byte ptr [r9]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: Client.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800b420340 -- (.trap 0xfffff8800b420340)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000980 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000980 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c9db38 rsp=fffff8800b4204d0 rbp=fffff8800b420670
r8=fffffa801496d030 r9=ffffffff8ad90000 r10=000000000000097f
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe nc
nt!MmProbeAndLockPages+0x118:
fffff800`02c9db38 410fb601 movzx eax,byte ptr [r9] ds:ffffffff`8ad90000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c288af to fffff80002c81fc0
STACK_TEXT:
fffff880`0b4201d8 fffff800`02c288af : 00000000`00000050 ffffffff`8ad90000 00000000`00000000 fffff880`0b420340 : nt!KeBugCheckEx
fffff880`0b4201e0 fffff800`02c800ee : 00000000`00000000 ffffffff`8ad90000 00000000`00000000 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x437c1
fffff880`0b420340 fffff800`02c9db38 : fffff880`04f5bcc0 00000000`000007ff fffffa80`12ac6b30 00000000`00000020 : nt!KiPageFault+0x16e
fffff880`0b4204d0 fffff880`02f91cea : fffffa80`1496d000 00000000`00000000 00000000`00000002 ffffffff`8ad90000 : nt!MmProbeAndLockPages+0x118
fffff880`0b4205e0 fffffa80`1496d000 : 00000000`00000000 00000000`00000002 ffffffff`8ad90000 00000000`00000db8 : ctoss2k+0x5cea
fffff880`0b4205e8 00000000`00000000 : 00000000`00000002 ffffffff`8ad90000 00000000`00000db8 00000000`00000010 : 0xfffffa80`1496d000
STACK_COMMAND: kb
FOLLOWUP_IP:
ctoss2k+5cea
fffff880`02f91cea ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: ctoss2k+5cea
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ctoss2k
IMAGE_NAME: ctoss2k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4be16b4a
FAILURE_BUCKET_ID: X64_0x50_ctoss2k+5cea
BUCKET_ID: X64_0x50_ctoss2k+5cea
Followup: MachineOwner
---------
