Now I need to take a loan in order to afford 32gb for replacement thanks to the ai bros hoarding all the chips…
Tried on three different PCs, both Intel and AMD, both sticks are damaged, somehow
Now I need to take a loan in order to afford 32gb for replacement thanks to the ai bros hoarding all the chips…
Tried on three different PCs, both Intel and AMD, both sticks are damaged, somehow
wow i’m running linux, so it might be perfect
though i’m a bit scared that it will get worse over time. Today i got a freeze that forced me to test the ram with memtest86, but since september i got some random corruption in the btrfs filesystem (luckily always “useless” files like flatpak or docker stuff that i could delete and download again in seconds) and i assumed it was a btrfs bug, not hardware problem
If I were in this position I’d strongly consider using 16GB for the next year or two. Especially with an NVME SSD, good swap performance makes the impact of running out of memory much smaller than it used to be.
It’s very strange both sticks failed at the same time, have you tried them in another motherboard?
I had to do this on my busted ddr4 2 weeks ago. Badram didn’t work, but memmap did. I had to do bit flipping to get the translation from BADRAM as explained here.
I think the latest memtest86+ has the option to report in memmap format. But you will need to take a photo of the screen, coz it’s Foss and not as fancy as Passmarks memtest.
Edit: Adding badram to grub broke grub for me, I have to undo the grub config using a live boot rescue thingamajig. Then I went hunting why.
You can even make linux run an automatic memtest on boot and reserve the bad areas it finds. This is with the memtest=N kernel parameter, where N is the number of passes. memtest=17 tests all patterns. With this, the kernel will run an automatic test on every boot.
To add to what the above commenter said: afaik Grub allows specifying kernel parameters at boot by pressing some hotkey. You could type in the string from memtest86 if you find what the parameter should be called (or add the
memtestparameter instead).