Easy Anti-Cheat

Did you make an exlcusion to anit-cheat or one of its parts?

@GaryHost4184 This is certainly a curious issue. I would start by disabling XMP/DOCP on your memory. Since these anti-cheat software often scan what is currently running within system memory, it's possible that it's flipping a bit it shouldn't be and is crashing the system. Often times you'd get a BSOD with this, which is why I find it odd that your particular crashing isn't doing so, but it's worth a shot anyways.

The ram you've chosen is 3600 C16 dual-rank DIMM's which can be quite difficult for AMD's memory controller to handle outright without some manual tweaking unless you have a solid motherboard memory topology and CPU memory controller. Memory on the edge of stability can do odd things sometimes, so this will help determine if this is indeed the cause of the crashing or if something else is at fault here. I know you've already performed a memory check, but those often determine if the DIMM's themselves are functional, and do very little to confirm if the CPU's memory controller agrees with the timing parameters trained by the board.

No worries, I made the assumption that you had one loaded based on the speed of the memory you purchased. Do you recall entering your BIOS at all to adjust the memory speed? Easiest way to tell would be to check Task Manager for the reported memory speed:

My speed being listed at 1200 is actually running at 2400. With DDR (Double Data Rate), your effective clock is double your "real" clock. So my effective memory clock speed would be 2400Mhz.

If you can get me a screenshot of this page, we can confirm if your XMP/DOCP profile is loaded or not.

Yours actually looks normal. Mine is still showing "real clock" instead of effective clock because my version of Windows 10 is fairly outdated. Yours operating at 2133 means you do not have XMP/DOCP loaded, which rules out my original theory about this being related to the speed/timing combination of your memory relative to EAC's poking around in memory.

I am finding it less likely that the software itself would trigger a kernel power error instead of a crash dump BSOD, it just doesn't seem all that possible to me. We might be overlooking something else here.

Do you have any means of monitoring CPU temperatures while gaming? The GPU temperature in your Task Manager screenshot looks normal, but I am curious about your CPU temps. I see from your purchase history that a Kraken M22 was purchased and is likely being used in this build, but I want to make sure that the pump is working properly and that the CPU thermals are not at fault for the system shutting down here. Depending on the game you are playing, some may be more or less CPU demanding than others, and it may present itself as an issue with games using EAC when in fact it's games that are more CPU bound, not GPU bound.

If you need tools to monitor CPU temperatures, my preferred software would be HWInfo64 as it allows you to monitor nearly every system sensor available. You can launch it in a "Sensors Only" mode, and look for your CPU temperatures here:

My sensors may look different as I am using a 2200G APU while you are using a newer 5000 series CPU. Still, look for those CPU temperature sensors and see if you can provide a screenshot with one of your games running in the background (preferably a game that won't immediately crash you).

Looks like you are exacting them correctly. Remember that you need to have the flash drive formatted to FAT32 on ASRock boards in order for the flash drive to be recognized by their Instant Flash utility. Once you have a FAT32 flash drive with the BIOS file on the drive, the instant flash utility should see it and handle the rest for you automatically.

Again, I am happy to walk you through this if you need a hand.