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\090110-10250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02854000 PsLoadedModuleList = 0xfffff800`02a91e50
Debug session time: Wed Sep 1 18:36:17.584 2010 (GMT-4)
System Uptime: 0 days 0:03:47.569
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002bb79b2, fffff88003369a48, fffff880033692b0}
Probably caused by : ntkrnlmp.exe ( nt!CmpDelayDerefKCBWorker+d6 )
Followup: MachineOwner
---------
4: 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: fffff80002bb79b2, The address that the exception occurred at
Arg3: fffff88003369a48, Exception Record Address
Arg4: fffff880033692b0, 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:
nt!CmpDelayDerefKCBWorker+d6
fffff800`02bb79b2 4038ae380b0000 cmp byte ptr [rsi+0B38h],bpl
EXCEPTION_RECORD: fffff88003369a48 -- (.exr 0xfffff88003369a48)
ExceptionAddress: fffff80002bb79b2 (nt!CmpDelayDerefKCBWorker+0x00000000000000d6)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880033692b0 -- (.cxr 0xfffff880033692b0)
rax=fffffa80048f0bb0 rbx=0000000000000000 rcx=fffff8a0041c56a8
rdx=0000000000000baf rsi=fbfff8a000c9e010 rdi=fffff8a0041c55d0
rip=fffff80002bb79b2 rsp=fffff88003369c80 rbp=0000000000000001
r8=fffff8a008bfcd78 r9=00000000384af7e5 r10=fffff8a0041c5130
r11=fffffa80048f0b60 r12=fffff80002ac9ee0 r13=fffff80002ac9f40
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
nt!CmpDelayDerefKCBWorker+0xd6:
fffff800`02bb79b2 4038ae380b0000 cmp byte ptr [rsi+0B38h],bpl ds:002b:fbfff8a0`00c9eb48=??
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: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002afc0e0
ffffffffffffffff
FOLLOWUP_IP:
nt!CmpDelayDerefKCBWorker+d6
fffff800`02bb79b2 4038ae380b0000 cmp byte ptr [rsi+0B38h],bpl
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff800028d1961 to fffff80002bb79b2
STACK_TEXT:
fffff880`03369c80 fffff800`028d1961 : fffff800`02bb78dc fffff800`02a695f8 fffffa80`048f0b60 00000000`00000000 : nt!CmpDelayDerefKCBWorker+0xd6
fffff880`03369cb0 fffff800`02b68c06 : 01cb49cb`efd762d0 fffffa80`048f0b60 00000000`00000080 fffffa80`048da040 : nt!ExpWorkerThread+0x111
fffff880`03369d40 fffff800`028a2c26 : fffff880`03186180 fffffa80`048f0b60 fffff880`031910c0 01cb49cb`efd9c52a : nt!PspSystemThreadStartup+0x5a
fffff880`03369d80 00000000`00000000 : fffff880`0336a000 fffff880`03364000 fffff880`03369970 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpDelayDerefKCBWorker+d6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
STACK_COMMAND: .cxr 0xfffff880033692b0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!CmpDelayDerefKCBWorker+d6
BUCKET_ID: X64_0x7E_nt!CmpDelayDerefKCBWorker+d6
Followup: MachineOwner
---------
