Error 55 Issue with the 8Pack Approved Binned Intel Core i7 6700K @ 4.80GHz Overclocked Bundle **£15

Callum Dunt · 30 Jul 2017 at 17:03

Hi there, we have installed the new motherboard, RAM, and CPU and we are getting a consistent boot problem with error 55. The PC booted once, and came up with the normal settings for overclocking, and then we turned it off as we realised we had a fan facing the wrong direction. When we turned the PC back on it did not boot and just had error code 55.

We switched around the RAM, and we auto configed the RAM and restarted everything multiple times. We have now used the flashback drive to reset the Bios and we are still getting the recurring error.

We have been wracking our brains for the past few hours not knowing what to do. Any advice would be much appreciated. Thank You!

Blackbadger · 30 Jul 2017 at 17:33

A few things to try.

1) Try only 1 ram stick at a time, and change the slot's it goes in. If the system boots ok and is stable, try adding more ram or swapping the chips about.
2) Check you have not over tightened the cpu /cooler retention, it should be firmly fitted but not silly tight.
3) It's possible that a setting may need to be changed on the OC profile for stability, annoying however sometimes even if tested prior, tweeks are sometimes needed.

- powerdown
- leave powercord to the pc
- push to clear the bios button once & hold for 5 sec ( on the back of the IO )

My guess is, in no order.

A) one of the ram chips is bad
B) Cpu cooler retention is overtight causing stress on the motherboard path's.
C) The CPU socket has been damaged - the pins are very fragile.
D) OC profile may need tweeking
E) Contact support.

lude1962 · 30 Jul 2017 at 17:35

error 55 should be listed in the motherboard manual

Blackbadger · 30 Jul 2017 at 17:40

Error 55 is no memory detected. I believe.

Also ensure the 8 pin power connected from the PSU is connected to the motherboard.

If you do get it back up and running, I suspect the RAM voltage may need a minor boost - 0.05v However I'd check with support before fiddling with such things.