Custom Resolution Utility (CRU)

[Drew707]

Hey, Toasty; thank you so much for this utility. I had no idea it existed and was pulling my hair out until SurfaceDockGuy on Reddit sent me your way.

I have a Surface Book 2 13" i7/1050 (3000x2000@59), an LG 2560x1440 I've dropped to 30, and an LG 2560x2880 that I was previously able to drop to 30 so I could run all three monitors, but something happened a couple weekends ago, and now I cannot get it to save 2560x2880@30. CRU says a restart is required, but I have restarted multiple times to no avail. The highest resolution available in settings is 2560x2048@59. This was working for many weeks before whatever happened happened. Running 11 Pro, 22H2, Build 22621.2283.

Any idea is greatly appreciated.

[windenchanter]

Thank you for creating this utility.

I have an old ASUS VE247H.

I was using CRU for a while to enable 1920x1080 resolution and it has been working.
However, it just happened recently the monitor is not recognized and only works under 1024x768 resolution, and Windows 11 detected it as a Generic Non-PnP Monitor.
When I tried to use CRU, there was this "(restart required)" text following the device. And this monitor is not showing as "(active)". Restarting the computer and using restart.exe and restart64.exe does not change the status of this "(restart required)".

Any suggestions why this is the case? I am using a Nvidia 2060 mobile GPU and updated to the latest driver.

[ToastyX]

(09-27-2023 11:00 PM)windenchanter Wrote:  Thank you for creating this utility.

I have an old ASUS VE247H.

I was using CRU for a while to enable 1920x1080 resolution and it has been working.
However, it just happened recently the monitor is not recognized and only works under 1024x768 resolution, and Windows 11 detected it as a Generic Non-PnP Monitor.
When I tried to use CRU, there was this "(restart required)" text following the device. And this monitor is not showing as "(active)". Restarting the computer and using restart.exe and restart64.exe does not change the status of this "(restart required)".

Any suggestions why this is the case? I am using a Nvidia 2060 mobile GPU and updated to the latest driver.

You shouldn't need to use CRU to enable 1920x1080. Generic Non-PnP Monitor means the graphics driver is not getting a valid EDID from the monitor, so either the EDID is corrupted on the monitor, which can happen sometimes with old monitors, or something is wrong with the cable. Windows 11 ignores EDID overrides for monitors without a valid EDID, which Windows lists as Generic Non-PnP Monitor, so CRU will not work in this case.

You have three options:

1. The easiest option would be if you're using the DVI port on the monitor, try using the HDMI port, or vice versa. Usually each port has a separate EDID, so the other one might not be corrupted. HDMI-DVI cables/adapters work in both directions, so you should be able to convert between them easily if needed.

2. If you're using HDMI on the computer's end, you can get one of these to emulate a proper EDID: https://www.amazon.com/dp/B07YMS18T7/?tag=mtests-20#ad

3. If you have access to an AMD/ATI GPU, I have a program that can fix the EDID: https://www.monitortests.com/forum/Threa...yID-Writer

You will need to figure out a way to enter the service menu, which usually involves holding down the menu button while powering on the monitor for ASUS monitors. Then press the menu button to enter the service menu, and enable "burn in mode" to disable write protection. Then you should be able to use EDWriter to read the EDID, which should give you an option to fix the EDID if it's corrupted, and then write the fixed EDID to the monitor.

[ToastyX]

(09-26-2023 05:53 PM)Drew707 Wrote:  Hey, Toasty; thank you so much for this utility. I had no idea it existed and was pulling my hair out until SurfaceDockGuy on Reddit sent me your way.

I have a Surface Book 2 13" i7/1050 (3000x2000@59), an LG 2560x1440 I've dropped to 30, and an LG 2560x2880 that I was previously able to drop to 30 so I could run all three monitors, but something happened a couple weekends ago, and now I cannot get it to save 2560x2880@30. CRU says a restart is required, but I have restarted multiple times to no avail. The highest resolution available in settings is 2560x2048@59. This was working for many weeks before whatever happened happened. Running 11 Pro, 22H2, Build 22621.2283.

Any idea is greatly appreciated.

How did you drop it to 30 Hz before? CRU often has no effect on laptop screens with Intel GPUs because of driver restrictions. If something changed that used to work before, then Windows probably updated the driver to a newer version automatically, and the newer driver either has a bug or some new restriction that's preventing you from getting the correct resolutions. You should probably report this to Intel support.

[ToastyX]

(09-26-2023 08:12 AM)Dinkles Wrote:  Thanks toasty,
I’ll run this after work and post the results shortly.

Will it assist much though if we are unable to set native res above 4095?

If the nVidia driver is picking it up wrong, can we amended that so the driver/card/monitor recognise the “actual” recommended resolution of 5120 as its honestly so frustrating having the monitor reset every time I switch to my other monitor and not being able to use things like scaling etc as they all try to scale to the incorrect “recommended” resolution.

