[Solved] Overclocking RAM DDR4: MemTweakIt, Asus ROG, i5 6600k, Corsair Vengeance LPX DDR4 3000MHz

Hello, I would like to know if anyone will give me any tips on overclocking the RAM memory. More precisely, I am talking about the right program, what the temperature should be, how much volts. I have a program included in the mainboard software: MemTweakIt from Asus ROG. I see that timings can be changed there, but you can not change the frequency. At the beginning try to increase the voltage in the BIOS, then the frequency and at the end of the timing? If so, how much to increase the voltage and frequency of clocking. Is it worth to take basic timings for them, ie "secondary timings", "tertiary timings"?

CPU: i5 6600k @ 4.6 GHz 1.385 V
GPU: GTX 660 2GB Palit (I am collecting on GTX 1060 6GB, maybe even on GTX 1070)
MOBO: Asus Maximus VIII Ranger
RAM: Corsair Vengeance LPX DDR4, 2x8GB, 3000MHz, CL15 (CMK16GX4M2B3000C15)
ROM: Samsung SM951-NVMe 128GB, Goodram Iridium Pro 240 GB, WD Blue 500 GB, Seagate Barracuda 2 TB
CPU cooling: Raijintek TISIS + additional third fan from SilentiumPC - Mistral 140mm
Housing: SilentiumPC Aquarius X95W
Case cooling: 3x SilentiumPC Mistral 140mm, 3x fans 120mm mounted as standard in the housing
Power supply: BeQuiet Pure Power L8 730W

Hardware configurations have been written in full and accurate (boast), but you forgot to specify what operating system you have.

Download the program from the attachment according to your system version, run in the "Sensors-only" mode and insert the screen from the section "CPU [# 0]: xxx" and "Memory Timings"

I'm sorry, I did not think about the system. I have Windows 10 Home 64bit.

Can anyone help ? Any general advice on DDR4?

The general rules are the same regardless of whether it is DDR4 or other.
It starts with lifting the timing in the bios best, then when on some timing they are unstable, the voltage increases, and finally, when you set everything up you are combining with timings.
Write maybe what you would like to get.

I wonder if it would be possible to overclock these memories up to 3300 MHz when the delays change to CL14 with an average voltage increase (about 1.4 volts). The most and I care about conquering timing as much as possible without some torturing of these bones. Delays are a minor matter - but I would like to try to learn. As far as I know, high-clocked Intel processors prefer high memory clocks - more performance can be achieved than on delay classes. In AMD processors it's the other way round. It is better to choose lower classes of delays than higher clock speeds.

Do not hesitate, just check, we will not tell you this, because every memory can be overclocked differently, each plate will bear it differently, etc. Here you do not have to wonder, check and the rest will come out alone.

I found some time to crank RAM. I managed to turn the above bones to stable 3200 MHz primary timings 15/17/17/35 1.36v (this voltage was already set at the XMP profile at 3000 MHz). After overclocking to 3333 MHz with the same voltage and the same primary timings, OC Failed jumped out. I decided to raise the voltage to 1.39v. The UEFI motherboard has adjusted voltage to 1.3926v by itself. At this voltage, we managed to crank up to stable 3333 MHz primary timings 15/17/17/35. I also tried to change the primary timings, however, each change at 3200 MHz and 3333 MHz (voltages of 1.36v and 1.3926v for both timings) was ineffective - OC Failed and Bad Pool Header. It's possible that I make a mistake when changing timings. In UEFI, I change CAS # Latency and RAS # to CAS # Delay. Combinations of these primary timings: 14/14, 14/15, 14/16, 15/15, 15/16.

Stable these modules after OC?

Yes, stable 3333 MHz 15/17/17/35, however at 1.3926v. Ever since I turned it up, everything works as it should. I tested OCCT with Linpack by default, 30 min (90% of RAM). Separately I have included a lot of tabs in Google Chrome, various programs - so that the memory and processor can be loaded as much as possible. Each change of timings, even at a lower clock, results in OC Failed. And once Bad Pool Header joined ... I saw on one forum that someone turned Corsair Vengeance LPX and had such results:
-> Nominal 2666 MHz 15/17/17/32 1,2v (4 modules) of 4 GB each:
- 2400 MHz 12/12/12/32 1.35v
- 2666 MHz 13/13/13/32 1.35v
- 2800 MHz 15/17/17/32 1.35v
- 2800 MHz 15/15/15/32 1.35v
- 3000 MHz 16/16/16/38 1.35v
-> Nominal 3200 MHz 16/18/18/36 1.35v (2 modules) 8 GB each:
- 3466 MHz 16/17/17/35 1.35v
- 3600 MHz 17/18/18/36 1.35v
- 3733 MHz 16/18/18/36 1.45v (only here, somebody manually increased the voltage)

Below is a link to the site where I found it.
http://www.overclockers.com/forums/showthread...e-LED-2x8GB-DDR4-3200-CL16-CMU16GX4M2C3200C16

Of course, the bones are different than mine, but the same line - Vengeance LPX. I've improved in the timing setting - more precisely on UEFI on the Maximus VIII series. Unfortunately, the result is the same. I'm surprised why I can not make timings at all. The timing went very well and the timings were not able to move. The only thing I have not tried yet is the multiplier 100: 133. Maybe if I find some time I will check with this multiplier.

Download from here: http://www.memtest.org/#downiso
Unzip, burn the image to a disc and start the computer from it. You can also download the version on the pendrive. (two program transitions).

Ps. Not every memory module will get the same - even if they are the same modules.

Get acquainted with: http://pclab.pl/art59968-11.html

In conclusion, the timing has some effect on performance, timing is not anymore - it all depends on the game / application / test.

However, after a while it turned out that the memory is not stable at 3333 MHz 15/17/17/35 at 1.3926v. Neither Memtest released all night, neither Prime 95 nor tests from Aida 64 did not detect this. Every once in a while (once a day / once in a few days) on the computer I got BSOD IRQL not less or equal. I guessed that this could be due to the OC of the processor or RAM. Since I have decreased the RAM clock speed to 3200 MHz and reduced the voltage to 1.36 v, I do not have these BSODs anymore. I just got the memory that can be turned up by only 200 MHz. Life. Now I can close the topic.