Restarting during gameplay or testing benchmarks
Restarting during gameplay or testing benchmarks
Hello, It has been a long time that I'm stuck with this issue and I recently wanted to fix it. While I'm gaming, I sometimes experience a weird pc Crash. My screen goes black, I hear a little pop sound in my headphones, and my pc restarts itself after a few seconds. What's intringuing is that during this crash, my fans are still turning normaly my PC's rgb don't shut down. I recently decided to download Heaven Benchmark and the error occurs on it (My CPU temps are normal, Gpu max temps during the benchmark is 80°C at 100% usage.). I've done a DDU and installed new gpu drivers, nothing changed. At first i thought of a PSU problem, but i bought a new one and it didn't change. I crash a lot on Rocket league, The Forest, FiveM. The weird game that causes me problems is Muck, muck is a game with REALLY low graphics and not a lot of content in it. The fact that I crash on this game but i still have good perfomances on big games like Dayz is weird? My BIOS is on default settings and I never overclocked or undervolted. My PC config: Windows 10 X64 Ryzen 5 3600 ASUS TUF RX 5700 XT 2x8 GB DDR4 2133mHz Corsair Vengeance MOBO: ASUSTeK PRIME X570-P (bios 0807)
A BIOS update has been released—there are now 21 updates since your current version.
Oh yeah my bad, I did the bios update last week but forgot to change the version in my message. Even with the fresh bios, nothing changes. I read in various forums that changing pcie from gen 4 to gen 3 may be a fix, as pcie 4 is pretty instable on amd, but it didn't solve it for me.
I believe RAM might be the issue... Remove one RAM module and see if the problem continues. If it does, try swapping it with the other or upgrade to DDR4-3200, as your CPU supports that speed. If the power supply was the cause, the fans would briefly stop or the PC would shut down completely.
I searched in the BIOS and turned on DOCP in AI Tweaker. My RAM speed was limited and I didn’t see it. After that, my PC passed the survival benchmark, so I think the issue was related to RAM. Thanks for pointing it out—I’ll check again in a few days if it’s fixed, but I’m confident this was the fix.