You’d think nVidia/Microsoft and AOC could get the basics.

I’ll run this asap and post the results..

I just want to see if the monitor is defining the correct native resolution or if it's an NVIDIA driver issue. It's possible to make the native resolution higher with CRU if you delete all the other resolutions, which includes anything in extension blocks and data blocks.

[windenchanter]

(09-28-2023 04:33 AM)ToastyX Wrote:  

(09-27-2023 11:00 PM)windenchanter Wrote:  Thank you for creating this utility.

I have an old ASUS VE247H.

I was using CRU for a while to enable 1920x1080 resolution and it has been working.
However, it just happened recently the monitor is not recognized and only works under 1024x768 resolution, and Windows 11 detected it as a Generic Non-PnP Monitor.
When I tried to use CRU, there was this "(restart required)" text following the device. And this monitor is not showing as "(active)". Restarting the computer and using restart.exe and restart64.exe does not change the status of this "(restart required)".

Any suggestions why this is the case? I am using a Nvidia 2060 mobile GPU and updated to the latest driver.

You shouldn't need to use CRU to enable 1920x1080. Generic Non-PnP Monitor means the graphics driver is not getting a valid EDID from the monitor, so either the EDID is corrupted on the monitor, which can happen sometimes with old monitors, or something is wrong with the cable. Windows 11 ignores EDID overrides for monitors without a valid EDID, which Windows lists as Generic Non-PnP Monitor, so CRU will not work in this case.

You have three options:

1. The easiest option would be if you're using the DVI port on the monitor, try using the HDMI port, or vice versa. Usually each port has a separate EDID, so the other one might not be corrupted. HDMI-DVI cables/adapters work in both directions, so you should be able to convert between them easily if needed.

2. If you're using HDMI on the computer's end, you can get one of these to emulate a proper EDID: https://www.amazon.com/dp/B07YMS18T7/?tag=mtests-20#ad

3. If you have access to an AMD/ATI GPU, I have a program that can fix the EDID: https://www.monitortests.com/forum/Threa...yID-Writer

You will need to figure out a way to enter the service menu, which usually involves holding down the menu button while powering on the monitor for ASUS monitors. Then press the menu button to enter the service menu, and enable "burn in mode" to disable write protection. Then you should be able to use EDWriter to read the EDID, which should give you an option to fix the EDID if it's corrupted, and then write the fixed EDID to the monitor.

Thank you for your valuable suggestions.
I will look into the debugging options. Its great to know that windows 11 will not accept override when monitor is not supplying valid EDID. I know understand it's just an issue with the monitor or HDMI cable.
I used Nvidia control panel to set custom resolution, its working but since the real resolution is still 1024x768, it's just a bit blurry. I think that works for me for office work for now, but if I will also try a new HDMI cable to see if that is the problem (the two cables I swapped and tried already are both old cables)

[ToastyX]

(09-28-2023 03:16 PM)windenchanter Wrote:  Thank you for your valuable suggestions.
I will look into the debugging options. Its great to know that windows 11 will not accept override when monitor is not supplying valid EDID. I know understand it's just an issue with the monitor or HDMI cable.
I used Nvidia control panel to set custom resolution, its working but since the real resolution is still 1024x768, it's just a bit blurry. I think that works for me for office work for now, but if I will also try a new HDMI cable to see if that is the problem (the two cables I swapped and tried already are both old cables)

NVIDIA control panel custom resolutions should not be blurry. You're doing something wrong. The real resolution should not be 1024x768 unless you set it that way. You need to set the active pixels to the resolution you want, not just the display mode.

If you already tried two cables, then the cable is not the problem. HDMI cables usually don't break that way even if they are old, so the monitor probably has a corrupted EDID. If you are using the HDMI port on the monitor, the easiest option would be to try using the DVI port on the monitor with an HDMI-DVI cable/adapter because the DVI port might have a different EDID that's not corrupted.

[windenchanter]

Thank you!
You are correct! I tried another HDMI cable, it's still the same issue.
Then I switched to DVI with an HDMI to DVI adapter (I took from another computer), and it started to work again and my computer actually knows the monitor's name.

(09-28-2023 03:46 PM)ToastyX Wrote:  

(09-28-2023 03:16 PM)windenchanter Wrote:  Thank you for your valuable suggestions.
I will look into the debugging options. Its great to know that windows 11 will not accept override when monitor is not supplying valid EDID. I know understand it's just an issue with the monitor or HDMI cable.
I used Nvidia control panel to set custom resolution, its working but since the real resolution is still 1024x768, it's just a bit blurry. I think that works for me for office work for now, but if I will also try a new HDMI cable to see if that is the problem (the two cables I swapped and tried already are both old cables)

NVIDIA control panel custom resolutions should not be blurry. You're doing something wrong. The real resolution should not be 1024x768 unless you set it that way. You need to set the active pixels to the resolution you want, not just the display mode.

