Custom Resolution Utility (CRU)

[IAmOrion]

(10-14-2022 07:57 PM)ToastyX Wrote:  I'm not aware of any issues with 22H2. Use the latest version of DDU to clean out all the old drivers: https://www.wagnardsoft.com/forums/viewtopic.php?t=4142

Then install the latest AMD driver: https://www.amd.com/en/support/kb/releas...in-22-10-1

Hmm interesting...

I already did that - although due to fortnite *still* being buggy with any AMD driver later than 22.2.2, I re-installed 22.2.2. But I was always on 22.2.2 as I disabled windows updating drivers etc so my only change is that Windows upgraded to 22H2

Anything later than 22.2.2 - for me at least, causes random 2-3 second freezes, where FPS drops to *ZERO* like it's a stutter or something.

I already overclocked the GPU (6700XT) and set min to just 50 lower than the max overclocked value and tweaked the rest and turned off ULSS (I think it was called ULSS from memory - was done via msi afterburner) - but again, all that was done prior to 22H2 and was fine without issue.

Perhaps I'll reinstall latest AMD just to see if CRU works again - maybe there's an issue with the combination of 22H2 and AMD 22.2.2

[Chunky1311]

I'm encountering a weird issue since upgrading to 22H2. Well, at least, I'm only now noticing it and am certain it wasn't present previously.
I can't think of anything else that has changed.

Making ANY change to the EDID of my LG CX using CRU causes issues with gsync.
It causes gsync to make the screen go black at any fps below 40fps.
This includes flickering black if the fps fluctuates even a moment to what would equal less than 40fps.
EXCEPT for 20fps exactly, this will show an image.
While this issue is present (a.k.a. after any alterations to the EDID using CRU) will also cause the PC to completely freeze and need a hard restart then toggling gsync on or off in the NVCP.

Literally all I did was change the HDR Metadata to suit my display.
What's extra odd, is even reverting the changes using CRU, does not fix the issue of the screen going black.
I need to use CRU's 'reset-all.exe' and NOT edit the EDID again whatsoever for gsync to operate properly.
I tested and this issue continues across the last 3 nvidia driver updates so I doubt it's driver related.

I'm happy to perform additional troubleshooting.

[trenx]

Hi, I have a similar issue after "upgrading to 22H2" - so many issues, what a nightmare...

Before, I had 119.88hz and 120.00hz refresh rates available that I could switch between freely, after upgrading I thought it best to use DDU and start the graphics drivers from scratch

Now, when I try to add these custom refresh rates it does add but they will always override one another:- I can have 120 but not 119.88, or I can have 119.88 but not 120

I guess whenever I want to change I can go into CRU and change it out but that's an extra step that wasn't required before.

Hope this can be fixed

[ToastyX]

(10-16-2022 11:37 AM)trenx Wrote:  Now, when I try to add these custom refresh rates it does add but they will always override one another:- I can have 120 but not 119.88, or I can have 119.88 but not 120

CRU does not have control over this. It's up to the graphics driver whether or not it can support multiple fractional refresh rates. Historically, Windows would consider both to be 120 Hz so only one would take effect.

[ToastyX]

(10-16-2022 08:16 AM)Chunky1311 Wrote:  I'm encountering a weird issue since upgrading to 22H2. Well, at least, I'm only now noticing it and am certain it wasn't present previously.
I can't think of anything else that has changed.

Making ANY change to the EDID of my LG CX using CRU causes issues with gsync.
It causes gsync to make the screen go black at any fps below 40fps.
This includes flickering black if the fps fluctuates even a moment to what would equal less than 40fps.
EXCEPT for 20fps exactly, this will show an image.
While this issue is present (a.k.a. after any alterations to the EDID using CRU) will also cause the PC to completely freeze and need a hard restart then toggling gsync on or off in the NVCP.

Literally all I did was change the HDR Metadata to suit my display.
What's extra odd, is even reverting the changes using CRU, does not fix the issue of the screen going black.
I need to use CRU's 'reset-all.exe' and NOT edit the EDID again whatsoever for gsync to operate properly.
I tested and this issue continues across the last 3 nvidia driver updates so I doubt it's driver related.

This is 100% an NVIDIA driver bug and should be reported to them.

[Peppe90]

(10-06-2022 02:21 PM)ToastyX Wrote:  Yes, but NVIDIA stores its settings in the registry.

Just made a try on the SD CRT Tv. Couldn't make anything to work

When I load the modified EDID with nvidia CP, it sees the actual original resolutions of the device from which I exported the EDID, it doesn't see any modification I made with CRU (only CRU see the modifications).

So, either I'm doing something wrong or there's some incompatibilities with my configuration.

I'm not even sure if the EDID from file function on nvidia CP, actually sends a signal (maybe is just an edid emulator for remote control...).

