i have blue screen and .dmp file but i don t understand what all the symbols mean

at 6 days ago i have a blue screen so i open the .dmp file that my pc generate but i don t understand what mean the diferent numbers and symbols that appear in this file so i need your help pls

here is the content of the file .dmp:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Raul del Rio\Desktop\040619-50435-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\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.23915.amd64fre.win7sp1_ldr.170913-0600
Machine Name:
Kernel base = 0xfffff800`03a06000 PsLoadedModuleList = 0xfffff800`03c48750
Debug session time: Sat Apr  6 22:46:44.128 2019 (UTC - 3:00)
System Uptime: 15 days 6:33:29.512
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc500409d0, ffffffffc0000185, 264efe880, fffff8a00813a0e4}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3158a )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc500409d0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 0000000264efe880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a00813a0e4, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc0000185 - El dispositivo de E/S ha comunicado un error de E/S.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  NVIDIA Web Hel

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800dfc9580 -- (.trap 0xfffff8800dfc9580)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a008138000 rbx=0000000000000000 rcx=fffff880163a9000
rdx=0000000000000ff8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003d54960 rsp=fffff8800dfc9710 rbp=fffff8a00813a0e4
 r8=0000000000000ffc  r9=0000000000000fff r10=fffff880163a9000
r11=fffff8a00813a0e4 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiPerformFixups+0x80:
fffff800`03d54960 410fb603        movzx   eax,byte ptr [r11] ds:fffff8a0`0813a0e4=00
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003aeb512 to fffff80003a76e00

STACK_TEXT:  
fffff880`0dfc9268 fffff800`03aeb512 : 00000000`0000007a fffff6fc`500409d0 ffffffff`c0000185 00000002`64efe880 : nt!KeBugCheckEx
fffff880`0dfc9270 fffff800`03a9edc7 : fffffa80`0d5b3c90 fffff880`0dfc93e0 fffff800`03cb5600 fffffa80`0d5b3c90 : nt! ?? ::FNODOBFM::`string'+0x3158a
fffff880`0dfc9350 fffff800`03a85039 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b
fffff880`0dfc9420 fffff800`03a74f2e : 00000000`00000000 fffff8a0`0813a0e4 fffff880`0dfc9500 fffff880`163a9000 : nt!MmAccessFault+0x1399
fffff880`0dfc9580 fffff800`03d54960 : fffffa80`0a737950 fffffa80`09b246f0 fffff880`0dfc9780 fffffa80`0cb4edc0 : nt!KiPageFault+0x16e
fffff880`0dfc9710 fffff800`03d50acb : 00000000`00000000 fffffa80`0b08a480 00000000`00000000 fffff8a0`08138000 : nt!MiPerformFixups+0x80
fffff880`0dfc9770 fffff800`03aa720b : fffffa80`03370b30 fffffa80`09afbbe0 00000000`00000000 fffffa80`09b24600 : nt!MiRelocateImagePfn+0x127
fffff880`0dfc97d0 fffff800`03a9edc7 : fffffa80`09afbb20 fffff880`0dfc9940 fffffa80`0c71eea8 fffffa80`09afbb20 : nt!MiWaitForInPageComplete+0x7ef
fffff880`0dfc98b0 fffff800`03a8510a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b
fffff880`0dfc9980 fffff800`03a74f2e : 00000000`00000008 00000000`67430ba8 00000000`00000001 00000000`00000000 : nt!MmAccessFault+0x146a
fffff880`0dfc9ae0 00000000`67430ba8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0bb7f668 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x67430ba8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+3158a
fffff800`03aeb512 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+3158a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  59b946d1

FAILURE_BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+3158a

BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+3158a

Followup: MachineOwner
---------