GTX 1080Ti Power management Modes are stupid and broken

[Vayra86]

It's really not rocket science, you just modify your own bios to run at p0 except for idle.

I know but re read this thread mate...

 

[phanbuey]

I know but re read this thread mate...

oh lol...

 

[RejZoR]

We have been here before man, its your own stubborn point of view that is the cause of your issues. Open your mind a bit before opening such a topic and the obvious solutions shall appear before you. You are smart enough for that, surely

Pal, there is a difference between "doesn't need to" and "doesn't want to". Because if you haven't noticed it, it's the later. It should run at max clock no matter what when set to max performance and yet it doesn't because it has a god damn mind of it's own. If I want it to run at 500 gazillion MHz for only 30fps, it should fucking do so. What's the point of having 3 different power modes when they behave identical to every last bit of it? Eh? But sure, I'm dumb here and you're clever as fuck.

 

[Space Lynx]

Was playing Quake Champions and because it's running like dodo I've decided to lower the details to really pump out the framerate. Just to find out it runs EVEN WORSE. Further inspection showed that "clever" NVIDIA's power management keeps core clock at 1500MHz instead of 1950+ MHz on GTX 1080Ti for no logical reason what so ever. Which explains why it runs like total garbage despite lowering ALL settings.

Set it to Adaptive. Same. 1500MHz. Set it to Maximum Performance. Same. 1500MHz. WHAT THE F ?! Can NVIDIA ever do anything right without breaking bloody EVERYTHING? First all the problems with anti-tearing features and now something as basic as actually harnessing the power of what I bloody paid for.

Tried even older drivers 397.93 and same nonsense. Now I'll try the 390.65 from January 2018 if stupid Windows 10 will even allow me to keep it...

Your issue seems kind of odd, but I have noticed when I leave drivers "optimized" I get a higher boost clock, but maximum performance, its only like 30mhz less on max perf, so I just leave it on max cause I don't trust optimized or Windows, lol

 

[Vayra86]

Pal, there is a difference between "doesn't need to" and "doesn't want to". Because if you haven't noticed it, it's the later. It should run at max clock no matter what when set to max performance and yet it doesn't because it has a god damn mind of it's own. If I want it to run at 500 gazillion MHz for only 30fps, it should fucking do so. What's the point of having 3 different power modes when they behave identical to every last bit of it? Eh? But sure, I'm dumb here and you're clever as fuck.

Because Pascal / Gpu boost 3.0 works that way. The technology is precisely the reason Nv cards can achieve better performance and their high clocks as they do within a nice TDP budget. Forcing max boost only works counterproductive because it will also force max voltage = higher temp = lost boost bins.

For a car analogy; what you are trying to do is rev the engine way into the red when all you need is 1200 rpm to get up the hill. Drive a modern car like that and it will limit you in much the same way, too.

 

[RejZoR]

Your car analogy doesn't work. If car creates maximum torque at 3500 RPM only a retard would limit it at 1200 RPM for a hill...

 

[Vayra86]

And there we go: stubborn in your views of modern technology. Its not stupid or retarded when a method achieves better results at higher efficiency, which is what you fail to grasp here.

 

[SnakeDoctor]

This is a waist of time if dont do what people suggest or even read there posts

 

[Tsukiyomi91]

Have he tried cleaning the drivers prior to this problem? if he did, it shouldn't come up as a problem & starts complaining about how Nvidia "screws up" their high-end Pascal cards. How about this... if he has older cards or borrows from elsewhere, install it, run a few games without OCing the card & see if the problem persist. IF it does not, then the answer is obvious. Highly doubt the PSU or the OS is the main problem here.

 

[newtekie1]

Your car analogy doesn't work. If car creates maximum torque at 3500 RPM only a retard would limit it at 1200 RPM for a hill...

My car happily goes up hills at 12-1500RPM, so that is what it is at most of the time when going up them. If I don't need the torque/hp, I'm not going to waste the gas by downshifting just to run at a higher RPM that I don't need.

In fact, despite the fact that I know my car gets the maximum torque at about 4600RPM, it almost never sees that unless I'm doing something fun stupid. I'd say a good 90% of the time the engine never goes past 2500. And the reason for that is fuel efficiency.

So the analogy works perfectly. The card doesn't need higher clocks, the higher clocks will not help in any way, the higher clocks will only result in higher power use, so the card is smart enough to know not to use the higher clock speeds.

 

[RejZoR]

How is it "smart" when it feels like a turd because of it? And you'd assume running at constant 144fps would be buttery smooth. But it just wasn't and isn't.

 

[R0H1T]

How is it "smart" when it feels like a turd because of it? And you'd assume running at constant 144fps would be buttery smooth. But it just wasn't and isn't.

I think you should just dump Nvidia once & for all, get the Vega 10/20 with 32GB HBM2 & set yourself free for the next 3 years. A 1000$ card should really pay for itself, you shouldn't have to endure this BS!

 

