Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Yussi\Downloads\SZANTOFAMILY-PC-Thu_09_03_2015__73048_99\090215-18111-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.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`02e10000 PsLoadedModuleList = 0xfffff800`03057730
Debug session time: Wed Sep 2 06:52:45.882 2015 (UTC + 6:00)
System Uptime: 0 days 0:28:05.710
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
.......
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88005e6aa5c, fffff880050b16b8, fffff880050b0f10}
Probably caused by : RTKVHD64.sys ( RTKVHD64+191a5c )
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: fffff88005e6aa5c, The address that the exception occurred at
Arg3: fffff880050b16b8, Exception Record Address
Arg4: fffff880050b0f10, 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:
RTKVHD64+191a5c
fffff880`05e6aa5c 4c8b4158 mov r8,qword ptr [rcx+58h]
EXCEPTION_RECORD: fffff880050b16b8 -- (.exr 0xfffff880050b16b8)
ExceptionAddress: fffff88005e6aa5c (RTKVHD64+0x0000000000191a5c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000100000057
Attempt to read from address 0000000100000057
CONTEXT: fffff880050b0f10 -- (.cxr 0xfffff880050b0f10)
rax=0000000000000001 rbx=fffffa8007ab5000 rcx=00000000ffffffff
rdx=fffffa80088a5eb0 rsi=fffffa8008c7dc10 rdi=fffffa80088a5e60
rip=fffff88005e6aa5c rsp=fffff880050b18f0 rbp=0000000000000000
r8=fffffa80088a5e60 r9=fffffa80088a5e60 r10=007300790053005c
r11=fffff880050b19f0 r12=0000000000000004 r13=0000000000000001
r14=0000000000000000 r15=fffff880009ef040
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
RTKVHD64+0x191a5c:
fffff880`05e6aa5c 4c8b4158 mov r8,qword ptr [rcx+58h] ds:002b:00000001`00000057=????????????????
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: 0000000100000057
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c1100
GetUlongFromAddress: unable to read from fffff800030c11c0
0000000100000057 Nonpaged pool
FOLLOWUP_IP:
RTKVHD64+191a5c
fffff880`05e6aa5c 4c8b4158 mov r8,qword ptr [rcx+58h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 8000000000000000 to fffff88005e6aa5c
STACK_TEXT:
fffff880`050b18f0 80000000`00000000 : fffffa80`08acc820 00000000`c00000bb 00000000`00000000 00000000`00000000 : RTKVHD64+0x191a5c
fffff880`050b18f8 fffffa80`08acc820 : 00000000`c00000bb 00000000`00000000 00000000`00000000 fffff800`02ecf71c : 0x80000000`00000000
fffff880`050b1900 00000000`c00000bb : 00000000`00000000 00000000`00000000 fffff800`02ecf71c fffffa80`08c7dc10 : 0xfffffa80`08acc820
fffff880`050b1908 00000000`00000000 : 00000000`00000000 fffff800`02ecf71c fffffa80`08c7dc10 fffff800`02ecf71c : 0xc00000bb
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: RTKVHD64+191a5c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RTKVHD64
IMAGE_NAME: RTKVHD64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4caaf6d0
STACK_COMMAND: .cxr 0xfffff880050b0f10 ; kb
FAILURE_BUCKET_ID: X64_0x7E_RTKVHD64+191a5c
BUCKET_ID: X64_0x7E_RTKVHD64+191a5c
Followup: MachineOwner
---------
2: kd> lmvm RTKVHD64
start end module name
fffff880`05cd9000 fffff880`05f3c800 RTKVHD64 T (no symbols)
Loaded symbol image file: RTKVHD64.sys
Image path: RTKVHD64.sys
Image name: RTKVHD64.sys
[COLOR="Red"] Timestamp: Tue Oct 05 15:58:40 2010 (4CAAF6D0)[/COLOR]
CheckSum: 0026A429
ImageSize: 00263800
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
rb: