Memory_Corruption BSOD Windows 10 Error

[bdrew50]

I recently built my own computer about 5 months ago and starting around 2 months ago I started having an issue where my computer would encounter a blue screen error with varying error messages saying "Your PC ran into a problem and needs to restart. We're just collecting some error info and then we'll restart for you".

I use my desktop everyday after getting back from work, and probably encounter this error 3 days or so out of the week (so not every time i use my computer). Most of the time what happens is i'll start my computer up and will immediately encounter this error, then my computer will automatically restart and work fine for the rest of the night. However i've also had issues where a couple of times while i'm using my computer it will all of a sudden crash and i will encounter this blue screen error and computer will turn off.

I would like advice on how to troubleshoot whether or not this is a driver issue or a hardware issue, and how i should go about solving this.

My Build:

CPU: AMD - Ryzen 5 1600 3.2GHz 6-Core Processor

Motherboard: Gigabyte - GA-AB350-GAMING 3 ATX AM4

Memory: Corsair - Vengeance LPX 16GB (2 x 8GB) DDR4-3000 Memory

Storage: Western Digital - Blue 250GB 2.5" Solid State Drive Western Digital - Caviar Blue 1TB 3.5" 7200RPM Internal Hard Drive

Video Card: Asus - GeForce GTX 1070 8GB STRIX Video Card

Case: Cooler Master - MasterBox 5 (Black) ATX Mid Tower Case

Power Supply: EVGA - 650W 80+ Gold Certified Semi-Modular ATX Power Supply

Mini Dump Error:



Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 16299 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff802`78c06000 PsLoadedModuleList = 0xfffff802`78f6d110
Debug session time: Sun Feb 18 23:47:23.648 2018 (UTC - 5:00)
System Uptime: 3 days 3:20:40.305
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061948, The subtype of the bugcheck.
Arg2: 000000001585f311
Arg3: 0000000000000001
Arg4: 000000001585f311

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR: 0x1a_61948

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80278dc7954 to fffff80278d7b430

