8 gb total 3.96 usable

ikillu1009

Reputable
Jul 25, 2014
7
0
4,510
Specs: Gigabyte 970a-ud3p BIOS F1
Corsair Vengeance 2x4 gb 1600 mhz 9-9-9-24
Windows 7 Home Premium 64 Bit
Sapphire Radeon r9 270

So I looked at my RAM and it says 8gb total 3.96 available, so I did some research and I tried all the normal things, the msconfig min memory uncheck, the clock down speed, and I am 100% sure that the ram is in the right place as the motherboard states that ddr3 1 and ddr3 2 sockets are the best for dual channel. The BIOS from what I can tell is the latest and greatest, and yet nothing seems to work. I did install the chipset from the cd that came with the mobo, could that have anything to do with it? I also looked for that memrepager thing or something I cant remember what it is called but I couldn't find it in my BIOS. In my BIOS it sees all 8 gb of ram at 1600 mhz but not in windows. I ran resource monitor and it said that about 4 gbs was stored.

I really need help this is my first build.

Also the RAM I got was used, but I dont think it would even boot up and show 8 gbs if it was broken.

Here are some pics

http://imgur.com/a/xr4np
 
Solution


Memtest only tests the memory that the firmware has mapped into the physical address space. The firmware may be able to read the SPD (the EEPROM chip on the DIMM that contains information about the module) which will tell the system that there's a module installed in that slot, but if the module is faulty or not installed correctly it will not map it in.
There's a difference between how much memory the firmware believes is installed based on SPD readings, and...
This commonly occurs when one of the modules is faulty, the socket / bus is faulty, or the module is not seated correctly. Reseating the modules can sometimes fix this issue, but if it doesn't you will have to perform a process of elimination to find and isolate the faulty component.
 


Don't know what this CD contained, but if you have any type of RAM Disk application installed, it could have reserved half of your RAM, even more sometimes.

The easiest thing you can do: just boot any recent linux distribution from USB stick or DVD. See how much of your RAM can Linux see. If it can see all of your RAM, you can exclude hardware as a reason: something in your Windows is the culprit. A clean reinstall might help.
 

ikillu1009

Reputable
Jul 25, 2014
7
0
4,510


I dont think I installed any ramdisk applications, is there any way I could see what drivers I have installed?
 

ikillu1009

Reputable
Jul 25, 2014
7
0
4,510
Welp I did a single ram test and with 1 piece of ram it would not boot at all, now I used the other stick with only 1 stick to boot in every slot and it booted fine, so I am guessing that one piece of ram is dead, it is strange that the memtest would not have picked that up.
 


Memtest only tests the memory that the firmware has mapped into the physical address space. The firmware may be able to read the SPD (the EEPROM chip on the DIMM that contains information about the module) which will tell the system that there's a module installed in that slot, but if the module is faulty or not installed correctly it will not map it in.
There's a difference between how much memory the firmware believes is installed based on SPD readings, and how much it is able to actually verify is installed based on power up tests.
 
Solution

ikillu1009

Reputable
Jul 25, 2014
7
0
4,510


I just tried all the other slots with that bad RAM and no boot, although it did do it once, it never did it again, I just find it so strange that it says that there is 8 gb installed even though clearly something is wrong with the RAM.
 

ikillu1009

Reputable
Jul 25, 2014
7
0
4,510


Would that be in the BIOS to look at? And possible change?