If you already tried two cables, then the cable is not the problem. HDMI cables usually don't break that way even if they are old, so the monitor probably has a corrupted EDID. If you are using the HDMI port on the monitor, the easiest option would be to try using the DVI port on the monitor with an HDMI-DVI cable/adapter because the DVI port might have a different EDID that's not corrupted.

[Drew707]

(09-28-2023 04:35 AM)ToastyX Wrote:  

(09-26-2023 05:53 PM)Drew707 Wrote:  Hey, Toasty; thank you so much for this utility. I had no idea it existed and was pulling my hair out until SurfaceDockGuy on Reddit sent me your way.

I have a Surface Book 2 13" i7/1050 (3000x2000@59), an LG 2560x1440 I've dropped to 30, and an LG 2560x2880 that I was previously able to drop to 30 so I could run all three monitors, but something happened a couple weekends ago, and now I cannot get it to save 2560x2880@30. CRU says a restart is required, but I have restarted multiple times to no avail. The highest resolution available in settings is 2560x2048@59. This was working for many weeks before whatever happened happened. Running 11 Pro, 22H2, Build 22621.2283.

Any idea is greatly appreciated.

How did you drop it to 30 Hz before? CRU often has no effect on laptop screens with Intel GPUs because of driver restrictions. If something changed that used to work before, then Windows probably updated the driver to a newer version automatically, and the newer driver either has a bug or some new restriction that's preventing you from getting the correct resolutions. You should probably report this to Intel support.

Sorry for the confusion. I've left the laptop screen as it was. It was the two LG externals (2560x1440 and 2560x2880) that I dropped to 30 via CRU. They were working fine on a Friday, and then the custom resolution for the 2880 screen disappeared on Monday.

[Dinkles]

(09-28-2023 04:36 AM)ToastyX Wrote:  

(09-26-2023 08:12 AM)Dinkles Wrote:  Thanks toasty,
I’ll run this after work and post the results shortly.

Will it assist much though if we are unable to set native res above 4095?

If the nVidia driver is picking it up wrong, can we amended that so the driver/card/monitor recognise the “actual” recommended resolution of 5120 as its honestly so frustrating having the monitor reset every time I switch to my other monitor and not being able to use things like scaling etc as they all try to scale to the incorrect “recommended” resolution.

You’d think nVidia/Microsoft and AOC could get the basics.

I’ll run this asap and post the results..

I just want to see if the monitor is defining the correct native resolution or if it's an NVIDIA driver issue. It's possible to make the native resolution higher with CRU if you delete all the other resolutions, which includes anything in extension blocks and data blocks.

Hey,
Thanks for checking this for me, here is the attached test file as requested, and a screenshot of the NCP showing that the "recommended" resolution vs the actual native resolution.

The monitor is connected via DP and i have tried both DP1/DP2 neither of which make a difference.

I am using a very expensive DP cable capable of DP2.0 8k VESA certified etc.

The monitor works fine, but if i switch to my 4k TV it defaults back to the "recommended" resolution when return and scaling in games simply scales to the incorrect resolution.

Anything you can do to help would be much appreciated.

Thanks again.

Edit:
Here is a link to the driver for the monitor i am using and you can see the specs are 5120x1440@120 hz etc.
https://aoc.com/uk/gaming/products/monit.../downloads

I am also using an nVidia RTX 3080 with driver version 537.34 but its been like this through multiple driver revisions.

The generic monitor in the pic attached is my 4k LG TV. Removing this from the menu and/or disabling it and/or removing the HDMI etc does not change the behavior.


Edit 2:
I noticed in the specs that the monitor supports "DP ALT Mode"
**USB-C 3.2 x 1 (DP alt mode, upstream, power delivery up to 65 W)**

Could it be that the monitor is reporting the maximum resolution supported by DP ALT Mode (DP over USB-C) even though i am not using USB-C / DP ALT Mode or DP over USB-C etc?
https://aoc.com/uk/gaming/products/monit...cification

If so could this be removed from the monitor/driver etc as its not something i would ever use anyway?

Edit 3:
I read this (about the v2 of this monitor)
https://totalgamingaddicts.com/aoc-agon-...x2-review/
https://www.displayninja.com/aoc-ag493ucx2-review/

Which states interestingly that the max resolution supported on the AG493UCX using DP ALT Mode (DP over USB-C) is 3840x1080 however this has been increased on the v2 model to 5120x1440 but at a reduced refresh rate.

Again, as i don't use DP ALT Mode or DP Over USB-C or even the USB ports of the monitor at all, is there anyway we can get around this and stop it reporting the (which i now assume) DP ALT Mode resolution?


Edit4:
I have added an interesting screen grab from that site above, it does seem that its reporting the DP ALT Mode resolution as that's far to much of a coincidence?


Edit 5:
Here is the driver for the V2 version of this monitor of that is useful (for reference purposes).
https://aoc.com/api/frontberg/downloadab...Signed.zip