STACK_TEXT:
fffffd0d`df8a03f8 fffff802`78dc7954 : 00000000`0000001a 00000000`00061948 00000000`1585f311 00000000`00000001 : nt!KeBugCheckEx
fffffd0d`df8a0400 fffff802`78c89ae3 : 0a000003`cfea6c62 00000000`00000000 00000000`00000001 00000000`00000001 : nt!MiDereferenceIoPages+0xccea8
fffffd0d`df8a04b0 fffff802`78c2999b : ffffb606`9abdc040 00000000`00000000 ffffc713`50200000 ffffb4e3`89a81000 : nt!MiDeletePteRun+0x553
fffffd0d`df8a0630 fffff802`790a5849 : ffffb606`a2ba3a80 fffff802`78e2cb15 ffffdb00`00000000 ffffb606`a2ba3580 : nt!MiDeletePagablePteRange+0x27b
fffffd0d`df8a07b0 fffff802`78c29c95 : 00000000`00000000 00000000`0bcb5000 ffffb606`a2ba3580 ffffb606`a2ba3580 : nt!MiDeleteVadBitmap+0x55
fffffd0d`df8a07f0 fffff802`790a573f : ffffb606`a2ba3580 00000000`00000000 ffffb606`a2ba3858 ffffb606`a2ba3b48 : nt!MiDeleteFinalPageTables+0x109
fffffd0d`df8a08b0 fffff802`78c27fab : ffffb606`a2ba3580 ffffb606`a2ba3858 ffffb606`9abdc040 ffffb606`a2ba3580 : nt!MmDeleteProcessAddressSpace+0x5f
fffffd0d`df8a0900 fffff802`7913a0be : ffffb606`a2ba3858 ffffb606`a2ba3550 ffffb606`a2ba3858 00000000`00000000 : nt!PspProcessDelete+0x19b
fffffd0d`df8a09a0 fffff802`78c51a36 : 00000000`00000000 00000000`00000000 ffffb606`a2ba3858 ffffb606`a2ba3580 : nt!ObpRemoveObjectRoutine+0x7e
fffffd0d`df8a0a00 fffff802`790a54e2 : 00000000`00000000 ffffb606`9ad4da28 ffffb606`9ad4da28 00000000`00000000 : nt!ObfDereferenceObjectWithTag+0xc6
fffffd0d`df8a0a40 fffff802`7913a0be : fffff802`78ce1900 ffffb606`9ad4d350 fffff802`78ce1900 ffffb606`9ad4d350 : nt!PspThreadDelete+0x1d2
fffffd0d`df8a0ab0 fffff802`78c51a36 : 00000000`00000000 00000000`00000000 fffff802`78ce1900 ffffb606`9ad4d380 : nt!ObpRemoveObjectRoutine+0x7e
fffffd0d`df8a0b10 fffff802`78ce1972 : 00000000`00000000 00000000`00000000 ffffb606`9a6d82a0 ffffb606`9ad4d998 : nt!ObfDereferenceObjectWithTag+0xc6
fffffd0d`df8a0b50 fffff802`78c414d5 : ffffb606`9abdc040 ffffb606`9a6d82a0 ffffb606`9a6d8200 fffff806`ed2f4150 : nt!PspReaper+0x72
fffffd0d`df8a0b80 fffff802`78d1cb87 : ffffb606`9abdc040 00000000`00000080 ffffb606`9a6fe440 ffffb606`9abdc040 : nt!ExpWorkerThread+0xf5
fffffd0d`df8a0c10 fffff802`78d82be6 : fffff802`77bf0180 ffffb606`9abdc040 fffff802`78d1cb40 00000000`00000000 : nt!PspSystemThreadStartup+0x47
fffffd0d`df8a0c60 00000000`00000000 : fffffd0d`df8a1000 fffffd0d`df89b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiDereferenceIoPages+ccea8
fffff802`78dc7954 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiDereferenceIoPages+ccea8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5a7e7659

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x1a_61948_nt!MiDereferenceIoPages+ccea8

BUCKET_ID: X64_0x1a_61948_nt!MiDereferenceIoPages+ccea8

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

 

[ragnar-gd]

Start with using only one 8GB RAM-stick at a time. It is not optimum, but except for some very modern games that demand much memory, it shoud at least run.
Watch for a few days with each stick. If one of your RAM-sticks is damaged, you'll notice real soon. Then come back and report, and if that didn't help, we'll see what else we can do.

 

[bdrew50]

I will try this i appreciate your answer. One other note is that i ran a Windows Memory Diagnostic where it ran a test and that didn't find any problems. Also, not sure if this helps but here is the minidump error message i get when i first start up my computer and it automatically blue screens and restarts (while the other one was a crash while using the computer).

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 16299 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`6a01e000 PsLoadedModuleList = 0xfffff803`6a385110
Debug session time: Thu Feb 22 20:26:33.722 2018 (UTC - 5:00)
System Uptime: 3 days 20:37:18.437
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffdd301713208, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8036a07753f, address which referenced memory

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
fffffdd301713208

CURRENT_IRQL: 2

FAULTING_IP:
nt!RemoveListHeadPte+bb
fffff803`6a07753f 488911 mov qword ptr [rcx],rdx

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: explorer.exe

BAD_PAGES_DETECTED: 80c7

