BSOD memory_corruption error

Question

I built a pc using some used parts and getting BSOD every now and then. I ran the Memory.DMP file on windbg and following are my result. Please help me identify the issue. thanks

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

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\Temp*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\Temp*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff803`c268c000 PsLoadedModuleList = 0xfffff803`c2a3a170
Debug session time: Fri Aug 17 00:29:21.367 2018 (UTC - 7:00)
System Uptime: 0 days 5:38:10.215
Loading Kernel Symbols
...Page 200004995 too large to be in the dump file.
..................................Page 2001ecd50 too large to be in the dump file.
.........Page 2001d39ad too large to be in the dump file.
...............Page 20000034d too large to be in the dump file.
..
Page 20000480b too large to be in the dump file.
..Page 200807d14 too large to be in the dump file.
...Page 200800f21 too large to be in the dump file.
.....Page 2001d47e3 too large to be in the dump file.
......Page 20000491f too large to be in the dump file.
.Page 2008062f7 too large to be in the dump file.
.Page 20080870c too large to be in the dump file.
..Page 200805f87 too large to be in the dump file.
..Page 200807d6d too large to be in the dump file.
..Page 200805091 too large to be in the dump file.
.Page 200806300 too large to be in the dump file.
.Page 2008063bb too large to be in the dump file.
..Page 20000263b too large to be in the dump file.
..Page 2008084fa too large to be in the dump file.
.Page 2001ed123 too large to be in the dump file.
.Page 20080a892 too large to be in the dump file.
...Page 20080a855 too large to be in the dump file.
.........Page 20080a6c8 too large to be in the dump file.
.Page 200806a59 too large to be in the dump file.
.Page 200806a59 too large to be in the dump file.
..Page 20080a987 too large to be in the dump file.
..Page 200802477 too large to be in the dump file.
.Page 20080cbd0 too large to be in the dump file.
.Page 200806610 too large to be in the dump file.
.Page 2008066d8 too large to be in the dump file.
.Page 20080a897 too large to be in the dump file.
...Page 200802566 too large to be in the dump file.
.Page 200804462 too large to be in the dump file.
...Page 20080a795 too large to be in the dump file.
...
....Page 200804467 too large to be in the dump file.
....Page 20080572d too large to be in the dump file.
Page 200802d00 too large to be in the dump file.
.Page 2001d8c23 too large to be in the dump file.
.......Page 2001e951d too large to be in the dump file.
..Page 2001d6d18 too large to be in the dump file.
.....Page 2001c19e8 too large to be in the dump file.
.Page 2001d20ed too large to be in the dump file.
...Page 2001ce78b too large to be in the dump file.
.Page 2001c642b too large to be in the dump file.
..Page 2001f2240 too large to be in the dump file.
....Page 2001c0393 too large to be in the dump file.
..Page 2001c740a too large to be in the dump file.
.....Page 200101b45 too large to be in the dump file.
.Page 200102062 too large to be in the dump file.
..Page 200100ce4 too large to be in the dump file.
.Page 2001007fb too large to be in the dump file.
.Page 200103dff too large to be in the dump file.
.Page 2001c69e6 too large to be in the dump file.
..Page 200130166 too large to be in the dump file.
.Page 200114cb3 too large to be in the dump file.
.Page 20011483a too large to be in the dump file.
..Page 2001c2922 too large to be in the dump file.
.Page 20023b28b too large to be in the dump file.
.Page 2001587c6 too large to be in the dump file.
..
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000f5`45fe7018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {1, ffffffffc0000005, ffffd781525f4580, fffffafd5f8db000}

Page 200802d00 too large to be in the dump file.
Page 200802d00 too large to be in the dump file.
Probably caused by : memory_corruption ( nt!MiGetNextPageTablePte+179576 )

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

nt!KeBugCheckEx:
fffff803`c2834ca0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff40c`4846f200=000000000000007a
1: 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: 0000000000000001, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000005, error status (normally i/o status code)
Arg3: ffffd781525f4580, current process (virtual address for lock type 3, or PTE)
Arg4: fffffafd5f8db000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

KEY_VALUES_STRING: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  Z97X-Gaming 5

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  To be filled by O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F6

BIOS_DATE:  04/21/2015

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  Z97X-Gaming 5

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  1

BUGCHECK_P1: 1

BUGCHECK_P2: ffffffffc0000005

BUGCHECK_P3: ffffd781525f4580

BUGCHECK_P4: fffffafd5f8db000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

BUGCHECK_STR:  0x7a_c0000005

CPU_COUNT: 8

CPU_MHZ: fa0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 22'00000000 (cache) 22'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXPNP: 1 (!blackboxpnp)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-DGGKL1J

ANALYSIS_SESSION_TIME:  08-17-2018 01:04:04.0752

ANALYSIS_VERSION: 10.0.18206.1001 amd64fre

LAST_CONTROL_TRANSFER:  from fffff803c2865086 to fffff803c2834ca0

STACK_TEXT:  
fffff40c`4846f1f8 fffff803`c2865086 : 00000000`0000007a 00000000`00000001 ffffffff`c0000005 ffffd781`525f4580 : nt!KeBugCheckEx
fffff40c`4846f200 fffff803`c26ea2d7 : fffff40c`4846f660 00000800`00000000 fffffafd`7eafc6d8 fffff40c`00000000 : nt!MiGetNextPageTablePte+0x179576
fffff40c`4846f250 fffff803`c26ea662 : fffff40c`4846f660 fffffafd`7eafc6d8 fffff40c`00000002 fffff40c`00000000 : nt!MiWalkPageTablesRecursively+0x317
fffff40c`4846f330 fffff803`c26e8367 : fffff40c`4846f660 fffffafd`7ebf57e0 00000000`00000003 fffff803`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
fffff40c`4846f410 fffff803`c26d2a93 : fffff40c`4846f660 ffffd781`00000001 00000000`00000000 ffffd781`00000000 : nt!MiWalkPageTables+0x1e7
fffff40c`4846f500 fffff803`c2b5fc43 : ffffd781`52243170 ffffd781`4ba23340 ffffd781`52243170 ffffd781`525f4a80 : nt!MiDeleteVad+0x8d3
fffff40c`4846f830 fffff803`c2b7d844 : ffffd781`52243170 ffffd781`525f4a80 ffffd781`5344b700 00000000`00000000 : nt!MiUnmapVad+0xa7
fffff40c`4846f860 fffff803`c2b7d683 : ffffd781`4e2ce1c0 ffffd781`4e2ce1c0 ffffd781`52243170 ffffd781`525f4a80 : nt!MiCleanVad+0x30
fffff40c`4846f890 fffff803`c2b7d3cd : ffffffff`00000000 ffffffff`ffffffff fffff40c`4846fb01 ffffd781`525f4580 : nt!MmCleanProcessAddressSpace+0x11f
fffff40c`4846f910 fffff803`c2be3858 : ffffd781`525f4580 ffffb50a`91d52500 fffff40c`4846fb80 00000000`00000000 : nt!PspRundownSingleProcess+0x129
fffff40c`4846f990 fffff803`c2bd4e0f : 00000000`00000000 fffff40c`4846fb01 000000f5`45fe8000 ffffd781`5344b700 : nt!PspExitThread+0x5ac
fffff40c`4846fa90 fffff803`c2845343 : ffffd781`00000fcc ffffd781`5344b700 ffffd781`525f4580 00000000`00000000 : nt!NtTerminateProcess+0xeb
fffff40c`4846fb00 00007ff8`0dbaa434 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000f5`4607f868 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`0dbaa434

THREAD_SHA1_HASH_MOD_FUNC:  d543e52a0de2dd7e1ae97ce87f1d23b2c6b31c28

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  b39e78cb92a19e4c5fbe8dff4317d7443481eb7f

THREAD_SHA1_HASH_MOD:  fe34192f63d13620a8987d294372ee74d699cfee

FOLLOWUP_IP: 
nt!MiGetNextPageTablePte+179576
fffff803`c2865086 cc              int     3

