Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\021211-37034-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02800000 PsLoadedModuleList = 0xfffff800`02a3de50
Debug session time: Mon Feb 7 08:18:58.551 2011 (UTC - 5:00)
System Uptime: 0 days 0:07:04.220
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image \??\C:\Windows\system32\Drivers\SYMEVENT64x86.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMEVENT64x86.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT64x86.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88003e8a010, fffff88003386938, fffff880033861a0}
Probably caused by : SYMEVENT64x86.SYS ( SYMEVENT64x86+1a010 )
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: fffff88003e8a010, The address that the exception occurred at
Arg3: fffff88003386938, Exception Record Address
Arg4: fffff880033861a0, 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:
SYMEVENT64x86+1a010
fffff880`03e8a010 48397b10 cmp qword ptr [rbx+10h],rdi
EXCEPTION_RECORD: fffff88003386938 -- (.exr 0xfffff88003386938)
ExceptionAddress: fffff88003e8a010 (SYMEVENT64x86+0x000000000001a010)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000001000010
Attempt to read from address 0000000001000010
CONTEXT: fffff880033861a0 -- (.cxr 0xfffff880033861a0)
rax=fffffa8003d3b401 rbx=0000000001000000 rcx=fffff88003e98108
rdx=67efca7dd9003201 rsi=fffff88003e98108 rdi=fffffa8003d3b400
rip=fffff88003e8a010 rsp=fffff88003386b70 rbp=000000000000009c
r8=0000000000000000 r9=0000000000000000 r10=0000000000501903
r11=fffff88003386bc0 r12=0000000000000004 r13=0000000000000040
r14=fffff8a0004fb430 r15=0000000000000001
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
SYMEVENT64x86+0x1a010:
fffff880`03e8a010 48397b10 cmp qword ptr [rbx+10h],rdi ds:002b:00000000`01000010=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
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: 0000000001000010
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002aa80e0
0000000001000010
FOLLOWUP_IP:
SYMEVENT64x86+1a010
fffff880`03e8a010 48397b10 cmp qword ptr [rbx+10h],rdi
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 0000000000000040 to fffff88003e8a010
STACK_TEXT:
fffff880`03386b70 00000000`00000040 : fffff880`03e98100 00000000`0000009c 00000000`00000002 00000000`00000001 : SYMEVENT64x86+0x1a010
fffff880`03386b78 fffff880`03e98100 : 00000000`0000009c 00000000`00000002 00000000`00000001 fffff880`03e89b9c : 0x40
fffff880`03386b80 00000000`0000009c : 00000000`00000002 00000000`00000001 fffff880`03e89b9c fffff880`03e96430 : SYMEVENT64x86+0x28100
fffff880`03386b88 00000000`00000002 : 00000000`00000001 fffff880`03e89b9c fffff880`03e96430 00000000`00000000 : 0x9c
fffff880`03386b90 00000000`00000001 : fffff880`03e89b9c fffff880`03e96430 00000000`00000000 00000000`00000000 : 0x2
fffff880`03386b98 fffff880`03e89b9c : fffff880`03e96430 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff880`03386ba0 fffff880`03e96430 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000004 : SYMEVENT64x86+0x19b9c
fffff880`03386ba8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000004 fffff880`03e7e28c : SYMEVENT64x86+0x26430
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: SYMEVENT64x86+1a010
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SYMEVENT64x86
IMAGE_NAME: SYMEVENT64x86.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4c535ad7
STACK_COMMAND: .cxr 0xfffff880033861a0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_SYMEVENT64x86+1a010
BUCKET_ID: X64_0x7E_SYMEVENT64x86+1a010
Followup: MachineOwner
---------
