Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\bsod\Windows_NT6_BSOD_jcgriff2\053111-17160-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`0304a650
Debug session time: Tue May 31 16:30:56.659 2011 (GMT-4)
System Uptime: 0 days 10:50:20.344
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002e8ebc0, fffff88002fe6ec8, fffff88002fe6720}
Probably caused by : fvevol.sys ( fvevol!FveFilterDeviceControl+1d0 )
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: fffff80002e8ebc0, The address that the exception occurred at
Arg3: fffff88002fe6ec8, Exception Record Address
Arg4: fffff88002fe6720, 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!IofCallDriver+50
fffff800`02e8ebc0 49ff64c070 jmp qword ptr [r8+rax*8+70h]
EXCEPTION_RECORD: fffff88002fe6ec8 -- (.exr 0xfffff88002fe6ec8)
ExceptionAddress: fffff80002e8ebc0 (nt!IofCallDriver+0x0000000000000050)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000000e0
Attempt to read from address 00000000000000e0
CONTEXT: fffff88002fe6720 -- (.cxr 0xfffff88002fe6720)
rax=000000000000000e rbx=fffff8800195b3b0 rcx=fffffa800464a060
rdx=fffffa80068a1010 rsi=fffffa80068a1010 rdi=fffffa800770bc10
rip=fffff80002e8ebc0 rsp=fffff88002fe7108 rbp=0000000000000001
r8=0000000000000000 r9=000000000000000e r10=fffff8000300c348
r11=fffffa80039dc040 r12=fffffa800770bac0 r13=fffffa800ac1a450
r14=0000000000000002 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210282
nt!IofCallDriver+0x50:
fffff800`02e8ebc0 49ff64c070 jmp qword ptr [r8+rax*8+70h] ds:002b:00000000`000000e0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
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: 00000000000000e0
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b4100
00000000000000e0
FOLLOWUP_IP:
fvevol!FveFilterDeviceControl+1d0
fffff880`0192c808 8bd8 mov ebx,eax
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffff8800192c808 to fffff80002e8ebc0
STACK_TEXT:
fffff880`02fe7108 fffff880`0192c808 : 00000000`00000000 fffff800`02e96ab1 00000000`00000000 fffff880`0f25ca8c : nt!IofCallDriver+0x50
fffff880`02fe7110 fffff880`01891082 : fffffa80`068a1010 00000000`00000000 fffffa80`068a13b0 fffffa80`04d50190 : fvevol!FveFilterDeviceControl+0x1d0
fffff880`02fe7180 fffff800`031417ba : fffffa80`04d50040 fffffa80`04d50040 00000000`00000000 fffff880`02fe7af0 : volsnap!VolSnapDeviceControl+0x72
fffff880`02fe71f0 fffff880`018872c5 : 00000000`00000000 fffff880`01886cf0 fffffa80`0596fb01 fffffa80`04d50190 : nt!IoVolumeDeviceToDosName+0x92
fffff880`02fe7ac0 fffff880`01886d1c : 00000000`00000001 fffff880`01886cf0 fffffa80`048eb658 fffffa80`039dc040 : volsnap!VspLogErrorWorker+0x85
fffff880`02fe7c40 fffff800`02e8f021 : fffff880`01886cf0 fffff800`030222b8 fffffa80`039dc040 fffffa80`00000000 : volsnap!VspMediumPriorityWorkItem+0x2c
fffff880`02fe7c70 fffff800`0312132e : 208780b7`99002b24 fffffa80`039dc040 00000000`00000080 fffffa80`0396d990 : nt!ExpWorkerThread+0x111
fffff880`02fe7d00 fffff800`02e76666 : fffff880`009e9180 fffffa80`039dc040 fffff880`009f3f40 219143a7`9431a163 : nt!PspSystemThreadStartup+0x5a
fffff880`02fe7d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: fvevol!FveFilterDeviceControl+1d0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: fvevol
IMAGE_NAME: fvevol.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce793b6
STACK_COMMAND: .cxr 0xfffff88002fe6720 ; kb
FAILURE_BUCKET_ID: X64_0x7E_fvevol!FveFilterDeviceControl+1d0
BUCKET_ID: X64_0x7E_fvevol!FveFilterDeviceControl+1d0
Followup: MachineOwner
---------
