GTX 1080 will not downclock. Stuck on 1633Mhz core clocks

[EdInk]

I apologise if this is the 1000th time this has been posted but I couldn't find any existing threads regarding this matter.

As the title says, my card will not return to it 139/405Mhz clocks, even after a restart.

What I've tried:

Fresh Windows 10 install but Win OS installed 388.13 drivers. So I DDU'd, set for windows update not to pull down drivers and installed the latest, 419.35 but the problem still persists. I also flashed the BIOS, DDU'd and reinstalled the latest driver.

What I've found works temporarily till I launch a GPU intensive task (gaming) is going to device manager and disabling and re-enabling display driver. I'm looking for a permanent fix.

Is this a bug?

p.s I've updated my System Specs

 

[thebluebumblebee]

Is there any load on the card?

 

[EdInk]

Is there any load on the card?

No load, checked using task manager and process explorer.

 

[king of swag187]

What power plan?
And (not trying to be rude, so excuse me) but why does it matter?

 

[eidairaman1]

2 monitors or 1?

 

[windwhirl]

I take it you already tried to reset the clocks through other programs, like MSI Afterburner?

And (not trying to be rude, so excuse me) but why does it matter?

I think we both know people here that would pay for a card that can't or won't downclock

However, it is still a problem, besides the energy waste, the card's life span could be shortened... Sadly.

 

[king of swag187]

It's not going to be shortened by a amount that would matter, but I do see the energy thing coming into play.
Have you checked window's power plans?

@/OP
Try low power/balanced

 

[Hockster]

If you've got more than one monitor connected nvidia cards don't drop to 2D speeds. There's millions of threads on numerous forums, most fixes I've tried don't work. My 1080 sli setup never dropped clocks in multi monitor, and neither does my 2080Ti.

 

[eidairaman1]

If you've got more than one monitor connected nvidia cards don't drop to 2D speeds. There's millions of threads on numerous forums, most fixes I've tried don't work. My 1080 sli setup never dropped clocks in multi monitor, and neither does my 2080Ti.

Yup its because gpus cant handle multi monitor with clocks being too low

 

[Wavetrex]

https://www.guru3d.com/files-details/nvidia-inspector-download.html

Find "Multi display power saver" on right click above the "Show overclocking" button.
[X] check your GPU, [X] check "Activate Full 3D by GPU usage" with 30% threshold.

