Last month I wrote a story that detailed some odd behavior with NVIDIA's GeForce GTX graphics cards and high refresh rate monitors, in particular with the new ASUS ROG Swift PG279Q that has a rated 165Hz refresh rate. We found that when running this monitor at 144Hz or higher refresh rate, idle clock speeds and power consumption of the graphics card increased dramatically.
The results are much more interesting than I expected! At 60Hz refresh rate, the monitor was drawing just 22.1 watts while the entire testing system was idling at 73.7 watts. (Note: the display was set to its post-calibration brightness of just 31.) Moving up to 100Hz and 120Hz saw very minor increases in power consumption from both the system and monitor.
But the jump to 144Hz is much more dramatic – idle system power jumps from 76 watts to almost 134 watts – an increase of 57 watts! Monitor power only increased by 1 watt at that transition though. At 165Hz we see another small increase, bringing the system power up to 137.8 watts.
When running the monitor at 60Hz, 100Hz and even 120Hz, the GPU clock speed sits comfortably at 135MHz. When we increase from 120Hz to 144Hz though, the GPU clock spikes to 885MHz and stays there, even at the Windows desktop. According to GPU-Z the GPU is running at approximately 30% of the maximum TDP.
We put NVIDIA on notice with the story and followed up with emails including more information from other users as well as additional testing completed after the story was posted. The result: NVIDIA has confirmed it exists and has a fix incoming!
In an email we got from NVIDIA PR last night:
We checked into the observation you highlighted with the newest 165Hz G-SYNC monitors.
Guess what? You were right! That new monitor (or you) exposed a bug in the way our GPU was managing clocks for GSYNC and very high refresh rates.
As a result of your findings, we are fixing the bug which will lower the operating point of our GPUs back to the same power level for other displays.
We’ll have this fixed in an upcoming driver.
This actually supports an oddity we found before: we noticed that the PG279Q at 144Hz refresh was pushing GPU clocks up pretty high while a monitor without G-Sync support at 144Hz did not. We'll see if this addresses the entire gamut of experiences that users have had (and have emailed me about) with high refresh rate displays and power consumption, but at the very least NVIDIA is aware of the problems and working to fix them.
I don't have confirmation of WHEN I'll be able to test out that updated driver, but hopefully it will be soon, so we can confirm the fix works with the displays we have in-house. NVIDIA also hasn't confirmed what the root cause of the problem is – was it related to the clock domains as we had theorized? Maybe not, since this was a G-Sync specific display issue (based on the quote above). I'll try to weasel out the technical reasoning for the bug if we can and update the story later!
Will the fix be available to
Will the fix be available to everyone or just those who use GFE?
Do others have to wait 3 months for it to be available without GFE?
Hopefully it is for 144hz
Hopefully it is for 144hz monitors also and not just the 165hz monitor.
I completely trust when a
I completely trust when a corporation promises me a fix at some unspecific time in the future. /s
Better than denying it though
Better than denying it though eh?
It depends. A promise can
It depends. A promise can turn to a lie. Denying a fix could be a honest reply if it can not be fixed.
The tone of Nvidia’s response
The tone of Nvidia’s response seems genuinely cooperative. They do not appear to be upset that this problem was found and are reacting publicly how I’d hope all companys would, with a “can do” attitude.
Also, I’m glad this issue can be resolved in a driver update. It just didn’t make sense that this behaviour was intentional or necessary for Nvidia GPUs.
They’ve had similar issues
They’ve had similar issues when connecting more then one monitor in the past. Where the clocks stay higher then they should.
Just like the laptop overclocking and various others as per GeForce Forums back and forth it gets re-introduced into the driver every so often.
Issues made public
Uproar
fix coming soon
3 month pass
Issue re-introduced
Repeat the cycle.
We’ve brought up several NV
We've brought up several NV driver issues in the past (most unpublished), and their record with us is that if they say a fix is incoming, we typically see it in the very next driver release. No reason to suspect otherwise here, especially with the enthusiasm of their reply.
I wonder if they’ll get
I wonder if they’ll get around to fixing the awful sluggishness inherent in their control panel interface.
The reintroduction of a bug
The reintroduction of a bug can happen very easily in source code control systems. They often branch of of a main line to work on new features. Sometimes a bug is fixed on the main line or on a branch which has been merged into the mainline. When the development branch is merged back in to the main line, the bug is accidentally reintroduced. This can easily happen when the code with the bug in it has been modified on the development branch. It is common practice to create a test case for each fixed bug to make sure it is not reintroduced in some manner. Some things are more difficult to test than others though.
Also, in such cases, it is
Also, in such cases, it is generally really easy to fix since it has been fixed before.
Thanks Ryan,
PCPer is the
Thanks Ryan,
PCPer is the best when it comes to looking out for the consumer. Now I just need Micro Center to finally get stock of the PG279Q.
this is why PCPer is still my
this is why PCPer is still my main source for reviews, because you lot keep them honest. Thanks guys.
How does this even get past
How does this even get past Nvidia?
Anywho, nice job PCper.
Thanks for bringing this to
Thanks for bringing this to Nvidia’s attention. Eagerly awaiting the fix for my 980 Ti.
-.-…..so….nvidia finally
-.-…..so….nvidia finally decided to fix this power drain issue on 144hz? Geez…..it has been complaint of many 144hz monitor users since Kepler card was launched..
They are only fixing it
They are only fixing it because there was a publication about it.
If there wasn’t one they still be denying it on their forums, business as usual.
You mean since Fermi
You mean since Fermi architecture… Iv’e got 2pcs og GTX580’s and a screen running 100hz this makes the primary card jump to 3D clocks eg. Somewhat kinda half the full 3D clock speed “in my case 405mhz” instead og the 50mhz that is the 2D clock speed.
This has been driving me insane fue to power usage and thus turning my PC into a spaceheater even though om not gaming on it…
Og I go to 110mhz on the monitor it gies into full 3D mode 950mhz
So please NVIDIA don’t just look at current Maxwell cards but the whole line up since Fermi!!!!
Good work PCper!
Good work PCper!
This is why we love PCPER.
This is why we love PCPER.
no no. we LOVE pcper because
no no. we LOVE pcper because of CANADA…
good ol’american CANADA
gj guys XD!
It seems that it had to come
It seems that it had to come from PCPerspective to make Nvidia respond. This shows that PCPerspective is something more than just one more site.
Why I am saying it? Because it seems that Nvidia cards have this problem for much time now. Just a quick Googling
5 months ago
https://www.reddit.com/r/nvidia/comments/38vonq/psa_nvidia_users_with_a_high_refresh_rate_monitor/
6/20/14
http://www.overclock.net/t/1497172/did-you-know-that-running-144-hz-causes-ridiculously-high-idle-temperatures-and-power-draw-on-your-nvidia-gpu
Mar 03 2013
http://linustechtips.com/main/topic/6019-switch-from-60hz-to-144hz/
ikr – it must be conspiratory
ikr – it must be conspiratory that nvidia responds to a review site’s email instead of reading/responding to reddit and forums posts . .
Yeah, it’s almost like they
Yeah, it’s almost like they have a better track record of knowing what they’re talking about then a bunch of randos on various forums.
I mean, who really needs credibility anyways?
(C’mon.)
Yeah, it’s almost like they
Yeah, it’s almost like they have a better track record of knowing what they’re talking about then a bunch of randos on various forums.
I mean, who really needs credibility anyways?
(C’mon.)
”Guess what? You were right!”
”Guess what? You were right!” … no comment
Seems like this problem is much older, BUT nVidia did… nothing till now…
Are nvidia going to fix this issue or not?
Best regards PCPerspective!
I’m surprised to hear that
I’m surprised to hear that this problem is “fixable”. It seems like you would need a certain clock speed to push as many frames as one would need for 144 Hz and above.
Not with AMD hi end GPUs
Not with AMD hi end GPUs based on PCPer’s tests.
The pixel clock thing was
The pixel clock thing was just a working theory really. It was busted as soon as we were able to push a different 25×14 panel at 144 without seeing the same power increase. This means the issue is more likely (or in this case, can be) fixable with driver level power management tweaks.
Just wanted to say thanks for
Just wanted to say thanks for this work. I always thought the higher power draw, etc. at 144hz was normal, glad to hear it will (hopefully) get fixed.
Yeah nVidia has F’ed up so
Yeah nVidia has F’ed up so many times this year. Hopefully next gen AMD is worth switching to.
Thanks, Obama.
On a serious
Thanks, Obama.
On a serious note, I’m glad Nvidia listened to you.
Do you think they’ll be bringing the “fix” to previous generation cards like Kepler and such? Or will it just be for Maxwell?
I’m personally still running
I'm personally still running SLI 680s, and will test any update / report on that config as well. Given that multiple platforms show a similar type of issue, I suspect the fix should work for all that are impacted.
It’s such a first world
It’s such a first world problem, but quite annoying to power users.
BTW, did you know your GTX 680s are limited to 1.15v? I can unlock them to 1.21V and get rid of TDP or temperature throttling. Wink wink.
You get the same problem when
You get the same problem when you plug in more than two monitors.
nice work guys!
nice work guys!
This issue has been going on
This issue has been going on for years now, and now that press is finally paying attention to this nvidia decides to do something about it?