Custom Resolution Utility (CRU)

[ToastyX]

(08-11-2017 11:56 AM)GodlimaN Wrote:  Nope, don't think so!
https://gyazo.com/08a6f20c1d556689f180fd99dd6acdd4

Then it's an NVIDIA driver bug. CRU 1.3 automatically adds a blank extension block to work around this issue for monitors that do have an extension block by default, but apparently that triggers the bug for monitors that don't have any extension blocks.

Three solutions:

1. Use CRU 1.2.6 and choose the "No extension block" option to work around the problem.
2. Use HDMI. If you're using the pixel clock patch, you won't need it with HDMI.
3. Upgrade to Windows 10. NVIDIA's driver doesn't seem to have this issue with Windows 10.