Installed 2 more ddr 3 ram sticks and this happens. Please help.

Sn1per_Ch1cken

Honorable
Jul 4, 2013
5
0
10,510
Hello everybody.

I have had 8gb of ddr3 ram ( two 4gb sticks ) for the past 15 months and decided to upgrade. I put in two more sticks ( the exact same type ) and I get a weird message on start up. The type of ram is this "Kingston HyperX KHX1600C9D3K2/8GX 8GB 2X4GB DDR3-1600 XMP Dual Channel Memory Kit"

I have never entered my BIOS and messed around. I've always left it the way it's been since I got this computer.

"the system has experienced boot failures because of overclocking"

I bypass this message and can freely go into my computer as normal... When I am in my computer I go to my control panel and look at my installed memory it is in fact 16gb. I am just curious if that message is something to be concerned about. Here is a picture of it.

i5r6ld.jpg
 

Sn1per_Ch1cken

Honorable
Jul 4, 2013
5
0
10,510

I don't overclock. What do you mean by "matching the sets in the MoBo"?
 


That's a pretty common error message after a hardware change or power failure. It will usually disappear after a fresh power cycle. If it persists, try clearing your firmware settings (consult your manual on how to do this) and installing a new firmware revision if one is available.
 

Sn1per_Ch1cken

Honorable
Jul 4, 2013
5
0
10,510


I removed the 2 sticks and I do not get any error message. I am going to leave the sticks out until I do some troubleshooting etc. What do you mean a fresh power cycle? There are also a new BIOS for my gigabyte ga 970 a-d3 motherboard that I don't have downlaoded... the current bios I am using is over a year old but I have not had any issues with my pc so ive never had to update BIOS
 


Install the new firmware, it may very well solve the issue. It certainly can't hurt anyway. Occasionally old values get stuck in the firmware's SRAM (where it stores the firmware parameters, as opposed to the ROM which stores the firmware code) which get mismatched against the values detected on startup. It's just a bug. This can usually be solved by flushing the firmware settings completely and forcing your PC to reinitialize everything.
 

Sn1per_Ch1cken

Honorable
Jul 4, 2013
5
0
10,510


Sounds good. Now how do I do that? Does that mean updating to the most recent motherboard BIOS?
 


That's exactly what it is. BIOS is the old standard PC firmware interface.