(04-10-2025 04:20 PM)daydr34m Wrote: [ -> ]Hi ToastyX! Thanks for your program and forum support!
I have a question: I read the forum and found two people who wrote that after using CRU they had permanent artifacts and flickering on their monitors
Lenovo Y50 (post: https://www.monitortests.com/forum/Threa...80#pid7880)
and
MG279Q (post: https://www.monitortests.com/forum/Threa...ge#pid7878)
I want to know if using CRY is absolutely safe and cannot cause any damage to any components of my PC, including the monitor?
Thank you in advance for your reply!
There's always a risk when overclocking anything, but damage is extremely rare. Most monitors will not display anything they aren't designed to handle, but laptop panels and monitors without scalers might not have that protection. Any monitor with an on-screen menu has a scaler, and they will usually display an "out of range" message or black screen if the resolution or refresh rate isn't supported.
The first case with the Lenovo Y50 I'm not sure about. Laptop panels often don't have protection against unsupported refresh rates, so it's possible the panel was damaged. Usually if a panel can't handle a refresh rate, it will be immediately obvious because it won't display correctly, but he said it worked for 2 hours before the computer crashed.
The second case with the MG279Q is a defective monitor and definitely not damage from using CRU. He wasn't even overclocking, only rounding the refresh rate to 144 Hz, and it was working for 6 months before it failed for an unrelated reason.
(04-10-2025 09:33 PM)ToastyX Wrote: [ -> ] (04-10-2025 04:20 PM)daydr34m Wrote: [ -> ]Hi ToastyX! Thanks for your program and forum support!
I have a question: I read the forum and found two people who wrote that after using CRU they had permanent artifacts and flickering on their monitors
Lenovo Y50 (post: https://www.monitortests.com/forum/Threa...80#pid7880)
and
MG279Q (post: https://www.monitortests.com/forum/Threa...ge#pid7878)
I want to know if using CRY is absolutely safe and cannot cause any damage to any components of my PC, including the monitor?
Thank you in advance for your reply!
There's always a risk when overclocking anything, but damage is extremely rare. Most monitors will not display anything they aren't designed to handle, but laptop panels and monitors without scalers might not have that protection. Any monitor with an on-screen menu has a scaler, and they will usually display an "out of range" message or black screen if the resolution or refresh rate isn't supported.
The first case with the Lenovo Y50 I'm not sure about. Laptop panels often don't have protection against unsupported refresh rates, so it's possible the panel was damaged. Usually if a panel can't handle a refresh rate, it will be immediately obvious because it won't display correctly, but he said it worked for 2 hours before the computer crashed.
The second case with the MG279Q is a defective monitor and definitely not damage from using CRU. He wasn't even overclocking, only rounding the refresh rate to 144 Hz, and it was working for 6 months before it failed for an unrelated reason.
Thanks for the answer!
I set the values ​​to 165Hz and 1280x960 on my monitor MSI G244F E2, IPS, 180Hz and I got a black screen with artifacts and flashing white stripes. I pressed F8, deleted the created profile in CRU and the picture returned, everything became fine, but I was left with a bad feeling and did not understand whether something could have happened to the matrix of my monitor when artifacts appeared on the black screen of the monitor.
(04-10-2025 02:14 PM)ToastyX Wrote: [ -> ]What happens if you delete the extension override data block in the CTA-861 extension block and then add a DisplayID 1.3 extension block with the detailed resolution in there? If that doesn't help, does it work if you disconnect the LG C1?
Thank you for the response. I realized that I was actually doing it wrong, as I was editing the existing CTA-861 block and then changing the block type to "DisplayID 1.3" and then adding the new resolution, which was then overwriting the whole CTA-861 block, and that is why the monitor would not produce an output anymore after driver restart. Instead of this, I tried adding a new DisplayID 1.3 block and added 5120x1440 @ 144 Hz inside that, and after driver restart, I did manage to get the monitor to run at 144 Hz, but unfortunately G-Sync no longer works in this case.
Is there any way to add this resolution to the CTA-861 block itself? The "Detailed resolutions" part of the CTA-861 still won't accept 5120 as a valid width, so I cannot add it there. However, the original 5120x1440 @120 and @240 Hz resolutions that the monitor supports should be defined somewhere (inside the CTA-861 block?), but I cannot see them anywhere in CRU.
(04-11-2025 01:55 AM)maftul Wrote: [ -> ]Is there any way to add this resolution to the CTA-861 block itself? The "Detailed resolutions" part of the CTA-861 still won't accept 5120 as a valid width, so I cannot add it there. However, the original 5120x1440 @120 and @240 Hz resolutions that the monitor supports should be defined somewhere (inside the CTA-861 block?), but I cannot see them anywhere in CRU.
It doesn't need to be in the CTA-861 data block. In fact the monitor has a DisplayID 1.3 extension block with 5120x1440 @ 60 Hz and 120 Hz that CRU doesn't currently show because it doesn't support extension overrides yet. You can add those manually if you want them. For G-SYNC to work, you would need to edit the VRR range in the HDMI 2.1 data block in the CTA-861 extension block, but VRR seems to be disabled in the monitor because the range isn't set. I see a FreeSync data block, but NVIDIA doesn't support FreeSync.
(04-10-2025 10:40 PM)daydr34m Wrote: [ -> ]Thanks for the answer!
I set the values ​​to 165Hz and 1280x960 on my monitor MSI G244F E2, IPS, 180Hz and I got a black screen with artifacts and flashing white stripes. I pressed F8, deleted the created profile in CRU and the picture returned, everything became fine, but I was left with a bad feeling and did not understand whether something could have happened to the matrix of my monitor when artifacts appeared on the black screen of the monitor.
That seems more like a scaler limitation. 1280x960 @ 165 Hz should be within the operating limits of the monitor. You might be better off using GPU scaling and SRE:
https://www.monitortests.com/forum/Threa...Editor-SRE
Thanks very much for the CRU Tool
I tried to add overclocked Res via Extension Block DisplayID2.0 but got Blackscreen and had to reset.
Alienware 3423dwf , rtx 5090.
Via nvidia customres these settings work but cant be used as soon as dsr option is on, so i need cru tool.
Max 10bit option for the monitor is 3440+100hz. For 10bit+165hz i need overclock pixelclock at 856.68 MHz . (165hz Refreshrate)
Values in "Total Pixels": Horizontal: 3520, Vertical: 1475.
Are there settings that i could have missed to get it working ?
https://www.reddit.com/r/ultrawidemaster..._cru_tool/
(04-11-2025 03:18 AM)ToastyX Wrote: [ -> ] (04-10-2025 10:40 PM)daydr34m Wrote: [ -> ]Thanks for the answer!
I set the values ​​to 165Hz and 1280x960 on my monitor MSI G244F E2, IPS, 180Hz and I got a black screen with artifacts and flashing white stripes. I pressed F8, deleted the created profile in CRU and the picture returned, everything became fine, but I was left with a bad feeling and did not understand whether something could have happened to the matrix of my monitor when artifacts appeared on the black screen of the monitor.
That seems more like a scaler limitation. 1280x960 @ 165 Hz should be within the operating limits of the monitor. You might be better off using GPU scaling and SRE: https://www.monitortests.com/forum/Threa...Editor-SRE
Yes, I now use only GPU scaling, since my monitor scaling is incredibly bad :/
I found information on the Internet about resetting possible errors in the monitor firmware and possible inconsistencies in data transfer between the monitor and the GPU, does this really work?
1. Turn off the PC -> Power off the PC
2. Disconnect DisplayPort (any other wire connecting the GPU and the monitor) and Power off the monitor
3. Wait for >=5 minutes
4. Connect everything to the power supply -> enter safe mode -> reset the monitor OSD to factory settings -> use DDU and remove the video card driver
5. Perform a normal system startup -> install the driver on the monitor -> Reboot
6. Install the driver on the GPU -> Reboot
7. Configure the monitor OSD
And you can add: "8. Remove unused connected devices via Device Cleanup Tool"
(04-10-2025 09:33 PM)ToastyX Wrote: [ -> ] (04-10-2025 05:22 PM)LGBoy Wrote: [ -> ]Hi ToastyX,
I don't know what I'm doing wrong. I am trying to get a custom resolution to work with DLDSR. My config is 3080/LG C1/Windows 10.
For a while I've been using a custom 3824x2151 on C1 for two reasons: there is no overprovision of pixels so with oled pixel shift screen is going few pixels out of bounds every now and then, and second reason is in the last few month I noticed a lot of dead pixels near the edges of the screen. When using slightly lower 3824x2151 these problems are gone.
I've been trying to get DLSS/DLDSR combo to work to increase image quality in games I play, but for the life of me I can't get it to work with my custom resolution. What I want is to retain 3824x2151 as windows desktop resolution and create a 2.25x 5736x3226 (rougly) DLDSR resolution for games where I will use the DLSS/DLDSR for superior image quality.
I followed a guide that said I needed to change 3840x2160 detailed resolution in CRU to 3824x2151 (to make 3824x2151 native resolution and therefor eligible as DLDSR baseline), but when I do that and restart, windows changes back to 3840x2160 and 3824x2151 is not in the resolution list anymore. I can still see it in NVidia driver in Change resolution panel/Customize but there I can't select it or delete it.
I'm sure there are more steps I need to do but I have no idea where to start.
Thank you in advance!
You might have to delete all instances of 3840x2160 for DSR to work correctly with 3824x2151. They can be in the extension block in several places, such as in the TV resolutions and HDMI support data blocks.
I did what you suggested, deleted several 3840x2160 resolutions under TV resolutions and 3x 3840x2160 under HDMI Support. After restart I've got this in NV control panel (1 in attachment) - 3840x2160 was gone and 3824x2151 was promoted to native res, but only custom 3824x2151 resolution was looking ok (and even there it wasn't possible to select 10-bit color depth, only 8-bit).
Native 3824x2151 was blurry as if it was upscaled from lower res and it was also limited to 60Hz (2 in attachment). When I enabled DLDSR, new 5736x3227 res was created and it also looked blurry as "native" 3824x2151 and it was also limited to 60Hz. Any idea what else could I try ?
Thanks again for your time!
(04-11-2025 07:19 AM)ildottore101 Wrote: [ -> ]Thanks very much for the CRU Tool
I tried to add overclocked Res via Extension Block DisplayID2.0 but got Blackscreen and had to reset.
Alienware 3423dwf , rtx 5090.
Via nvidia customres these settings work but cant be used as soon as dsr option is on, so i need cru tool.
Max 10bit option for the monitor is 3440+100hz. For 10bit+165hz i need overclock pixelclock at 856.68 MHz . (165hz Refreshrate)
Values in "Total Pixels": Horizontal: 3520, Vertical: 1475.
Are there settings that i could have missed to get it working ?
https://www.reddit.com/r/ultrawidemaster..._cru_tool/
You need to edit the existing 165 Hz in the DisplayID extension block, not add it in a new extension block.
(04-11-2025 10:27 AM)daydr34m Wrote: [ -> ]Yes, I now use only GPU scaling, since my monitor scaling is incredibly bad :/
I found information on the Internet about resetting possible errors in the monitor firmware and possible inconsistencies in data transfer between the monitor and the GPU, does this really work?
1. Turn off the PC -> Power off the PC
2. Disconnect DisplayPort (any other wire connecting the GPU and the monitor) and Power off the monitor
3. Wait for >=5 minutes
4. Connect everything to the power supply -> enter safe mode -> reset the monitor OSD to factory settings -> use DDU and remove the video card driver
5. Perform a normal system startup -> install the driver on the monitor -> Reboot
6. Install the driver on the GPU -> Reboot
7. Configure the monitor OSD
And you can add: "8. Remove unused connected devices via Device Cleanup Tool"
If the monitor's firmware glitched, all you need to do is unplug the monitor's power for a minute to reboot it. All that other stuff has nothing to do with the monitor.