BugCheck 50, {fffffa8026ab37dc, 0, fffff80002482d5c, 0}
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Could not read faulting driver name
Probably caused by : snapman.sys ( snapman+2f900 )
Followup: MachineOwner
---------
1: 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: fffffa8026ab37dc, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002482d5c, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800026ca100
GetUlongFromAddress: unable to read from fffff800026ca1c0
fffffa8026ab37dc Nonpaged pool
FAULTING_IP:
nt!IoBuildAsynchronousFsdRequest+2c
fffff800`02482d5c 418a4f4c mov cl,byte ptr [r15+4Ch]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: mms.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
TRAP_FRAME: fffff88019aab830 -- (.trap 0xfffff88019aab830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002482d5c rsp=fffff88019aab9c0 rbp=fffff88019aaba70
r8=fffff8800202f900 r9=0000000000000200 r10=fffffa8026ab3790
r11=0000fffffffff000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!IoBuildAsynchronousFsdRequest+0x2c:
fffff800`02482d5c 418a4f4c mov cl,byte ptr [r15+4Ch] ds:00000000`0000004c=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002508de7 to fffff8000248d8c0
STACK_TEXT:
fffff880`19aab6c8 fffff800`02508de7 : 00000000`00000050 fffffa80`26ab37dc 00000000`00000000 fffff880`19aab830 : nt!KeBugCheckEx
fffff880`19aab6d0 fffff800`0248b9ee : 00000000`00000000 fffffa80`26ab37dc fffff880`19aab900 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4172f
fffff880`19aab830 fffff800`02482d5c : fffffa80`26caaa00 fffff800`00000000 fffffa80`17214670 fffffa80`17214670 : nt!KiPageFault+0x16e
fffff880`19aab9c0 fffff880`0202f900 : 00000000`00000000 00000000`059d0000 fffffa80`26ab3790 00000000`00400000 : nt!IoBuildAsynchronousFsdRequest+0x2c
fffff880`19aaba10 00000000`00000000 : 00000000`059d0000 fffffa80`26ab3790 00000000`00400000 fffff880`19aabab0 : snapman+0x2f900
STACK_COMMAND: kb
FOLLOWUP_IP:
snapman+2f900
fffff880`0202f900 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: snapman+2f900
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: snapman
IMAGE_NAME: snapman.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 54c27838
FAILURE_BUCKET_ID: X64_0x50_snapman+2f900
BUCKET_ID: X64_0x50_snapman+2f900
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x50_snapman+2f900
FAILURE_ID_HASH: {492f7a58-d469-825b-08cd-55d21b4b6ba9}
Followup: MachineOwner
---------
1: kd> lmvm snapman
start end module name
fffff880`02000000 fffff880`0204f000 snapman T (no symbols)
Loaded symbol image file: snapman.sys
Image path: \SystemRoot\system32\DRIVERS\snapman.sys
Image name: snapman.sys
Timestamp: Fri Jan 23 22:05:04 2015 (54C27838)
CheckSum: 00055D1F
ImageSize: 0004F000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4