g.skill sniper RAM with Asus VI hero

Macterror

Reputable
Mar 30, 2014
13
0
4,510
Hello everyone!

I have just finished building my first rig but unfortunately I am getting code 53 on my motherboard. I read the manual and it has something to do with the RAM I have installed. I made sure to get RAM that was compatible (based on the QVL) with the motherboard and I have tried all the slot combinations ( 1 - 3, 2 - 4 and single memory stick in all of them) I have also tried the memok function but to no avail. I am not sure what else to do at this point. The ram model is F3-14900CL9D and it runs at 1866. I have also made sure to press far enough for the ram to lock in.

Anything else I could do to this fix issue? Any help would be appreciated!

Forgot to add that the RAM sticks worked on another desktop i own, but the motherboard was an x78 sabertooth
 


Hello tradesman thank you for the quick reply!

I tried what you suggested but nothing appears on the screen. I tried connecting the HDMI cable first to my gtx 680 and then to the motherboard itself (killed the psu before switching the output) but there is unfortunately no signal.

 


Fans do run and I can hear the hard drive booting up too so it is safe to assume that the problem is only RAM related. Reoving the videocard unfortunately did not help. What kind of connectors am I supposed to use in the slot above the cpu? 1 8-pin or 2 4-pin? I read online that using the 4 pins solved the problem for another person but I did not feel confident trying without someone else's expert opinion

 
Is there a way to do that without accessing the bios? I unfortunately do not get anything on the screen. If so could you give me a guide or instructions on how to do so?
 


Unfortunately this did not work either. Although I also noticed that I am getting the same exact error code if no RAM is inserted in the motherboard.
I noticed that my ram needs to have the XMP profile active, which im guessing is not on by default. Could that be it? If not what else could I do to solve this?
 
Couple of things, 1 since we know the DRAM works, and 2 it's from it's GSkill (I've tried most all GSkill sets in my Hero) then it's possible that you have bad slots or one more thing that comes to mind you might try (fairly easy) - try loosening the CPU heat sink, then snug it back down, not super tight, but snug, if too tight in a corner or on one side then it maybe slightly tilted in the socket, then give that a try, and another might pull the CPU and check for debris (lint, TC, etc) in the socket or bent pins
 
Hello Tradesman,

I am going to try your solution and as I checked my heatsink, it was not mounted evenly! Thank you for catching that. Unfortunately I have to head out of the house for now, but as soon as I reinstall it I will report back. Furthermore nothing was obstructing the CPU in the socket
 
And we are back!

Unfortunately reseating the heatsink and checking for any debris did not work. I get the same error code (53). I find it hard to believe that all 4 slots are bad though, what are the possibilities of that happening? Any other solutions I could try? I am starting to lose hope on this
 
I tried keeping the GPU disconnected but I unfortunately still get the same error code. As for ram I live about 400 miles away from home so I do not really have access to any. Being in college and all, everyone has laptops for the most part. Could you recommend me a cheap 1 stick ram that does not require a xmp profile running at something lower than 1866? I feel that If am at least able to get the bios with it, my actual ram will start working if i set the xmp profile. Would this work at all?
 
I would also like to add the following information:

- the dram led next to the 24 pin connector stays always red
- I followed the bench guide and made sure there were no shorts on the motherboard.

I am seriously starting to think that something happened to both of my ram sticks despite the fact that it is hard to believe so. Is there any other troubleshooting I can do? the memok function should also reset CMOS already and I have been using it any time i change a variable

I am actually thinking of simply pulling the battery out, wait a couple of minutes and turn everything on again just to see what happens