Tested RAM on another motherboard, killed it?

jj9987 · August 18, 2016

Hi,

So I got a new motherboard, which is an Asus Z10PA-D8. I hadn't ordered RAM for it yet, so I took my 4 sticks of 8GB Kingston HyperX 2133MHz (rather standard) from my main PC to test out the motherboard.

The new motherboard didn't POST, gave B1 memory error - then remembered that the motherboard only takes ECC RAM. Okay, no biggie, will get ECC RAM for it and continue with the build.

So I put my 4 sticks back to the main PC and...my Maximus VIII Hero board is now giving post code 55 error - "Memory not installed". Okay, what the f.

Tried to boot up with 1-2 sticks in different slots. Nope. Still same. Reset CMOS. Nothing. MemOK does not help.

Did I just kill my RAM?

chris76816 · August 18, 2016

Probably

APasz · August 18, 2016

Very odd. I've never heard of ram being killed in such a way.

ECC (Error Correction Code or Error Checking and Correcting) is basically an add-on to standard meaning that if one component in the loop doesn't support it, it defaults to standard mode and it can do this because they're not physically or electrically different, just micro-code.

SLAYR · August 18, 2016

The asus board will take non ecc as well as ecc memory, try just a single ram stick at a time to see whether or not just one of them isn't working.

jj9987 · August 18, 2016

25 minutes ago, SLAYR said:

The asus board will take non ecc as well as ecc memory, try just a single ram stick at a time to see whether or not just one of them isn't working.

Apparently, according to the specs, this board does not. It never posted past memory ones.

30 minutes ago, APasz said:

Very odd. I've never heard of ram being killed in such a way.

ECC (Error Correction Code or Error Checking and Correcting) is basically an add-on to standard meaning that if one component in the loop doesn't support it, it defaults to standard mode and it can do this because they're not physically or electrically different, just micro-code.

Same here.

For the sake of science, I gave it another go (that was 4th or 5th try, I believe) in my main PC. Against all possible logic, somehow my PC booted up now with all 32GB memory.