Microsoft (R) Windows Debugger Version 6.2.8229.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\051512-42401-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
Executable search path is: C:\Windows\System32
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16988.amd64fre.win7_gdr.120401-1505
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`0304ae70
Debug session time: Tue May 15 02:39:12.034 2012 (UTC + 2:00)
System Uptime: 0 days 8:43:17.346
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
...............
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff800030d4c9c, fffff880031929c8, fffff88003192230}
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : ntkrnlmp.exe ( nt!CmpDelayCloseWorker+98 )
Followup: MachineOwner
---------
1: 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: fffff800030d4c9c, The address that the exception occurred at
Arg3: fffff880031929c8, Exception Record Address
Arg4: fffff88003192230, Context Record Address
Debugging Details:
------------------
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
nt!CmpDelayCloseWorker+98
fffff800`030d4c9c 488901 mov qword ptr [rcx],rax
EXCEPTION_RECORD: fffff880031929c8 -- (.exr 0xfffff880031929c8)
ExceptionAddress: fffff800030d4c9c (nt!CmpDelayCloseWorker+0x0000000000000098)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88003192230 -- (.cxr 0xfffff88003192230)
rax=fffff80003082f70 rbx=fffffa800ca8d040 rcx=ff13f8a01ac24330
rdx=00000000000005ca rsi=0000000000000000 rdi=0000000000000001
rip=fffff800030d4c9c rsp=fffff88003192c00 rbp=fffff88003192ca4
r8=fffff8a01a3a3b98 r9=0000000000000a67 r10=fffff88003192c38
r11=fffff8a017d3b5e0 r12=0000000000000004 r13=0000000000000004
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!CmpDelayCloseWorker+0x98:
fffff800`030d4c9c 488901 mov qword ptr [rcx],rax ds:002b:ff13f8a0`1ac24330=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b50e0
GetUlongFromAddress: unable to read from fffff800030b5198
ffffffffffffffff
FOLLOWUP_IP:
nt!CmpDelayCloseWorker+98
fffff800`030d4c9c 488901 mov qword ptr [rcx],rax
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff80002e8b1e1 to fffff800030d4c9c
STACK_TEXT:
fffff880`03192c00 fffff800`02e8b1e1 : fffff800`030d4c04 fffff800`030225f8 fffffa80`0ca8d040 00000000`00000000 : nt!CmpDelayCloseWorker+0x98
fffff880`03192cb0 fffff800`0311d6e6 : 00000000`00000000 fffffa80`0ca8d040 00000000`00000080 fffffa80`0ca7b040 : nt!ExpWorkerThread+0x111
fffff880`03192d40 fffff800`02e5c566 : fffff880`03088180 fffffa80`0ca8d040 fffff880`03093040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03192d80 00000000`00000000 : fffff880`03193000 fffff880`0318d000 fffff880`03192900 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpDelayCloseWorker+98
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4f7912ee
STACK_COMMAND: .cxr 0xfffff88003192230 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!CmpDelayCloseWorker+98
BUCKET_ID: X64_0x7E_nt!CmpDelayCloseWorker+98
Followup: MachineOwner
---------
