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\112310-19890-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e1d000 PsLoadedModuleList = 0xfffff800`0305ae50
Debug session time: Mon Nov 22 17:32:36.834 2010 (UTC - 5:00)
System Uptime: 0 days 8:32:44.567
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80003189c3f, fffff880031c4a38, fffff880031c42a0}
Probably caused by : hardware ( nt!IopProcessWorkItem+1f )
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: fffff80003189c3f, The address that the exception occurred at
Arg3: fffff880031c4a38, Exception Record Address
Arg4: fffff880031c42a0, 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!IopProcessWorkItem+1f
fffff800`03189c3f cb retf
EXCEPTION_RECORD: fffff880031c4a38 -- (.exr 0xfffff880031c4a38)
ExceptionAddress: fffff80003189c3f (nt!IopProcessWorkItem+0x000000000000001f)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880031c42a0 -- (.cxr 0xfffff880031c42a0)
rax=fffffa800472de60 rbx=fffffa80045955e0 rcx=000000000472de60
rdx=fffff8800176e9a0 rsi=fffffa8003b64040 rdi=fffffa800472de60
rip=fffff80003189c3f rsp=fffff880031c4c78 rbp=fffff800030325f8
r8=fffffa8003af4918 r9=0000000000000000 r10=fffffffffffffffb
r11=fffffa800472de60 r12=fffffa800472de60 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!IopProcessWorkItem+0x1f:
fffff800`03189c3f cb retf
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 fffff800030c50e0
ffffffffffffffff
FOLLOWUP_IP:
nt!IopProcessWorkItem+1f
fffff800`03189c3f cb retf
BUGCHECK_STR: 0x7E
MISALIGNED_IP:
nt!IopProcessWorkItem+1f
fffff800`03189c3f cb retf
LAST_CONTROL_TRANSFER: from fffff80003189c1f to fffff80003189c3f
STACK_TEXT:
fffff880`031c4c78 fffff800`03189c1f : fffff800`02e9a961 fffff800`03032500 fffff800`03189c20 fffffa80`03b64040 : nt!IopProcessWorkItem+0x1f
fffff880`031c4ca8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWaitForMultipleObjects+0x112
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!IopProcessWorkItem+1f
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .cxr 0xfffff880031c42a0 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
Nice.
