Will abnormal GPU usage hurt my GPU?

[Mussels]

okay, so GFE has no impact whatsoever on GPU usage with regard to games and apps then?

the programs that were being affected by the abnormal GPU usage were showing up in the list there next to my games as being "optimised". Further to that, one of the GFE sub headings shown when i click on the programs in the list is "hardware acceleration", which was turned on.

My work apps have a Hardware acceleration option internal to the programs themselves, which i keep on and should only be making the GPU use about 15-20% at any give time, perfectly normal.
When it's turned off, this drops down to around 2-5% and navigating in the 3D windows becomes very sluggish.

When the GFE HA is also turned on, the GPU usage treats the program like a game and i get load level clocks usage up to around 70-80%, just from even hovering the mouse over some linework, don't even need to be rotating around 3D objects.

As soon as i removed them from the GFE optimisation list, this upclocking "bug" associated with said programs has since gone - and for the period there where the bug was absent by itself, none of my games or apps were being optimised ("info could not be retrieved, please try again later") and i was getting terrible performance issues with a lot of my games

is there really no way that's at all connected?

GFE can use GPU, if you have the recording functions on

It's only meant to be active in games, but you can set it to record your desktop (or accidentally make it think that afterburner is a game, or an overlay) and it could be recording all the time, using some GPU resources and smashing your C: drive

GFE is just another control panel - it's the features you enable, that actually do something

Pressing Alt-Z brings up the overlay "instant replay" is the one that can be always on, if configured wrong.

 

[Atticus_Maytrap]

cheers for the tip, i'll look into that

ive never used any recording function, but the in-game overlay is often turned on by default

 

[Atticus_Maytrap]

it seems the GFE was not at the culprit, i turned on the machine last night and the upclocking bug was there again, bouncing up to load levels just by running the mouse over the Afterburner graphs.

checked out the GFE app, the in-game overlay thing was turned off like i like it, restarted the machine and the bug was gone again

strangest thing

 

[Mussels]

it seems the GFE was not at the culprit, i turned on the machine last night and the upclocking bug was there again, bouncing up to load levels just by running the mouse over the Afterburner graphs.

checked out the GFE app, the in-game overlay thing was turned off like i like it, restarted the machine and the bug was gone again

strangest thing

Alt-R (Nvidia/GFE still) and Win+G (windows Game Bar) can also be used for alternative methods of monitoring clocks, without afterburner needing to be running

You can pin them as transparent overlays, letting you see the clocks realtime as you do whatever, and let you rule out afterburner as part of the issue

 

[eidairaman1]

Contact Nvidia and software makers.

 

[Ownedtbh]

No worries, as you can not fix this issue. The abnormal GPU Usage comes from Windows Processes like Desktop Windows Manager or Client-Server-Runtime process.

 

[Atticus_Maytrap]

Contact Nvidia and software makers.

did that way back when it first kicked off. Software makers claimed it was a fault of the GPU, Nvidia claimed it was the fault of the software makers

c'est la vie

Alt-R (Nvidia/GFE still) and Win+G (windows Game Bar) can also be used for alternative methods of monitoring clocks, without afterburner needing to be running

You can pin them as transparent overlays, letting you see the clocks realtime as you do whatever, and let you rule out afterburner as part of the issue

tried that back when it started up, using GPU-Z and CPUID, Afterburner it was not

No worries, as you can not fix this issue. The abnormal GPU Usage comes from Windows Processes like Desktop Windows Manager or Client-Server-Runtime process.

that is interesting, when i run the mouse over the afterburner graphs and the GPU usage and clock shoot up, the process shown as using the extra juice in the Task Manager is not actually afterburner but rather some other windows process - i think its actually the Client_server-Runtime process if memory serves

it is different when it relates to my work apps though, there in the Task Manager it def shows them as using the extra juice from the GPU

this is an odd problem right? Surely there must be a definitive fix for it?

 

[Ownedtbh]

that is interesting, when i run the mouse over the afterburner graphs and the GPU usage and clock shoot up, the process shown as using the extra juice in the Task Manager is not actually afterburner but rather some other windows process - i think its actually the Client_server-Runtime process if memory serves

it is different when it relates to my work apps though, there in the Task Manager it def shows them as using the extra juice from the GPU

this is an odd problem right? Surely there must be a definitive fix for it?

You can also see how the GPU Usage Shoots by the above named process when you open your Task Manager and also open GPU % Usage Tab. Then just drag around across your PC very fast any Window.
I also don't like how much GPU Performance it uses and i also don't have a fix for that.
My idea would be to turn off Hardware acceleration in Windows settings but as my 5600X has no iGPU i don't think the process can satisfied with just CPU calculation instead GPU.

 

[Mussels]

My idea would be to turn off Hardware acceleration in Windows settings but as my 5600X has no iGPU i don't think the process can satisfied with just CPU calculation instead GPU.

Thats not how it works, and it hurts my brain to try and comprehend that enough to counter it
the CPU and IGP are seperate. If you disabled the IGP's hardware acceleration... it would not be used.

 

[DrCR]

I am currently on driver 511.23, i did a clean install of it on Saturday and it made no difference. The sequence of events for me has been:



Driver 466.47, everything running as it should be.

Drivers 466.77-471.12, all having the upclocking bug with regard to certain programs.

Roll backed to 466.47, everything running normal again.

Rolled forward to driver 496.13 on release, everything still running normal (*see below)

skipped over the next few drivers due to negative user reviews.

Rolled forward to driver 497.29, everything still running normal.

after a few weeks, encountered some intermittent poor performance with a few games (GPU usage dropping to zero and causing stuttering).

Reinstalled the same driver after using DDU in safe mode to remove it.

Upclocking bug reappears after fresh install of driver 497.29.

Rolled back to 496.13, upclocking bug still there (where it wasnt before)

Roll forward over to studio driver 511.09, everything running normal

work for a few hours, load and create some real time renders with Enscape, GPU clock behaving exactly as it should - clocking up for the renders, clocking down again after once the render window is closed.

Put machine into sleep mode to go for a walk, come back and the upclocking bug is there again on studio driver 511.09

Rolled forward with a fresh install of 511.23, upclocking bug still there.



* It's also worth pointing out that while on driver 496.13 the upclocking wasnt there (for a time at least) with Revit, but WAS there with other programs like Autocad or Adobe Premier Pro

im currently using Revit, Autocad and Adobe indesign on my office machine and the GPU clock and usage are behaving as expected.
So strange.....

For whatever it may be worth, thought I’ve been winos-free for some years now and maybe this reflects outdated thinking from a simpler era, when I used to use nvidia cards on winoses starting back in the single digit driver era to the ~300s or so, I almost never ran the latest driver. Latest does not necessarily mean best for your purpose. If, say, 466.47 works flawlessly for you, I’d just then use it and forget about drivers for the next long while.

 

[Atticus_Maytrap]

For whatever it may be worth, thought I’ve been winos-free for some years now and maybe this reflects outdated thinking from a simpler era, when I used to use nvidia cards on winoses starting back in the single digit driver era to the ~300s or so, I almost never ran the latest driver. Latest does not necessarily mean best for your purpose. If, say, 466.47 works flawlessly for you, I’d just then use it and forget about drivers for the next long while.

tried going back to 466.47, this time around it made no difference