GPU clocks locked at constant max clock speed (frequency not utilisation).

[COVID-19]

I have a 1080 Ti on Windows 10 x64.

The GPU clock speed is at max constantly, never varies.

This happens in DX12 and DX11 in both Fullscreen and borderless modes.

Only happens in this game.

Any ideas?

[trek554]

are you kidding? that is exactly what your gpu is supposed to do if being pushed hard.

[COVID-19]

With previous drivers it ran under max clocks and was very smooth. Now it's actually locked at max and never varies.

[trek554]

Originally posted by So Immersed:

With previous drivers it ran under max clocks and was very smooth. Now it's actually locked at max and never varies.

Should have known better than to ask a technical question on Steam.

in other words you are an idiot for having to ask in the first place. pretty much any demanding game will put my 1080 ti at max boost.

[COVID-19]

I don't know what your max GPU clock is but I don't believe it's locked at max in every demanding game you play.

Also, tried lowering settings to medium and low, both have the GPU locked at max. So I'd say there's definitely an issue there.

[Vassago Rain]

Are you using kboost?

[COVID-19]

No

[Vassago Rain]

Are you using any third party tool similar to kboost (found in EVGA precision and many other clones of afterburner) to achieve an actual locked P0 state, while simultaneously actually, for real, hardlocking boost to state 2? What's your BIOS ID? Can you give me precise read-outs on your MCU while doing these things that totally 'lock clocks to the max?'

What's your actual model number, make, OEM, and refresh of GPU? Do you have a set PaT target? Any documented factory clock offsets? What's your reported core voltage, and does it differ from any documented (and undocumented, aka, things you did yourself, and/or had a friend do for you) estimations of voltage? Are you equipped with an SC, reference, or OEM card?

[COVID-19]

I doubt it's my card, it's fine in every other game but I do use Afterburner just to monitor in-game.
It's factory OC'd card (EVGA 1080 Ti SC Black Edition) and I just run it as is.

After driver version 384.94 it started, so it's probably either nvidia or windows.

Killing ApplicationFrameHost.exe in task manager used to fix it but now it doesn't.

[Vassago Rain]

Originally posted by So Immersed:

I doubt it's my card, it's fine in every other game but I do use Afterburner just to monitor in-game.
It's factory OC'd card (EVGA 1080 Ti SC Black Edition) and I just run it as is.

After driver version 385.41 it started, so it's probably either nvidia or windows.

Killing ApplicationFrameHost.exe in task manager used to fix it but now it doesn't.

I'm disappointed that you had absolutely no idea what half the things I wrote even are, although I probably shouldn't be. All the actual computer savy people who used to frequent disappeared forever ago.

Since you don't know what a PaT target is, and don't know how to check MCU, I'm gonna have to go with a default answer to your very default setup: any application run on any system built maxes out clocks, to the specified limits. These limits are defined by performance levels (P9 through 0), with 0 being the 'high performance, all systems to full power' state. If you were truly maxed out (which you're not, by the way), you'd theoretically (under water) be looking a speeds far past 2200 for the core. The reason you 'max out' is because the 10xxx series (actually, all of pascal) is equipped and configured to take full advantage of nvidia boost 3.0. It goes to the maximum rated clock, defined by the state, without compromising heat gain or power curve. Pascal, under 3.0, doesn't actually throttle the way previous generations did, by TT, then resorting to TJm checks when critical state is reached - rather, pascal looks at speed, step, state, temp, voltage. In other words, it's a dynamic system, divided in internal 'steps' of 12mhz.

In exchange for this dynamic system, that typically gives far higher clocks than what's advertised (without getting anywhere near the maximum someone who actually knows computers could get out of the hardware), gains through overclocking are lower, and harder to attain. Overclocking and everything related to it has also been made much more difficult by Nvidia's harsher encryption, which makes a BIOS replacement on pascal a challenge. On the other hand, you can actually increase your clocks simply by installing better cooling, or making your default GPU fan run at higher speeds. The cooler you run, the more 'steps' pascal can take, with, as might be expected, further steps requiring more power. Pascal has an absolute voltage maximum of 1.093, but you're not likely to go anywhere near that doing gaming.

To the average user, that being yourself, this is of no concern. To power users, that being people like me, this is quite the sad state of affairs. Pascal should be operating in the 1700 to 1950 range on P0 - which coincidentally, DX11 games are by default, unless you specify to the metal that it must maintain a lower state, and even if you do, pascal's 'step' program means one can't actually disable boost completely, let alone fully control it. Looking into the matter more closely, your GPU only has P5, P2, and P0, which is to be expected from a performance card aimed at enthusiasts, made by a company formed from enthusiasts, selling primarily to enthusiasts - of which you are not one.

The .exe you think is causing issues isn't causing issues, and is an integral part of how windows 10 operates alongside the windows store in the win10 environment. 'Killing' it doesn't actually kill it, and running a bypass means you can't access the store, period. It's also primarily concerned with CPU resources, and as it's a UWP app, not a traditional win32 feature, it needs to be contained in its own entity, and can't be bundled into something like svchost. You might have noticed that when you 'kill' the app, any instances of things like the calculator simply go poof.

TL;DR, no, there's nothing wrong with anything, except for the obvious fact that you think you know more than you actually do, while knowing extremely little. A cursory google check, an email to EVGA, or a call (you bought black, you're entitled to support) would have told you all of this.

[COVID-19]

Arrrgh, I know what you posted earlier. I'm simply saying that they aren't the cause of the issue.

Plus I never claimed to know it all.

Unbelievable.

I don't know if you even read my last post, the issue began after driver 385.41 and can be reproduced by installing different driver versions.

If ending ApplicationFrameHost drops the clock speed of the GPU, (or at least used to) and the game still runs perfectly fine albiet at the cost of not having calculator running needlessly in the background while I'm gaming then there's something in Windows obviously triggerring the GPU unnecessarily.

[Vassago Rain]

Yes, indeed. The issue is that you don't have an issue.

You also aren't 'triggering the GPU unnecessarily.' I literally made a huge post about how the pascal arc works. Are you too dumb to actually read it?

[COVID-19]

Except the issue I'm not having wasn't there before.

[Vassago Rain]

Maybe you should call Nvidia and tell them that their pascal arc isn't performing properly by clocking as it's instructed to do under an app that calls upon boost 3.0 correctly, and mention to them that this is all happening while you're in P0?

I'm fairly certain they'll be as amused as I am.

[Livix]

are u stupid or what XD

[COVID-19]

Well I just think it's stupid that my card runs at 1987MHz on low, medium, high etc. settings when it never used in this game.