Overclocking memory and stress testing related queries
Overclocking memory and stress testing related queries
A few days back I posted about choosing the best RAM for my system, short summary: Based on a suggestion from @RONOTHAN##, I stuck with what I had. Now I have some thoughts on overclocking, voltages, density, and stress tests—it's getting more interesting.
Details about my setup: DDR4 Corsair Vengeance LPX 32GB (2x16) at 3200MHz CL16 (16-18-18-36) with CMK32GX4M2E3200C16. I ran Thaiphoon Burner to check my current specs; the results showed a clock speed of 3600Mhz, and I manually adjusted timings to 16-18-18-36 (stock/xmp). When auto was enabled, the motherboard automatically lowered them. The BIOS is now updated to version F22 (motherboard listed below).
Questions:
1. How accurate is my current configuration? How does it stack up against others like B-die?
2. What voltage ranges are safe for VCCIO and VCCSA? I’m currently using 1.3V.
3. Besides luck, what can I realistically expect from this build?
4. Should I aim for lower timings or higher MHz? Since I mainly use it for gaming/editing, I want a balance.
5. Is TestMem5 with Extreme 1 @anta777 working well? How long should I run it? How many cycles?
6. Should I use Memtest86 for stability checks? It only does 4 passes if I run it on USB.
7. If I pass both tests, does that guarantee daily reliability?
8. Should I test both profiles to confirm stability before committing?
I’m learning how time-consuming it can be to tweak RAM settings one at a time. Any advice would be greatly appreciated!
PC specs: CPU i7-12700K (5.1GHz P-cores, 3.8GHz E-cores), 1.29V LLC, Turbo MOBO, Gigabyte Z690, X360 DDR4, ASUS RTX 3080 TUF Gaming, OC at 0.925V for 1980MHz (plus 300Mhz memory). PSU: EVGA 850 G2, case: Fractal design, white color, TG SSD, Samsung 850 EVO, 250GB, Windows 10 21H2.
It varies based on the manufacturer and density. The 8Gb Hynix A die (also known as AFR) is well-known for its issues, but the 16Gb version (referred to as AJR) seems better, though still not ideal. Around 1.45V is typical, both for the 12th gen and newer models. They don’t have VCCIO in the latest versions; instead, they use a different VDDQ TX voltage, which affects stability. There’s some disagreement about safe levels—some suggest 1.55V, others 1.45V. I lean toward 1.45V, especially since my boards haven’t needed to go above 1.4V without problems. Raising it further doesn’t improve stability much. Both aim for optimal performance, so you’re likely settling near the lower end of that range. It really depends on the maker. The 8Gb AFR might reach around 3600 CL18, the Samsung A die behaves similarly, and the 16Gb AJR could hit about 4000 CL18.
MHz-wise, this is mainly due to poor memory timing in most A die designs, so you won’t see significant gains. You should aim for high speeds but stay within stable settings—generally below 1.45V.
As for testing, running multiple stress tests can help, though a single TestMem5 or HCI Memtest at full speed is also acceptable. It’s not the most convenient, but it works. I usually do TestMem5, HCI Memtest at 700%, and Y Cruncher VST for two hours. Results differ between people, so four passes are usually enough.
If you’re okay with an OC, it’s fine if both pass except Intel DDR5, since high speeds often cause controller issues above 6600MT/s. Running VST can help verify stability.
You might find a tool like "ASUS MemTweakIt" useful—it lets you adjust timing settings directly in Windows, saving time during reboots. It simplifies finding limits in BIOS rather than testing repeatedly.
MSI Dragonball offers a similar experience with its interface, though MemTweakIt gives more precise control. Personally, I prefer it for its flexibility.
Thank you for your feedback! Here are your questions rephrased:
1. If I encounter a crash or lockup using ASUS Memtweak, will a simple reboot be enough? Would changing BIOS settings cause more issues, like needing to reset the CMOS repeatedly during overclocking?
2. You mentioned MHz over timings—currently I'm using 16-18-18-36 at 3600MHz. Should I switch to CL18 and higher frequencies, or stick with CL16? If yes, what starting point would be best for CL18 tuning?
3. I’m uncertain about the next steps. Should I keep increasing MHz at CL16, or try a different setup like CL18 for potentially higher clocks?
Essentially just restart everything and reset your settings. It’s best to configure them in the BIOS for permanent changes, though it’s fast. Be careful with a few parameters MemTweakIt can’t fix—like tCL, tCWL, command rate, and RTLs (unless you’re an advanced overclocking expert). Those should stay in BIOS while you handle the rest in the operating system. Yes, skip CL16 and aim for the highest stable frequency you can achieve. You might land on CL16 or CL17 eventually, but
You should configure the timings for (cl20-30-30-50) in BIOS and use them as your baseline. This way, if stability problems appear during MSI Dragonball, it will revert to those BIOS-set settings. Leaving timings on auto in BIOS might lead to issues.
Essentially, no—shouldn’t be that way. I usually adjust the main categories, but they should learn on their own without any specific direction.
I invest much effort exploring various settings, and ultimately, I can achieve the timing my rig provides at 3600MHz instead of 3200, which is a solid improvement. When checking the controller limits, I realized that attempting 3800MHz doesn't work on gear 1, even with high timings. In the end, I remain satisfied with the included 400MHz boost. Thanks again for your assistance.
Recent notes for those keeping up. After my previous update, I wasn't able to hit 3800mhz on gear 1 because the DRAM voltages weren't working right. The new BIOS helped a bit. 4100mhz was only achievable with gear 2 using high timings, but I didn’t want to abandon gear 1. Right now I’m stable at 3800mhz with cl16-18-18-36. Voltages are around 1.39v for VDDQ TX and 1.4v for VCCSA. Values above 1.4 on VDDQ seem to lead to instability. More voltage seems better, but I’m still learning about RAM overclocking. Maybe @RONOTHAN## can share some thoughts.