Anyway, I can keep trying hotswitching the cable from a VGA connected monitor, using CRU Automatic CRT settings as a clue to correctly tweak the values on Nvidia cp custom resolution tab.
That's the only way I'm 100% sure it could work (since I managed to perfectly see a 320x240 image on the SD CRT once).

[Chunky1311]

(10-16-2022 06:32 PM)ToastyX Wrote:  

(10-16-2022 08:16 AM)Chunky1311 Wrote:  I'm encountering a weird issue since upgrading to 22H2. Well, at least, I'm only now noticing it and am certain it wasn't present previously.
I can't think of anything else that has changed.

Making ANY change to the EDID of my LG CX using CRU causes issues with gsync.
It causes gsync to make the screen go black at any fps below 40fps.
This includes flickering black if the fps fluctuates even a moment to what would equal less than 40fps.
EXCEPT for 20fps exactly, this will show an image.
While this issue is present (a.k.a. after any alterations to the EDID using CRU) will also cause the PC to completely freeze and need a hard restart then toggling gsync on or off in the NVCP.

Literally all I did was change the HDR Metadata to suit my display.
What's extra odd, is even reverting the changes using CRU, does not fix the issue of the screen going black.
I need to use CRU's 'reset-all.exe' and NOT edit the EDID again whatsoever for gsync to operate properly.
I tested and this issue continues across the last 3 nvidia driver updates so I doubt it's driver related.

This is 100% an NVIDIA driver bug and should be reported to them.

I can report it to them, no worries.
Why does the issue not occur unless the EDID is edited, though?
Is there any extra info I could find to provide them?

EDIT: Setting the refresh rate to below 40hz using the NVCP also causes the screen to go black and stay black with gsync enabled.

[ToastyX]

(10-18-2022 02:49 AM)Chunky1311 Wrote:  I can report it to them, no worries.
Why does the issue not occur unless the EDID is edited, though?
Is there any extra info I could find to provide them?

The driver has a bug that triggers when any EDID override is present. I started getting reports of driver freezes/crashes with EDID overrides starting around driver version 471.11 or 471.41, so it's not exclusive to 22H2. I don't know what conditions trigger the bug because not everyone has the problem, and I haven't seen it myself.

[Chunky1311]

(10-18-2022 07:55 PM)ToastyX Wrote:  

(10-18-2022 02:49 AM)Chunky1311 Wrote:  I can report it to them, no worries.
Why does the issue not occur unless the EDID is edited, though?
Is there any extra info I could find to provide them?

The driver has a bug that triggers when any EDID override is present. I started getting reports of driver freezes/crashes with EDID overrides starting around driver version 471.11 or 471.41, so it's not exclusive to 22H2. I don't know what conditions trigger the bug because not everyone has the problem, and I haven't seen it myself.

Fair enough, that makes things difficult XD
Is there anything I can do that'd offer any insight?
I'll try a clean DDU install and see if it fixes anything.

[Peppe90]

(10-18-2022 07:55 PM)ToastyX Wrote:  

(10-18-2022 02:49 AM)Chunky1311 Wrote:  I can report it to them, no worries.
Why does the issue not occur unless the EDID is edited, though?
Is there any extra info I could find to provide them?

The driver has a bug that triggers when any EDID override is present. I started getting reports of driver freezes/crashes with EDID overrides starting around driver version 471.11 or 471.41, so it's not exclusive to 22H2. I don't know what conditions trigger the bug because not everyone has the problem, and I haven't seen it myself.

Also happened to me a freeze when trying a customized resolution from Nvidia cp on a LCD Tv (I created a custom res that the tv doesn't supports, normally it goes back after 15 secs. but this time it freezed in a black screen. Unplugging and plugging back the HDMI cable made the image to come back on screen but nvidia cp was freezed, I had to force it to close with Task manager).

Never happened to me before but I'm not sure it could be related to the use of CRU since it doesn't seem to do anything on my PC.

I tested the EDID emulation with the PC monitor (I loaded the HD CRT EDID on DP 2 with the monitor connected) and it correctly sends the signal from the EDID (indeed i got 1080i that's the main res of the HD-CRT, also i had all of his res selectable).

I edited the EDID with CRU again (I replaced 1080i and 720p with 576i and 480i), pressed ok and rebooted the PC but on both nvidia cp and windows mode list I always get the res from the original EDID as if it was not edited at all.

I don't know if it is windows preventing it from work or the gpu drivers.

One thing that works is the reset-all.exe on CRU folder. I can say it works because I got the aspect ratio setting on nvidia cp resetted, after running the exe and rebooting the PC. This make me think that the position where CRU points (where EDIDs are stored on registry) is correct. I wonder why custom res aren't applied.