Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\012011-20982-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a4e000 PsLoadedModuleList = 0xfffff800`02c8be50
Debug session time: Thu Jan 20 05:54:05.930 2011 (UTC - 5:00)
System Uptime: 5 days 16:37:07.020
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
...........
Unable to load image \??\C:\Windows\system32\Drivers\EpsCe.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for EpsCe.sys
*** ERROR: Module load completed but symbols could not be loaded for EpsCe.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880060ded03, fffff880031779e8, fffff88003177250}
Probably caused by : EpsCe.sys ( EpsCe+fd03 )
Followup: MachineOwner
---------
2: 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: fffff880060ded03, The address that the exception occurred at
Arg3: fffff880031779e8, Exception Record Address
Arg4: fffff88003177250, 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:
EpsCe+fd03
fffff880`060ded03 4c397038 cmp qword ptr [rax+38h],r14
EXCEPTION_RECORD: fffff880031779e8 -- (.exr 0xfffff880031779e8)
ExceptionAddress: fffff880060ded03 (EpsCe+0x000000000000fd03)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000038
Attempt to read from address 0000000000000038
CONTEXT: fffff88003177250 -- (.cxr 0xfffff88003177250)
rax=0000000000000000 rbx=fffffa800659e001 rcx=fffffa8003a41751
rdx=0000000000000001 rsi=fffffa8005f612d0 rdi=fffffa800659e1c0
rip=fffff880060ded03 rsp=fffff88003177c20 rbp=0000000000000000
r8=0000000000000000 r9=fffff88002f63180 r10=fffffa80036ff810
r11=fffffa8003a41750 r12=fffffa8005bf8a00 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
EpsCe+0xfd03:
fffff880`060ded03 4c397038 cmp qword ptr [rax+38h],r14 ds:002b:00000000`00000038=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
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: 0000000000000038
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf60e0
0000000000000038
FOLLOWUP_IP:
EpsCe+fd03
fffff880`060ded03 4c397038 cmp qword ptr [rax+38h],r14
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffffa800659e1c0 to fffff880060ded03
STACK_TEXT:
fffff880`03177c20 fffffa80`0659e1c0 : 00000000`00000000 00000000`45504345 00000000`00000000 fffff880`02f63180 : EpsCe+0xfd03
fffff880`03177c28 00000000`00000000 : 00000000`45504345 00000000`00000000 fffff880`02f63180 00000000`00000000 : 0xfffffa80`0659e1c0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: EpsCe+fd03
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: EpsCe
IMAGE_NAME: EpsCe.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b9e0530
STACK_COMMAND: .cxr 0xfffff88003177250 ; kb
FAILURE_BUCKET_ID: X64_0x7E_EpsCe+fd03
BUCKET_ID: X64_0x7E_EpsCe+fd03
Followup: MachineOwner
---------