The maximum safe core voltage for the i9-10980xe is typically around 1.5 volts.
The maximum safe core voltage for the i9-10980xe is typically around 1.5 volts.
It's unlikely this will occur. Concerning voltage, the amount needed differs for each chip. You'll need to test it yourself. VRMs generally don't need water cooling unless you're using the cheapest X299 board, as most solid HEDT boards are bulky, but that's up to you. Note: I just realized you're using two 360mm rads—still not a guarantee of reaching 5GHz. In short, aim for under 1.25V to keep temperatures manageable (even with your custom loop). Check out Gamers Nexus' review of the 10980XE; they reported significant overclocking and voltage usage, around 500W. Edited July 1, 2020 by Mateyyy
Test different settings carefully. Each i9-10980XE might respond uniquely, even with identical chips. The performance could vary significantly—some might hit closer to 4.9 GHz while others cap around 4.6 GHz.
Right now I'm performing reliably at 4.8ghz with a 1.23V core voltage across all 18 cores @-rascal-
They altered the approach compared to Skylake-X, though not dramatically. If it reaches similar performance levels, it could ease things, but cooling will remain a challenge. The main issue remains overheating the CPU, limiting voltage increases and forcing a compromise between temperature and reliability. Based on my experience with the 7920X using a Noctua D15, I typically hit around 4.5 GHz at about 1.15 volts. Beyond that, thermal limits cause instability. The 10980XE offers some improvements—it's newer and soldered, which helps—but expect limited gains. You might manage a bit further, but thermal constraints will likely set an upper bound before you hit risky voltages. A solid clock, but pushing it further isn't practical.
Thank you. The 4.8GHz at 1.23V is perfect for continuous, 24/7 operation. My temperatures remain stable across cores—my hottest core stays around 60°C with Porina.
You're checking which workloads affect stability. It seems some compute tasks might cause issues, but skipping them is fine. You're also open to experimenting with AVX offsets if required.