[remixedcat]

Perhaps NVIDIA is preparing you for the next gen upgrade due soon with much better performance?

Sounds like apple to me, when they slow down older phones to get you to buy new ones. Ugh nvidia is getting shadier by the day.

 

[newtekie1]

How is it "smart" when it feels like a turd because of it? And you'd assume running at constant 144fps would be buttery smooth. But it just wasn't and isn't.

We've already proved in this thread that it isn't running like a turd because of the clock speed. It is running like a turd because you limited the framerate in the game and that limit conflicts with Fast V-Sync(because you failed to understand how that technology works too). We've already established this as fact. Now we are back to where the thread started and you have ignored everything everyone has said. Your mistakes caused the problem, not nVidia's power saving. /Thread

 

[RejZoR]

No, I understand it perfectly well. And for your info, it feels like turd even without Fast V-Sync at constant 144fps. But do keep going on with it. If I set the god damn thing to max performance, it should run at fucking 1950MHz at 30fps or 500 gazillion fps. End of discussion. I don't give a damn if it's eating 5 kilowatts or 200 watts.

 

[newtekie1]

No, I understand it perfectly well. And for your info, it feels like turd even without Fast V-Sync at constant 144fps. But do keep going on with it. If I set the god damn thing to max performance, it should run at fucking 1950MHz at 30fps or 500 gazillion fps. End of discussion. I don't give a damn if it's eating 5 kilowatts or 200 watts.

Really, because that's not what you said earlier.

After uncapping the framerate, the clocks ramped up to 1950MHz and while it's a lot hotter and louder now, the gameplay is buttery smooth as well. Capped at 144fps it felt horrible despite being 144fps at all times. Go figure.

So, to recap:

1.) You have no clue how Fast V-Sync works, because if you did you wouldn't have put a framerate cap on that is anywhere near your refresh rate.
2.) Taking the framerate cap off makes thing "buttery smooth" and makes the card boost to normal clock speeds. Meaning the framerate cap was the problem all along, and higher clock speeds would not have mattered. The card would not have performed any better, because YOU limited the performance.
3.) You don't under stand the basics of how power states work, so you just label them as stupid.

Time to move on. The problem you caused is fixed. The thread's purpose is over.

 

[RejZoR]

I'm not even gonna bother responding to you anymore because you're the genius and everyone else is retarded apparently.

 

[Norton]

snip.

Not ok to use that kind of language here

Public warning- additional infractions will be issued if anyone wishes to try

 

[RejZoR]

Context, do you even? You know what, nevermind.

 

[cucker tarlson]

Well,you've learnt your lesson with nvidia. Should be flying off to grab a Vega, they're available in good supply now so there should be no problem.

 

[Kursah]

Context, do you even? You know what, nevermind.

Feel free to review our guidelines if you or anyone else involved here want to know what kind of context and treatment of others is and isn't acceptable. I strongly suggest it.

https://www.techpowerup.com/forums/threads/forum-guidelines.197329/

 

[RejZoR]

Well,you've learnt your lesson with nvidia. Should be flying off to grab a Vega, they're available in good supply now so there should be no problem.

No point in doing it now as I'd just be throwing money away, but might happen with Navi. NVIDIA is really starting to get on my nerves and I only had 2 of their modern cards...

 

[cucker tarlson]

No point in doing it now as I'd just be throwing money away, but might happen with Navi. NVIDIA is really starting to get on my nerves and I only had 2 of their modern cards...

Well you'd still get a very,very good resale price on that 1080Ti. I see no better chance to do it than now, before the launch of the next nvidia series. Aftar that the value of that 1080Ti will plummet.

I might try one more thing, uncapping the framerate. Fast V-Sync does limit frame output to the monitor, but doesn't prevent it from computing them (they just get dropped). Meaning GPU should churn out as many frames as it can, but only 144 will be actually rendered per monitor sync.

Then why is GPU usage always lower when you play with v-sync on if it still computes those frames ?

And why do you keep referring to some sort of "fast v-sync" ? there's fast sync and v-sync, there're a separate and a very different thing. And fast sync never limits the fps.

 

[R0H1T]

You've got lots of options here ~

1) Try some of the things that other users have suggested.
2) Try other things that you think will work better.
3) Get a replacement GPU, if you think this is a hardware problem.
4) Try get in touch with Gigabyte or Nvidia & see what they have to say about your solutions, to the given problem.
5) Get a gsync monitor.
6) Dump the card.

There's a few more but we'll save them for later.

 

[Vya Domus]

Use Afterburner , press L while the last point in the frequency/voltage curve is selected and then hit apply. It will make the card stay at it's highest possible clocks no matter what (until it will hit a perfcap of course). No BIOS flashing (Jesus Christ...) , no driver settings or anything of the sort needed

Three entire pages of comments, irrelevant information and insults could have been avoided.