Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Crash\Windows_NT6_BSOD_jcgriff2\022711-16489-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0361b000 PsLoadedModuleList = 0xfffff800`03860e90
Debug session time: Mon Feb 28 01:46:24.458 2011 (GMT-5)
System Uptime: 0 days 0:00:17.785
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, fffff880033bd988, fffff880033bd1e0}
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: fffff880033bd988, Exception Record Address
Arg4: fffff880033bd1e0, 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:
+16
00000000`00000000 ?? ???
EXCEPTION_RECORD: fffff880033bd988 -- (.exr 0xfffff880033bd988)
ExceptionAddress: 0000000000000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000008
Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000
CONTEXT: fffff880033bd1e0 -- (.cxr 0xfffff880033bd1e0)
rax=fffffa8007ceb370 rbx=fffffa80087ad9e0 rcx=0000057ff8314ff8
rdx=0000000000000000 rsi=0000057ff7852708 rdi=0000057ff8314ff8
rip=0000000000000000 rsp=fffff880033bdbc8 rbp=fffff80003838658
r8=fffff88005f34101 r9=fffffa80087ad9e0 r10=fffffa80078a4c70
r11=0000000000000000 r12=fffffa80087a48f0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 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 fffff800038cc0e8
0000000000000000
FOLLOWUP_IP:
MijXfilt+2d21
fffff880`05f22d21 ?? ???
FAILED_INSTRUCTION_ADDRESS:
+60ff952f043ade40
00000000`00000000 ?? ???
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88005f22d21 to 0000000000000000
STACK_TEXT:
fffff880`033bdbc8 fffff880`05f22d21 : fffffa80`087ad8f0 fffff880`047a2b0f 00000000`00000000 fffff800`00000000 : 0x0
fffff880`033bdbd0 fffffa80`087ad8f0 : fffff880`047a2b0f 00000000`00000000 fffff800`00000000 00000000`00000031 : MijXfilt+0x2d21
fffff880`033bdbd8 fffff880`047a2b0f : 00000000`00000000 fffff800`00000000 00000000`00000031 fffffa80`087a48f0 : 0xfffffa80`087ad8f0
fffff880`033bdbe0 fffff800`03991f33 : fffffa80`07efb490 00000000`00000000 fffffa80`0672db60 fffffa80`0672db60 : usbhub!UsbhHubProcessChangeWorker+0x19b
fffff880`033bdc40 fffff800`036a5a21 : fffff800`03838600 fffff800`03991f01 fffffa80`0672db00 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`033bdc70 fffff800`03938cce : 00000000`00000000 fffffa80`0672db60 00000000`00000080 fffffa80`066a3840 : nt!ExpWorkerThread+0x111
fffff880`033bdd00 fffff800`0368cfe6 : fffff880`03164180 fffffa80`0672db60 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033bdd40 00000000`00000000 : fffff880`033be000 fffff880`033b8000 fffff880`033bd9a0 00000000`00000000 : nt!KxStartSystemThread+0x16
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 0xfffff880033bd1e0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_NULL_IP_MijXfilt+2d21
BUCKET_ID: X64_0x7E_NULL_IP_MijXfilt+2d21
Followup: MachineOwner
---------
