Custom Resolution Utility (CRU)

[Potty]

Hello! Please help to understand. I have a monitor Gigabyte m27q. When connecting to my old laptop, I cannot use extended 2560x1440 60Hz. Through the program, I realized that I can only use the general pixel frequency limits of no more than 225 Mhz. I don't understand why this is so, because when installing any of the linux, I can use the extension 2560x1440 60Hz as well as 1920x1080 120Hz. On the Windows system, it can only be 1920x1080 96Hz and 2560x1440 55Hz, but no more

[Tealc]

(03-29-2023 03:30 PM)PLU Wrote:  

(03-26-2023 09:43 PM)ToastyX Wrote:  That's all you need to do to add the resolution. Make sure to delete the old resolution in the other extension block so that doesn't take effect.

Ok so that was the issue and now it's applying, however if I edit the vertical blanking until it downclocks or use CVT-RB(2) it can go down to 200 Hz but the monitor starts to perform really poorly. There's a noticeable input delay and the refresh rate definitely isn't 165 Hz even if it's reported as such. I can't say for sure but it feels and looks like it's just 60 Hz. Even the UFO test says it's 165 Hz but maybe it's just reading what Windows is reporting.
I tried copypasting my default 165 Hz timings (that trigger max VRAM clock) to make sure what I'm editing actually works and yes, it does perform as it should.

