Could it be oom-killer? If your system runs out of ram it will inexplicably kill the largest user of ram, like your game.
Running dmesg in terminal right after a crash could tell you.
this post was submitted on 01 Dec 2025
35 points (100.0% liked)
Linux Gaming
22296 readers
223 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
No memes/shitposts/low-effort posts, please.
Resources
WWW:
- Linux Gaming wiki
- Gaming on Linux
- ProtonDB
- Lutris
- PCGamingWiki
- LibreGameWiki
- Boiling Steam
- Phoronix
- Linux VR Adventures
Discord:
IRC:
Matrix:
Telegram:
founded 2 years ago
MODERATORS
Have you tried switching to an older proton version? That fixed it for me (different game, same issue)
I've seen odd behaviour occasionally on proton. I would usually set the proton version manually starting with experimental and working backwards until I get a version that works
If it just started out of nowhere, and you haven't updated recently, then check your heat, power and memory.
If you've updated recently, check and see what got updated and go back to the previous versions.
I'm fairly new to Linux / Bazzite so I have limited advice, but if it used to work you could try rolling back to a prior version and see if that helps. Bit of a band aid solution but you will know if an update to Bazzite caused the issues or not.
https://docs.bazzite.gg/Installing_and_Managing_Software/Updates_Rollbacks_and_Rebasing/
worth a shot!
Before that you can also just try an older version of proton. You might be on latest / experimental and it updated.
Maybe do a memtest to see if your ram is ok.
More info: MemTest86 is the standard. Put that on a flash drive, boot into it, and run it overnight. It needs to complete a full pass, which takes 4+ hours. A single failure or two is OK, any more is not.
If we are testing hardware, I would also suggest a CPU test with Prime95 an a GPU test with Furmark. Both of these tests are faster than the memory test, and you can always do them from a live linux environment if you want to remove your current installed OS as a factor.
Prime95 using the memory testing option might be sufficient to test RAM stability, too. When I was doing manual RAM overclocking, 30min was enough for a safe pass, but my errors typically appeared within 15min or less.
In case you're dual booting - Windows also has a memory diagnostic tool. This did identify my RAM as broken almost immediately, while Memtest reported everything OK after a full scan of several hours. As I only knew Memtest back then it took me weeks to find why my PC was constantly randomly crashing, until I learned of that.
But that was about 2 years ago, so maybe Memtest did improve since then? (Or maybe I had some very weird behaving RAM and finding it with other tools was just pure luck...)