Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\New folder\042411-29437-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`03807000 PsLoadedModuleList = 0xfffff800`03a44e50
Debug session time: Sun Apr 24 14:42:46.601 2011 (GMT-4)
System Uptime: 0 days 0:02:51.583
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
.
Unable to load image \SystemRoot\system32\DRIVERS\MijXfilt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, 0, fffff88002fe0988, fffff88002fe01f0}
Probably caused by : MijXfilt.sys ( MijXfilt+2d21 )
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: 0000000000000000, The address that the exception occurred at
Arg3: fffff88002fe0988, Exception Record Address
Arg4: fffff88002fe01f0, 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:
+2d21
00000000`00000000 ?? ???
EXCEPTION_RECORD: fffff88002fe0988 -- (.exr 0xfffff88002fe0988)
ExceptionAddress: 0000000000000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000008
Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000
CONTEXT: fffff88002fe01f0 -- (.cxr 0xfffff88002fe01f0)
rax=fffffa8003fae370 rbx=fffffa8003fb0720 rcx=0000057ffc051ff8
rdx=0000000000000000 rsi=0000057ffc04f9c8 rdi=0000057ffc051ff8
rip=0000000000000000 rsp=fffff88002fe0bc8 rbp=fffff80003a1c5f8
r8=fffff88008f82101 r9=fffffa8003fb0720 r10=fffffa8003f28d20
r11=0000000000000000 r12=fffffa8004058c10 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
00000000`00000000 ?? ???
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: 0000000000000008
EXCEPTION_PARAMETER2: 0000000000000000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003aaf0e0
0000000000000000
FOLLOWUP_IP:
MijXfilt+2d21
fffff880`08f70d21 ?? ???
FAILED_INSTRUCTION_ADDRESS:
+6289952f031edc30
00000000`00000000 ?? ???
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88008f70d21 to 0000000000000000
STACK_TEXT:
fffff880`02fe0bc8 fffff880`08f70d21 : fffffa80`03fb0630 00000000`00000000 00000000`000007ff 00000000`00000030 : 0x0
fffff880`02fe0bd0 fffffa80`03fb0630 : 00000000`00000000 00000000`000007ff 00000000`00000030 00000000`00000031 : MijXfilt+0x2d21
fffff880`02fe0bd8 00000000`00000000 : 00000000`000007ff 00000000`00000030 00000000`00000031 fffffa80`04058c10 : 0xfffffa80`03fb0630
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: MijXfilt+2d21
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: MijXfilt
IMAGE_NAME: MijXfilt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ca69a22
STACK_COMMAND: .cxr 0xfffff88002fe01f0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_NULL_IP_MijXfilt+2d21
BUCKET_ID: X64_0x7E_NULL_IP_MijXfilt+2d21
Followup: MachineOwner
---------