FAULT_INSTR_CODE:  ffb2cccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiGetNextPageTablePte+179576

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5b63c7b5

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  179576

FAILURE_BUCKET_ID:  0x7a_c0000005_nt!MiGetNextPageTablePte

BUCKET_ID:  0x7a_c0000005_nt!MiGetNextPageTablePte

PRIMARY_PROBLEM_CLASS:  0x7a_c0000005_nt!MiGetNextPageTablePte

TARGET_TIME:  2018-08-17T07:29:21.000Z

OSBUILD:  17134

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-08-02 20:10:45

BUILDDATESTAMP_STR:  180410-1804

BUILDLAB_STR:  rs4_release

BUILDOSVER_STR:  10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME:  b43

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7a_c0000005_nt!migetnextpagetablepte

FAILURE_ID_HASH:  {d4584103-842d-cac6-0c84-edfb0f8fe0b3}

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

Answer 1

I ran MemTest86 for all 13 passes and got no errors.

Answer 2

Also, if you have not already try installing the following SATA driver from Intel which may be the latest for the chipset:

https://downloadcenter.intel.com/download/26759...

As a general precaution create a System Restore Point beforehand.

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

Answer 3

I suggest you to Run memory test for at least 8 passes, prefarably Overnight.

https://www.tenforums.com/tutorials/14201-memte...
If you have a DDR4 RAM, use MemTest86 rather than MemTest86+
https://www.memtest86.com/

When the test completes post back the Image(You can use your phone's camera).
Disclaimer: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.