Also add the games that you play to the list so GPU clocks up as soon as you start it (so it doesn't depend on usage, which might on occasion cause stuttering)

Yup its because gpus cant handle multi monitor with clocks being too low

They can handle them just fine.
This is just Nvidia being Nvidia.

I have 4 monitors on one 1080, two of them are QHD and above, for a total of over 8000 x 1920 pixels.
Been working like this since I bought the card 2 years ago, and surprise, it works perfectly with 139 Mhz CORE and 101 Mhz MEM:

 

[cucker tarlson]

If you've got more than one monitor connected nvidia cards don't drop to 2D speeds.

never had problems with it,it's downclocking fine.
but agree it's been a pain in the ass for many users apparently.

 

[FireFox]

Yup its because gpus cant handle multi monitor with clocks being too low

I have used multi Monitors for a long time and it worked without issues downclocking the GPU to 139MHz, I remember having the issue that the GPU didn't return to low clocks but that was with one monitor, the issue was some setting in Nvidia Control Panel ( Manage 3D Settings )

 

[Wavetrex]

Obviously Orbmu2k who coded NVIDIA Inspector created the specifically named "Multi Display Power Saver" tool because there is a problem. Not because he was bored and had nothing better to do with his or her life.

It's a very known problem that has existed long before Pascal cards, I think since the age of Fermi ( 400 series ), but it might be even older, I don't really know.

I for one certainly had it with Maxwell. Before that I used a Radeon 7970 GE card which did downclock with multi-monitors no issue. And before that card I only had one monitor so no personal experience.

 

[kastriot]

His monitor is 144Hz maybe if he sets it to 60Hz it will downclock?

 

[FireFox]

His monitor is 144Hz maybe if he sets it to 60Hz it will downclock?

If he sets it to 60Hz It will downclock, personal Experience.

 

[EdInk]

2 monitors or 1?

Single monitor.

It's not going to be shortened by a amount that would matter, but I do see the energy thing coming into play.
Have you checked window's power plans?

@/OP
Try low power/balanced

I’ve tried changing power plans in Win OS and NV control panel, rebooting in between. No joy

If he sets it to 60Hz It will downclock, personal Experience.

Not sure why I’ll buy a 144Hz monitor and run at 60hz. Dropping to 120hz made no difference.

https://www.guru3d.com/files-details/nvidia-inspector-download.html

Find "Multi display power saver" on right click above the "Show overclocking" button.
[X] check your GPU, [X] check "Activate Full 3D by GPU usage" with 30% threshold.

Also add the games that you play to the list so GPU clocks up as soon as you start it (so it doesn't depend on usage, which might on occasion cause stuttering)



They can handle them just fine.
This is just Nvidia being Nvidia.

I have 4 monitors on one 1080, two of them are QHD and above, for a total of over 8000 x 1920 pixels.
Been working like this since I bought the card 2 years ago, and surprise, it works perfectly with 139 Mhz CORE and 101 Mhz MEM:
View attachment 118550View attachment 118551

What driver version?

If you've got more than one monitor connected nvidia cards don't drop to 2D speeds. There's millions of threads on numerous forums, most fixes I've tried don't work. My 1080 sli setup never dropped clocks in multi monitor, and neither does my 2080Ti.

Only have 1 connected.

 

[FireFox]

Not sure why I’ll buy a 144Hz monitor and run at 60hz. Dropping to 120hz made no difference.

Thats wasn't my suggestion i was just confirming to @kastriot that he was right.

 

[EdInk]

What power plan?
And (not trying to be rude, so excuse me) but why does it matter?

It uses more power running at higher clocks whilst idling and runs warmer. I’d rather it didn’t.

I’ve tried all 3 plans.

 

[eidairaman1]

It uses more power running at higher clocks whilst idling and runs warmer. I’d rather it didn’t.

I’ve tried all 3 plans.

Contact card maker and nvidia

 

[CounterZeus]

Obviously Orbmu2k who coded NVIDIA Inspector created the specifically named "Multi Display Power Saver" tool because there is a problem. Not because he was bored and had nothing better to do with his or her life.

It's a very known problem that has existed long before Pascal cards, I think since the age of Fermi ( 400 series ), but it might be even older, I don't really know.

I for one certainly had it with Maxwell. Before that I used a Radeon 7970 GE card which did downclock with multi-monitors no issue. And before that card I only had one monitor so no personal experience.

That problem was (should have been?) fixed since Kepler series. My GTX1080 is downclocking to 139MHz atm.

Did some digging, lots of different setups still have it. Guess it's just really bugged :-D

 

[Shou Miko]

It's a known problem with 144hz on Nvidia cards that they don't downclock to idle when running 144hz but if you lower your refresh rate to 120hz then a lot of users report normal idle clocks.

I run 165hz on my screen never had a issue so investication shows it's only at 144hz not more or less.

 

[EdInk]

Seeing as only restarting my GPU resolved the issue. Use a script to restart Device adapter at log on.

 

[Vayra86]

Seeing as only restarting my GPU resolved the issue. Use a script to restart Device adapter at log on.

Take a look at your (if any) OC then as well, because Afterburner for example applies overclocking at startup. That might influence your script, you may want to have it start it up AFTER resetting the GPU.

 

[EdInk]

Take a look at your (if any) OC then as well, because Afterburner for example applies overclocking at startup. That might influence your script, you may want to have it start it up AFTER resetting the GPU.

I’ve delayed script to start up after MSIAB launches that seems to work fine. Will keep an eye on it. MSIAB doesn’t seem to like being delayed.

I run GPU at stock speeds and undervolted.

Take a look at your (if any) OC then as well, because Afterburner for example applies overclocking at startup. That might influence your script, you may want to have it start it up AFTER resetting the GPU.

You were right, MSIAB profile isn’t active that way. I can’t get MSIAB to delay launch.

 

[Shou Miko]

@EdInk it's didn't sound right you need to restart your
Graphics card to make it idle at what frequency us you running your monitor at¿

Plus have you tried running DDU and totally reinstall your Nvidia driver¿