Sudden crashes related to CPU undervolting

nashradical

New member
Having some really weird crashes lately. I've had my CPU (Ryzen 7700x) undervolted through PBO2 at negative 20 for a few months now, and have literally never had a crash with deadlock or any other game (in fact my PC has never even blue screened before this)

As of yesterday, my game is guaranteed to crash within 5 minutes of being in a match. Only happens in matches in the actual map, not in the hero testing. Most crashes the game just suddenly closes with no errors. A few times, there's been a small error popup saying "unrec steam cmd" with a bunch of random numbers after - different each time. There have been a few times where my PC just shuts off and starts rebooting.

I don't have this issue with any other games, including other Source 2 games like CS2.

If I reduce my undervolt to negative 15 (from negative 20), the crashes completely stop. But I've tested my undervolt with so many programs, I've used CoreCycler, I've used cinebench, everything you can think of. Absolutely no crashes or errors or weird quirks I've noticed, and nothing else on my PC crashes. I also haven't had Deadlock crash from this undervolt since yesterday.

I can post a dump file from the crash if necessary, but I'm not sure if that is safe to post on a public forum.

EDIT: It may be worth mentioning that I am running my ram with EXP0 at 6000 MT/s. I've been doing this for probably a year now with no issue, but running !analyze -v on the dump file seems to throw the error ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
 
Last edited:
Test your OC with OCCT, it's really good at coaxing errors,
I usually get PBO undervolt errors in ~2 minutes, but if I run OCCT for an hour it always comes up with an error if it's unstable.

Also when you are testing CPU undervolt, you should be playing all your games in 720p or lower with minimum settings,
to allow maximum stress on the CPU. That's why in some games you get errors, some don't.
Deadlock is a very cpu hungry game, especially in big fights. Just a edge case of over clock instability
 
Back
Top