update on still current problem, i decided to get the reading for the minidump file and this is what i got
Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\012017-27939-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
Built by: 7601.23572.amd64fre.win7sp1_ldr.161011-0600
Machine Name:
Kernel base = 0xfffff800`02c57000 PsLoadedModuleList = 0xfffff800`02e99730
Debug session time: Fri Jan 20 19:18:58.449 2017 (UTC + 0:00)
System Uptime: 0 days 3:53:45.978
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, fffff880090f507e, fffff880031a8538, fffff880031a7d90}
Probably caused by : RTKVHD64.sys ( RTKVHD64+2eb07e )
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: fffff880090f507e, The address that the exception occurred at
Arg3: fffff880031a8538, Exception Record Address
Arg4: fffff880031a7d90, Context Record Address
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.23572.amd64fre.win7sp1_ldr.161011-0600
SYSTEM_MANUFACTURER: MSI
SYSTEM_PRODUCT_NAME: MS-7721
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: 7.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: V32.8
BIOS_DATE: 12/12/2014
BASEBOARD_MANUFACTURER: MSI
BASEBOARD_PRODUCT: A55M-E33 (MS-7721)
BASEBOARD_VERSION: 7.0
DUMP_TYPE: 2
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff880090f507e
BUGCHECK_P3: fffff880031a8538
BUGCHECK_P4: fffff880031a7d90
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
RTKVHD64+2eb07e
fffff880`090f507e 488b01 mov rax,qword ptr [rcx]
EXCEPTION_RECORD: fffff880031a8538 -- (.exr 0xfffff880031a8538)
ExceptionAddress: fffff880090f507e (RTKVHD64+0x00000000002eb07e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
CONTEXT: fffff880031a7d90 -- (.cxr 0xfffff880031a7d90)
rax=fffffa800a2f6e80 rbx=0000000000000002 rcx=0000000000000000
rdx=fffff880031a8828 rsi=fffffa8007ab8930 rdi=0000000000000003
rip=fffff880090f507e rsp=fffff880031a8770 rbp=0000000000000000
r8=fffff8a009f167d0 r9=0000000000000130 r10=fffff880009f3cc0
r11=fffffa8007ad2000 r12=0000000000001938 r13=0000000000000000
r14=00000000ffffffff r15=fffffa8007ab8aa0
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+0x2eb07e:
fffff880`090f507e 488b01 mov rax,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
Resetting default scope
CPU_COUNT: 4
CPU_MHZ: f35
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 13
CPU_STEPPING: 1
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_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
FOLLOWUP_IP:
RTKVHD64+2eb07e
fffff880`090f507e 488b01 mov rax,qword ptr [rcx]
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f03100
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff80002f032e8
GetUlongPtrFromAddress: unable to read from fffff80002f03498
GetPointerFromAddress: unable to read from fffff80002f030b8
0000000000000000
BUGCHECK_STR: 0x7E
ANALYSIS_SESSION_HOST: PETR-PC
ANALYSIS_SESSION_TIME: 01-20-2017 19:40:34.0362
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff880031a8788 to fffff880090f507e
STACK_TEXT:
fffff880`031a8770 fffff880`031a8788 : 00000000`00000002 00000000`00000000 fffff880`090e89b2 fffffa80`00000000 : RTKVHD64+0x2eb07e
fffff880`031a8778 00000000`00000002 : 00000000`00000000 fffff880`090e89b2 fffffa80`00000000 00000000`00000000 : 0xfffff880`031a8788
fffff880`031a8780 00000000`00000000 : fffff880`090e89b2 fffffa80`00000000 00000000`00000000 00000000`0000001a : 0x2
THREAD_SHA1_HASH_MOD_FUNC: df41f740f2162adabb970a3adc9d96e3ca11b45b
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 4c40dc47e2ae5f22309b5fa934e767e6fe72accb
THREAD_SHA1_HASH_MOD: df41f740f2162adabb970a3adc9d96e3ca11b45b
FAULT_INSTR_CODE: ff018b48
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: RTKVHD64+2eb07e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RTKVHD64
IMAGE_NAME: RTKVHD64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 58469fa3
STACK_COMMAND: .cxr 0xfffff880031a7d90 ; kb
FAILURE_BUCKET_ID: X64_0x7E_RTKVHD64+2eb07e
BUCKET_ID: X64_0x7E_RTKVHD64+2eb07e
PRIMARY_PROBLEM_CLASS: X64_0x7E_RTKVHD64+2eb07e
TARGET_TIME: 2017-01-20T19:18:58.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-10-11 15:57:55
BUILDDATESTAMP_STR: 161011-0600
BUILDLAB_STR: win7sp1_ldr
BUILDOSVER_STR: 6.1.7601.23572.amd64fre.win7sp1_ldr.161011-0600
ANALYSIS_SESSION_ELAPSED_TIME: 640
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x7e_rtkvhd64+2eb07e
FAILURE_ID_HASH: {68ec2fac-6363-7aa8-72be-638c050183c2}
Followup: MachineOwner
---------
Facebook
Twitter
Instagram