Custom Resolution Utility (CRU)

[ToastyX]

(05-13-2019 08:28 PM)SirHawk Wrote:  In example, I currently run 70Hz with timings set as in the screenshot from post #4011 but I had to lower pixel clock to 165MHz to be listed (and working without any random noise).

Those timing parameters at 165 MHz would be 68 Hz, not 70 Hz.

(05-13-2019 08:28 PM)SirHawk Wrote:  If I am to exceed this 165MHz, the custom resolution is not even listed at all.

Is this with HDMI-DVI or plain DVI? With HDMI-DVI, that would mean the patch is not working. With plain DVI, that should not happen because the driver should list anything up to 330 MHz even without the patch. The only difference is without the patch, anything beyond 165 MHz will send a dual-link signal, while with the patch, anything up to 230 MHz will send a single-link signal.

(05-13-2019 08:28 PM)SirHawk Wrote:  Concerning the noise - it's just some pixels going white and blinking, as in the screenshot shows. Depending on how wrong timings are, they appear in different quantity on whole screen or contrasting edges. They're like a badly tuned TV.

That would mean the monitor can't handle the timing parameters, but I've never seen that vary between different video cards, so I'm not sure what's going on.

(05-13-2019 08:28 PM)SirHawk Wrote:  - On 290X with dual DVI-D Dual Link cable exceeding 66Hz refresh rate resulted in screen being torn, red, green and blue pixels were visible all over the screen, you could see pieces of the image that should be displayed distorted as well. It was also a bit zoomed in.

That would make sense with the "LCD native" timing parameters if the driver wasn't patched because it would send a dual-link signal, while the monitor expects a single-link signal. That should not happen if the driver is patched. HDMI/DisplayPort-DVI would not have this issue since it's always single-link.