Question Memory intensive games are crashing, tried literally anything I can Google

[clyspe]

CPU i7-8700k
GPU Asus Rog Strix gtx 1080 ti
Mobo Asus Rog Strix z370-h
RAM G Skill F4-3400C16-8GSXW
Monitor 1440p G Sync 165Hz

When I play games that are very demanding, the game will close without an error, until I go to event viewer where I get this:
Faulting application name: MonsterHunterWorld.exe, version: 0.0.0.0, time stamp: 0x5e463c73
Faulting module name: MonsterHunterWorld.exe, version: 0.0.0.0, time stamp: 0x5e463c73
Exception code: 0xc0000005
Fault offset: 0x000000001e31d40b
Faulting process id: 0xa0c
Faulting application start time: 0x01d5f7155f040d06
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe
Report Id: 63d0c3a4-57c6-4c94-918f-6ed235e5fbb2
Faulting package full name:
Faulting package-relative application ID:

Any help you can give me would be greatly appreciated, I've tried everything I can troubleshoot myself and nothing is even helping. Things I've tried:

tdrdelay set to 5, 10, 60
fresh install of windows, wiping old install
Taking out half the RAM (I thought I remembered a problem with this cpu running ram dual channel)
reducing the resolution and capping the framerate

I still intermittently crash. The reason I'm posting it here is I'm pretty sure the problem is with my RAM, but I'm not sure. My computer with all 4 sticks (32GB) passed memtest64 in about 6 hours.

 

[cherry blossoms]

Was the memory bought as a single kit, or seperately? Lot to lot variations in components may make things unstable if not bought as a 4x8 kit.

Overclocking at all? Drop to stock clocks.

Drop memory clocks down to standard frequency, not the XMP frequency

A 2x memory configuration is easier on the memory controller than a 4x configuration.

Your motherboard manufacturer does not list your memory on their QVL. It may work fine, it may have been tested and failed. No way to tell.

 

[drivinfast247]

Latest BIOS?

 

[clyspe]

The memory was bought separately as 2 16 gig packages.

I am not overclocked as far as I can tell

I have removed two of the memory sticks, and the crash is still happening.

I am on latest bios

 

[drivinfast247]

RAM is only guaranteed to work together when bought as a kit.

 

[Deleted member 14196]

Try it with just the two new RAM sticks

 

[clyspe]

OK, I've run them as 4 sticks for like a year and a half and it has just started doing this, so it'll take a little trial and error to find out which two were shipped together, is there a more efficient way to crash my computer other than playing a game for like thirty minutes and seeing if there's an error? The only two programs that are currently crashing are Monster Hunter World and For The King.

 

[Deleted member 14196]

They’ve been running fine for a year and a half then that’s not the issue it’s probably your windows is messed up. It would be nice if you could back up all your data and do a clean windows 10 install by formatting all your drives and letting the windows installer install windows fresh

 

[clyspe]

I have already done a fresh install on windows, my other drives are still plugged in with old data, but windows and all my applications are installed on the cleanly installed drive.

 

[Deleted member 14196]

Take a look at your reliability history and even the event viewer and see if it can shed any light on what’s happening when crashes occur

Also I would test each ram stick individually using memtest86

 

[clyspe]

I have the event viewer in the OP, here is reliability history for the most recent crash

Description
Faulting Application Path: C:\Program Files (x86)\Steam\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: MonsterHunterWorld.exe
Application Version: 0.0.0.0
Application Timestamp: 5e463c73
Fault Module Name: MonsterHunterWorld.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 5e463c73
Exception Code: c0000005
Exception Offset: 000000001e31d40b
OS Version: 10.0.18363.2.0.0.768.101
Locale ID: 1033
Additional Information 1: 29c3
Additional Information 2: 29c39ec9d6ea7a79ce4cf9fc5e8a2633
Additional Information 3: 75d4
Additional Information 4: 75d4701a0e8b012ae13af629b6ce79c1

Extra information about the problem
Bucket ID: c6b5c295f497cfc574cc2d6f6b39e3c4 (1498622732571108292)

 

[Deleted member 14196]

Look up that exception code for that game and see what that tells you

 

[PEnnn]

0xc0000005: if one were to Google it, it seems to be a blackhole with tons of suggestions!
But if it's really RAM then MS suggests the following (I am copying and pasting from their KB):

"However Win OS have a simple solution & memory setting,simply R.click my computer/properties/advanced/virtual memory/advanced/change button.With C: highlited,set to "Let system manage" click set 2X,close,restart pc.This being ram memory is ok & at default...."

This links offers suggestions that include: Registry, Virus, RAM, Printer Drivers, DEP, video drivers, ...!!
How to Fix 0xC0000005 Error

PS: If this fails, any chance the PSU is acting up??

 

[clyspe]

I don't understand why it could be the registry, since this is a fresh install. I have tried every combination of RAM sticks that I got and it is still throwing up this error.

Same error from For The King
Faulting application name: FTK.exe, version: 2017.2.2.48228, time stamp: 0x5aafbc52
Faulting module name: UnityPlayer.dll, version: 2017.2.2.48228, time stamp: 0x5aafbf0b
Exception code: 0xc0000005
Fault offset: 0x00000000002fb500
Faulting process id: 0xaa4
Faulting application start time: 0x01d5f75b2ccdbe0f
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\For The King\FTK.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\For The King\UnityPlayer.dll
Report Id: 67e39e63-5444-4a0f-a72e-14896fffc9ef
Faulting package full name:
Faulting package-relative application ID:

It seems to me only games using the unreal engine are having this problem. I am on the latest nvidia drivers fresh installed off of those, this problem came up about two months ago, maybe a change in their driver has sparked this? Kinda at my wits end here.