Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\041511-36909-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c46e50
Debug session time: Fri Apr 15 18:57:02.102 2011 (GMT-4)
System Uptime: 0 days 0:02:27.178
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff80002a992b3}
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
Probably caused by : SYMEVENT64x86.SYS ( SYMEVENT64x86+198e5 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a992b3, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb10e0
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!IopCompleteRequest+ae3
fffff800`02a992b3 488b09 mov rcx,qword ptr [rcx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: rundll32.exe
IRP_ADDRESS: ffffffffffffff89
TRAP_FRAME: fffff8800578a210 -- (.trap 0xfffff8800578a210)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800578a418 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a992b3 rsp=fffff8800578a3a0 rbp=fffff8800578a4f0
r8=0000000000000000 r9=fffff8800578a4a0 r10=0000000000000002
r11=fffffa8003fc7690 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po cy
nt!IopCompleteRequest+0xae3:
fffff800`02a992b3 488b09 mov rcx,qword ptr [rcx] ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a78ca9 to fffff80002a79740
STACK_TEXT:
fffff880`0578a0c8 fffff800`02a78ca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0578a0d0 fffff800`02a77920 : 00000000`00000001 fffffa80`036fe930 00000000`00000000 fffffa80`01688af0 : nt!KiBugCheckDispatch+0x69
fffff880`0578a210 fffff800`02a992b3 : fffff800`01bf3e80 fffffa80`03d51060 00000000`00000200 fffff800`02a81de7 : nt!KiPageFault+0x260
fffff880`0578a3a0 fffff800`02a560b7 : 00000000`00000001 00000000`00000000 fffffa80`01045000 00000000`00000000 : nt!IopCompleteRequest+0xae3
fffff880`0578a470 fffff800`02a56477 : fffff8a0`01703830 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`0578a4f0 fffff880`02ed18e5 : 00000000`00000040 00000000`00000000 fffffa80`03044c80 fffffa80`01b92280 : nt!KiApcInterrupt+0xd7
fffff880`0578a680 00000000`00000040 : 00000000`00000000 fffffa80`03044c80 fffffa80`01b92280 fffff8a0`00652690 : SYMEVENT64x86+0x198e5
fffff880`0578a688 00000000`00000000 : fffffa80`03044c80 fffffa80`01b92280 fffff8a0`00652690 00000000`00000040 : 0x40
STACK_COMMAND: kb
FOLLOWUP_IP:
SYMEVENT64x86+198e5
fffff880`02ed18e5 ?? ???
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: SYMEVENT64x86+198e5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SYMEVENT64x86
IMAGE_NAME: SYMEVENT64x86.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a849385
FAILURE_BUCKET_ID: X64_0xA_SYMEVENT64x86+198e5
BUCKET_ID: X64_0xA_SYMEVENT64x86+198e5
Followup: MachineOwner
---------
0: kd> lmvm SYMEVENT64x86
start end module name
fffff880`02eb8000 fffff880`02eee000 SYMEVENT64x86 T (no symbols)
Loaded symbol image file: SYMEVENT64x86.SYS
Image path: \??\C:\Windows\system32\Drivers\SYMEVENT64x86.SYS
Image name: SYMEVENT64x86.SYS
Timestamp: Thu Aug 13 18:28:21 2009 (4A849385)
CheckSum: 0002F10A
ImageSize: 00036000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
