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\021111-21886-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
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c0c000 PsLoadedModuleList = 0xfffff800`02e49e50
Debug session time: Fri Feb 11 09:43:52.159 2011 (UTC - 5:00)
System Uptime: 0 days 0:21:34.964
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff80002c808b6}
Unable to load image \SystemRoot\system32\DRIVERS\vfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for vfilter.sys
Probably caused by : vfilter.sys ( vfilter+29a6 )
Followup: MachineOwner
---------
1: 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: fffff80002c808b6, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb40e0
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeSetEvent+226
fffff800`02c808b6 488b09 mov rcx,qword ptr [rcx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
TRAP_FRAME: fffff88006369c10 -- (.trap 0xfffff88006369c10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800581e658 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c808b6 rsp=fffff88006369da0 rbp=0000000000000002
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe cy
nt!KeSetEvent+0x226:
fffff800`02c808b6 488b09 mov rcx,qword ptr [rcx] ds:0002:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c7bca9 to fffff80002c7c740
STACK_TEXT:
fffff880`06369ac8 fffff800`02c7bca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`06369ad0 fffff800`02c7a920 : 00000000`00000000 fffffa80`0581e650 00000000`d6d70035 fffffa80`06055000 : nt!KiBugCheckDispatch+0x69
fffff880`06369c10 fffff800`02c808b6 : fffff880`06369e10 fffff880`02d31b0e 00000000`00000052 fffff880`06369e90 : nt!KiPageFault+0x260
fffff880`06369da0 fffff880`02d319a6 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`0581e640 : nt!KeSetEvent+0x226
fffff880`06369e10 fffffa80`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0581e640 00000000`00000000 : vfilter+0x29a6
fffff880`06369e18 00000000`00000000 : 00000000`00000000 fffffa80`0581e640 00000000`00000000 fffff880`02d3142b : 0xfffffa80`00000000
STACK_COMMAND: kb
FOLLOWUP_IP:
vfilter+29a6
fffff880`02d319a6 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: vfilter+29a6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: vfilter
IMAGE_NAME: vfilter.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b048bff
FAILURE_BUCKET_ID: X64_0xA_vfilter+29a6
BUCKET_ID: X64_0xA_vfilter+29a6
Followup: MachineOwner
---------
