GTX 1080 boost clock stuck at low speeds after PC has been on for a while

[litwicki22]

Help i dont know what is causing this. I think its drivers?! Because i have found other users with similiar issues.

 

So.........

My pc was running all time so smooth and without problems. Gpu clocks was fine always 1990-2000mhz in games and benchmarks.

But last time i rest from gaming and my pc was idle on desktop Windows 10 ,4-5 days. So till today was everything working fine. Today i run some game i saw that clock is very very below normal values. So like i said. I didn't install any software IE: MSI afterburner, precision or anything like that. I am using only GPUZ and FRAPS . I dont change anything in Windows and bios. Even dont change power managament in windows because its balanced. All default like always. This issue appear from itself. I am still using 368.69 drivers. But just today after being idle 4-5 days i sit to pc and no matter what game or benchmark i run i saw low fps, Then of course i check gpu core clock. 1278MHZ no matter what. I restarted pc and all back to normal clocks and normal fps.

 

So question . It was driver related?

Screen:

 

 

 

Also link with somebody and the same issue:

https://forums.geforce.com/default/topic/949132/geforce-drivers/gtx-1080-boost-clock-stuck-at-low-speeds-after-pc-has-been-on-for-a-while/

 

 

 

 

 

PC: 6700K no OC

 

 

2x8GB Kingston Hyperx

 

 

Corsair 750 RM

 

 

Gigabyte Gtx 1080 Xtreme

 

 

SSD Crucial Bx 100 256 GB

 

 

Asus Z170-P

 

 

Windows 10

 

 

Somebody said:"The graphics card will get stuck a lower than full frequency if you have done any overclocking on either card that was not completely stable, it is pretty common for a restart to fix that""

 

So that can be because my factory oc not stable or its a driver issue?

Edited August 1, 2016 by litwicki22

[ccokeman]

Would most likely have been from a driver crash and failed recovery. Could be that it did not come out of sleep mode properly. If a reboot fixed it then you most likely had a crash then failed recovery. 

[litwicki22]

It was not driver crash.  I check logs. Empty.

 

Also i have found topic with similiar issue:

 

https://forums.geforce.com/default/topic/916069/geforce-drivers/gtx970-clock-rate-throttling-and-temporary-fix-/4/

 

 

BUt somebody said this:"It can't be a driver, because for me it happened with all driver 970 and 1080 , and all I did to fix the 970 and 1080 was the bios settings. it's only something with Power/Heat or not working properly bios setting. I can't pinpoint because there are too much to it. but it's not a driver, can't sure why it does work with old drivers for you. but you get nothing if you can't update drivers which is just something you need to do, and 95% of the people doesn't have this issue either, it just can't be the drivers."


So maybe its mobo related? But i dont had that problem with my 980 Ti . So maybe mobo or drivers related?

Edited August 1, 2016 by litwicki22

[wevsspot]

You kind of answered your own question then right?

[Waco]

Funny how you seem to have the exact same issues and screenshots as OTHER PEOPLE. Please stop this.

 

http://techreport.com/forums/viewtopic.php?f=3&t=118304

 

Or, you created another account on TR since you got banned for this type of thing. But why change the wording slightly? Why the questions without reading any responses?

[litwicki22]

Really sorry for my language. Maybe i explain more brighter now.

 

At some point after having my system powered on, it often happens while the system is some time idle, my GTX 1080 becomes permanently throttled. The graphics clock is halved from a maximum of 1950-1960mhz (factory OC) to 1285mhz . When this occurs, it doesn't matter how much I load my card, be it games or other demanding applications, it does not ever go past the above caps. The only solution I have had up until now was to reboot the system .GPU-Z reports the "perfcap" reason as PWR

 

 

 

There are many topics about this issue on geforce. com forum.

 

I have 0 driver crashes. And normally the event log will show the drive crash report which in my case it doesn't show. So its not related to driver crash.

 

 

 

 

 

Somebody said this to me :"Improper overclocking causes these symptoms.

 

My card usually locks into a non-performance power state after too many hardware faults due to overclocking. Like others have said, a reboot will solve it, but double-check the stability of your overclocking.

 

The driver will not necessarily throw you a TDR ("Display driver stopped responding") error, either. The overclock can fail silently after X errors."

 

 

I am worried a little that can be card issue,even if driver not necessary throw a TDR error. But there are many reports with this issue on geforce forum.

 

 

Any opinions ? Please help me, thank you. Is something with my card or problem is elsewhere because many peoples suffer this problem.

 

PC: 6700K No Oc

 

16gb DDR4 Kingston Hyperx

 

750W Corsair RM

 

Asus Z170-P

 

SSD Crucial Bx100 256GB

 

 

I have installed only GPUZ , CPUZ , FRAPS + 3 games. No installed overclocking utilities like Evga Precision or Afterburner. Thats all.

What you think?

Edited August 3, 2016 by litwicki22

[Waco]

I think you should reboot if this happens. No further action required, a driver update will likely fix it in the future.

[litwicki22]

Just worry because somebody said:""I have a Zotac FE... I think it may be an overclock issue (possibly) I know that with my 980ti and TitanX if the driver crashes and recovered sometimes the card wouldn't boot properly afterward. So it's possible that if you push the card too much maybe the driver recovers after a crash and then doesn't boost again (properly) until a restart? I don't know I'm just throwing a theory out there.
It's very possible. The drivers have had a bunch of issues that took a while to surface so maybe it's "mini" crashing or something. I don't even know what that means but what you're saying makes sense."

 

 

Maybe my factory oc is not stable? But from the other side, there some users on geforce com with the same issue.