Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\USER\Downloads\Compressed\SF_30-12-2014\123014-11481-01.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 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02c0c000 PsLoadedModuleList = 0xfffff800`02e4f890
Debug session time: Tue Dec 30 12:11:53.806 2014 (UTC + 6:00)
System Uptime: 1 days 3:02:23.476
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
..........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffffa8006c52431, fffff880035777e8, fffff88003577040}
*** WARNING: Unable to verify timestamp for SaiK0CD7.sys
*** ERROR: Module load completed but symbols could not be loaded for SaiK0CD7.sys
Probably caused by : SaiK0CD7.sys ( SaiK0CD7+186a3 )
Followup: MachineOwner
---------
4: 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: fffffa8006c52431, The address that the exception occurred at
Arg3: fffff880035777e8, Exception Record Address
Arg4: fffff88003577040, 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:
+0
fffffa80`06c52431 007300 add byte ptr [rbx],dh
EXCEPTION_RECORD: fffff880035777e8 -- (.exr 0xfffff880035777e8)
ExceptionAddress: fffffa8006c52431
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000
CONTEXT: fffff88003577040 -- (.cxr 0xfffff88003577040)
rax=fffffa8006c52420 rbx=0000000000000000 rcx=fffffa800c089fe0
rdx=fffffa80083515e0 rsi=fffffa800ecc5010 rdi=0000000000000000
rip=fffffa8006c52431 rsp=fffff88003577a20 rbp=fffffa800a386098
r8=fffff88003577ac0 r9=0000000000000000 r10=0000000000000000
r11=fffff880009b3180 r12=fffffa800c089fe0 r13=fffff88003577ac0
r14=fffffa80083515e0 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
fffffa80`06c52431 007300 add byte ptr [rbx],dh 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: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb9100
GetUlongFromAddress: unable to read from fffff80002eb91c0
0000000000000000 Nonpaged pool
FOLLOWUP_IP:
SaiK0CD7+186a3
fffff880`021076a3 ?? ???
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffffa800a386098 to fffffa8006c52431
STACK_TEXT:
fffff880`03577a20 fffffa80`0a386098 : fffff880`021076a3 00000000`00000000 fffffa80`00000000 fffffa80`0e278000 : 0xfffffa80`06c52431
fffff880`03577a28 fffff880`021076a3 : 00000000`00000000 fffffa80`00000000 fffffa80`0e278000 00000000`00000001 : 0xfffffa80`0a386098
fffff880`03577a30 00000000`00000000 : fffffa80`00000000 fffffa80`0e278000 00000000`00000001 fffff880`02113808 : SaiK0CD7+0x186a3
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: SaiK0CD7+186a3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SaiK0CD7
IMAGE_NAME: SaiK0CD7.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 505aea0c
STACK_COMMAND: .cxr 0xfffff88003577040 ; kb
FAILURE_BUCKET_ID: X64_0x7E_SaiK0CD7+186a3
BUCKET_ID: X64_0x7E_SaiK0CD7+186a3
Followup: MachineOwner
---------
4: kd> lmvm SaiK0CD7
start end module name
fffff880`020ef000 fffff880`0211e000 SaiK0CD7 T (no symbols)
Loaded symbol image file: SaiK0CD7.sys
Image path: \SystemRoot\system32\DRIVERS\SaiK0CD7.sys
Image name: SaiK0CD7.sys
Timestamp: Thu Sep 20 16:03:56 2012 (505AEA0C)
CheckSum: 0002DD0D
ImageSize: 0002F000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
