Help with DDR4 chip and 10700K overclocking.
Help with DDR4 chip and 10700K overclocking.
Hey, just checking in on the update. I completed the RAM testing and managed to hit 5.1Ghz across all cores using an adaptive voltage offset of -0.105V (1.326V Peak running Prime95, LLC4 and 79C). That’s a solid result so far. Still in the process, but everything looks stable with P95, AIDA64, Cinebench20 and Asus Realbench.
After about 15 minutes I confirmed it's stable but received a BSOD with "faulty hardware corrupted page" message. It might be related to RAM issues. I'll run memtest86 again to check for errors and consider adjusting the VCC and VCCSA voltage slightly.
VCCIO influences the voltage for the Super I/O, including the Lan controller in some motherboards, based on my understanding.
I discovered something that supports this idea.
If VCCIO was initially set below 1.0v, it could account for many stability issues.
Intel restricts DDR4 voltages under XMP 2.0 to a maximum of 1.5v regardless of speed or timing, and they strongly advise against exceeding this. This appears to be the only reliable 'safe' limit I've encountered for DDR4 voltages.
My Skylake system, both the Hero VIII and Gaming 5 models, clearly show they are POST-Haswell. They function as VCCSA/System agent and VCCIO only. There is no VCCIO or VTT present on the Gaming 5 as indicated in HWinfo. On the Hero VIII, however, both VCCIO and VCCSA appear, with no VTT, suggesting some differences between generations and even between boards within the same generation.
Overclocking settings for these systems have proven reliable. The recommended VCCIO and VCCSA voltages are well-established, performing consistently across all boards I've used, without unusual issues with I/O or LAN hardware.
Whether this applies to Canyon Lake remains uncertain since I haven't tested it yet. Based on available information, there don’t appear to be major discrepancies between this architecture and previous Skylake-based setups regarding these configurations.
Even the Intel datasheet suggests up to 1.06v for standard operation, while overclocked systems often reach 1.25v or more, with higher values possible if needed. As far as I understand, we remain on Skylake architecture despite using the Canyon Lake process.
A fresh update to a previous overhaul would help Intel, as the repeated skylake design is becoming outdated.
Absolutely in agreement, there are various naming conventions among different manufacturers and even within boards. I haven’t found a VCCIO A/D listing before, but it’s likely present on higher-end boards like Extreme or Godlike. On simpler boards, it might be combined with other categories or omitted entirely. The BIOS on my third-generation Asus model included PLL and System Agent, but I don’t recall seeing VCCIO, VTT, or similar entries. Since it was a basic Z77 model, the bios were much simpler compared to even lower-tier ROG boards.
Hey guys, sorry to bother you again. I removed the "solved" since I ended up in another issue now. I discovered a method to test if my OC will cause my PC to crash instantly, and it’s analyzing Intel's XTU V/F curve. Even with auto settings and adjusting only the clock multiplier, my PC just restarts without any error messages (like a BSOD). I’ve attached a video as an example of this problem. Do you know why this is happening? It doesn’t occur when I use stock parts or just overclock the memory.
I don't like XTU and I don't recommend using it.
If you've tested with Memtest86, Prime95 (Small FFT for thermals and either the Blend mode or the custom settings mode I outlined in my guide) and Realbench, then there is really no reason whatsoever to need to test with anything else but if you STILL want to, then I'd recommend using OCCT or Intel burn test, but really, if you've run these others and were stable, it's sort of putting a boot to the ashes of the body you already burned.
I also don't like XTU, but I only needed to retrieve the default V/F curve, which is what was provided. My OC isn't stable even when using XTU, so I'm unsure if any BIOS changes will help with the crashes.
It seems the issue might stem from an unstable memory setup. You may need higher voltage or a reduced frequency if you notice crashes not appearing in default configurations.