Ram compatability issue

retzman22

Honorable
Jan 21, 2014
33
0
10,530
I have mushkin enhanced 2x4gb silverline and a Asrock z87 extreme 4 motherboard. I am getting errors on boot on the led of 55 10 and 55. It will boot once then reboot about a min later flash the number 10 then come back up with 55 over and over same process. Mushkin ram not on the Asrock verified vendor list deal. Could this be the problem?
 
Solution
To properly test the RAM, install only 1 stick in the preferred/primary slot that your mobo instruction manual details. Then try to boot up and see if you continue to get error codes. Repeat for the 2nd stick. This will help determine if only 1 or both sticks are DOA.

I would still guess its a RAM issue but check the slots to make sure there are no bent pins. You may need to return the RAM and hope the replacements are good. If the replacements don't work then the motherboard could be the culprit after all.

retzman22

Honorable
Jan 21, 2014
33
0
10,530
01 - 54
(except 0d),
5A- 60
Problem related to memory. Please re-install the CPU and
memory then clear CMOS. If the problem still exists, please
install only one memory module or try using other memory
modules.

55 The Memory could not be detected. Please re-install the
memory and CPU. If the problem still exists, please install
only one memory module or try using other memory
modules.

I have tried removing the ram and installing just 1 and using other slots. No luck. Left battery out of CMOS last night for 20 minutes with no change.
 

Teejers

Honorable
Oct 1, 2012
48
0
10,560
To properly test the RAM, install only 1 stick in the preferred/primary slot that your mobo instruction manual details. Then try to boot up and see if you continue to get error codes. Repeat for the 2nd stick. This will help determine if only 1 or both sticks are DOA.

I would still guess its a RAM issue but check the slots to make sure there are no bent pins. You may need to return the RAM and hope the replacements are good. If the replacements don't work then the motherboard could be the culprit after all.
 
Solution