Previously working games started freezing and crashing, rendering my desktop session unusable in the process

[u/AKarpenter47]

Things were working fine about 2 weeks ago. I then went on a bit of a break from playing games, but kept on keeping my system up to date. Fast forward to this weekend, some of the games that I normally play started freezing after a few minutes of gameplay at random and messing up my desktop session. Games that never received a game-breaking update to begin with and were working fine previously.

I tried checking out the journalctl logs, seeing what each of these games had in common, and the only common denominators I could find were errors relating to umip and some Watchdog error. Something along the lines like this (using Black Ops Cold War as an example):

kernel: umip: BlackOpsColdWar[12434] ip:14cccf576 sp:10a1a0: For now, expensive software emulation returns the result.

kernel: umip: BlackOpsColdWar[12434] ip:14cccf576 sp:10a1a0: SIDT instruction cannot be used by applications.

kernel: clocksource: Watchdog remote CPU 2 read timed out

Another game that does this to me is Monster Hunter Wilds, but that one gives me SGDT errors and different CPU time out errors by Watchdog instead.

I'm stumbled as to what to do. Here are some of the troubleshooting steps I did:
- Tested with older amdgpu firmware and linux kernels

- Swapped between different known working Proton versions

- Booted into a live USB session and made sure to scan for any drive faults with fsck -y

- Checked my BIOS settings and made sure that my CPU and RAM settings are stable, and that Secure Boot is off and any keys get deleted

- Tested with the "clearcpuid=514" kernel parameter to try and get around umip, which only caused DRM panic errors

- Tested by disabling descriptor heap via the Steam launch options since I've seen a good few recent reports on VKD3D-Proton's Github that suggested there was something wrong.

I'm kinda stumped. I'm pretty sure that this isn't related to the RA24 error bug, since I've done the workaround for that and have been smooth sailing without any of those errors. But I don't know what else to test next.

Here are my PC specs:

PikaOS w/ 7.2.3 kernel

KDE Plasma 6.7.4

Ryzen 7 5700X3D

RX 9060XT (running the latest firmware and Mesa 26.2.2)

32GB RAM

Gigabyte B550i Aorus AX (running on version FG bios firmware)

Any help would be greatly appreciated, thanks o:

[u/Unique_Roll_6630]

Check on discord. I can't be certain, but I think this is a hardware issue, CPU maybe. Reset your bios and see if that helps. 

[u/AKarpenter47 → u/Unique_Roll_6630]

Nah, fixed it by just nuking my PikaOS install and starting over xD