Can't play a single match without a system crash

[Blackshot]

Problem:
In a matter of 10 to about 40 minutes (depending on if I'm in a match or just in sandbox), my PC freezes and reboots on its own when playing Deadlock.

I play many different games. A Unity game (7 days to die), a few Unreal Engine 5 games (Tekken 8, The Finals come to mind), Hunt Showdown, Overwatch 2, Quake Champions and I've played CS2 and Dota 2 before just fine but I don't crash in any of these games. I used to crash in 7 Days to Die when hosting a server until I upgraded my RAM, I've crashed once in Silent Hill 2 before (launch version, haven't touched the game since) and recently once in Marvel Rivals (after having played 10 hours at launch with no problems besides low FPS).

I've looked up what other people have tried to fix the same issue and tried possible solutions such as:
- Verifying game files
- Reinstalling GPU drivers (using DDU)
- Using vulkan instead of dx11
- Running project8.exe in compatibility mode (as Windows 8)
- Limiting power consumption to 90% through system control settings
- Underclocking my GPU by 50 mhz
- Disabling AMD Precision Boost Overdrive (PBO)
but none have worked out for me.

My settings are:
AMD Anti-Lag 2.0 Enabled. Upscaling on FSR (Rendering at 85%). Everything on high except shadows on mid. Effects turned on, Vsync off and MBOIT off (tried it on too). Playing at 1080 native resolution with fullscreen focus locked at 144 FPS.

I'm running an AMD setup using Ryzen 5 5600 and an RX 6650 XT with 32 GB of DDR4 RAM. I've stress tested using OCCT (and a few other tools) before for an hour with no issues.

Pretty sure my old PC was able to run this game without crashes albeit at a low FPS. That PC had an Intel i7-6700, a GTX 980 and 16 GB of DDR4 RAM on Windows 10.

 

[Firebeard]

This is weird but I had consistent BSODs multiple times per match until I removed Corsair iCUE. Maybe disable or remove any RGB control software you may have and see if that fixes the issue. Switching to OpenRGB fixed the crashing for me. Maybe that could be it for you too. Also have a look at your windows reliability monitor to get an idea of what .exe windows thinks is causing the crashes.

 

[Disgruntled]

I can play one or two matches, then when I get back to the menu the whole system locks up and I have to manually shut it off. Windows won't keep any relevant records, so I can't find out what's causing this.

It's happening in DOTA2 as well. Something's really messed up.

 

[Blackshot]

I've finally done a memory test using Memtest86 and found several errors in test 8. Since I was sure my RAM sticks were seated in properly I went into my BIOS in the hopes of fixing it by reducing the DRAM frequency. Went from Auto (said it was at something above 3700 Mhz) to 3600 Mhz (I've never touched this setting before).

Did another Memtest after that doing 3 passes of test 8 with no errors. I then played a whole bot match without crashing. I'll update you if or when I crash again.

 

[Disgruntled]

I've finally done a memory test using Memtest86 and found several errors in test 8. Since I was sure my RAM sticks were seated in properly I went into my BIOS in the hopes of fixing it by reducing the DRAM frequency. Went from Auto (said it was at something above 3700 Mhz) to 3600 Mhz (I've never touched this setting before).

Did another Memtest after that doing 3 passes of test 8 with no errors. I then played a whole bot match without crashing. I'll update you if or when I crash again.

Fuuuuuuck I hope my memory isn't messed up.

 

[Blackshot]

I've finally done a memory test using Memtest86 and found several errors in test 8. Since I was sure my RAM sticks were seated in properly I went into my BIOS in the hopes of fixing it by reducing the DRAM frequency. Went from Auto (said it was at something above 3700 Mhz) to 3600 Mhz (I've never touched this setting before).

Did another Memtest after that doing 3 passes of test 8 with no errors. I then played a whole bot match without crashing. I'll update you if or when I crash again.

I was able to play several matches after this (on different sessions) without crashing. Recently, a Deadlock and Windows update later (not like I think that has to do with it), I've begun crashing again.

So I did the Memtest86 again, all of a sudden I got errors in it. Decided to take out my previous duo of ram sticks and only left in my new pair (so I'm back at 16 GB), of course seated them in the optimal slots, checked the settings, did a test, had no errors and tried to play again. Think I was able to play a match. The other day then, I started crashing again just playing in sandbox for a while (maybe 25 minutes). Tested again, all of a sudden got errors again. Only thing I can say is that I had played a Unity game like 2-3 hours before that which I find worth mentioning cause Unity games are like the only ones that make my computer loud and run the temperatures noticeably higher (still in a perfectly fine range, mind you).
Later did another complete Memtest, had no errors, sat in sandbox making a build for about 25 minutes and then played a bot match which had me crashing about 15-20 minutes in.

I only took care of the dust inside and especially on the computer. Afterwards I tried testing CPU + Memory with OCCT again for 45 minutes using Large Dataset, Extreme Mode and Load Type on Steady cause I wanted to see if it could be temperature related. No errors and also, the computer was still really cold somehow (I do have a non-stock CPU cooler which seems to be doing a killer job generally speaking). To be extra sure I restarted my computer and did another shallow Memtest with no errors.
Tried playing an actual online match and crashed after 15 minutes or so. I did notice that the PC blows out hot air when I check what's up right after a crash. But that's probably just standard temperature for any game. It's again not the CPU or GPU that are particularly hot, just practically anything on the motherboard (not the RAM though, not like RAM is meant to overheat anyway).

The only other game that seems to be causing me trouble is Marvel Rivals with its huge frame drops that happen like once or twice a match for a couple seconds. And Rainbow Six Siege has frequent micro stutters whenever its loading something new (like an Operator on the main menu or while playing the game), but that's a common complaint when the game is run with dx 12 instead of 11 (which works fine for me).

I've gone on to mention a couple rather redundant things cause I'm just clueless on what to do anymore. Perhaps I'll try playing CS2 on max settings in order to find out if this has anything to do with Source 2 in general. But I've played my fair share of CS2 on this PC just fine, I don't think that'll reap any results.
What I'll actually attempt is underclocking my RAM (even further), or maybe up the voltage on it, which is pretty annoying to do for like a singular game but we're playtesters aren't we.

Edit: Worth mentioning perhaps: When I reconnect after a crash, there's a high chance the game won't work properly before inevitably crashing withing minutes if not seconds. The animations don't play when shooting or sometimes when dashing. I guess the game doesn't load well before it lets me play again. Don't know why or how that's possible when I obviously restarted the computer before starting the game again.

 

[Blackshot]

I've changed my RAM frequency from 3600 to 3200 which allowed me to play for close to an hour yesterday (played almost 2 whole bot matches, quit early after the second one cause I got bored). So today I thought I'd be able to play a game but nope, crashed during the laning stage.

Suppose that'll be the last of me for a while until this issue gets fixed. I'll play the dozens of other games that actually do work like a charm. I'm at my limit