Custom Resolution Utility (CRU)

[y.c]

Hello everyone,
I need your help with the following case.
My RX 7900 xt permanently clocks the VRAM boost at 2487 MHz.
I've already played around with cru, but I don't understand everything yet, so I just wanted to ask here if anyone knows the optimal settings for my monitor configuration.

1. Monitor: 3840x2160 144hz (Gigabyte M32U)
2. Monitor: 3440x1440 100hz (HP M34D)
3. Monitor: 1920x1080 75hz (ACER QG271)

I've already played around with the Hz numbers and the resolutions, but unfortunately I haven't been able to find the optimal settings.
I've already increased the blanking time a little, but I wasn't sure how high I could go. If anyone has an idea how I can reduce my VRAM clock speed, I would be very grateful.
All three monitors are needed, ideally with the appropriate resolution, theoretically I would only need the maximum Hz number on monitor 1.

thanks

[ToastyX]

(11-28-2024 10:02 PM)y.c Wrote:  Hello everyone,
I need your help with the following case.
My RX 7900 xt permanently clocks the VRAM boost at 2487 MHz.
I've already played around with cru, but I don't understand everything yet, so I just wanted to ask here if anyone knows the optimal settings for my monitor configuration.

1. Monitor: 3840x2160 144hz (Gigabyte M32U)
2. Monitor: 3440x1440 100hz (HP M34D)
3. Monitor: 1920x1080 75hz (ACER QG271)

I've already played around with the Hz numbers and the resolutions, but unfortunately I haven't been able to find the optimal settings.
I've already increased the blanking time a little, but I wasn't sure how high I could go. If anyone has an idea how I can reduce my VRAM clock speed, I would be very grateful.
All three monitors are needed, ideally with the appropriate resolution, theoretically I would only need the maximum Hz number on monitor 1.

The blanking periods must be synchronized on all three monitors to be able to change the VRAM clock. There's no way to synchronize the monitors with three different resolutions and three different refresh rates unless all the monitors support some form of variable refresh rate (M34d doesn't). This would happen on NVIDIA as well.

[banderman]

Hello i recently downloaded the CRU resolution changer and i deleted all resolutions and restarted my laptop now i have a black screen

[ToastyX]

(11-30-2024 08:47 AM)banderman Wrote:  Hello i recently downloaded the CRU resolution changer and i deleted all resolutions and restarted my laptop now i have a black screen

(09-07-2012 09:06 PM)ToastyX Wrote:  Before making any changes, familiarize yourself with booting Windows in safe mode using a recovery drive in case you can't see the screen. If you don't have a recovery drive, press and hold the power button to shut off the computer while Windows is booting. Doing this twice should give you recovery options that you can use to get into safe mode: Troubleshoot > Advanced options > Startup Settings > Restart

(09-07-2012 09:06 PM)ToastyX Wrote:  To reset a display back to the default configuration, use the "Delete" button at the top to delete the override from the registry and reboot. To reset all displays, run reset-all.exe and reboot. This can be done in safe mode if necessary.

[jeffeh12133]

Found a weird issue. When using CRU to add CVT-RB 1920x1080 143.981hz, upon reboot, my windows regedit shows VideoStandard as "255"

When deleting this CRU res and adding the same detailed res with nvidia custom resolution (CVT-RB 1920x1080 143.981hz in nvidia CP instead), i go into regedit:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Con​figuration\ACR0742TH5AA0038521_34_07E4_11^CC793B8FD95ECAE1C053C2FC37090D8E\00\00​

and it shows VideoStandard 3.

i looked up what VideoStandard means. https://learn.microsoft.com/en-us/window...l_standard

3 = D3DKMDT_VSS_VESA_CVT
255 = D3DKMDT_VSS_OTHER

to replicate, you might have to change your res to something lower, then back to the cvt-rb one in order to see the VideoStandard change between 255 and 3. CRU CVT-RB = VideoStandard 255, nvidia CVT-RGB = VideoStandard 3 (seems proper)

so despite adding a 143.981hz CVT-RB resolution in CRU, the regedit in windows always only shows 255 as the VideoStandard whereas adding CVT-RB via nvidia CP as a custom resolution shows the proper VideoStandard being 3 which means D3DKMDT_VSS_VESA_CVT according to above microsoft link.

[ToastyX]

(12-01-2024 12:01 AM)jeffeh12133 Wrote:  Found a weird issue. When using CRU to add CVT-RB 1920x1080 143.981hz, upon reboot, my windows regedit shows VideoStandard as "255"

When deleting this CRU res and adding the same detailed res with nvidia custom resolution (CVT-RB 1920x1080 143.981hz in nvidia CP instead), i go into regedit:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Con​figuration\ACR0742TH5AA0038521_34_07E4_11^CC793B8FD95ECAE1C053C2FC37090D8E\00\00​

and it shows VideoStandard 3.

i looked up what VideoStandard means. https://learn.microsoft.com/en-us/window...l_standard

3 = D3DKMDT_VSS_VESA_CVT
255 = D3DKMDT_VSS_OTHER

to replicate, you might have to change your res to something lower, then back to the cvt-rb one in order to see the VideoStandard change between 255 and 3. CRU CVT-RB = VideoStandard 255, nvidia CVT-RGB = VideoStandard 3 (seems proper)

so despite adding a 143.981hz CVT-RB resolution in CRU, the regedit in windows always only shows 255 as the VideoStandard whereas adding CVT-RB via nvidia CP as a custom resolution shows the proper VideoStandard being 3 which means D3DKMDT_VSS_VESA_CVT according to above microsoft link.

