Motherboard Error Code 55

[Mludlow]

My PC, which was working properly and smoothly for over two years, all of a sudden is giving me code 55 on the LED display on boot -which means there is no RAM installed- yet there is, and the RGB on the 4 sticks is working.

The fist time this occurred was after a system restart once I finished updating the latest version of AMDs Adrenalin Software for my Asus Strix LC 6900XT OC. Not sure if that is related? 

My MB is a ROG Maximus Hero XII WiFi. 
My RAM is 4x 16GB DDR4 GSkill Trident Z Neo RGB 3000mhz

Ive already tried reseating all four sticks of ram and moving them around. 

Anyone know what could cause this sudden error after working properly without any hardware change in year?

[Silent_Scone]

Hello, it's not uncommon depending on the mount for the CPU to encounter pin pad contact issues after enough heat cycles. I would first look to remount the CPU and also definitely repaste as it's been two years.

[Mludlow]

CPU has been repasted and reseated about 6 months ago. I doubt that’s it

[Silent_Scone]

And without trying, I doubt you'll know 😃. Beyond a hard fault, 55 is almost always a pin pad contact issue assuming the memory is installed correctly and not faulty.

[Mludlow · Accepted solution]

Problem solved, issue was the AMD Adrenalin Software.
I removed the GPU from the PCI slot and was able to boot with integrated graphics, wihtout moving RAM or reseating CPU.
I then completley uninstalled GPU drivers and software.
Added the GPU back into PCI slot and reinstalled drivers from scratch, and it all worked again.

Found a few articles mentioning boot issues from AMD Display Drivers, odd that the issue brings a 55 code to the Asus MB, though. 
https://wccftech.com/latest-amd-radeon-graphics-drivers-reportedly-causing-pc-boot-issues-corrupting...

[Silent_Scone]

It’s odd because it wouldn’t, given the qcode means something entirely different. The article is not related in any sense to a POST stop code.

Seems like the steps taken were a red herring. May have disturbed something in the process but at least you managed to POST again.