Computer freezes when playing some games on Steam

Are you using steam-native or steam-runtime? Please try using the other.

Have you ruled out hardware. Maybe a hardware issue try another GPU if you have another hanging around or install windows and if it still freezes itā€™s hardware. Try reseating the GPU connections.

I tried both with the same result

My computer is two years old. And for first year and half I used Manjaro. Everything was working nice, without any crash. It all started after installing EndeavourOS on the November last year. Then I installed Cachyos cca 4 week ago and problems are the same.

Sorry, get a new SDD for CachyOS and need to reinstall itā€¦
But back to Steam, did you try to enable the ā€œSteam Beta Client Versionā€ its under ā€œSteam/Settings/Interfaceā€

Good morning, today I tried to test Witcher 3 from GOG, I installed/launched it with Heroic game launcher and guess what? After about 20 second my computer freezed. So the problem is definitely not in Steam.

you have witcher3 on gog and on steam? or did you use heroic and the insidebuild steam option of heroic

-b 0 is for the current boot, if you run this after the reboot from freeze, we wonā€™t see the journal with the problem.
You need to run -b 1 to get the previous boot.

Also make sure that the system is actually locked not just a display stack crash.

Thereā€™s two ways to check afaik. Switch to tty with ctrl+alt+f3 or f4+. This might not work sometimes, you need to also try to login with ssh.

Iā€™m suggesting this because with journalctl -f you can see in real time the journal messages. You can do this from a smartphone too if you donā€™t have another pc available. Ssh is better because you can watch on a second screen and scroll back in the terminal. Real time messages helped me a few times to track down issues.

I have Witcher 3 both on Steam and GOG, because I did not know Heroic game launcher and with Lutris I was never able to run it. This is tha case that I own some GOG games also on Steam. So yesterday I run the GOG version of Witcher 3. With the same freezing result.

Hello mihalycsaba, I overlooked your previous post about how to properly view my previous boot journal. So I will switch to tty on new boot and then I will run journalctl -b 1 | paste-cachyos

So today I tried Witcher 3 on Steam runtime, this time I lowered details to middle quality (instead of very high) and after 20 second my computer crashed. So here is output of my journal (this time made from tty and with the right parameter -b 1):

I think you misunderstood me. -b 1 is for when you reboot after crash. Did you manage to switch to tty when it crashed? If yes you need to run -b 0, because youā€™re still in the crashed boot.

So I still donā€™t know if you sent the correct journal. Only run -b 1 if you reboot after crash. You can check the timestamps to make sure you got the correct journal.

Itā€™s not necessary to run it from tty, I just mentioned tty and ssh so you can see in real time with journalctl -f, this way it would be easier to identify which one is the crash message.

Anyway the log you posted doesnā€™t have much, just this kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. I donā€™t know if this is because of the crash. But I googled it and found https://bbs.archlinux.org/viewtopic.php?id=295937 and https://bbs.archlinux.org/viewtopic.php?id=299868 maybe try the nomodeset or the fbdev thing. Iā€™m still not sure if this error message is because of the crash.

I donā€™t know much about nvidia. If nomodeset and the fbdev fails and you posted the correct journal, I can only suggest for you to try gnome or kde x11. I also know there are different drivers for nvidia, but I donā€™t know how you can switch. Maybe check the https://wiki.cachyos.org/

Thank you for your replay mihalycsaba. I have to turn off/on my computer after every game freeze, so the journal I sent was with -b 1, for the boot when the crash occured. I will check both links you provided. Thanks once gain.

Also try to search this forum, I saw some threads where changing the nvidia driver solved the issues.