Custom Resolution Utility (CRU)

[ToastyX]

(08-01-2015 05:37 PM)Haemato Wrote:  So I got all 3 EDID interceptor boards now and I went to test them. They work perfectly with AMD cards and with the 980ti too using the windows standard VGA driver. Once I load the nvidia drivers I get no video once I get to the windows login screen.

I think I've found the problem though. I was using CRU to generate the hardware EDID and it doesn't include the Monitor Range Limits Descriptor. I think the nvidia driver reads the EDID and sees that's missing and so doesn't complete the monitor plugin.

I doubt that's the problem. The monitor range limits descriptor is not required, and that information is not used for anything as far as I have seen. CRU does not include one because it would use up a detailed resolution slot, and it could interfere with custom resolutions if the driver actually did use that information.

I don't know what timing parameters you used, but if the pixel clock is not greater than 165 MHz, then there shouldn't be any issues with HDMI. Otherwise, you need to add an HDMI support data block in the extension block for the driver to accept higher pixel clocks unless you're using the pixel clock patcher. Make sure to run reset-all.exe if you're not using EDID overrides anymore. That will also reset the Windows screen resolution settings just in case it's stuck on some other unsupported resolution.