That shouldn't matter. I wouldn't expect VideoStandard to be accurate. Detailed resolutions don't have a way to specify what standard it is. The timing options in CRU are just calculators to help fill in the values. The driver probably reports all detailed resolutions as D3DKMDT_VSS_OTHER because otherwise it would have to calculate and compare all the timing standards for every resolution, which would be pointless work. NVIDIA control panel custom resolutions are a vendor-specific implementation, so if you choose CVT-RB, it knows what you chose.

[jeffeh12133]

(12-01-2024 01:18 AM)ToastyX Wrote:  

(12-01-2024 12:01 AM)jeffeh12133 Wrote:  Found a weird issue. When using CRU to add CVT-RB 1920x1080 143.981hz, upon reboot, my windows regedit shows VideoStandard as "255"

When deleting this CRU res and adding the same detailed res with nvidia custom resolution (CVT-RB 1920x1080 143.981hz in nvidia CP instead), i go into regedit:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Con​figuration\ACR0742TH5AA0038521_34_07E4_11^CC793B8FD95ECAE1C053C2FC37090D8E\00\00​

and it shows VideoStandard 3.

i looked up what VideoStandard means. https://learn.microsoft.com/en-us/window...l_standard

3 = D3DKMDT_VSS_VESA_CVT
255 = D3DKMDT_VSS_OTHER

to replicate, you might have to change your res to something lower, then back to the cvt-rb one in order to see the VideoStandard change between 255 and 3. CRU CVT-RB = VideoStandard 255, nvidia CVT-RGB = VideoStandard 3 (seems proper)

so despite adding a 143.981hz CVT-RB resolution in CRU, the regedit in windows always only shows 255 as the VideoStandard whereas adding CVT-RB via nvidia CP as a custom resolution shows the proper VideoStandard being 3 which means D3DKMDT_VSS_VESA_CVT according to above microsoft link.

That shouldn't matter. I wouldn't expect VideoStandard to be accurate. Detailed resolutions don't have a way to specify what standard it is. The timing options in CRU are just calculators to help fill in the values. The driver probably reports all detailed resolutions as D3DKMDT_VSS_OTHER because otherwise it would have to calculate and compare all the timing standards for every resolution, which would be pointless work. NVIDIA control panel custom resolutions are a vendor-specific implementation, so if you choose CVT-RB, it knows what you chose.

gotcha

i have displayport connected to an EDID 1.4 monitor. by default, the base EDID lists 1920x1080 60hz cta-861 timing as the preferred/native timing. i currently have it edited to use 1920x1080 143.981hz as the first base EDID detailed timing. is this ok to do or should i leave it at the cta-861 1920x1080 60hz and just include the 144hz as a displayID extension block

also about displayID extension blocks, my monitor probably doesnt support it but displayID 1.3 extension block works properly and identified any detailed res i create in there. is it ok to use displayID extension block despite this or does the monitor specifically have to support it for it to work properly? and do you recommend putting the cvt-rb 1920x1080 144hz timing in displayID or under base EDID first detailed timing?

i notice differences between both

[ToastyX]

(12-01-2024 01:53 AM)jeffeh12133 Wrote:  i have displayport connected to an EDID 1.4 monitor. by default, the base EDID lists 1920x1080 60hz cta-861 timing as the preferred/native timing. i currently have it edited to use 1920x1080 143.981hz as the first base EDID detailed timing. is this ok to do or should i leave it at the cta-861 1920x1080 60hz and just include the 144hz as a displayID extension block

also about displayID extension blocks, my monitor probably doesnt support it but displayID 1.3 extension block works properly and identified any detailed res i create in there. is it ok to use displayID extension block despite this or does the monitor specifically have to support it for it to work properly? and do you recommend putting the cvt-rb 1920x1080 144hz timing in displayID or under base EDID first detailed timing?

i notice differences between both

You keep focusing on things that don't matter. Although the first detailed resolution is considered the preferred resolution and refresh rate, Windows only cares about the resolution part for determining the native resolution, so it doesn't matter which refresh rate is first. The monitor doesn't need to support anything to use DisplayID. It's just a data structure that describes what the monitor can do. The same resolution and timing parameters should behave the same as the EDID version. The only difference with DisplayID is it's not limited to 4095x4095 or 655.35 MHz pixel clock, and DisplayID 2.0 supports three decimal places of precision for the pixel clock.

[conron]

Hey there, I added an edid from one of my monitors onto a 4K Headless EDID emulator with passthrough. I need to add a higher resolution, however, because the base EDID of the monitor has a max clock rate of ~170khz, I cant add anything higher than 1080p 75hz or 720p ~165hz. I tried to change the monitor ranges in CRU, and I also tried exporting that to an EDID file and loading it onto the edid emulator that way, but windows still does not let me set it to a resolution with a Clock rate higher than 170. Any ideas what might be stopping me from doing this? I also tried editing the edid in AW EDID Editor as well with no luck. Thanks!

[ToastyX]

(12-01-2024 09:28 PM)conron Wrote:  Hey there, I added an edid from one of my monitors onto a 4K Headless EDID emulator with passthrough. I need to add a higher resolution, however, because the base EDID of the monitor has a max clock rate of ~170khz, I cant add anything higher than 1080p 75hz or 720p ~165hz. I tried to change the monitor ranges in CRU, and I also tried exporting that to an EDID file and loading it onto the edid emulator that way, but windows still does not let me set it to a resolution with a Clock rate higher than 170. Any ideas what might be stopping me from doing this? I also tried editing the edid in AW EDID Editor as well with no luck. Thanks!

You need to specify what the hardware is. What is the emulator? What is the GPU? What port are you using? What resolution and refresh rate do you need?