*******************************************************************************
* *
* 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:
+1e7952f00a1dfdc
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff88005e98888 -- (.exr 0xfffff88005e98888)
ExceptionAddress: fffff88001570000 (volsnap!VspWriteApplicationInfo)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000003
Attempt to read from address 0000000000000003
TRAP_FRAME: fffff88005e98930 -- (.trap 0xfffff88005e98930)
Unable to read trap frame at fffff880`05e98930
LAST_CONTROL_TRANSFER: from fffff8000328446e to fffff8000328c710
STACK_TEXT:
fffff880`05e97978 fffff800`0328446e : 00000000`00000000 fffff880`05e98170 00000000`00000000 fffff800`032e0f6b : nt!KeBugCheck
fffff880`05e97980 fffff800`032b240d : fffff800`03498cf8 fffff800`033dbaf0 fffff800`0321c000 fffff880`05e98888 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`05e979b0 fffff800`032b9a90 : fffff800`033dbae8 fffff880`05e97a28 fffff880`05e98888 fffff800`0321c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`05e979e0 fffff800`032c69ef : fffff880`05e98888 fffff880`05e980f0 fffff880`00000000 fffff8a0`00000004 : nt!RtlDispatchException+0x410
fffff880`05e980c0 fffff800`0328bd82 : fffff880`05e98888 fffffa80`03eca650 fffff880`05e98930 fffffa80`054bb390 : nt!KiDispatchException+0x16f
fffff880`05e98750 fffff800`0328a8fa : 00000000`00000000 fffffa80`03eca650 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`05e98930 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`0328446e 90 nop
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
Followup: MachineOwner