This is how CRU looks by default, I copy the top resolution timings, delete the extension block and add a new DisplayID 2.0 one with the pasted timings and then edit them. If I apply that and restard I only have two selectable refresh rates in Windows: 60 Hz (I'm assuming this is the detailed resolution in the main window of CRU at the top) and the 165 Hz one I created.

Hello!

I have the same monitor and the same issue as you. Have you managed to find a solution?

Thanks!

P.S. I managed to make mine work at 155Hz with no apparent loss in performance, but it's the maximum before the limit hits.

[ToastyX]

(04-30-2024 02:08 PM)Potty Wrote:  Hello! Please help to understand. I have a monitor Gigabyte m27q. When connecting to my old laptop, I cannot use extended 2560x1440 60Hz. Through the program, I realized that I can only use the general pixel frequency limits of no more than 225 Mhz. I don't understand why this is so, because when installing any of the linux, I can use the extension 2560x1440 60Hz as well as 1920x1080 120Hz. On the Windows system, it can only be 1920x1080 96Hz and 2560x1440 55Hz, but no more

The GPU's driver limits the pixel clock. It must be a very old GPU to have that limit.

[ToastyX]

(04-30-2024 05:25 AM)ApolloPM Wrote:  Here you go, this is with my CRU settings still active.
The Gigabyte FO32U2P is the one that is named "GBT3215"

That seems to be one of the monitors impacted by the NVIDIA driver bug. The driver ignores EDID overrides for monitors with the extension override data block even if the data block is deleted. Are you using HDMI? What happens if you use DisplayPort?

[ApolloPM]

(05-02-2024 12:15 AM)ToastyX Wrote:  

(04-30-2024 05:25 AM)ApolloPM Wrote:  Here you go, this is with my CRU settings still active.
The Gigabyte FO32U2P is the one that is named "GBT3215"

That seems to be one of the monitors impacted by the NVIDIA driver bug. The driver ignores EDID overrides for monitors with the extension override data block even if the data block is deleted. Are you using HDMI? What happens if you use DisplayPort?

No luck with both HDMI and DP.
I think I'm just going to wait for a firmware update at this point.

[Nyaako]

Need help in getting modified VRR range to stick on a LG 27GR95QE-B with HDMI 2.1.

Modified VRR range from 48-240 to 85-240 in both "Range Limits" and "FreeSync range" because I'm trying to mitigate as much VRR flickering as I can using LFC.
When I game at 60-80fps+ and it shows VRR working with the refresh rate at 120Hz+ and such after using restart64.exe, but the issue is after I restart my entire PC and suddenly the VRR range is messed up and doesn't activate LFC at 60-80fps+ unless I limit the game to 57 fps or below (CRU still shows the modified VRR ranges at 85-240). Have to use reset-all.exe and re-configure the VRR range again.

For the record, this seems to be an issue when using HDMI 2.1 on my end. When I use DisplayPort, the modified VRR range works as intended even after restarting my PC. The reason why I'm not using DisplayPort is to avoid relying on DSC for 1440p 240Hz (and using HDR).

[ToastyX]

(05-03-2024 12:26 AM)Nyaako Wrote:  Need help in getting modified VRR range to stick on a LG 27GR95QE-B with HDMI 2.1.

Modified VRR range from 48-240 to 85-240 in both "Range Limits" and "FreeSync range" because I'm trying to mitigate as much VRR flickering as I can using LFC.
When I game at 60-80fps+ and it shows VRR working with the refresh rate at 120Hz+ and such after using restart64.exe, but the issue is after I restart my entire PC and suddenly the VRR range is messed up and doesn't activate LFC at 60-80fps+ unless I limit the game to 57 fps or below (CRU still shows the modified VRR ranges at 85-240). Have to use reset-all.exe and re-configure the VRR range again.

For the record, this seems to be an issue when using HDMI 2.1 on my end. When I use DisplayPort, the modified VRR range works as intended even after restarting my PC. The reason why I'm not using DisplayPort is to avoid relying on DSC for 1440p 240Hz (and using HDR).

Why do you need to run reset-all.exe and reconfigure the VRR range? You should be able to just run restart.exe. If the VRR range works correctly after running restart.exe, then it's a graphics driver bug. Is this happening after restarting the PC or only after turning the PC off and back on? Issues that come up after turning the PC off and back on can usually be resolved by disabling fast startup: https://www.asus.com/support/faq/1045548/

[Nyaako]

(05-03-2024 07:06 PM)ToastyX Wrote:  

(05-03-2024 12:26 AM)Nyaako Wrote:  Need help in getting modified VRR range to stick on a LG 27GR95QE-B with HDMI 2.1.

Modified VRR range from 48-240 to 85-240 in both "Range Limits" and "FreeSync range" because I'm trying to mitigate as much VRR flickering as I can using LFC.
When I game at 60-80fps+ and it shows VRR working with the refresh rate at 120Hz+ and such after using restart64.exe, but the issue is after I restart my entire PC and suddenly the VRR range is messed up and doesn't activate LFC at 60-80fps+ unless I limit the game to 57 fps or below (CRU still shows the modified VRR ranges at 85-240). Have to use reset-all.exe and re-configure the VRR range again.

For the record, this seems to be an issue when using HDMI 2.1 on my end. When I use DisplayPort, the modified VRR range works as intended even after restarting my PC. The reason why I'm not using DisplayPort is to avoid relying on DSC for 1440p 240Hz (and using HDR).

Why do you need to run reset-all.exe and reconfigure the VRR range? You should be able to just run restart.exe. If the VRR range works correctly after running restart.exe, then it's a graphics driver bug. Is this happening after restarting the PC or only after turning the PC off and back on? Issues that come up after turning the PC off and back on can usually be resolved by disabling fast startup: https://www.asus.com/support/faq/1045548/

I guess it was confusing to read. But yes, after setting the custom VRR range (85-240) I ran restart.exe and LFC worked as intended. However, it was after I restarted or turn off/on my PC (not restart.exe) that the custom VRR range bugged out and for some reason LFC only activated when it's 57 fps or below. I open up CRU and see that the 85-240 is saved and such. That's when I have to use reset-all.exe to reset and re-configure the custom VRR range to 85-240 and using restart.exe to make it work again. Of course, it still breaks again when I restart or turn off/on my PC.

Fast startup has already been disabled.

Again, this issue seems to only be happening when I use HDMI 2.1. This doesn't happen when I use DP 1.4.

[ToastyX]

(05-03-2024 08:54 PM)Nyaako Wrote:  I guess it was confusing to read. But yes, after setting the custom VRR range (85-240) I ran restart.exe and LFC worked as intended. However, it was after I restarted or turn off/on my PC (not restart.exe) that the custom VRR range bugged out and for some reason LFC only activated when it's 57 fps or below. I open up CRU and see that the 85-240 is saved and such. That's when I have to use reset-all.exe to reset and re-configure the custom VRR range to 85-240 and using restart.exe to make it work again. Of course, it still breaks again when I restart or turn off/on my PC.

I'm asking what's the point of running reset-all.exe and reconfiguring the VRR range? All that does is put what you already had. Why not just run restart.exe after restarting the PC? If doing that works around the problem, then it's a graphics driver bug.

[Nyaako]

(05-04-2024 12:18 AM)ToastyX Wrote:  

(05-03-2024 08:54 PM)Nyaako Wrote:  I guess it was confusing to read. But yes, after setting the custom VRR range (85-240) I ran restart.exe and LFC worked as intended. However, it was after I restarted or turn off/on my PC (not restart.exe) that the custom VRR range bugged out and for some reason LFC only activated when it's 57 fps or below. I open up CRU and see that the 85-240 is saved and such. That's when I have to use reset-all.exe to reset and re-configure the custom VRR range to 85-240 and using restart.exe to make it work again. Of course, it still breaks again when I restart or turn off/on my PC.

I'm asking what's the point of running reset-all.exe and reconfiguring the VRR range? All that does is put what you already had. Why not just run restart.exe after restarting the PC? If doing that works around the problem, then it's a graphics driver bug.

Oh, I tried using restart.exe after my PC restarted and still doesn't work. So I guess it's a graphics driver bug for HDMI 2.1 on the LG 27GR95QE-B.