Help - Problem with crucial memory and Asus x99 Deluxe

[Alexander Blake]

Hi,
I am having problem with the Crucial Ballistix BLS4C4G4D240FSA memory, and motherboard asus deluxe x99. The memory is 16GB (4x4).

The board has an LED that will indicate each initialization step and the manual has a table to identify any errors that appear. I did the installation carefully, at first boot bios started normally. Installed windows 8.1 and realized that the system was only recognizing 8gb. I rebooted the system, and froze in error 53. After three restart attempts, started the windows, this time recognized only 4gb of memory.

I decided to remove and put all the combs to see if the windows would recognize the 16gb. And after that the Q LED froze in error 53. And no longer starts. According to the asus manual it is a memory initialization error. And the memory is not on the list of certified memories to the board. But others of the same brand are with only a code on different model. I do not think that has been a problem of conflict with the model ... cuz the list contains the same brand with almost identical model. It was not static because I took care. And already booted once, including win installation 8.1.

How do I resolve this? I'll have to buy the memories again? I need to put my pc running immediately.

Table asus with "Memory Qualified Vendors List"
http://dlcdnet.asus.com/pub/ASUS/mb/LGA2011/X99-A/X99_Series_DRAM_QVL_20150108.pdf
MEMORY:
http://www.amazon.co.uk/Ballistix-BLS4C4G4D240FSA-PC4-19200-Unbuffered-NON-ECC/dp/B00MTSWMVQ

 

[alexoiu]

Hi, Try clearing the CMOS and testing with single RAM module each slot. See the result.

 

[Tradesman1]

Do you have the latest BIOS?

 

[sora]

OP, clearing the CMOS battery should clear the errors for you.

 

[Alexander Blake]

I checked the slots with a comb at a time. And reseted the cmos, and pressed the MemOK button. It did not work.

The board starts and stops with error 53. The memook led is on. It is as if there were no memory connected.

 

[alexoiu]

I suspect a CPU socket bent pins issue, but... hard to say. Try removing the CPU and see if any bent pins.

 

[Alexander Blake]

I removed the cooler and the processor, seems all normal. I can not see if any are bent ... are hundreds of pins. I put all the combs memories and continues to happen the same thing.

The certainty with RMA will be long, and I need the machine running.
Man, this is bad. It will be a good choice to buy another motherboard?

 

[alexoiu]

Try buying a different RAMs kit (a cheap one), that you can return in case it doesn't solve the issue.

 

[Alexander Blake]

I'm suspecting that the motherboard is the problem. I live in Brazil and my options right now are buying a gigabyte mother board UD4 by U $ 470 or memory stick for u $ 176.

As I am in a hurry, even if money does not grow on trees, and I suspect the motherboard is defective, I will buy the motherboard.
In the best hypothesis to asus has a problem, and I have a pc running with 16 gb memory as quickly as possible.

And worse, the cpu pin bent. Why did you suspected the cpu pin?

 

[alexoiu]

"at first boot bios started normally. Installed windows 8.1 and realized that the system was only recognizing 8gb. I rebooted the system, and froze in error 53. After three restart attempts, started the windows, this time recognized only 4gb of memory."

The system degraded and I thought that a short at the LGA level could create such issue.

 

[Alexander Blake]

I remembered more things now. I installed an old DVD player that was working on the first boot and then stopped working too, before the pc does not start more.

Is this more evidence that may have been the processor pin ...?
Is there any possibility of appearing a memory error in the debug LED (53) of the mother and the problem is the processor board (CPU)?

This was the first PC I built, so I'm half nooby when it comes to hardware. I have not decided what I'm going to buy to find the error. Find other test components is not now a possibility. My choices at the moment are: 1. buy another motherboard and 2. buy a memory stick. So I can test them and find the problem. But if the problem is in the processor'm screwed.

 

[Tradesman1]

Might want to bench it and work your way through a component at a time, have a guide that may help here:

http://www.tomshardware.com/faq/id-1753671/bench-troubleshooting.html