Getting Debug Code 55 on my motherboard

thugslife

Honorable
Feb 11, 2013
205
0
10,690
Hi Guys
I am here for your help I was using 12gb vengeance 1600mhz 4GB x 3 module but after one night i started my PC it was giving me 55 debug code I tried different RAM SLOTS but I end up installing 2x modules only in the 3rd and 4th slot and packed up my 4gb module any reason why the 55 code is still there , I also installed all the stick one by one all was working fine , also cleared my CMOS

MY SPECS
Motherboard : Asrock Z68 Gen Extreme3
CPU : 3570K @stock was able to gain 4.2ghz
GPU : r9 390 G1 gaming
RAM : 12GB Vengeance 1600mhz
HDD: 3TB Seagate
SSD : X110 Sandisk 1280GB
 
Solution


Installed the third module without touching anything also swap all the three modules with each other working 100% thanks all I think it was just a temporary bug
This is a long shot, but what version is your BIOS? Ivy Bridge requires ver. P2.10 or later. There are several threads, from 2012, with the same problem and a BIOS update solved it.

Asrock CPU SUPPORT LIST (LINK)

Another possible cause is bent pin(s) in the CPU socket or the RAM socket(s). Remove the mobo and the CPU. Examine the CPU socket and RAM sockets closely under a magnifying glass and a bright light source. If you find any that are bent, you can try to straighten them but this is quite risky as they may snap off!

You said that "I also installed all the stick one by one all was working fine." Did you also try each DIMM in EACH socket?

Yogi
 

thugslife

Honorable
Feb 11, 2013
205
0
10,690



yes I did each with each ram slot, btw the rams was working fine untill i turned in my pc in the morning it is wired no one touch the pc...

 


Did you check the CPU socket too?

Yogi

 

thugslife

Honorable
Feb 11, 2013
205
0
10,690


Did not check the socket as some days I got I changed the thermal paste I think It might be the cause
 

thugslife

Honorable
Feb 11, 2013
205
0
10,690


Installed the third module without touching anything also swap all the three modules with each other working 100% thanks all I think it was just a temporary bug
 
Solution