How to test and safely keep using your janky RAM without compromising stability using memtest86+ and the memmap kernel param.
You must log in or register to comment.
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.
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.
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…
