this post was submitted on 01 Dec 2025
41 points (100.0% liked)
Linux Gaming
22296 readers
296 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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...)