Failing RAM? In this economy?
Now to go beg to the RMA gods
Fffuuuuuu
Check the used market first
this post was submitted on 25 Jun 2026
254 points (97.0% liked)
PC Master Race
21963 readers
743 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
If it's still under warranty, why wouldn't you try to RMA it first?
If it's still under warranty, why wouldn't you try to RMA it first?
You can try... but several manufacturers are opting to refund you what you paid for the product, instead of replacing it, per their warranty terms. Terms that never were an issue before. And obviously what you paid years ago won't get you anywhere near a similar product now.
But OP would still get something.
worth asking anyway... but if they demand the pair back and only offer a refund, you're losing money over keeping a single stick probably.
Sure? I don't know what RMA stands for lol
Return Merchandise Authorization. Return it to the manufacturer for a replacement
to add...
most ram, purchased new at retail from a legit or 'authorized' merchant or store should be covered by a manufacturers warranty. those sellers on amazon marketplace with random 'kdfguuugggu' names probably not selling warranty-eligible products. you would more than likely need a proof of purchase receipt to show when and from where you purchased the ram.
if it was in a prebuilt or major oem (dell, hp, lenovo, etc) system you're usually at the mercy of the builder and its system warranty. if purchased direct, the seller should have record of the system purchase. if purchased at retail, same deal as above--need the receipt.
if the ram was acquired as used product, you're probably out'a luck.
Warranty claim
Warranty exchange basically
load more comments
(1 replies)
They're very few addresses, you can tell the OS not to use them. Take a look at this: https://www.memtest86.com/blacklist-ram-badram-badmemorylist.html
Dawg you're the GOAT with that link
It didn't even occur to me it could be done, makes sense.
You can edit the grub config (assuming you're using Linux) and add reserved ranges for the affected physical address.
find the linux boot command and add a memmap=$ argument This tells the kernel to avoid the bad parts.
In your case it looks like a relatively small chunk of bad memory so.. memmap=64K$0x130FEF000
I've used this trick to stabilise systems with faulty RAM and it works.
Don’t know what brand you’ve got but I had two 16GB sticks of G.Skill DDR4 go bad a few months back and their RMA process worked a treat.
Wishing you success as well.
GSkill yep. Should be good. I originally built in 2020 with 2x8gb and then in October 2024 I got another 2x8gb because it was only $35USD why not lol
The exact same set is currently $135...
And go figure the new sticks were the ones that failed.
Just to be clear: are you trying to add the new set of two to the existing set? I.e., 4x8GB?
That can sometimes cause problems due to timing variations between batches. Make sure to memtest each stick individually, to make sure that isn't the issue.
Edit: just realized that you implied that this setup has been working since 2024, so you can probably ignore my advice here
load more comments
(2 replies)
Just buy a bunch of NAND gates and make your own registers
Sure, you can do that....if you're a casual. Real PC users build their own NAND gates out of MOSFETs.
Sorry, I can't hear you over the sound of my relays
Relays are for kids and cowards who are too soft to use mercury delay-line memory
Oh, the relays are just a side project that I'm toying with. My daily driver is a hamster-wheel-powered marble-run abacus running floating point arithmetic
load more comments
(2 replies)
I prefer to do the old fashioned way like granny taught me, by weaving my own damn memory.
load more comments
(1 replies)
Remove the sticks, blow out your sockets with some compressed air and re-test. I had something similar recently and a full memtest pass ran clean after that.
Also, disable any OC. I had my ram fail tests because it is not supported by my mobo. After reducing speed to factory stock it would pass flawlessly.
load more comments
(2 replies)
Seems like its always the same core that is creating the error. Could be a bad overclock. Try reseting the bios to default. Also try reseating the RAM (and clean out the slots with compressed air) and rerunning the test. I've had similar issues in the past that were fixed by this.
Once stable overclocks can fail after many years as it slowly wears out some transistors.
f
F
Not good. The pattern is not consistent.
Take the RAM out and carefully clean the contacts with e.g. alcohol and a piece of lint-free cloth.
RAM has lifetime warranties, typically. Send in an RMA request, after you isolate which sticks are bad, and get new ones.
F. Godspeed.
had a 2x8 kit fail as well, thankfully I clocked it down from 3600 to 3200 and it passed the ~2 hour test.
perhaps relax the timings and/or increase voltage?
load more comments
(1 replies)
If it’s not a large amount of bad RAM, there are tools to patch around it via EFI or kernel for many operating systems. It might get you by until you get new
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.
load more comments
(1 replies)
Dude you are running DDR 4 Ram at 2134MHz and with 15 timings. The Timings are good but the frequenzy is shit. You want atleast 3000 MHz with modern Ryzen CPUs for their Virtual Memory Fabric. You can probably get equally good Ram for a few bucks because these sticks suck.
Unless you already lowerd the Frequenzy in that case RIP.
I'm not sure what you're talking about. DDR4 without XMP typically runs at 2133 or 2400mhz. It's probably best to run a mem test at the stock frequency.
Yeah I lowered it to make sure that wasn't the problem
F! That sucks. Time to mortgage your house.
Dang, i'm a bit worried for my own RAM as well. I keep getting random reboots on my pc every now and then. I initially suspected my distro to be the problem since it started happening after i hopped, but after feeling like i checked everything on the software side, i'm checking hardware now just to be safe anyway. Started with removing the OC from my RAM. I also have my 5800X3D undervolted though since i saw it recommended at the time. Now that it's a few years old i might just not be stable anymore at that voltage.
I've got two 16GB sticks that I bought in 2020 pullin me through—I'm praying they last long enough til prices go back down haha
view more: next ›