TRAP_FRAME: ffff840920516d00 -- (.trap 0xffff840920516d00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000002602e2641 rbx=0000000000000000 rcx=fffffdd301713208
rdx=78036a3a50000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8036a07753f rsp=ffff840920516e90 rbp=ffff840920516fd0
r8=fffffd8000000000 r9=fffff8036a3a5768 r10=fffffdd10163ac00
r11=2602e26400000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
nt!RemoveListHeadPte+0xbb:
fffff803`6a07753f 488911 mov qword ptr [rcx],rdx ds:fffffdd3`01713208=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8036a1a6529 to fffff8036a193430

STACK_TEXT:
ffff8409`20516bb8 fffff803`6a1a6529 : 00000000`0000000a fffffdd3`01713208 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffff8409`20516bc0 fffff803`6a1a2659 : ffff8409`20516da1 fffff803`6a0ca019 ffff8d8e`9ef7cf00 fffff80e`74536d4d : nt!KiBugCheckDispatch+0x69
ffff8409`20516d00 fffff803`6a07753f : 8d8e9c66`32d004c2 fffffdee`076df6d8 00000000`000027a0 00000000`00000000 : nt!KiPageFault+0x519
ffff8409`20516e90 fffff803`6a077053 : 00000000`00000000 ffff8d8e`9d6587ef 00000000`00001000 ffffffff`ffffffff : nt!RemoveListHeadPte+0xbb
ffff8409`20516ed0 fffff803`6a07675e : ffff8d8e`9bc45ad0 00000000`00000000 ffff8d8e`9bc45ad0 00000000`00000000 : nt!MiObtainSystemCacheView+0x233
ffff8409`205170a0 fffff803`6a07643c : ffff8d8e`98334f78 ffff8d8e`9d2767c0 00000000`00000000 00000000`00000000 : nt!MmMapViewInSystemCache+0xfe
ffff8409`20517210 fffff803`6a06f93f : ffff8d8e`96787c00 ffff8d8e`00000000 ffff8409`00000000 00000000`00000000 : nt!CcGetVacbMiss+0xdc
ffff8409`205172a0 fffff803`6a51a499 : 00000000`00000000 fffff803`00000000 ffff8409`205173e0 ffff8409`205173f0 : nt!CcGetVirtualAddress+0x2df
ffff8409`20517340 fffff803`6a06f04c : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8d8e`9976a101 : nt!CcMapAndCopyFromCache+0x79
ffff8409`205173e0 fffff80e`991c25ee : ffffdc0e`00000000 ffffdc0e`00000000 ffff8d8e`0000040c ffffdc0e`00000000 : nt!CcCopyReadEx+0x12c
ffff8409`20517470 fffff80e`991c4dff : 00000000`0000040c ffff8409`20517710 ffffdc0e`e2332150 ffffdc0e`e23321a8 : NTFS!NtfsCachedRead+0x182
ffff8409`205174e0 fffff80e`991c29b8 : ffff8d8e`988fc3c8 ffff8d8e`98e4b010 00000000`0000001c ffffdc0e`e2332150 : NTFS!NtfsCommonRead+0x224f
ffff8409`205176e0 fffff803`6a052669 : ffff8d8e`9cf85c00 ffff8d8e`98e4b010 00000000`00000000 ffff8d8e`98e4b3b0 : NTFS!NtfsFsdRead+0x1d8
ffff8409`205177a0 fffff80e`98818773 : ffff8d8e`98e4b010 ffff8409`20517880 ffff8d8e`9d51a540 00000000`00000000 : nt!IofCallDriver+0x59
ffff8409`205177e0 fffff80e`98816db6 : ffff8409`20517870 00000000`00000000 ffff8409`20517801 ffff8409`20517880 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x1a3
ffff8409`20517850 fffff803`6a052669 : ffff8d8e`98e4b010 fffff803`6a516760 00000000`00000000 00000000`00000000 : FLTMGR!FltpDispatch+0xb6
ffff8409`205178b0 fffff803`6a4f621e : 00000000`00000000 ffff8d8e`9d6587e0 ffff8d8e`98e4b3f8 00000000`00000004 : nt!IofCallDriver+0x59
ffff8409`205178f0 fffff803`6a4f6c1a : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8409`20517b80 : nt!IopSynchronousServiceTail+0x19e
ffff8409`205179a0 fffff803`6a1a6003 : ffff8409`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x68a
ffff8409`20517a90 00007ffb`36d6ff44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0994d258 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffb`36d6ff44


STACK_COMMAND: kb

SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: PAGE_NOT_ZERO

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

*** Memory manager detected 32967 instance(s) of page corruption, target is likely to have memory corruption.

 

[ragnar-gd]

Unfortunately, people that can read crash-dumps are rare, and it is very time-consuming. But:

>> *** Memory manager detected 32967 instance(s) of page corruption, target is likely to have memory corruption.

...hints in that very direction, bad RAM.
BUT it could also be an error on the MoBo, but i'd start with testing the RAM-sticks.
Overclocking, or the MoBo applying the RAM-timings in an inappropriate manner, was also a common cause in former times - it's just that your board is so new i'd not start with that.