Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp9_minidump.zip\Mini041210-05.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:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18160.amd64fre.vistasp2_gdr.091208-0542
Machine Name:
Kernel base = 0xfffff800`02607000 PsLoadedModuleList = 0xfffff800`027cbdd0
Debug session time: Mon Apr 12 15:36:01.759 2010 (GMT-4)
System Uptime: 0 days 0:01:02.634
Loading Kernel Symbols
...............................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\drivers\iastor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iastor.sys
*** ERROR: Module load completed but symbols could not be loaded for iastor.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002668fcb, fffffa60022e8a18, fffffa60022e83f0}
Probably caused by : hardware ( iastor+49cd1 )
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: fffff80002668fcb, The address that the exception occurred at
Arg3: fffffa60022e8a18, Exception Record Address
Arg4: fffffa60022e83f0, 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!KeWaitForMultipleObjects+2cb
fffff800`02668fcb 0300 add eax,dword ptr [rax]
EXCEPTION_RECORD: fffffa60022e8a18 -- (.exr 0xfffffa60022e8a18)
ExceptionAddress: fffff80002668fcb (nt!KeWaitForMultipleObjects+0x00000000000002cb)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000100
Attempt to read from address 0000000000000100
CONTEXT: fffffa60022e83f0 -- (.cxr 0xfffffa60022e83f0)
rax=0000000000000100 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffffdffd149d06 rsi=fffffa60019d27f0 rdi=fffffa80055f85d0
rip=fffff80002668fcb rsp=fffffa60022e8c50 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000002
r11=fffffa800519ec8a r12=0000000000000000 r13=fffffa60022e8d10
r14=fffffa80055f86c8 r15=fffffa60019d2180
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!KeWaitForMultipleObjects+0x2cb:
fffff800`02668fcb 0300 add eax,dword ptr [rax] ds:002b:00000000`00000100=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 5
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: 0000000000000100
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000282e080
0000000000000100
FOLLOWUP_IP:
iastor+49cd1
fffffa60`00a55cd1 ?? ???
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
MISALIGNED_IP:
nt!KeWaitForMultipleObjects+2cb
fffff800`02668fcb 0300 add eax,dword ptr [rax]
LAST_CONTROL_TRANSFER: from fffffa6000a55cd1 to fffff80002668fcb
STACK_TEXT:
fffffa60`022e8c50 fffffa60`00a55cd1 : fffffa80`00000002 fffffa80`06128b58 00000000`00000000 fffffa80`00000000 : nt!KeWaitForMultipleObjects+0x2cb
fffffa60`022e8cd0 fffffa80`00000002 : fffffa80`06128b58 00000000`00000000 fffffa80`00000000 21cfdf00`00000000 : iastor+0x49cd1
fffffa60`022e8cd8 fffffa80`06128b58 : 00000000`00000000 fffffa80`00000000 21cfdf00`00000000 fffffa60`022e8d00 : 0xfffffa80`00000002
fffffa60`022e8ce0 00000000`00000000 : fffffa80`00000000 21cfdf00`00000000 fffffa60`022e8d00 00000000`00000000 : 0xfffffa80`06128b58
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: iastor+49cd1
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .cxr 0xfffffa60022e83f0 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
