Gtx 1080 Xtreme boost clock stuck at low speeds after PC has been idle few days.

Get weird issue with my Gigabyte 1080 Xtreme. Happened just once, but i dont know why.
I left idle my pc for i think 4 days. When i back i run some application and core clock stuck on 1275mhz instead of 1990mhz like always. Memory clock was not affected. Gpuz reports PWR limit at 32%. Reboot pc fixes.

Any experience this issue? Card is OC by factory only.

I am sure i have good psu. Corsair 750 W

All sleep options are turned OFF. All power management options in Windows set to Balanced ( default ). In on nvidia is adaptive ( default ).

There are some peoples experiencing the same issue on geforce forum.

Screen:

https://s32.postimg.org/e1kq6bpyd/1080b.jpg

Beside that, card is stable on full load,no crashes,no freezes.


Is this something with my card? : (((

Mostly likely software. Windows default power management settings still attempt quite a few software saving tricks and it's likely one of these didn't play nicely with the GPU driver, or the GPU driver didn't come out of idle (adaptive) all that well. Both windows and the GPU stuff is new, so you could give them some time to mature, or if you need it you might want to disable all the power saving modes in windows and the GPU. Otherwise since it's a one-off just reboot and carry on.

Ah i forgot. Somebody said to me that issue is because graphic driver propably crashed.
But it didnt. 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.

Quote:

---

Originally Posted by kik23

Ah i forgot. Somebody said to me that issue is because graphic driver propably crashed.
But it didnt. 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.

---

I didn't suggest it's related to a driver crash, merely software issues, which might not have resulted in a crash.

So propably its not caused by GPU itself? Not reason to Rma card?
It happened once to me.


There are several raports with peoples with the same issue on GEforce forum.

Also i had only GPUZ and fraps opened thats all. I dont have installed overclocking utilities like Afterburner or Precision. So i think this was not caused by application.

Quote:

---

Originally Posted by kik23

There are several raports with peoples with the same issue on GEforce forum.

---

And I expect 100% of them are using Windows together with nVidia drivers so nothing is ruling out software.

Has anyone from Nvidia picked up the issue? If everyone with the issues submits a ticket/bug report they might look into it. I'm with kalniel that it looks very much like a software thing; either a bug in the driver or its interaction with Windows, either way Nvidia need to know.

Out of interest though, have you tried closing every program to see if it changes? A few years ago I saw a load of cards getting stuck in 2D clocks if e.g. a Youtube video was open/paused in the background.

Only had GPUZ, FRAPS opened during this. No other apps . No overclocking utilities like Afterburner or Precision.

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."






So it can be related to my card ?

Is it overclocked?

Quote:

---

Originally Posted by watercooled

Is it overclocked?

---

From the OP:

Quote:

---

Originally Posted by kik23

... Card is OC by factory only. ...

---

So it doesn't look like it, or at least if it is, not in a way that will void warranty cover.

From the otherside i dont had driver crash. Any some peoples with Gtx 1070/1080 experiencing the same issue when lefting idle pc some time. So i am confused now. Is this reason to RMA card if it happen once or ignore it?


My card is OC by factory only.

In which case

Quote:

---

Originally Posted by kik23

So it can be related to my card ?

---

Possibly, but I don't think it's the most likely cause. It's quite rare for CPUs or GPUs to be unstable at stock clocks, even factory OC.

I'd try to get in touch with Nvidia - it wouldn't be fun to RMA the card and either get one back and have the same problem, or have the RMA rejected as 'no fault found' and possibly get charged. Having said that, it might be worth notifying the retailer (e.g. though tech support) in case they have any suggestions, and to make them aware of the issue in case you have to RMA it later.

I suspect it's a driver bug, tbh, and may be fixed eventually - it's just jogged my memory on an issue AMD cards had when they first introduced Zero Core: some cards wouldn't come out of their low power state after sleep. I think that only applied to cards with manual (i.e. non-factory) overclocks, but it's a similar issue that was (I think) fixed in a driver update.

Given how new the 10-series are I'd be amazed if there wasn't something similar, where the card gets locked into a lower power state after waking from sleep. Chances are it only affects in under certain conditions, so might be difficult for nvidia to reproduce. If the card performs normally after a re-start, then I wouldn't worry about it, and perhap think about turning your computer off when you've finished using it rather than leaving it to idle/sleep?

It happened once after long idling my pc.And then core clock throttle from 1990mhz to 1285mhz. Restart pc fixed. And this issue never comes back. I tried to reproduce issue by idling pc for 3 days and nothing.

Card on full boost is stable, no crashes.

Quote:

---

Originally Posted by kik23

It happened once after long idling my pc.And then core clock throttle from 1990mhz to 1285mhz. Restart pc fixed. And this issue never comes back. I tried to reproduce issue by idling pc for 3 days and nothing.

Card on full boost is stable, no crashes.

---

You have to remember that to RMA the card, the shop will need to prove to the manufacturer that there is a fault. So they need to be able to reproduce it quite easily. If you can't see the error again after 3-days idle then it's really unlikely the shop will be able to either. Especially given that their software environment will likely be different to your own (unless you supply a VM I suppose.. though I don't think they're an accepted gaming environment yet - but even then ruling out a software error is quite an ask).

So, assume it's a software bug and either forget about it, or take the measures I suggested in my first reply to reduce software power state change issues.

So during 2 weeks i cant reproduce issue.I left few times pc for 3 days in idle and still nothing. Maybe i must left pc idle longer then? What is your opinion ,try to rma? or just ignore that single occurance?

Quote:

---

Originally Posted by kik23

So during 2 weeks i cant reproduce issue.I left few times pc for 3 days in idle and still nothing. Maybe i must left pc idle longer then? What is your opinion ,try to rma? or just ignore that single occurance?

---

If you've failed to reproduce the issue after several attempts, just ignore it. Certainly don't RMA - if you can't reproduce it the manufacturer/retailer won't be able to, they'll send it back "no fault" and you'll have to pay for shipping and possible an admin charge.

Update. Left pc for 3 days in idle.Today back from work. Throttled occured,screen:

https://s10.postimg.org/vs9lf8ru1/122.jpg



Core: 1163mhz from 1990mhz

memory:1152mhz from 1251mhz




No driver crash in logs.

GPUZ: PWR LIMIT



And yes i am sure its not my mobo,because on 980 Ti never happened this. So definitely its not my PSU issue or mobo issue.
Card i think is ok because many peoples from GF forum and other forums with GTX 1080/1070 suffer from this issue, so my guess its the drivers.



What is your opinion?

Thread closed. This 'issue' has been posted here before, and on multiple other forums.