EVGA

Multi-monitor idle power/clock bug

Author
tox1c90
New Member
  • Total Posts : 18
  • Reward points : 0
  • Joined: 4/18/2015
  • Status: offline
  • Ribbons : 0
Saturday, November 03, 2018 3:25 PM (permalink)
Hi!
 
I have a problem with idle clocks of my new EVGA RTX 2080 XC Gaming.
This is my monitor setup:
1. Display-Port: ViewSonic XG2703 (G-Sync), running 1440p @ 144 Hz
2. Display-Port: DELL U2414h, running 1080p @ 72 Hz (slightly overclocked using custom timings)
The purpose of this slight overclock is to have both refresh rate being an integer multiply of each other. Otherwise I experience bad stutter on my U2414h, because 144/60 = 2.4 and Windows Display Manager is not able to handle this properly.
 
Problem is, that while my old card (EVGA GTX 970 FTW+) was running in these conditions with idle clock (it didn't matter if I have the DELL running at 72 or 60 Hz), the new EVGA 2080 XC is not able to do this.
If I put the DELL to 60 Hz, I get 300 Mhz GPU clock in idle, as soon as I put it to 72 Hz, I get 1200 MHz idle clock.
 
In principle, it should be even easier for the card to do 144/72 instead of 144/60. This together with the fact that the 970 was able to do it, I assume it's just a bug, which EVGA might be able to solve in a BIOS update?
Or are there any other suggestions?
 
 
 
#1

5 Replies Related Threads

    d.burnette
    CLASSIFIED Member
    • Total Posts : 3508
    • Reward points : 0
    • Joined: 3/8/2007
    • Status: offline
    • Ribbons : 17
    Re: Multi-monitor idle power/clock bug Saturday, November 03, 2018 3:51 PM (permalink)

    Don 
     
     
    EVGA Z390 Dark MB | i9 9900k CPU @ 5.2 GHz all cores | EVGA RTX 3090 FTW3 Ultra | 32 GB G Skill Trident Z 3200 MHz CL14 DDR4 Ram | Corsair H150i Pro Cooler | EVGA T2 Titanium 1000w Power Supply | Samsung 970 Pro 1TB m.2 Nvme | Samsung 970 Evo 1TB m.2 Nvme | Samsung 860 Evo 1TB SATA SSD | EVGA DG 87 Case |
     
     
     
     
     
     
     
     
     
     
    #2
    somethingc00l
    EGC Admin
    • Total Posts : 752
    • Reward points : 0
    • Joined: 3/14/2009
    • Status: offline
    • Ribbons : 11
    Re: Multi-monitor idle power/clock bug Saturday, November 03, 2018 10:01 PM (permalink)
    Have you tried running 60/144 and seeing if you still get the stutter? I think they might have fixed that issue on the 20 series cards.
    #3
    tox1c90
    New Member
    • Total Posts : 18
    • Reward points : 0
    • Joined: 4/18/2015
    • Status: offline
    • Ribbons : 0
    Re: Multi-monitor idle power/clock bug Saturday, November 03, 2018 11:07 PM (permalink)
    somethingc00l
    Have you tried running 60/144 and seeing if you still get the stutter? I think they might have fixed that issue on the 20 series cards.


    Yes, I have it now @ 144/60 and unfortunately it's still stuttering like hell, as it was before with the 970.
     
    d.burnette
    Compliments of Sajin:

     
    Works great for me.
     

     
    Thanks, I might try that… but still I think it's a bug on hardware/BIOS side that should be fixed there. I don't think it's meant to be like that, the 2080 shouldn't have less capabilities in this regard compared to a 970.
    #4
    GTXJackBauer
    Omnipotent Enthusiast
    • Total Posts : 10335
    • Reward points : 0
    • Joined: 4/20/2010
    • Location: (EVGA Discount) Associate Code : LMD3DNZM9LGK8GJ
    • Status: offline
    • Ribbons : 48
    Re: Multi-monitor idle power/clock bug Sunday, November 04, 2018 3:52 AM (permalink)
    tox1c90
     
     
    Yes, I have it now @ 144/60 and unfortunately it's still stuttering like hell, as it was before with the 970.
     
    Thanks, I might try that… but still I think it's a bug on hardware/BIOS side that should be fixed there. I don't think it's meant to be like that, the 2080 shouldn't have less capabilities in this regard compared to a 970.




    If your GPU is stuttering like it was with your previous GPU, it could be something wrong with your PC's hardware and or software side.
     
    Check your task manager and see if there's any load on the GPU while idle.

     Use this Associate Code at your checkouts or follow these instructions for Up to 10% OFF on all your EVGA purchases:
    LMD3DNZM9LGK8GJ
    #5
    tox1c90
    New Member
    • Total Posts : 18
    • Reward points : 0
    • Joined: 4/18/2015
    • Status: offline
    • Ribbons : 0
    Re: Multi-monitor idle power/clock bug Sunday, November 04, 2018 8:55 AM (permalink)
    GTXJackBauer

    If your GPU is stuttering like it was with your previous GPU, it could be something wrong with your PC's hardware and or software side.
     
    Check your task manager and see if there's any load on the GPU while idle.


    You didn't get the point, the stuttering has nothing to do with the GPU or Nvidia and I didn't really want to discuss the stuttering part here as it is distracting from the main topic.

    It is a known problem of Microsoft DWM for ages.
    Whenever you have multiple monitors that are running with refresh rates that are not integer multiplies of each other, the secondary display will stutter.

    DWM is doing all the rendering stuff at 144 Hz of your primary display and forcing Vsync. If the secondary display is running at 72 Hz, all it needs to do is display just every second frame on it - > FINE.

    At 60 Hz, it needs to display every 2.4th frame, which is not possible so it will have to skip frames - > stuttering.

    At the moment it is technically impossible to have a 144/60 setup run without stuttering on one of two screens on windows desktop, because DWM can NOT render the desktop independently for both screens. It wants to be in Vsync for both displays simultaneously, which is only possible for setups like 120/60, 144/72.
    If I connect my laptop (Intel GPU, 60Hz) to a 144 Hz monitor and extend the desktop, it's completely the same thing.


    I already wrote in my main post, if I have it at 144/72, all stutter is completely gone! It's just a problem of the 2080 not running at idle clocks then, while the 970 was.
    post edited by tox1c90 - Sunday, November 04, 2018 9:00 AM
    #6
    Jump to: