Overclocking RAM settings for Corsair Vengeance 1600Mhz 12GB (3x4GB) on Foxconn Flamingblade GTI

StevenPuttemans

Commendable
Sep 27, 2016
2
0
1,510
As discussed in the official corsair forum i am looking for a solution to getting my new RAM installed correctly.

I had a Foxcon Flamingblade GTI motherboard with Intel Core i7 processor and 6 GB in RAM (DDR3, Patriot, 3x2GB). However 1 of the RAM cards broke down some time ago (tested by adding each single card, and one did not fire up the system, also memtests generates issues when this RAM card is in the PC).

Now I bought corsair vengeance 12GB DDR3 RAM 3x4GB which should run on my motherboard by overclocking as to the specs of the motherboard (http://www.foxconnchannel.com/Produc...U=en-us0000458). I ensured that MXP was enabled inside BIOS, because the memory carries an MXP profile.


  • * Putting in 1 x 4GB CORSAIR VENGEANCE memory results in award bios detecting the 4GB of RAM and Windows starting up just fine with 4GB of memory. The award bios has MXP enabled and at the memory overview it clearly states that there is 1600 Mhz memory detected and the correct amount.

    * Putting in 2 x 4GB CORSAIR VENGEANCE memory results in award bios detecting the 8GB of RAM and Windows starting up but generating a new memory access error each time it reboots. The award bios has MXP enabled and at the memory overview it clearly states that there is 1600 Mhz memory detected and the correct amount.

    * Putting in 3 x 4GB CORSAIR VENGEANCE memory results in the POST not finishing and giving a continious beep. According to the award bios overview for POST signals, this indicates a RAM issue, as described here (http://www.computerhope.com/beep.htm)

The order of the memory sticks in which I do this has been swapped to try out different layouts, so that leaves me to believe that there is not a wrong or broken RAM in the new package.

I noticed that in award BIOS after taking default settings and reactivating mxp, that DRAM voltage is red and at 1.7V. According to the internet, the red means that someone configured it to run at a higher voltage then default. However my corsair DDR3 RAM is suggested to run at 1.5V so I would wish to lower it. When entering the overview of voltages however, I cannot find the BIOS tab that allows me to set this. Is there are way to lower this to the prescribed 1.5V? If Yes can someone explain me how?

Finally when looking at the RAM sticks, I notice they suggest using 9-9-9-24 timings on the label. However, I am not able to locate the place where this values need to be entered in Award BIOS. Is someone able to point me there into the correct direction?

Also a tons of options in my BIOS are greyed out and not accessible for changes. Does anyone know how I can solve that?

NEW info: just looked up my cpu configuration. Its a Intel(R)Core(TM) i7 930 @ 2.8 GHz 2.93 GHz, which I derived from the Windows System tool.
 

StevenPuttemans

Commendable
Sep 27, 2016
2
0
1,510
@Tradesman1 thank you for the response. After digging around I got the RAM to fire up this morning using the following procedure

1. As suggested I resetted the CMOS without DRAM and tried installing the RAM afterwards. However, this led to a new error after the POST, namely a 4E on the 2 segment displays. After some googling I found the following topic on this website: http://www.tomshardware.co.uk/forum/321649-30-12gb-memory-foxconn-flamingblade

2. So following the suggestion in that topic, I updated my BIOS version from version 7 to version 10.

3. After doing so I had to reset the CMOS again, then enter the RAM memory, then open up BIOS and load the default optimized values. This got my system to work.

However, now I am experiencing that my memory is running at 1033Mhz instead of 1600Mhz and that timings are not as suggested on the RAM sticker itself. Current is

DRAM frequency 534.5 MHz
FSB:DRAM 2:8
CL 8
tRCD 8
tRP 8
tRAS 20
tRFC 86
CR 1T

while the RAM says it should run at 9-9-9-24. Enabling the XMP profiles inside BIOS and letting it auto configure resulted in a Windows that keeps crashing at startup due to different memory access issues.