Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\020110-20514-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c54000 PsLoadedModuleList = 0xfffff800`02e91e50
Debug session time: Mon Feb 1 14:24:51.158 2010 (GMT-5)
System Uptime: 0 days 0:44:05.000
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88000e92946, fffff880035a1828, fffff880035a1080}
Probably caused by : cdrom.sys ( cdrom!RequestSetSentTime+1d )
Followup: MachineOwner
---------
3: 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: fffff88000e92946, The address that the exception occurred at
Arg3: fffff880035a1828, Exception Record Address
Arg4: fffff880035a1080, 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:
Wdf01000!imp_WdfObjectGetTypedContextWorker+1e
fffff880`00e92946 4c8b5110 mov r10,qword ptr [rcx+10h]
EXCEPTION_RECORD: fffff880035a1828 -- (.exr 0xfffff880035a1828)
ExceptionAddress: fffff88000e92946 (Wdf01000!imp_WdfObjectGetTypedContextWorker+0x000000000000001e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880035a1080 -- (.cxr 0xfffff880035a1080)
rax=0000000000000000 rbx=fffffa8007885b80 rcx=bdb2acfffeffeef8
rdx=424d530001001100 rsi=0000000000000000 rdi=fffffa8007de0c90
rip=fffff88000e92946 rsp=fffff880035a1a60 rbp=0000057ff8851b18
r8=fffff880031b0188 r9=0000000000000000 r10=fffffa80046eac80
r11=fffff880035a1b00 r12=00000000002d0940 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=00210246
Wdf01000!imp_WdfObjectGetTypedContextWorker+0x1e:
fffff880`00e92946 4c8b5110 mov r10,qword ptr [rcx+10h] ds:002b:bdb2acff`feffef08=????????????????
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 fffff80002efc0e0
ffffffffffffffff
FOLLOWUP_IP:
cdrom!RequestSetSentTime+1d
fffff880`031a35d5 48bb2003000080f7ffff mov rbx,0FFFFF78000000320h
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff880031a35d5 to fffff88000e92946
STACK_TEXT:
fffff880`035a1a60 fffff880`031a35d5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!imp_WdfObjectGetTypedContextWorker+0x1e
fffff880`035a1ab0 fffff880`031bdfd8 : 00000000`00000018 00000000`c00000bb 00000000`00000000 fffff880`033d3180 : cdrom!RequestSetSentTime+0x1d
fffff880`035a1ae0 fffff880`031b4dab : fffffa80`07de0c90 0000057f`f8851b18 00000000`00000000 fffff880`04c8b110 : cdrom!RequestSendMcnRequest+0x20
fffff880`035a1b30 fffff880`00e756fb : 00000000`00000000 fffffa80`07753db0 fffffa80`07687b80 fffff800`02e695f8 : cdrom!RequestProcessSerializedIoctl+0x583
fffff880`035a1c10 fffff800`02fbf527 : fffffa80`074d1e20 fffffa80`07753d00 fffffa80`036fd680 fffffa80`036fd680 : Wdf01000!FxWorkItem::WorkItemThunk+0x113
fffff880`035a1c40 fffff800`02cd3161 : fffff800`02e69500 fffff800`02fbf504 fffffa80`036fd680 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`035a1c70 fffff800`02f69166 : 00000000`00000000 fffffa80`036fd680 00000000`00000080 fffffa80`036e6040 : nt!ExpWorkerThread+0x111
fffff880`035a1d00 fffff800`02ca4486 : fffff880`03363180 fffffa80`036fd680 fffff880`0336dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`035a1d40 00000000`00000000 : fffff880`035a2000 fffff880`0359c000 fffff880`035a19b0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: cdrom!RequestSetSentTime+1d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: cdrom
IMAGE_NAME: cdrom.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11a
STACK_COMMAND: .cxr 0xfffff880035a1080 ; kb
FAILURE_BUCKET_ID: X64_0x7E_cdrom!RequestSetSentTime+1d
BUCKET_ID: X64_0x7E_cdrom!RequestSetSentTime+1d
Followup: MachineOwner
---------
