Custom Resolution Utility (CRU)

[AchillesBoi]

(11-14-2020 02:20 PM)ToastyX Wrote:  

(11-14-2020 12:24 PM)AchillesBoi Wrote:  Hey ToastyX, I have an issue with CRU. My monitor is an Acer ET322QU (1440p 48-75hz). After using CRU, if I turn my monitor off then on again everything will look dim/faded even if I don't overclock anything. I know it's not my monitor acting strange because the cursor is still white and bright, my monitor's OSD still shows up bright, it is only the rest of the OS that looks dim. If I reset the display driver using restart64 or by pressing Win + Shift + Ctrl + B it will fix the issue, but will present itself again if I turn the monitor off and on.

I am using an RX 480 with the latest drivers (20.11.1), and I'm running the latest version of Windows 10 (October 2020 update). I should note that my monitor does not support HDR and I am not messing with HDR settings on CRU.

Another thing I noticed this bug is causing is that when I turn my monitor off/on the resolution switches to 1024x768 then back to native 1440p. It sucks because sometimes I'll have some windows open and when my monitor turns off/on all my windows are resized to a tiny square and it's frustrating to have to resize everything everytime. I used a remote desktop app to prove this, because when I turn off the monitor and then access my desktop using the remote app I can see how small everything is and I can go to the display settings and it tells me it's at a low resolution.

If I use reset-all.exe it fixes the problem entirely but I lose my overclock. I hope you can help us out because I found a good OC that is helpful for less input lag and would love to use it without having to work around this nasty bug (although it probably has something to do with AMD's drivers).

It's an AMD driver bug, so I don't know what to do about it. Are you using HDMI or DisplayPort? Does it happen with one or both? The issue with windows moving around is normal for DisplayPort because DisplayPort doesn't keep a connection when you turn the monitor off, but it shouldn't happen with HDMI.

I am using DisplayPort, and even though it loses connection when I turn the monitor off the resolution stays the same if I use default settings. The moment I use CRU the resolution will go all the way down when I turn the monitor off, so I am absolutely sure CRU is doing something here.

I have not tried with HDMI, but I hear DisplayPort is much better so I intend to use that. I have tried deleting all data from CRU: Established resolutions, Standard resolutions, Extension blocks, and all Detailed resolutions except for my OC, just to see if one of them is the culprit. Turns out it still suffers the bug regardless of what I put in CRU. If I touch anything in the slightest, even if I don't overclock anything, it will "activate" the bug.

Maybe CRU is missing an important Extension block that it's not adding by default?