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\020311-32105-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e03000 PsLoadedModuleList = 0xfffff800`03040e50
Debug session time: Thu Feb 3 01:56:01.450 2011 (UTC - 5:00)
System Uptime: 0 days 0:11:35.090
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 \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, fffff880012e97cb, fffff880021f1788, fffff880021f0ff0}
Probably caused by : iaStor.sys ( iaStor+527cb )
Followup: MachineOwner
---------
1: 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: fffff880012e97cb, The address that the exception occurred at
Arg3: fffff880021f1788, Exception Record Address
Arg4: fffff880021f0ff0, 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:
iaStor+527cb
fffff880`012e97cb 80380e cmp byte ptr [rax],0Eh
EXCEPTION_RECORD: fffff880021f1788 -- (.exr 0xfffff880021f1788)
ExceptionAddress: fffff880012e97cb (iaStor+0x00000000000527cb)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
CONTEXT: fffff880021f0ff0 -- (.cxr 0xfffff880021f0ff0)
rax=0000000000000000 rbx=fffff88005fbb6c0 rcx=fffffa8008468130
rdx=fffffa8008486d71 rsi=fffffa8006292fc0 rdi=fffffa8008468130
rip=fffff880012e97cb rsp=fffff880021f19c8 rbp=fffffa8006293c68
r8=fffffa8008486d70 r9=0000000000000000 r10=fffffa8006293d80
r11=fffffa8006292fc0 r12=fffffa8006293000 r13=0000000000000000
r14=0000000000000009 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
iaStor+0x527cb:
fffff880`012e97cb 80380e cmp byte ptr [rax],0Eh ds:002b:00000000`00000000=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: NULL_DEREFERENCE
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: 0000000000000000
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ab0e0
0000000000000000
FOLLOWUP_IP:
iaStor+527cb
fffff880`012e97cb 80380e cmp byte ptr [rax],0Eh
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff880012e1cc2 to fffff880012e97cb
STACK_TEXT:
fffff880`021f19c8 fffff880`012e1cc2 : fffff880`05fbb6c0 fffffa80`06292fc0 00000000`00000000 fffffa80`06293000 : iaStor+0x527cb
fffff880`021f19d0 fffff880`05fbb6c0 : fffffa80`06292fc0 00000000`00000000 fffffa80`06293000 fffff880`021f19f0 : iaStor+0x4acc2
fffff880`021f19d8 fffffa80`06292fc0 : 00000000`00000000 fffffa80`06293000 fffff880`021f19f0 fffff880`021f19f0 : 0xfffff880`05fbb6c0
fffff880`021f19e0 00000000`00000000 : fffffa80`06293000 fffff880`021f19f0 fffff880`021f19f0 fffffa80`06295309 : 0xfffffa80`06292fc0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: iaStor+527cb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: iaStor
IMAGE_NAME: iaStor.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a287aa4
STACK_COMMAND: .cxr 0xfffff880021f0ff0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_iaStor+527cb
BUCKET_ID: X64_0x7E_iaStor+527cb
Followup: MachineOwner
---------
