VDDCR controls power delivery, while Curve Optimizer refines the voltage curve for efficiency.
VDDCR controls power delivery, while Curve Optimizer refines the voltage curve for efficiency.
The main distinction lies in how each method handles the voltage offset for the CPU. The only notable variation is that with VDDCR you can apply a much more negative offset and still get the system to work, though it causes performance issues at lower clock speeds. It's difficult to determine exactly how either setting influences the system since Ryzen 5000 monitoring becomes unreliable, with many applications displaying incorrect voltages and clocks.
The curve optimizer uses a changing voltage offset derived from the voltage/frequency relationship, which is why it's called that. In contrast, VDDCR applies a fixed offset throughout all frequencies. Ideally, the curve optimizer should offer greater stability since it can adjust, but with a constant undervolt it either succeeds or fails. Still, the curve optimizer works better because it can reduce the undervolt when more power is required, enabling stronger boost across the voltage spectrum.
Well, the VDDCR places offset to the curve as well. It's not a fixed offset really. It's fixed offset on a voltage curve CPU already uses. There is no option to set a constant or max allowed voltage like I had on Intel CPU where it was allowed to go lower, but not above specified voltage. Here it's just offset and it seems to follow some sort of curve regardless. Which is why I don't get what are the specifics between both.
Yes, but the setting remains consistent. Although it doesn't allow you to set the voltage directly, it achieves this indirectly. Using the curve optimizer, the adjustment is measured in steps rather than millivolts, and each step varies in mV. It works more like an undervolt at lower frequencies where power isn't required, and less so at higher frequencies. This shifts the curve to the right, giving you more frequency at lower voltages. With a fixed offset, the curve shifts downward, reducing both voltage and frequency.
VDDCR drops to -0.05V and CO is at -15, yet the output stays steady at 4.85GHz on a single core in R23 at just 1.35-1.38V (even before reaching the stock level). This is impressive. But now it consistently outputs 1.45V for multiple cores, which is unusual since stock always ran lower than single cores. After 5 seconds, clocks peak at 4.55GHz and temperatures rise to 90°C. It seems the system should adapt voltages according to settings, but instead it keeps switching to higher values.
Just CO -15 with R23: Single: 4.85GHz at up to 1.39V Multi: 4.53 GHz at up to 1.35V Because of some reason, not using extra negative voltage offset lowers the required voltage. Trying other options like VDDCR negative offset, PBO, or raised PBO clock offset only makes things worse. Setting VDDCR to a manually defined voltage doesn’t help either. I’ve set it to 1.35V, which should be the max, yet the CPU kept drawing .146V for no clear reason. Even using a strange offset like -0.200 doesn’t change the results. I just don’t understand it lol.