Failing RAM? In this economy?
Now to go beg to the RMA gods
this post was submitted on 25 Jun 2026
335 points (97.5% liked)
PC Master Race
21516 readers
931 users here now
A community for PC Master Race.
Rules:
- No bigotry: Including racism, sexism, homophobia, transphobia, or xenophobia. Code of Conduct.
- Be respectful. Everyone should feel welcome here.
- No NSFW content.
- No Ads / Spamming.
- Be thoughtful and helpful: especially when new beginners have questions.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Linux? I've heard if you can identify the bad blocks (assuming it's just one group of bad blocks) you can tell the kernel to not use those. If you're technically inclined.
I ran this too on mine, I had the mode set to memmap. Badram is old, grub these days expects memmap.
There were a few areas but they were close enough, so this is what I ended with.
Blocks of 64K were enough to fix this.
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash memmap=64K\\\$0x3c8f0000,64K\\\$0x49068000,96K\\\$0xa24660000"he has windows, but i'll mention the option to him next chance i get.
There is a option for Windows: https://www.memtest86.com/blacklist-ram-badram-badmemorylist.html#badmemorylist
Although it seems like it may be broken.