F5F Stay Refreshed Power Users Overclocking Corsair Vengeance OC question

Corsair Vengeance OC question

Corsair Vengeance OC question

M
MrAzazazaza
Member
222
04-27-2018, 11:44 PM
#1
I recently assembled a new setup using a Ryzen 2600 on an Asus Prime x470 pro with 16GB Corsair RAM. The memory runs at 3000MHz and has a 15ms latency. The RAM isn’t in the QVL, only the 16 latency variant is available. After enabling DOCP in BIOS and setting the frequency to 3000MHz, I allowed the system to auto-optimize, raising the voltage to 1.5 and keeping the frequency at 3000MHz.

I’m puzzled because when I switch to auto, the timing is set to 17. If I manually adjust it to 15, would that be problematic? Additionally, when opening the Corsair link, the reported frequency is 1496.4MHz, but why does it seem like half of the 3000MHz I configured?
M
MrAzazazaza
04-27-2018, 11:44 PM #1

I recently assembled a new setup using a Ryzen 2600 on an Asus Prime x470 pro with 16GB Corsair RAM. The memory runs at 3000MHz and has a 15ms latency. The RAM isn’t in the QVL, only the 16 latency variant is available. After enabling DOCP in BIOS and setting the frequency to 3000MHz, I allowed the system to auto-optimize, raising the voltage to 1.5 and keeping the frequency at 3000MHz.

I’m puzzled because when I switch to auto, the timing is set to 17. If I manually adjust it to 15, would that be problematic? Additionally, when opening the Corsair link, the reported frequency is 1496.4MHz, but why does it seem like half of the 3000MHz I configured?

M
MarioCovrigel
Member
195
04-28-2018, 12:28 AM
#2
DDR means Double Data Rate. This translates to approximately 3000Mhz when doubled. It’s important to perform a memory stress test prior to any adjustments to confirm stability before modifying configurations. Changing latency values from 17 to 16 or 15 might help, but setting a reliable baseline is essential for accurate comparisons.
Keep in mind, the QVL provides the only verified list of tested and confirmed memory, timing, and speed parameters. While other options exist, they often need further tuning and testing to achieve consistent results.
M
MarioCovrigel
04-28-2018, 12:28 AM #2

DDR means Double Data Rate. This translates to approximately 3000Mhz when doubled. It’s important to perform a memory stress test prior to any adjustments to confirm stability before modifying configurations. Changing latency values from 17 to 16 or 15 might help, but setting a reliable baseline is essential for accurate comparisons.
Keep in mind, the QVL provides the only verified list of tested and confirmed memory, timing, and speed parameters. While other options exist, they often need further tuning and testing to achieve consistent results.

E
Exinity
Member
54
04-28-2018, 02:58 AM
#3
DDR means Double Data Rate. This translates to approximately 3000Mhz when doubled. It’s important to perform a memory stress test prior to making adjustments to confirm stability before altering any configurations. Changing latency values from 17 to 16 or 15 might help, but setting a reliable baseline is essential for comparing outcomes.
Keep in mind, the QVL provides the only verified list of tested and confirmed memory, timing, and speed parameters. While other options exist, they often need further tuning and testing to achieve consistent results.
E
Exinity
04-28-2018, 02:58 AM #3

DDR means Double Data Rate. This translates to approximately 3000Mhz when doubled. It’s important to perform a memory stress test prior to making adjustments to confirm stability before altering any configurations. Changing latency values from 17 to 16 or 15 might help, but setting a reliable baseline is essential for comparing outcomes.
Keep in mind, the QVL provides the only verified list of tested and confirmed memory, timing, and speed parameters. While other options exist, they often need further tuning and testing to achieve consistent results.

S
snaari
Member
70
04-28-2018, 06:40 AM
#4
I don't have a specific program in mind, but I can suggest options for testing memory.
S
snaari
04-28-2018, 06:40 AM #4

I don't have a specific program in mind, but I can suggest options for testing memory.

D
dason_rar
Member
69
04-28-2018, 07:48 AM
#5
Memtest86 requires generating a bootable flash, but all instructions are available on their site. I prefer to perform 1-3 cycles for initial checks and 5-10 for final verification. It's taking too long to run 5-10 cycles after each minor adjustment. Good luck!
D
dason_rar
04-28-2018, 07:48 AM #5

Memtest86 requires generating a bootable flash, but all instructions are available on their site. I prefer to perform 1-3 cycles for initial checks and 5-10 for final verification. It's taking too long to run 5-10 cycles after each minor adjustment. Good luck!