Question Games Random CTD, CPU issue?

[ssassassa9]

OS: Windows 10 Pro Build 19043
PSU: Corsair RM850x
Motherboard: Gigabyte X570UD
CPU: R5 3600, Coolermaster Hyper 212x
GPU :Gigabyte RTX 2080 Super Gaming OC
RAM: Corsair Vengeance Black C16 3200Mhz 2 x 8GB

Hey guys, I've been experiencing random crashes to desktop while gaming in the last month. Crashes seem to be completely random and happens across all games that I've recently played, namely Prey, Dota 2 and The Outer Worlds. There does not seem to be a pattern to the crashes, sometimes it happens within the first 10-20 minutes of gaming, sometimes its hours before it happens.

I've tried the following to no avail:

1. Made sure CPU and GPU at default clocks
2. Updated latest drivers, including clean installs using DDU.
3. Tried different versions of Nvidia drivers
4. Clean Windows install
5. Replaced PSU, the previous PSU, an EVGA GD 700W had been an intermittently clicking noise since the first day that I've built the PC, there was no improvement with a new PSU despite albeit the clicking noise is gone now.

Managed to capture these events on event viewer when it crash while I was playing The Outer Worlds:

Information 2:13:28AM
Fault bucket 1164186027309905295, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: PrivateDivision.TheOuterWorldsWindows10_1.5.696.0_x64__hv3d7yfbgr2rp
P2: praid:App
P3: 0.0.0.0
P4: 00000000
P5: nvwgf2umx.dll
P6: 30.0.14.7111
P7: 60d011a8
P8: c0000005
P9: 00000000007c4c75
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF4E9.tmp.WERInternalMetadata.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_PrivateDivision._dc6983b3ea4346d6c8049681d21458b85b95e_bd4cc000_3fdcf069-a9dd-48b4-827c-81637866e112

Analysis symbol:
Rechecking for solution: 0
Report Id: 2bc088d8-5f66-4f7c-b694-5cc3bc78e40e
Report Status: 268435456
Hashed bucket: b83244f086225b44902805061247b58f
Cab Guid: 0

Information 2:13:26AM
Fault bucket , type 0
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: PrivateDivision.TheOuterWorldsWindows10_1.5.696.0_x64__hv3d7yfbgr2rp
P2: praid:App
P3: 0.0.0.0
P4: 00000000
P5: nvwgf2umx.dll
P6: 30.0.14.7111
P7: 60d011a8
P8: c0000005
P9: 00000000007c4c75
P10:

Attached files:

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_PrivateDivision._dc6983b3ea4346d6c8049681d21458b85b95e_bd4cc000_3fdcf069-a9dd-48b4-827c-81637866e112

Analysis symbol:
Rechecking for solution: 0
Report Id: 2bc088d8-5f66-4f7c-b694-5cc3bc78e40e
Report Status: 4
Hashed bucket:
Cab Guid: 0

Error 2:13:26AM
Faulting application name: IndianaWindowsStore-Win64-Shipping.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: nvwgf2umx.dll, version: 30.0.14.7111, time stamp: 0x60d011a8
Exception code: 0xc0000005
Fault offset: 0x00000000007c4c75
Faulting process id: 0x950
Faulting application start time: 0x01d76d0bbbc4d841
Faulting application path: C:\Program Files\WindowsApps\PrivateDivision.TheOuterWorldsWindows10_1.5.696.0_x64__hv3d7yfbgr2rp\Indiana\Binaries\Win64\IndianaWindowsStore-Win64-Shipping.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_4a746d937e6a7240\nvwgf2umx.dll
Report Id: 2bc088d8-5f66-4f7c-b694-5cc3bc78e40e
Faulting package full name: PrivateDivision.TheOuterWorldsWindows10_1.5.696.0_x64__hv3d7yfbgr2rp
Faulting package-relative application ID: App

Diagnostics:

1. Ran memtest overnight, nil issues
2. Unigine Heaven ran for hours with nil issues
3. Prime95 churning out FATAL ERRORs within minutes:

[Wed Jun 30 02:45:29 2021]
FATAL ERROR: Rounding was 0.4991048235, expected less than 0.4
Hardware failure detected running 480K FFT size, consult stress.txt file.
FATAL ERROR: Rounding was 0.4999217036, expected less than 0.4
Hardware failure detected running 480K FFT size, consult stress.txt file.
FATAL ERROR: Rounding was 0.4999954691, expected less than 0.4
Hardware failure detected running 480K FFT size, consult stress.txt file.
FATAL ERROR: Rounding was 0.4973672945, expected less than 0.4
Hardware failure detected running 480K FFT size, consult stress.txt file.
FATAL ERROR: Rounding was 0.4996067201, expected less than 0.4
Hardware failure detected running 480K FFT size, consult stress.txt file.
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!
Self-test 480K passed!

Wondering if I have enough evidence to suggest that is solely an issue with the CPU as I do not have hardware sitting around to swap components to confirm if its definitely an issue with the CPU. Suggestions from the community is much appreciated.

Thanks!

 

[RodroX]

Download some hardware monitor software, Ryzen Master, hwinfo 64 portable ("sensors only" option), whatever you want, and take a close look at the CPU temp, on idle and while on load.


- Did you build the system yourself?

- How old is it?

- Did you moved it from another location lately?

- Do you know how to check if the CM Hyper 212 is well mounted?

 

[ssassassa9]

Download some hardware monitor software, Ryzen Master, hwinfo 64 portable ("sensors only" option), whatever you want, and take a close look at the CPU temp, on idle and while on load.


- Did you build the system yourself?

- How old is it?

- Did you moved it from another location lately?

- Do you know how to check if the CM Hyper 212 is well mounted?

- Did you build the system yourself?
Yes

- How old is it?
Around 15 months old

- Did you moved it from another location lately?
Nope, haven't moved since building it.

- Do you know how to checpak if the CM Hyper 212 is well mounted?
While on Load, CPU max temp of 81.8 degrees, I don't have a record of previous tests when I first build it but I think temps has been consistent. Temps also quite rapidly drop on cessation of load.