Custom Resolution Utility (CRU)

[ToastyX]

(12-22-2015 01:54 PM)kaftul Wrote:  Does this mean that my monitor, even though its DVI port physically has all the dual-link pins, is actually only capable of processing single-link signals?

That's normally the case with 1920x1080 monitors. Only 120/144 Hz monitors have dual-link DVI.

(12-22-2015 01:54 PM)kaftul Wrote:  I also managed to reach 72 Hz with a pixel clock of less than 165 Hz while keeping the vertical total the same as the standard profile to keep my card at correct idle clocks but with 75 Hz, if I use the reduced profile to have a pixel clock of less than 165 MHz, my card will not go down to idle clocks anymore and if I keep the vertical total the same as the standard profile for correct idle clocks, I cannot bring the horizontal total low enough for the pixel clock to be lower than 165 MHz. Is there any way I can get 75 Hz with correct idle clocks for my GPU?

This is under 165 MHz for 75 Hz, but I don't know if your monitor will accept it:

H: 1920 8 16 16
V: 1080 3 5 31
75 Hz = 164.50 MHz pixel clock

Monitor limits are usually not exact, so you might be able to get away with slightly more than 165 MHz with the patch:

H: 1920 16 16 16 or 1920 8 16 24
V: 1080 3 5 31
75 Hz = 165.18 MHz pixel clock

You might have better luck with HDMI. 7000-series and newer cards don't need the patch if HDMI support is defined in the extension block, and the monitor might accept higher pixel clocks with HDMI.

(12-22-2015 01:54 PM)kaftul Wrote:  P.S. CRU reads the maximum pixel clock of my monitor as 170 Hz but I am not sure if that means what I think it does.

The range limits descriptor is informational and doesn't always reflect what the monitor will accept, which is why CRU doesn't include it by default. The maximum pixel clock can only be defined as a multiple of 10, so it's often defined as 170 MHz instead of 165 MHz.