Error code 55 on multiple msi Z170A Gaming M7s

mikecampo

Prominent
Mar 10, 2017
2
0
510
Hello,

My PC has been running fine for four months until yesterday when I turned it on and got no display. The mobo was showing an error code 55 seconds after booting.

My specs:

Intel i7 6700k
Z170A Gaming M7
2x 8GB Ripjaws V DDR4-3000
MSI GTX 1070
Corsair HX1000W psu
Corsair H100i gtx water cooler

After some research, I tried various things that was suggested to people with the same error. I made sure the RAM is pressed down all the way; I tried running with only 1 stick of RAM and tried each slot; I tried two sticks in various slot configs; no RAM; reset the CMOS; flashed the bios to the latest version; checked the CPU pins to see if any are bent (nope); disconnected the gpu; disconnected water cooler USB to mobo; tried a different gpu...all with the 55 error still coming up.

I then ordered a new Z170A M7 and 2x 8GB HyperX DD4-2133. I thought that this will help me identify if the Ripjaws are faulty or the original mobo. I tried the HyperX RAM in the original mobo and I got a 55 error. I then swapped the mobo out for the new one and I got a 55 for both sets of RAM.

I really don't know what to make of this. Could it be that the HyperX RAM is DOA and I should try a third set? Perhaps both the RAM and new mobo are faulty? (what are the odds). Could the PSU be causing this? It's about 6 years-old so I wouldn't be shocked if it was the culprit. Any ideas as to what I should try next?

Any help is appreciated. Thanks.
 
You will need a bios update for it to accept kingston hyper x
https://forum-en.msi.com/index.php?topic=261519.0

https://www.msi.com/Motherboard/support/Z170A-GAMING-M5.html#down-bios

Take your motherboard, ram, cpu to a reliable computer shop ask them to update your bios.
Also ask them to trouble shoot it, so that way when you leave and bring it back home.
You won't have the same problems or face new ones caused by them.
Also geeksquad can do the samething, just make the technician knows what you want done.
 

mikecampo

Prominent
Mar 10, 2017
2
0
510


Thanks for the suggestions. I'm running the latest BIOS so the hyperx should be fine. Not that it matters now, but you linked to the M5 driver/forum post and this is an M7.

I've isolated the problem to the CPU itself. The memory controller is likely fried. I've submitted an RMA to Intel so hopefully I'll be back in working order once they send me a new chip.