Custom Resolution Utility (CRU)

[ToastyX]

(02-24-2016 12:31 PM)albertfu Wrote:  By using DP port of a 290X tri-crossfire configuration, "Pixel Clock Patcher" shouldn't be needed right ?

The patch does nothing for DisplayPort, but pixel clock limitations can still exist.

(02-24-2016 12:31 PM)albertfu Wrote:  What is the reason of CRU's limitation upon refresh rate ?
(4K in LCD standard mode gives a 73Hz maxi refresh rate, anything above is forbidden in red color)

That's an EDID limitation. It's not possible to define a pixel clock greater than 655.35 MHz. Higher pixel clocks would require the DisplayID standard, which isn't widely used yet.

(02-24-2016 12:31 PM)albertfu Wrote:  Why refresh rate that can be chosen in Windows is lower than in CRU ?
(4K in LCD standard mode gives a 67Hz maxi refresh rate, anything above can't be displayed in scroll down list)

That's a driver limitation. I'm not sure what limit you're running into, but it looks like the driver is not allowing a horizontal scan rate greater than 150 kHz, which I haven't seen before.

(02-24-2016 12:31 PM)albertfu Wrote:  BTW, how does OCing of monitor impact its lifespan ? I'd like to hear from a forum dedicated to that.

That depends on the hardware. There's no way to know for sure, but something like 75 Hz shouldn't be an issue.