Loading Dump File [C:\DUMPS\Music46\021311-15834-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c16000 PsLoadedModuleList = 0xfffff800`02e53e50
Debug session time: Sun Feb 13 00:00:00.015 2011 (UTC + 0:00)
System Uptime: 0 days 5:31:34.545
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.........
Unable to load image \SystemRoot\System32\Drivers\VMC412.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VMC412.sys
*** ERROR: Module load completed but symbols could not be loaded for VMC412.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880024a19a8, fffff880021cf5e8, fffff880021cee50}
Probably caused by : VMC412.sys ( VMC412+289a8 )
Followup: MachineOwner
---------
2: 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: fffff880024a19a8, The address that the exception occurred at
Arg3: fffff880021cf5e8, Exception Record Address
Arg4: fffff880021cee50, 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:
VMC412+289a8
fffff880`024a19a8 0fb601 movzx eax,byte ptr [rcx]
EXCEPTION_RECORD: fffff880021cf5e8 -- (.exr 0xfffff880021cf5e8)
ExceptionAddress: fffff880024a19a8 (VMC412+0x00000000000289a8)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000001
Attempt to read from address 0000000000000001
CONTEXT: fffff880021cee50 -- (.cxr 0xfffff880021cee50)
rax=0000000000000001 rbx=0000000000000006 rcx=0000000000000001
rdx=0000000000000006 rsi=fffffa80041be080 rdi=0000000000000001
rip=fffff880024a19a8 rsp=fffff880021cf820 rbp=0000000000000024
r8=0000000000000000 r9=0000000000000001 r10=0000000000000006
r11=0000000000000140 r12=0000000000000035 r13=0000000000000006
r14=0000000000000000 r15=0000000000000140
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
VMC412+0x289a8:
fffff880`024a19a8 0fb601 movzx eax,byte ptr [rcx] ds:002b:00000000`00000001=??
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: 0000000000000001
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebe0e0
0000000000000001
FOLLOWUP_IP:
VMC412+289a8
fffff880`024a19a8 0fb601 movzx eax,byte ptr [rcx]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffffa80041be080 to fffff880024a19a8
STACK_TEXT:
fffff880`021cf820 fffffa80`041be080 : 00000000`000000c0 00000083`000000a0 fffff880`024a0efc 00000000`00000010 : VMC412+0x289a8
fffff880`021cf828 00000000`000000c0 : 00000083`000000a0 fffff880`024a0efc 00000000`00000010 00000000`00000216 : 0xfffffa80`041be080
fffff880`021cf830 00000083`000000a0 : fffff880`024a0efc 00000000`00000010 00000000`00000216 00000012`00000780 : 0xc0
fffff880`021cf838 fffff880`024a0efc : 00000000`00000010 00000000`00000216 00000012`00000780 00000001`00000035 : 0x83`000000a0
fffff880`021cf840 00000000`00000010 : 00000000`00000216 00000012`00000780 00000001`00000035 00000038`00000028 : VMC412+0x27efc
fffff880`021cf848 00000000`00000216 : 00000012`00000780 00000001`00000035 00000038`00000028 00000000`00000028 : 0x10
fffff880`021cf850 00000012`00000780 : 00000001`00000035 00000038`00000028 00000000`00000028 fffffa80`041be080 : 0x216
fffff880`021cf858 00000001`00000035 : 00000038`00000028 00000000`00000028 fffffa80`041be080 00000000`00000000 : 0x12`00000780
fffff880`021cf860 00000038`00000028 : 00000000`00000028 fffffa80`041be080 00000000`00000000 00000039`000000a2 : 0x1`00000035
fffff880`021cf868 00000000`00000028 : fffffa80`041be080 00000000`00000000 00000039`000000a2 fffffa80`041be080 : 0x38`00000028
fffff880`021cf870 fffffa80`041be080 : 00000000`00000000 00000039`000000a2 fffffa80`041be080 00000000`00042360 : 0x28
fffff880`021cf878 00000000`00000000 : 00000039`000000a2 fffffa80`041be080 00000000`00042360 00000000`00000003 : 0xfffffa80`041be080
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: VMC412+289a8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: VMC412
IMAGE_NAME: VMC412.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b5fa5e7
STACK_COMMAND: .cxr 0xfffff880021cee50 ; kb
FAILURE_BUCKET_ID: X64_0x7E_VMC412+289a8
BUCKET_ID: X64_0x7E_VMC412+289a8
Followup: MachineOwner