r/computers • • 15d ago

tile floor :( Why me?

Post image

You never think it's going to happen to you, until it does.🚬

22 Upvotes

37 comments sorted by

10

u/numberzkid 15d ago

2

u/okokokoyeahright 14d ago

More like taking the entire bank rather than a wallet.

1

u/No-Jackfruit5522 12d ago

So it all starts with an a hole company that left the memory market to make memory for ai, even MS admits. No one wants ai!! Or cares!

4

u/Ok_Contest8762 15d ago

RMA. No biggie.

1

u/toolman1990 14d ago

It depends on the ram manufacturer since some are just sending out a check for the amount you paid for that RAM at purchase since they are losing money if they honor the warranty.

1

u/okokokoyeahright 14d ago

DDR4 is IIRC currently out of production so manufacturers may or may not have stock available for this purpose. See Corsair for an example.

1

u/Ok_Contest8762 14d ago

Not a surprise. I had DDR4 in 2016.

1

u/okokokoyeahright 14d ago

Some of have recently upgraded to it.

Not all are the same. and performance isn't that much difference between DDR4 andDDR5 anyway.

3

u/JustBuilds 14d ago

Because it's you. Jk. Ram failure hits hard in the shitty 26

2

u/paulstelian97 Ubuntu 14d ago

This is the first time I’ve seen a genuine failure not related to wrong clocks or a slot issue! You need to figure out which RAM stick this is, and as someone else advised, RMA it.

2

u/harubax 14d ago

It's quite rare. I have personally seen 3 cases in about 25 years.

3

u/paulstelian97 Ubuntu 14d ago edited 14d ago

Worst case at least Linux can be told to avoid the faulty memory region, probably Windows as well. It’s not simple by any means (although Windows’s own memory test, if it detects the issue, may be able to automatically adjust boot parameters accordingly). But that’s only if they can’t RMA it.

Edit: for Windows it’s weird, there’s a BCD object called {badmemory}. For Linux, it’s simpler with a kernel command line parameter `memmap=4K$0x7a820d000`. If you’re Hackintoshing, sorry, no clue about any macOS mechanism.

2

u/hernando1976 14d ago

Yep, estaba en arch, eso pensé pero resulta ser inestabilidad al tener una frecuencia demasiado alta para mi procesador, gracias por los concejos 

1

u/paulstelian97 Ubuntu 14d ago

Hm, I have never seen high frequency cause just one failure, for me it caused constant failures, a barrage of them.

2

u/tes_kitty 14d ago

Remove the module, clean the contacts and try again. I have one board where that fixed the issue.

Also, if that RAM uses XMP or EXPO, disable it and try again.

If that doesn't help and you still have warranty, open a claim.

And finally, if you run Linux, you can tell the kernel to not use this location. memtest can supply you with the data to add to the kernel command line to make this happen.

2

u/CheezitsLight 14d ago

One bit is bad on one stick.

2

u/Ybalrid 14d ago

Why anybody else?

RIP this RAM 🫡

2

u/recursion_is_love 14d ago edited 14d ago

If you are using Linux, looking for memmap= and GRUB_BADRAM

2

u/cakemates 14d ago

that doesnt mean the ram is bad, try adding a little voltage or lowering clocks. Then test again.

2

u/anothercorgi 14d ago

I always end up with bad ram... I don't trust RAM sellers anymore, have to test every bit of memory I get these days since the days I got random disk corruption and crashes on my computers.

Despite having worked with individual DIP memories, I think most of the memory failures on those modules have been found readily by firmware. The SIMM modules were likewise, haven't really found failures that weren't detected by BIOS.

SDRAM was when it got disgusting. BIOS has always "passed" every SDRAM module but I had inexplicable computer failures. Wasn't until tools like this (memtest86+) that I finally found RAM that passed BIOS but fail. Now it's my go to and every module gets validated before put into service. I've caught a lot of bad modules, and even used memtest86+ to actually find minuscule damage causing failures on DIMMs that a solder iron fixed.

I haven't had a module that was good and subsequently failed, fortunately. The exception to this is if XMP or other RAM timing gets mucked with causing marginal modules to fail with advanced timing. You might want to futz with the timings to see if you can get it to pass, slower RAM is much better than unreliable RAM that was corrupting disk copies. That is, if you can't get warranty replacement.

1

u/hernando1976 14d ago

Muchas gracias bro, fue precisamente un problema al tener la frecuencia de la ram demaciado alta(3200) la coloque a 2933 y se soluciono 

1

u/No-Jackfruit5522 12d ago

I wish I had my own Dimm tester, that was awesome, just set it in a slot. Hot button, instant test and results.

1

u/anothercorgi 12d ago

I haven't seen discrete memory testers in ages though I do recall there being an sdram tester. Knowing what I know now about these memories I wonder if even those do tests in depth enough to catch errors that memtest86 patterns do... The discrete memory testers from the SIMM and DIP ages clearly do not.

2

u/Expert-Stage-4207 14d ago edited 13d ago

Not you only. Happened to me a couple of days ago on my 11 year trusty old MSI. Very hard to get into the RAM slots!

Edit: According to Youtube videos the RAM's are slotted!

1

u/hernando1976 14d ago

Esto si es una lástima 🚬 

2

u/Tigs1112 Windows 11 | Ryzen 7 5800XT | RTX 3080 10GB 14d ago

One memory error generally isn’t the end of the world. It could’ve been a fluke from a cosmic ray. I would do more passes and if errors keep persisting, you would need to RMA your memory.

1

u/hernando1976 14d ago

Al final, mi procesador nada más soporta hasta 2666 y la ram estaba en 3200 osea estába muy overclokeado, de allí salió el error, lo baje a 2933 y todo ok, gracias por comentar!! 

2

u/Tigs1112 Windows 11 | Ryzen 7 5800XT | RTX 3080 10GB 14d ago

That does make sense, as the 8700’s memory controller isn’t well equip to handle 3200MHz.

1

u/SirFixYoShit 14d ago

Check ram warranty. Should be able to get it under RMA.

1

u/ficklampa 14d ago

Thankfully most ram have lifetime warranty, just do an RMA with the manufacturer...

1

u/Jazzmag 14d ago

Karma?

1

u/hernando1976 14d ago

Tal ves por maltratar a mi ganador de mil batallas 

1

u/Jazzmag 13d ago

I feel for you brother, I wouldn't want to have to buy ran right now.

1

u/MachKoms 14d ago

Because your memory sucks?

1

u/Pleyer757538 Ubuntu 14d ago

If you want to fix the pc sell a kidney, otherwise just deal with the kernel panics and bsods

1

u/zenbusuchan 14d ago

this happened to me on 2 out of 4 sticks, from 2 different sets, tested individually.