You are not logged in.
Pages: 1
After new installation my system started behaving really weird and I found out that one of my RAM sticks is faulty. I was using my PC the entire day with no problems until that, so it must have happened during the installation process. Kinda strange. Anyways, did it again with the one stick left and all is good so far, so maybe just a coincidence.
Offline
It is hard to comment on this, without knowing what “killed” and “faulty” means. But, generally speaking, neither Arch nor any other operating system could hurt RAM.
Offline
If you want to know whether the DIMM is "faulty" see https://wiki.archlinux.org/title/Stress … Memtest86+ but as mpan pointed out: any OS would be an indicator, not the cause and RAM typically doesn't break from one minute to another lest a non-ignorable incident ("so, I left my notebook on the oven for 5 minutes and now it no longer boots => spaghetti must be bad for computers")
Offline
It is hard to comment on this, without knowing what “killed” and “faulty” means. But, generally speaking, neither Arch nor any other operating system could hurt RAM.
Everyone knows what it means... I did memtest which resulted in errors. It is fucked, useless, out of commission. And you never know what can or cannot destroy a piece of HW.
Offline
* voltage
* heat (these two are also called "XMP")
* you're overclocking it
* you're pairing incompatible DIMMs
* market pressure leading to sub-par DIMMs being sold off
* time
* radiation
* god hates you
* pretty much everything else
* still not software I'm afraid
Offline
* voltage
* heat (these two are also called "XMP")
* you're overclocking it
* you're pairing incompatible DIMMs
* market pressure leading to sub-par DIMMs being sold off
* time
* radiation
* god hates you
* pretty much everything else
* still not software I'm afraid
https://en.wikipedia.org/wiki/Killer_poke
Though that probably didn't happen here in this case. ![]()
Offline
Pages: 1