Custom Resolution Utility (CRU)

[ToastyX]

(08-17-2026 02:59 PM)joehannes Wrote:  Hey dude, thanks for the tool. I've had an annoying coil whine with my RTX 5070 and two new monitors, which is now almost gone.
Do you have a buymeacoffee.com account? I'd like to give you a tip.

I only have Patreon and PayPal. Thanks.

[AssadFaszad]

Hi,
I've got a laptop 1440p@165Hz GSync Compatible screen. I've managed to overclock it to 180Hz without frameskipping. Then I've adjusted V rate range to 180Hz. Windows 11 24H2 lists VRR as "Supported by driver" above 165Hz however it seems to be working fine. Curiously the original EDID has the range as 60-165Hz despite Windows and LFC kicking in at 70Hz. Changing the ID from CSO1509 to even a true GSync panel or one with a wider range removes GSync from NVCP. Are there any tricks or other improvements I could do? Here's the original EDID.

[Deus]

Hopefully this message will have a solution, since a few months/years when using CRU to change anything really on an Nvidia card if Gsync is enabled, Windows 10 will boot on a black screen and drivers will fail to initialize, for example I'm using this video for my LG monitor because LG didn't provide proper EDID with DSC off: https://youtu.be/v9C6YOvYSko?si=cMy_s_vTEgO-xMBz

The solution I found is to just disable Gsync in the Nvidia drivers and then everything works just fine. I don't "need" VRR support thankfully but for those who do that's a huge bummer. I don't know what can be done, if it's an issue CRU can even address, or if it's an Nvidia issue, or a Windows 10 issue.

[ToastyX]

(08-22-2026 06:55 PM)Deus Wrote:  Hopefully this message will have a solution, since a few months/years when using CRU to change anything really on an Nvidia card if Gsync is enabled, Windows 10 will boot on a black screen and drivers will fail to initialize, for example I'm using this video for my LG monitor because LG didn't provide proper EDID with DSC off: https://youtu.be/v9C6YOvYSko?si=cMy_s_vTEgO-xMBz

The solution I found is to just disable Gsync in the Nvidia drivers and then everything works just fine. I don't "need" VRR support thankfully but for those who do that's a huge bummer. I don't know what can be done, if it's an issue CRU can even address, or if it's an Nvidia issue, or a Windows 10 issue.

It's an NVIDIA driver bug that only happens with multiple monitors connected. There is a workaround listed in the first post: https://www.monitortests.com/forum/Threa...wn-scripts

[ToastyX]

(08-22-2026 03:58 PM)AssadFaszad Wrote:  Hi,
I've got a laptop 1440p@165Hz GSync Compatible screen. I've managed to overclock it to 180Hz without frameskipping. Then I've adjusted V rate range to 180Hz. Windows 11 24H2 lists VRR as "Supported by driver" above 165Hz however it seems to be working fine. Curiously the original EDID has the range as 60-165Hz despite Windows and LFC kicking in at 70Hz. Changing the ID from CSO1509 to even a true GSync panel or one with a wider range removes GSync from NVCP. Are there any tricks or other improvements I could do? Here's the original EDID.

That's all there is to do. Your limitation will be the actual hardware and not anything in the EDID.