Time of death: 1:19 am October 18
I wanted a spooky spooky season but not like this
Syndicated from the fediverse. Read and engage on the original instance.
View original on lemmy.worldView original on lemmy.world
Syndicated from the fediverse. Read and engage on the original instance.
View original on lemmy.worldI wanted a spooky spooky season but not like this
49 replies
This happened to me earlier this year, my friend had some spare ram randomly. I should've started the RMA process, but I was too lazy, idk if I still can.
*ramdomly
I have heard tell of people having their warranties on RAM spuriously denied with the explicit justification that the replacement stick is "worth" 600% or whatever of what the original was and therefore the manufacturer can't afford it. So I would not at all be surprised if you learned retroactively that you can't. Of course, after already surrendering your RAM stick to the manufacturer.
I returned a memory card to Sandisk the other week, and I'm fully expecting the same result.
Wow, keep it together please, no reason to start posting hard horror like this just because its the season.
And when they opened their computer... the memory was soldered onto the motherboard! 🎃
It's not as bad as you think. If you read it carefully you'll see that you can press any key to make the banner go away. I'm so glad I could help 🤗
Life saver, thank you 🙏
Easy fix, just get you a USB flash drive and convert it all to swap space, then make it your primary memory register 😎 no need to tell me I'm a genius, I already divined it in a bowl of alphabet soup
PC master race in 2030:
The best DDR2 rig
The cyberpunk reality will be computer users finding any way they can to keep their PCs running on an undernet disconnected from, but in parallel to, the CorpGov web. The latter is where you are tracked, monitored, monetized, ruled, caged, and where you own nothing but the CorpGov owns you. The former is an illegal hoard of history, media, software, 3d printing, and information disallowed on the main web.
No flying cars, no cyberpunk body parts, just people trying to keep from being controlled.
i mean my dad had a cool brain implant that significantly reduced his parkinsons symptoms. think neuralink but it actually works.
The downside, you've a stick of bad RAM.
Upside, DDR4 is easier to find for DDR5 if you need that slot back in action.
Downside, DDR4 has seen significant price hikes as well.
Upside, you have your pick of brand and style.
What brand is it?
G.Skill has a lifetime (sometimes 7 years) warranty on their sticks and they honored mine when it failed almost 3 years after purchase.
They take the whole kit back though, so you'll be ramless for about 2 weeks.
F
Can't you just add a kernel parameter to not use specific memory addresses?
It is doable.
🤷
You might have some luck reseating the ram after cleaning the contacts with isopropyl for single bit errors
If the errors are in the same address range everytime you can definitely reserve that address range in kernel parameters and nothing will be assigned there, you just lose a small amount of memory (Windows can do this too but I can't remember the process)
Last ditch effort is to manually adjust your ram timings, take note of what tests your ram fails on because there will be a corresponding setting for certain issues, this is very time intensive though and requires days of memtesting
Oh no friend, do you have a gofundme?
No that's OK I'm just going to sell the box for scrap metal and go live in the woods.
The best option!
48 gb you naughty dog
It ain't 64 GB DDR5 but it's aight
F
Excellent argument for having a large number of small RAM sticks, rather than just one or two big ones... If one fails, it's less of a loss that way.
Redundant Array of Incredibly expensive DRAM
RAIeDRAM
My servers have this option, either as a mirror or with hotspares. Seems expensive.
I'm so sorry this happened to you.
Such is life 🗿
That's an expensive fail
F
Is D.O.C.P. enabled? Is your RAM overclocked? If so, disable it and re-run the test. Try playing around with your RAM settings in BIOS.
OK, this could be a meme I am out of the loop for.This is a run if memtest, yeah? The huge letters are/were not a thing. My back hurts and the nurse said I could get an extra serving of pudding today.
I guess it just hit me. I have been away from Wondows for so long that I'm not even understanding memes anymore. I haven't seen a blue screen in maybe 20 years. (yes, I understand this is BIOS)
This is an instance of Memtest86+, which is different from the original memtest. It's booted from a ventoy flash drive in memboot mode. The big letters are real.
It says PASS when it's done some passes that were all successful.
It says FAIL when it has one error. It rattles off bad block addresses if you dismiss the FAIL and let it continue
Thanks. It has been a long time.
I feel like memory might have gotten more reliable in the last 25 years. This is the first time I had to memtest something in over a decade. Back in the day, I used to test heaps of rigs and find bad memory occasionally. And I've never had a memory failure on my personal hardware until now.
If I win the lotto I got you man, so sorry to hear. That is absolutely awful :(
47.8GB?
4 x 16GB but one of them is fully cooked and isn't even recognised (leaving 48GB) another module is failing with errors.
They are also specced at 3200mhz but running at 1066 currently 🤷
Wait, are you running it with the dead stick in?
You should memtest each stick on its own. Change settings in BIOS to match the sticks advertised speed. You might have to toggle XMP/DOCP on or off. Probably check timings and voltage, too.
And you're probably better off running 32 GB in dual channel mode. Unless you consistently use more than that, the extra speed is better than extra memory IMO.
If it's two sticks having issues, check if they are on the same channel. You might actually be having issues with your cpu not being fully seated. I had a buddy who could only ever get two of four to work, and it was a bent pin on the mobo.
Yeah, the time of death is a few years ago, they were cooked for a while...
Have you tried testing one module at a time at the original 3200?
I was going to suggest trying them at a lower clock but seems like you might be out of luck.
It is pretty rare to see multiple fails like this, do a search for your ram, mobo, chipset CPU and bios and see if anything flags. Might even be worth messing with latency settings, XMP can do stupid things.
Anyone already running memtest probably knows enough to check stuff but just in case.
Assuming it's a reputable brand it's probably worth attempting an RMA, it usually has pretty long warranty.
Tbf this is all kinds of fucky. 3x ddr4 is not a good start. Severly under clocked. The cas timings look very tight to me
I’ve killed DDR3 before by touching it while it was running. Not the smartest move, but yeah.
Remind me not to touch my DDR3 RAM.
I heard you get hairy palms if you touch there.
A small bright side, at least they are DDR4 not DDR5 or you'd be even more screwed!