8GB x 2 Crucial DDR Only Recognized as 8GB

papersock

Junior Member
Sep 9, 2010
4
0
0
I just finished(relative) a new build with 8gb x2 sticks of crucial dual channel DDR4 2133 ram in a GA-Z170x gaming 3 motherboard. I set these up in the color-coded slots, first and third from the cpu. Bios and windows pc properties (windows 8.1) both list total memory at only 8GB. I tried moving them to the second and fourth slots from the cpu (also color coded together) and got the same reading. They are sold as 1.2V sticks and are receiving this voltage as per the bios. voltage shouldn't be an issue despite the cpu's cap of 1.65v. Does anyone have experience with this or advice? Thanks.
 
Last edited:

Seba

Golden Member
Sep 17, 2000
1,512
172
106
First try with only one module at a time in the same slot (first one for instance). If both modules are working individually, then test each slot, one by one with one of the modules.

Before each test, power down, unplug the PC and press the power button after unplugging, to discharge the capacitors.
 

papersock

Junior Member
Sep 9, 2010
4
0
0
I tried booting with each one individually in one slot, and it booted ok each time, so I felt confident the ram was fine. I then tried one of the sticks in the first slot (had tried second) and it powered on for around 8 seconds and then attempted to restart. I tried the other stick in this slot, same boot issue. I then tried each stick in the next two slots individually, same boot problem. I was thinking my motherboard had fried the ram via the first slot somehow. On a whim I tried putting them back into the first and third slots, and it booted, and for the first time recognized them as 16GB total in windows. I don't know wtf happened, and yeah i'm curious as to what did because the whole thing was so strange. for now i'm going to go with it and try and address the other problems with my build (apparently faulty pump in my H50 unit, now looking at 110s, and high end air options; and then nasty issues with my onboard ethernet not working, not working with any driver I try on it, all kinds of sass. I'm hoping a motherboard bios update will help but it's just one try).
 
Feb 25, 2011
16,912
1,554
126
It's been a long time since I had a problem like that, but in my Athlon XP days, resetting the CMOS would usually be sufficient to get a motherboard to recognize new hardware when it was feeling cranky.