Code: Select all
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\081113-38157-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*O:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.22280.amd64fre.win7sp1_ldr.130318-1534
Machine Name:
Kernel base = 0xfffff800`03860000 PsLoadedModuleList = 0xfffff800`03aa4670
Debug session time: Sat Aug 10 21:35:21.027 2013 (UTC - 7:00)
System Uptime: 7 days 23:27:36.685
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
...........................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Unable to load image rxfcv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rxfcv.sys
*** ERROR: Module load completed but symbols could not be loaded for rxfcv.sys
Unable to load image snapman.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Probably caused by : rxfcv.sys ( rxfcv+9423 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP:
+6239643839303063
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: PDEngine.exe
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff8813495db38 -- (.exr 0xfffff8813495db38)
ExceptionAddress: fffff88001f6f423 (rxfcv+0x0000000000009423)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000038
Attempt to read from address 0000000000000038
TRAP_FRAME: fffff8813495dbe0 -- (.trap 0xfffff8813495dbe0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8019ac3cc0
rdx=fffff88076800000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001f6f423 rsp=fffff8813495dd70 rbp=0000000000000000
r8=fffffa800f7e1b40 r9=00000000ffffffff r10=fffff80003860000
r11=fffff88076800000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
rxfcv+0x9423:
fffff880`01f6f423 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800038ca07e to fffff800038d2650
STACK_TEXT:
fffff881`3495cc18 fffff800`038ca07e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`0392a44b : nt!KeBugCheck
fffff881`3495cc20 fffff800`038fe16d : fffff800`03ae32c8 fffff800`03a260d4 fffff800`03860000 fffff881`3495db38 : nt!KiKernelCalloutExceptionHandler+0xe
fffff881`3495cc50 fffff800`038fcf45 : fffff800`03a260cc fffff881`3495ccc8 fffff881`3495db38 fffff800`03860000 : nt!RtlpExecuteHandlerForException+0xd
fffff881`3495cc80 fffff800`0390dee1 : fffff881`3495db38 fffff881`3495d390 fffff881`00000000 fffffa80`19ac3cc0 : nt!RtlDispatchException+0x415
fffff881`3495d360 fffff800`038d1d02 : fffff881`3495db38 fffff881`38c5c700 fffff881`3495dbe0 fffffa80`132959e0 : nt!KiDispatchException+0x135
fffff881`3495da00 fffff800`038d087a : 00000000`00000000 00000000`00000038 fffff800`03a51e00 fffff881`38c5c700 : nt!KiExceptionDispatch+0xc2
fffff881`3495dbe0 fffff880`01f6f423 : fffff881`38c5c700 fffffa80`132959e0 fffffa80`0f7dca90 fffff880`024742cc : nt!KiPageFault+0x23a
fffff881`3495dd70 fffff881`38c5c700 : fffffa80`132959e0 fffffa80`0f7dca90 fffff880`024742cc fffffa80`0f7e1b40 : rxfcv+0x9423
fffff881`3495dd78 fffffa80`132959e0 : fffffa80`0f7dca90 fffff880`024742cc fffffa80`0f7e1b40 fffffa80`0f7e1a50 : 0xfffff881`38c5c700
fffff881`3495dd80 fffffa80`0f7dca90 : fffff880`024742cc fffffa80`0f7e1b40 fffffa80`0f7e1a50 00000000`00000000 : 0xfffffa80`132959e0
fffff881`3495dd88 fffff880`024742cc : fffffa80`0f7e1b40 fffffa80`0f7e1a50 00000000`00000000 00000002`00000000 : 0xfffffa80`0f7dca90
fffff881`3495dd90 fffffa80`0f7e1b40 : fffffa80`0f7e1a50 00000000`00000000 00000002`00000000 00000000`00000000 : snapman+0x202cc
fffff881`3495dd98 fffffa80`0f7e1a50 : 00000000`00000000 00000002`00000000 00000000`00000000 fffff880`01f716c5 : 0xfffffa80`0f7e1b40
fffff881`3495dda0 00000000`00000000 : 00000002`00000000 00000000`00000000 fffff880`01f716c5 00000000`00000000 : 0xfffffa80`0f7e1a50
STACK_COMMAND: kb
FOLLOWUP_IP:
rxfcv+9423
fffff880`01f6f423 ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: rxfcv+9423
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: rxfcv
IMAGE_NAME: rxfcv.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 51f20d1f
FAILURE_BUCKET_ID: X64_0x1E_0_rxfcv+9423
BUCKET_ID: X64_0x1E_0_rxfcv+9423
Followup: MachineOwner
---------