970 after Idle stuck on 680 mhz clock max

Hi, could you explain me what do we see ? I'm not sure what to look for, could I update to the firmware you are showing or you found something different ? I'm not sure which firmware I could upgrade that not in asus site.

EDIT : you mean I should look a firmware that just start with the 825mV and that's the one I should use right ?

 

No theese bios-firmwares are examples.

In theese cards with stuck clocks all the voltages starts with 825 mvolt.

So may be it is related.

see for example an another card from another manufacter:

 

Nice, thank you very much, I will move this info to nvidia. Could I possibly update the firmware with the higher voltage ? or anyone else can give me an info when he doesn't have the issue with his voltage information ?





Another person with the issue

https://rog.asus.com/forum/showthread.php?84751-GPU-Tweak-2-clock-issues-(1-2-0-3)

 

Does everyone use High Performance Energy windows profile ?

 

I use Balanced 0% min and 100% max CPU, Nvidia is set to Adaptive.

 

Balanced but with pcie link state management disabled

 

Oh nvm, the power % freezing came back, took a bit longer to show up. I started logging the clocks tho and they dont get stuck. Strange issue.

 

Thank you, so we all know. me formatting windows won't help cause someone else did it.


more updates

https://forums.geforce.com/default/...0-clock-rate-throttling-and-temporary-fix-/6/

Currently I'm using High Performance profile with Cpu 5% minimum and Maximum 100% just like the balanced. All other saving modes disable expect USB suspend.

I installed Potplayer x64 and I don't use NNEDI3 anymore cause it doesn't work with potplayer x64 for some reason it did work with the x86 version.
Potplayer x64 - Adaptive.
For now it didn't happen.

 

If you check your taskmanager, do you per change have CPU load on the task "System and compressed memory" when you have the issue?

 

I don't understand what do you mean.

You mean in the performance tab ?



EDIT : It happened again, clock stuck at 645 mhz while I left a movie in potplayer on pause mode , came back after 2 hr and playback, it got the clock stuck.... the **** is wrong with nvidia drivers.

 

No, under Details. There is an other possible bug you might be hitting, which is connected with that process.

 

Name PID Status User name CPU Memory (private working set) Description
System and compressed memory 4 Running SYSTEM 00 379,100 K NT Kernel & System


What am I suppose to see ?

 

Ok that looks good
If the 00 part was more like 12 (in an 8 threads system) or 25 (in a 4 thread system) you would be affected of the other bug.

 

There are so many threads about this....

wtf is going on


https://forums.geforce.com/default/...nvidia-fix-the-power-state-glitch-any-ideas-/

https://forums.geforce.com/default/.../gtx-970-gpu-core-clock-stuck-at-low-value/2/

https://forums.geforce.com/default/topic/809232/gtx-970-incorrect-clock-speeds-/

 

Did you install any software?

 

It is a gaming machine so just the usual - steam, bnet, afterburner, spotify.

 

You should try removing whatever you've installed since you didn't have the problem one by one to check if it's some software at fault here. Anything which is resident while the issue manifests would be a prime suspect.

 

Like no one has Battlenet, Msi afterburner and steam ?

he just reinstalled the windows, it could be alone be latest windows update, but it's impossible because it happens with windows 7 so it only leads to Nvidia Drivers and they know it, and they are checking it.

 

After having the 365.19 drivers installed for a day with all default settings and clean install (except gamma correction), I haven't had my power % freeze. Still tentative but seems good.

Edit Nope, still happens daily. I don't understand why it didn't happen for 2 days and then showed.

 

Ye, it takes couple of days or hours, that's what so annoying.

It seems like nvidia do this on purpose to sell the new cards so you will feel low performance but won't know why . for people who do not know how to check , and it's randomly goes so you can't figure what is the issue. And it happens after windows format, windows 10, windows 8 and 7, so it's global. it's something that is on purpose, can't figure why other people doesn't have the issue, but it is fishy hell since the new drivers.

What about the new drivers 368 ?