3080 undervolting/overclocking

Associate
Joined
3 May 2018
Posts
604
MSI Afterburner + Voltage curve editor = a massive time sink.

If you are expecting undervolting to make your card NOT sit slammed into the power limiter constantly, save a bit of power and not nurf your FPS too much, you'll not have that hard a time.

If you are expecting undervolting to get in under the power limiter for a few more Mhz it gets increasingly complicated.

First off, the curve editor is lying. Rather it's always out of date. I believe it is setting clock offsets for each voltage point on the voltage curve. However, the base curve is constantly updating by the driver. So when you set it to, save it, confirm it, set it again, save it confirm it.... to 1860Mhz@800mV it might run at 1845, 1860 or 1875, depending on how it's feeling. The reason behind this is the driver is constantly trying to learn, adapt and respond to the card, just like you the overclocker are. It's modifying that base curve in real time, while you try and set offsets against it. Luckily, it seems at least, it only moves it by 1 bin at a time.

Second, there are "other things at play". For example if you rotate the whole curve to favour lower voltages and lower the clocks at higher voltages, it will hit 100% utilisation, no power limit, no voltage limit, no temp limit, but not boost any higher. There is still room on the curve to go higher, but it's limiter status says "GO" and it still limits.

Next is those top end voltage clocks. When you use a curve wide offset, like with the normal slider. You will raise the clocks at lower voltages, that will increase your performance a little before... On these cards, you will rapidly slam into the power limiter which will halt your progress up that curve. However, how much current and therefore power the GPU consumes is not equal for all loads. Many benchmarks throw curve balls to test for this. Super Position does it at the start with a fade. This fade seems to max your GPU with a load so light your voltage rises far higher than normal, your clocks of course follow it... they hit SillyMhz and crash. Time Spy puts it at the ends just to tease you. Cap your top end of the curve. Hold control grab the top handle and pull the whole top end down. Then fix your 800/900/1000 points again, apply, repeat. This will stop it going silly on light loads designed to trick it and those that will occur from time to time gaming. I think 2040Mhz is reasonable. 2020Mhz maybe.

Again on the upper voltages. Yes you will slam into the power limiter instantly on timeframes of what you see and so those upper voltage settings don't seem to matter. "It always stops at 1860Mhz anyway, so what if at 1.0V it could boost to 2040Mhz, it's never going to do it."... wrong. It will go there and cause random crashes. To stop that as above completely flattening or locking out the upper clocks will work for "under volt to save power", but will lose out on a ton of performance.

It's all a bit of a juggling act with the power limiter and voltage which isn't made any easier because it's own auto-overclocking driver is moving the stage your standing on while you do it. All for at most, 10% more Hz, <10% more FPS and 50% more power.

Under volting it for power saving is easier, works better. I have "Farming Simulator 2022" (hey! don't judge!) on ULTRA 1440p ultrawide, VSync at 75Hz and pulling only 100W on the GPU. Rad fans at 20%. When it is under 100% it will hunt down the curve, so the bottom end is not unimportant. This is why I recommend never adjusting single points. Hold control and "bias" the curve by that handle point.

How sane are the VBIOS options, versus the shunt mod? Gigabyte Eagle. Asking for a friend. ;)
 
Associate
OP
Joined
3 May 2018
Posts
604
If you attempt to go with a "locked voltage", by, say opening the curve editor, selecting 800mV and hitting "L" then setting a known stable clock.

This will result in a nice undervolted, underpowered setup.

However. It will NOT save you power over even the short term. With the voltage and clock locked at 800mV/1800Mhz (fe) it will not be able to trigger the "No load" limiter and drop back to 730mV and 200Mhz or even STANDBY in some situations. Even on the desktop, idle, the 3080 at 800mV/1800Mhz draws 50W. Unlocked, the no load limiter drops that to 38W (oc).
 
Soldato
Joined
30 Jan 2005
Posts
2,938
Location
Inverness
I've been trying to limit the wattage my 3090 uses and had similar experiences. Undervolting the card makes very little difference when running benchmarks i think it must start drawing more amps as there's not much difference in power draw.
 
Soldato
Joined
22 Nov 2010
Posts
3,104
Location
Kettering
Has anyone ever got a DXGI_ERROR_DEVICE_HUNG error code in game whilst undervolting? I'm getting this mainly in Apex but had it a few times in COD also, just wondering if it's a known issue or if I'm going to hard on the undervolt.

I started at 875 at stock 1980, I've made .25adjustments up to 950 now.

However I'm also not sure if I'm being too aggressive with my PBO curve optimizer, currently on -25 with a 5800x
By the way, my GPU is a zotac RTX 3080 trinity
 
Soldato
Joined
14 Nov 2007
Posts
16,184
Location
In the Land of Grey and Pink
Has anyone ever got a DXGI_ERROR_DEVICE_HUNG error code in game whilst undervolting? I'm getting this mainly in Apex but had it a few times in COD also, just wondering if it's a known issue or if I'm going to hard on the undervolt.

I started at 875 at stock 1980, I've made .25adjustments up to 950 now.

However I'm also not sure if I'm being too aggressive with my PBO curve optimizer, currently on -25 with a 5800x
By the way, my GPU is a zotac RTX 3080 trinity

Yeh, I've had it a few times when undervolting, means the card isn't getting enough juice.

I've settled on 881/1920 now (on a 3080 Ti) and its been rock solid for a couple of weeks now.
 
Soldato
Joined
22 Nov 2010
Posts
3,104
Location
Kettering
Yeh, I've had it a few times when undervolting, means the card isn't getting enough juice.

I've settled on 881/1920 now (on a 3080 Ti) and its been rock solid for a couple of weeks now.
So am I supposed to reduce the core clock with the undervolt? I'm running stock clock while reducing the power at that speed
 
Soldato
Joined
24 Jul 2006
Posts
3,006
Location
Essex
So am I supposed to reduce the core clock with the undervolt? I'm running stock clock while reducing the power at that speed.
You can either:

A) Try finding the lowest voltage for the current max boost clock for your card.

B) Limit the max clock speed & then find the lowest voltage to achieve that speed.

The second option will yield you better power savings at the cost of a small amount of performance. For example, I think my 3070 is limited to 1,900MHz instead of the stock boost of 1,980MHz but it uses 20% less power doing so for what in real world in terms is a couple of FPS.
 
Soldato
Joined
7 Mar 2008
Posts
2,614
Location
Kent
yes but due to silicon lottery dont expect the exact same settings to work might have to play around to find stability,
Thanks, yeah I seem to stability but I have a stupid question then because how do you know exactly its working. I've tried it in Control and it seems to make no difference with it enabled or not. I have it set to 1900 at 887mv and with it enabled or not Control never goes above 1900mhz anyway and temps both reach the same heights. Also in Far Cry 6 the clock boosts to 1950mhz, I have to do more tests but its just confusing me.
 
Soldato
Joined
24 Jul 2006
Posts
3,006
Location
Essex
Thanks, yeah I seem to stability but I have a stupid question then because how do you know exactly its working. I've tried it in Control and it seems to make no difference with it enabled or not. I have it set to 1900 at 887mv and with it enabled or not Control never goes above 1900mhz anyway and temps both reach the same heights. Also in Far Cry 6 the clock boosts to 1950mhz, I have to do more tests but its just confusing me.
Use GPU-Z, set the metrics so that it records the highest values then run your game/benchmark using stock settings. Take a screenshot of those values, close & reopen GPU-Z and then run your game/benchmark again.
 
Back
Top Bottom