F5F Stay Refreshed Power Users Overclocking Corsair Vengeance LPX 16GB (2x8GB) DDR4 DRAM 3000MHz XMP compatibility issue

Corsair Vengeance LPX 16GB (2x8GB) DDR4 DRAM 3000MHz XMP compatibility issue

Corsair Vengeance LPX 16GB (2x8GB) DDR4 DRAM 3000MHz XMP compatibility issue

D
docsev
Junior Member
49
10-13-2024, 01:32 AM
#1
Hi everyone. I own an MSI Z170A SLI board paired with an i7-6700k processor. The CPU runs smoothly at 4.6GHZ (using the 4 V VCore). I attempted to enable XMP at 3000MHz in MSI click BIOS version 5, but the system won’t post and I have to reset the CMOS. After that, I manually stepped into XMP slowly, reaching only 2400MHz; anything above that causes a failure and forces another reset of the CMOS. I’ve adjusted the advanced DRAM settings according to the XMP profile listed below:

Voltage - 1.35V
Cycle Time 1 CLK (set command rate to 1 in click BIOS 5)
tCL - 15 CLK
tRCD - 17 CLK
tRP - 17 CLK
tRAS - 35 CLK
tRFC - 525 CLK
tRRD - 6 CLK
tRRD_L - 8 CLK
tFAW - 33 CLK
tRC - 52 CLK (no option in click BIOS, so I didn’t modify anything)

Am I doing this correctly? Or would you suggest an alternative approach to achieve the 3000MHz target? (I’m okay with my current setup for photo editing, video, and light gaming.)

EDIT – Just in case anyone asks, I haven’t touched Vsa and Vio. I’ve seen instructions to set them to 1.15V, but doing so still causes boot failures. They remain at auto.
D
docsev
10-13-2024, 01:32 AM #1

Hi everyone. I own an MSI Z170A SLI board paired with an i7-6700k processor. The CPU runs smoothly at 4.6GHZ (using the 4 V VCore). I attempted to enable XMP at 3000MHz in MSI click BIOS version 5, but the system won’t post and I have to reset the CMOS. After that, I manually stepped into XMP slowly, reaching only 2400MHz; anything above that causes a failure and forces another reset of the CMOS. I’ve adjusted the advanced DRAM settings according to the XMP profile listed below:

Voltage - 1.35V
Cycle Time 1 CLK (set command rate to 1 in click BIOS 5)
tCL - 15 CLK
tRCD - 17 CLK
tRP - 17 CLK
tRAS - 35 CLK
tRFC - 525 CLK
tRRD - 6 CLK
tRRD_L - 8 CLK
tFAW - 33 CLK
tRC - 52 CLK (no option in click BIOS, so I didn’t modify anything)

Am I doing this correctly? Or would you suggest an alternative approach to achieve the 3000MHz target? (I’m okay with my current setup for photo editing, video, and light gaming.)

EDIT – Just in case anyone asks, I haven’t touched Vsa and Vio. I’ve seen instructions to set them to 1.15V, but doing so still causes boot failures. They remain at auto.

S
superschut
Member
79
10-13-2024, 01:32 AM
#2
It might be a silicon lottery for your CPU. Some users avoid higher memory frequencies, particularly when overclocking the CPU cores. My 5820k doesn’t respond well to XMP 2800 and 3000 profiles even at its base speed. I can tweak settings and sometimes boot, but it eventually drops to 2666 and tightens the timings. You might want to try VSA adjustments, since AUTO isn’t reliable for my CPU with VCCSA too. Generally, you should just enable XMP and see if everything works, though make sure it doesn’t affect Vcore or other parameters.
S
superschut
10-13-2024, 01:32 AM #2

It might be a silicon lottery for your CPU. Some users avoid higher memory frequencies, particularly when overclocking the CPU cores. My 5820k doesn’t respond well to XMP 2800 and 3000 profiles even at its base speed. I can tweak settings and sometimes boot, but it eventually drops to 2666 and tightens the timings. You might want to try VSA adjustments, since AUTO isn’t reliable for my CPU with VCCSA too. Generally, you should just enable XMP and see if everything works, though make sure it doesn’t affect Vcore or other parameters.

C
ClumsySky
Senior Member
526
10-13-2024, 01:32 AM
#3
I faced the same issue with this memory too, and managed to stabilize it at 3000MHz by reducing the DRAM voltage to 1.29v.
It might seem odd, but it actually helped me.
C
ClumsySky
10-13-2024, 01:32 AM #3

I faced the same issue with this memory too, and managed to stabilize it at 3000MHz by reducing the DRAM voltage to 1.29v.
It might seem odd, but it actually helped me.

O
Olethewickd
Member
138
10-13-2024, 01:32 AM
#4
Command Rate 2T should be used for this memory instead of 1T
O
Olethewickd
10-13-2024, 01:32 AM #4

Command Rate 2T should be used for this memory instead of 1T

S
SpiritClaws
Member
217
10-13-2024, 01:32 AM
#5
Make sure to use Command Rate 2T instead of 1T for this memory.
S
SpiritClaws
10-13-2024, 01:32 AM #5

Make sure to use Command Rate 2T instead of 1T for this memory.