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!
I’ve seen multiple sites
I’ve seen multiple sites bring up this issue but this is the only one that went to the source for a resolution, much respect.
Multiple sites brought up
Multiple sites brought up this issue only after PCPer wrote their story about it, which only happened because a commenter brought it up in a thread on PCPer and it drew the staff’s attention enough to investigate.
So, for the PCPer folks and (some of) the commenters, even more much respect. 🙂
Umm tested your theory on my
Umm tested your theory on my ASUS 24″ NON G-Sync 144mhz monitor and the bug is also effecting it. The bug is present at any refresh rate above 60mhz. So 80mhz, 100mhz, 120mhz and 144mhz. GPUZ is setting at 961mhz.
Set up:
X3 24″ ASUS VG248QE monitors
X1 MSI 980 Gaming GPU
X1 ASUS P8Z77-V MOBO
X1 I7 3770K 4.5 H2o
X4 8GB Corsair Dominator
Wondows 7 pro
GPU driver 358.87 11/4/2015
Nice work, this issue has
Nice work, this issue has been bugging me for quite a while.
Any chance yall can do one about the problem where Windows 10 + dual monitors + gsync on one of them often results in horrible, unusable stuttering? 🙂
5+ months and still no 390X
5+ months and still no 390X review
see comment thread for 380x
see comment thread for 380x announcement
I submitted this issue
I submitted this issue shortly after getting my Acer 144hz G-sync IPS monitor ~4 months ago and was told by NVIDIA (after waiting a month for a reply) that they “do not notice any aberrant behavior” on their end and to just “check my personal settings”.
Well, at least they are finally admitting it and (hopefully) working on a fix
Maybe they should test it
Maybe they should test it with a GTX 980 or GTX 780, and not the GTX 970? Who but NVIDIA knows if for some reason G-Sync is accessing the card’s 0.5GB memory segment on the GTX 970, and maybe that’s the problem?
About time…This has been an
About time…This has been an issue since I remember
any update on this? changing
any update on this? changing between 120Hz and 144Hz when i want to play games is getting annoying
Driver 359.06
Issue still
Driver 359.06
Issue still there.
..waiting for promised fix.
Also waiting for a fix.
Also waiting for a fix.
Come on Nvidia, you can fix
Come on Nvidia, you can fix it!
omg, they finally fixed this
omg, they finally fixed this with driver 361.43! My 980 Ti is finally resting at 135 core / 810 mem @ 144hz
WOW! THX GOD!
WOW! THX GOD!
That driver 361.43 won’t help
That driver 361.43 won’t help if you have dual mon.
Confirmed!! So annoying.
Confirmed!! So annoying.
Someone said that with 361.43
Someone said that with 361.43 they fixed the problem, i updated my driver to 361.75 and i still have the same problem 🙁
im have it too still
im have it too still
Bug still present.
Here’s the
Bug still present.
Here’s the deal. Their “fix” was the switch your main display to 120Hz (from 144Hz) when you turn on the second monitor, allowing the GPU to clock down to 135MHz. Some fix, eh? WTF? They ignore all new comments about it too, which leads me to believe there is no way to sort this out. *sigh*
Very anoying.. we are in 2019
Very anoying.. we are in 2019 and still no FIX from NVIDIA, and this article is from 2015…. RIP