Custom Resolution Utility (CRU)

[ToastyX]

(02-09-2022 01:41 AM)JayBee Wrote:  Still convinced it has something to do with the big amount of data in the EDID report, as all devices with EDID copy function I tested with it also had issues (usually breaking several features).

Where are you seeing a big amount of data? The EDID dump looks perfectly fine, and CRU reads everything just fine. I also checked with edid-decode, and it didn't report any issues. The crash is definitely an NVIDIA driver bug as other people with NVIDIA GPUs have reported the issue with some displays.

What changes are you making? The only potential issue I see is the 4:2:0 capability map defines the first 8 TV resolutions as 4:2:0 resolutions, but if you have at least 8 TV resolutions, then the data is still valid, although maybe not what you want. You can delete the capability map if you're not using 4:2:0.