Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\KoolKat77\Downloads\ANDY-PC-Mon_07_13_2015_201009_54\071315-24117-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`03e62000 PsLoadedModuleList = 0xfffff800`040a9730
Debug session time: Mon Jul 13 18:36:59.226 2015 (UTC + 6:00)
System Uptime: 0 days 14:12:23.693
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
.......
*** 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, fffff880012e35b3, fffff880037247f8, fffff88003724050}
Probably caused by : iaStor.sys ( iaStor+2d5b3 )
Followup: MachineOwner
---------
0: 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: fffff880012e35b3, The address that the exception occurred at
Arg3: fffff880037247f8, Exception Record Address
Arg4: fffff88003724050, 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+2d5b3
fffff880`012e35b3 48894628 mov qword ptr [rsi+28h],rax
EXCEPTION_RECORD: fffff880037247f8 -- (.exr 0xfffff880037247f8)
ExceptionAddress: fffff880012e35b3 (iaStor+0x000000000002d5b3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88003724050 -- (.cxr 0xfffff88003724050;r)
rax=7fffffffffffffff rbx=fffff8800affd790 rcx=fffffa8004a2f000
rdx=fffffa8003b121a0 rsi=4f4963530400dcc6 rdi=fffffa8004a2f000
rip=fffff880012e35b3 rsp=fffff88003724a30 rbp=0000000000000000
r8=0000000000000002 r9=fffff8800affd790 r10=fffffa8004a2f000
r11=fffff88003724c48 r12=0000000000000000 r13=fffffa8004a3e000
r14=0000000000000002 r15=fffff880009ecf01
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
iaStor+0x2d5b3:
fffff880`012e35b3 48894628 mov qword ptr [rsi+28h],rax ds:002b:4f496353`0400dcee=????????????????
Last set context:
rax=7fffffffffffffff rbx=fffff8800affd790 rcx=fffffa8004a2f000
rdx=fffffa8003b121a0 rsi=4f4963530400dcc6 rdi=fffffa8004a2f000
rip=fffff880012e35b3 rsp=fffff88003724a30 rbp=0000000000000000
r8=0000000000000002 r9=fffff8800affd790 r10=fffffa8004a2f000
r11=fffff88003724c48 r12=0000000000000000 r13=fffffa8004a3e000
r14=0000000000000002 r15=fffff880009ecf01
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
iaStor+0x2d5b3:
fffff880`012e35b3 48894628 mov qword ptr [rsi+28h],rax ds:002b:4f496353`0400dcee=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_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 fffff80004113100
GetUlongFromAddress: unable to read from fffff800041131c0
ffffffffffffffff
FOLLOWUP_IP:
iaStor+2d5b3
fffff880`012e35b3 48894628 mov qword ptr [rsi+28h],rax
BUGCHECK_STR: 0x7E
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from 0000000000000001 to fffff880012e35b3
STACK_TEXT:
fffff880`03724a30 00000000`00000001 : fffffa80`04a4f09c fffffa80`07cbe340 fffffa80`04a4f001 00000000`00000000 : iaStor+0x2d5b3
fffff880`03724a38 fffffa80`04a4f09c : fffffa80`07cbe340 fffffa80`04a4f001 00000000`00000000 fffff880`012bf94e : 0x1
fffff880`03724a40 fffffa80`07cbe340 : fffffa80`04a4f001 00000000`00000000 fffff880`012bf94e fffff880`0affd790 : 0xfffffa80`04a4f09c
fffff880`03724a48 fffffa80`04a4f001 : 00000000`00000000 fffff880`012bf94e fffff880`0affd790 00000000`00000000 : 0xfffffa80`07cbe340
fffff880`03724a50 00000000`00000000 : fffff880`012bf94e fffff880`0affd790 00000000`00000000 00000000`00000000 : 0xfffffa80`04a4f001
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: iaStor+2d5b3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: iaStor
IMAGE_NAME: iaStor.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b0721b5
STACK_COMMAND: .cxr 0xfffff88003724050 ; kb
FAILURE_BUCKET_ID: X64_0x7E_iaStor+2d5b3
BUCKET_ID: X64_0x7E_iaStor+2d5b3
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x7e_iastor+2d5b3
FAILURE_ID_HASH: {7801cd24-0da2-4e37-d28d-4001b0a1e2d2}
Followup: MachineOwner
---------
0: kd> lmvm iaStor
start end module name
fffff880`012b6000 fffff880`014be000 iaStor T (no symbols)
Loaded symbol image file: iaStor.sys
Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
Image name: iaStor.sys
Timestamp: Sat Nov 21 05:09:41 2009 (4B0721B5)
CheckSum: 00085D2F
ImageSize: 00208000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4