i had to pronounce some ddr5 dead this morning. at least it was ‘only’ one 8gb stick, but it’s in an omen prebuilt, out of warranty.
user’s just a high school kid. gonna have to limp along with the remaining 8gb (not much for gaming then) or random crashes with 16gb until he or the parents can afford to replace it.
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 had to pronounce some ddr5 dead this morning. at least it was ‘only’ one 8gb stick, but it’s in an omen prebuilt, out of warranty.
user’s just a high school kid. gonna have to limp along with the remaining 8gb (not much for gaming then) or random crashes with 16gb until he or the parents can afford to replace it.
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.