Custom Resolution Utility (CRU)

[AchillesBoi]

(11-22-2020 07:17 PM)ToastyX Wrote:  

(11-22-2020 07:04 PM)AchillesBoi Wrote:  Sorry for the late response. I've exported the file after using restart-64.exe and I have attached it to this reply (I think). Thank you for the help, I really appreciate it.

Is this with DisplayPort? Try deleting the HDMI data block in the extension block. I don't know why some DisplayPort monitors include that block.

If that doesn't help, try importing this with "Import complete EDID" enabled:


That should remove 10 bpc color, which might work around the driver bug.

I tried removing the HDMI data block, same results. I tried using the profile you provided, same results. I tried manually selecting 8 bpc from Radeon Settings while on an overclocked profile, same results.

It seems like any change I make in CRU, no matter how big or small, will trigger the bug. Even if I only delete things instead of adding or editing them it will trigger the bug. If I so much as touch the EDID it will trigger the bug.

A new driver version came out recently and I clean-installed it but the bug is still present. I downgraded to several older versions from months ago to try to find one that works but the bug is present in all driver versions. The only way to avoid the bug is to use reset-all.exe then restart-64.exe (or reboot) and then not use CRU at all.

(I am using DisplayPort)