Custom Resolution Utility (CRU)

[Petrushka]

(12-12-2025 11:54 PM)ToastyX Wrote:  

(12-12-2025 06:54 PM)Petrushka Wrote:  Okay thanks @ToastyX! I did try disabling DDC/CI in the monitor's OSD. Unplugging the monitor's power for a minute to reset the monitors, factory resetting the monitors.

It seems a windows update started the issues as the monitors were working fine for a few months. would the DVI-D adapter bypass any handshake issues?

I was hoping that the CRU utility could force the correct resolution but I guess that is not possible with this bug?

CRU might be able to force the correct resolution with Windows 10 but not Windows 11 because Windows 11 ignores EDID overrides if the EDID can't be read. The U2412M doesn't have this issue with DVI, so an adapter should work.

Okay thanks! I was about to order DP to DVI-D active adapters when I decided to see if editing the windows registry would work. Here is what I did:

Check the PrimSurfSize.cx and PrimSurfSize.cy values: Navigate through the various keys in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuratio​n. In the right-hand pane, look at the PrimSurfSize.cx (width) and PrimSurfSize.cy (height) values. The entry showing the current low resolution (e.g., 640 and 480 in decimal) is likely your active monitor's configuration.

I basically changed all the monitors that listed only 640x480 to 1920x1200
the hexadecimal value for 1920 is 780 and for 1200 is 4b0 after making the changes. (I did backup up my registry by exporting it before making changes just in case) I rebooted the computer and got 1920 x 1200 back. You may need to do the above again after a display driver update.. but for now it seems like a fairly permanent and easy fix.

[Samba]

(05-10-2024 10:32 PM)ToastyX Wrote:  

(05-08-2024 07:14 PM)csobikaaa Wrote:  Any idea why it only shows 240Hz for FreeSync? It should be also 360Hz, or am I wrong?

The FreeSync data block can only define a maximum of 255 Hz. The data block is proprietary, so I don't know if there is a new way to define higher ranges. It might just be there for backward compatibility with older GPUs that don't support HDMI 2.1.

If I set the lower range to something like 180hz, for instance, will it change only the lower range, or am I gonna change the max range aswell(since I'm unable to set it to 360hz)?

Mine is at 255hz@1440p btw. Can't go higher than that(I can on Displayport... kinda regretting switching to HDMI).

[ToastyX]

(12-17-2025 03:28 AM)Samba Wrote:  If I set the lower range to something like 180hz, for instance, will it change only the lower range, or am I gonna change the max range aswell(since I'm unable to set it to 360hz)?

Mine is at 255hz@1440p btw. Can't go higher than that(I can on Displayport... kinda regretting switching to HDMI).

Latest version of CRU should support 360 Hz in the FreeSync data block.

[Samba]

(12-17-2025 03:41 AM)ToastyX Wrote:  

(12-17-2025 03:28 AM)Samba Wrote:  If I set the lower range to something like 180hz, for instance, will it change only the lower range, or am I gonna change the max range aswell(since I'm unable to set it to 360hz)?

Mine is at 255hz@1440p btw. Can't go higher than that(I can on Displayport... kinda regretting switching to HDMI).

Latest version of CRU should support 360 Hz in the FreeSync data block.

I'm on the latest version and it does support on Displayport.

On HDMI 2.1 it shows max range of 255hz on my monitor(Aorus FO27Q3) though.

Unless another version that fixed it was released this week(I just downloaded it a couple days ago)?

DP


HDMI 2.1


If I try to go over 255hz on HDMI the max value goes red and I can't apply the settings.

[ToastyX]

(12-17-2025 04:00 AM)Samba Wrote:  I'm on the latest version and it does support on Displayport.

On HDMI 2.1 it shows max range of 255hz on my monitor(Aorus FO27Q3) though.

Unless another version that fixed it was released this week(I just downloaded it a couple days ago)?

That's not the FreeSync data block. HDMI FreeSync doesn't use the range limits. Edit the FreeSync data block in the CTA-861 extension block.

[Samba]

(12-17-2025 02:06 PM)ToastyX Wrote:  

(12-17-2025 04:00 AM)Samba Wrote:  I'm on the latest version and it does support on Displayport.

On HDMI 2.1 it shows max range of 255hz on my monitor(Aorus FO27Q3) though.

Unless another version that fixed it was released this week(I just downloaded it a couple days ago)?

That's not the FreeSync data block. HDMI FreeSync doesn't use the range limits. Edit the FreeSync data block in the CTA-861 extension block.

Do you mean this one?



It was already set to 48-360hz. Do you mean I should set the limit I want to here instead of editing it in the monitor profile like I did with the displayport input?

I'm sorry, this is the first time I'm using the program. I don't know how to use it very well.

[ToastyX]

(12-17-2025 04:27 PM)Samba Wrote:  It was already set to 48-360hz. Do you mean I should set the limit I want to here instead of editing it in the monitor profile like I did with the displayport input?

Yes, if you have an AMD GPU. If you have an NVIDIA GPU, it's in the HDMI 2.1 data block, but you won't be able to raise the minimum beyond 48 Hz with HDMI VRR.

[GGoki]

CRU 1.5.3, nvidia 591.44 studio driver, ASUS RTX 5070ti prime


CRU cannot read native resolution of some displays anymore(LS32DG800S, MAG401QR)

how can I solve this?

[ToastyX]

(Yesterday 04:01 PM)GGoki Wrote:  CRU 1.5.3, nvidia 591.44 studio driver, ASUS RTX 5070ti prime


CRU cannot read native resolution of some displays anymore(LS32DG800S, MAG401QR)

how can I solve this?

By anymore, do you mean the EDID changed? Or do you mean for some newer displays? 42 is a different type of data block that CRU doesn't support yet. It will be a while before I add support because it's annoying to edit (varying descriptor sizes) and needs a new UI. It's basically a shorter way of defining resolutions using the CVT standard, so it doesn't give full control over the timing parameters. You can still add detailed resolutions separately, or delete the block and add the resolutions back manually. This is the first time I've seen the data block in the wild, so if you can export the EDID and post it here, that will help when I add support for it later.

[GGoki]

(Yesterday 04:55 PM)ToastyX Wrote:  

(Yesterday 04:01 PM)GGoki Wrote:  CRU 1.5.3, nvidia 591.44 studio driver, ASUS RTX 5070ti prime


CRU cannot read native resolution of some displays anymore(LS32DG800S, MAG401QR)

how can I solve this?

By anymore, do you mean the EDID changed? Or do you mean for some newer displays? 42 is a different type of data block that CRU doesn't support yet. It will be a while before I add support because it's annoying to edit (varying descriptor sizes) and needs a new UI. It's basically a shorter way of defining resolutions using the CVT standard, so it doesn't give full control over the timing parameters. You can still add detailed resolutions separately, or delete the block and add the resolutions back manually. This is the first time I've seen the data block in the wild, so if you can export the EDID and post it here, that will help when I add support for it later.

On RTX 5000-series graphics cards with the latest drivers, the native refresh rate no longer appears in CRU.
I’m not sure why this is happening, but I believe it’s an issue with the latest driver. The native refresh rate definitely used to be visible a few months ago.
Even in the case of the MAG401QR, this is not a cutting-edge display, and it is well within the pixel clock limit.
Or it could just be my misunderstanding, or it might only apply to the LS32DG800S.
Either way, I’ll extract the EDID file and share it with you later.