Imho not worth the risk. Nothing except ECC is protecting system from memory corruption. And consequences of flipped bit can be huge. Unless it is in a system you do not care about, just do not use it.
this post was submitted on 06 Jan 2026
43 points (93.9% liked)
Selfhosted
54761 readers
396 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Very cool to be able to do that even though I'm not sure it's worth it to run a RAM module that has a known defect.
If the fault spreads there will be corruption again.
There is one part in the post mentioning how to "pad holes" in failing areas. Maybe I should expand it with some details around aligning reserved address space.
Otherwise, corruption of the RAM itself does not usually spread like mold in bread or wear out and fail in similar ways to flash memory.
By spreading I meant thar if there is an underlying manufacturing defect it would be really difficult to predict where and when it would happen on memory. And if there is already a fault detected more might come later.
But I'm glad you documented how to do these types of workaround. It might be helpful with memory prices skyrocketing...
I tried this for a bit last year, and I never got it to work. I'm sure it was user error, but I'm super glad I got a new kit before shit blew up.
Might have to track down the bad kit I had and give this another try for giggles.
First rule in computer building is to always buy twice as much RAM as you actually need so you can just remove the bad stick when this happens
Second rule of computer building is just keep the receipt until after it passes 40 minutes of memtest. Third rule is to ignore rule one, nobody does that.
I always heard the first rule as "stay grounded". Having 1TB of RAM on stock just in case sounds not grounded.
A spare kit or two should be enough for most folks. With one or two spares of everything else so you can test suspicious parts separate from prod.
A bit of redundancy and foresight is good but no need to be excessive about it.
Needing 1TB of RAM is far outside the standard case.
Well he technically only need 512 gigs but had to double it because some dude on the internet said so.
OK, so let's cut it down and say we have 4 PCs for someone with a family and home server, with 4 DIMMs each.
You are saying the first rule of PC building says that this house should have at least 16 unused DIMMs on the shelf. I'd say 2-4 is reasonable if they are all compatible.
"Buy two extra of everything" is a good rule and scales for the individual. "Buy double of everything" is not.