Custom Resolution Utility (CRU)

[ToastyX]

(03-11-2024 12:45 PM)zyzzvya23 Wrote:  My active signal resolution defaults and locks to 4096x2160, which DLSDR then adds the 1.78 factor multiplier to. This results in a stretched image in 17:9 aspect ratio. I've tried using CRU to delete out all instances of this resolution but end up with a black screen and have to system restore to fix it

If the the driver is crashing, that's a driver bug that needs to be reported to NVIDIA.

[DesTeufelsMusterknabe]

Thank you!

[zyzzvya23]

(03-13-2024 04:08 AM)ToastyX Wrote:  

(03-11-2024 12:45 PM)zyzzvya23 Wrote:  My active signal resolution defaults and locks to 4096x2160, which DLSDR then adds the 1.78 factor multiplier to. This results in a stretched image in 17:9 aspect ratio. I've tried using CRU to delete out all instances of this resolution but end up with a black screen and have to system restore to fix it

If the the driver is crashing, that's a driver bug that needs to be reported to NVIDIA.

I've tried a few different drivers and encountered the same issue, is there any chance its related to HDR?

[ToastyX]

(03-13-2024 09:33 AM)zyzzvya23 Wrote:  I've tried a few different drivers and encountered the same issue, is there any chance its related to HDR?

I don't know what triggers it, but it's an NVIDIA driver bug that's been around for a while. Make sure you're deleting 4096x2160 in the HDMI data block as well.

[akwldrk123]

It seems that you're encountering an issue with your Radeon VRAM clock staying fixed after rebooting despite using CRU (Custom Resolution Utility). When you apply the settings and run the restart executable included in the compressed file, the clock returns to normal, but after rebooting, the VRAM clock always gets stuck at the maximum. While other settings like the refresh rate seem to apply correctly, the VRAM clock doesn't work as expected. Running the restart executable again brings the clock back down. It appears that the settings aren't persisting properly. How can I resolve this?

During this time, whenever I rebooted, the internet browser would automatically launch, so I assumed that the VRAM clock was normal since it seemed fine even when viewing the regular desktop background. However, I later discovered that even when simply browsing the internet, I needed to disable hardware acceleration for the VRAM clock to return to normal. Because of this, I didn't notice any issues even when using version 1.51.

Having to run the restart executable every time I reboot is incredibly cumbersome.

[ToastyX]

(03-17-2024 04:33 PM)akwldrk123 Wrote:  It seems that you're encountering an issue with your Radeon VRAM clock staying fixed after rebooting despite using CRU (Custom Resolution Utility). When you apply the settings and run the restart executable included in the compressed file, the clock returns to normal, but after rebooting, the VRAM clock always gets stuck at the maximum. While other settings like the refresh rate seem to apply correctly, the VRAM clock doesn't work as expected. Running the restart executable again brings the clock back down. It appears that the settings aren't persisting properly. How can I resolve this?

If restarting the driver works around the problem, then it's a driver bug that needs to be reported to AMD. CRU can't do anything about this.

[JUZY]

Hi,

I have an OMEN by HP 15-ax208no Laptop. I have recently replaced the original screen with a BOE NV156FHM-N4B 1920x1080 144hz.
The screen works as it should but when I installed it, only the 60hz (original screen hz) option came up.
I have tried different options via CRU but I can only get the screen to come up to 72hz. If I set it to 144hz, the screen splits in two and stutters. If I set it to 75hz, the color is washed out, almost making it black and white.
Anything above 75hz results in the screen splitting in two and stuttering.

I wonder if there is any way to solve this or if it is the screen that is wrong or the laptop?

[nea-sama]

I have the asus tuf a16 with amd apu+dgpu with 16:10 1920x1200p 165hz display. I tried making custom 1440x1200p 165hz stretched res with cru but half of my screen got dimmer which half of it got blurry and flickering while the last half is black (shown in the image attached). However, this isn't a problem if the refresh rate is set to 60hz or with GPU scaling enabled (in which the active signal stays at 1920x1200p but desktop turned to 1440x1200p). I've tried different timing presets but no luck. Is there any fix to this or my display simply isn't capable of custom res?

[ToastyX]

(03-21-2024 08:39 PM)nea-sama Wrote:  I have the asus tuf a16 with amd apu+dgpu with 16:10 1920x1200p 165hz display. I tried making custom 1440x1200p 165hz stretched res with cru but half of my screen got dimmer which half of it got blurry and flickering while the last half is black (shown in the image attached). However, this isn't a problem if the refresh rate is set to 60hz or with GPU scaling enabled (in which the active signal stays at 1920x1200p but desktop turned to 1440x1200p). I've tried different timing presets but no luck. Is there any fix to this or my display simply isn't capable of custom res?

Laptop screens don't have scalers. You have to use GPU scaling for non-native resolutions. It'd be easier to just add 1440x1200 with SRE: https://www.monitortests.com/forum/Threa...Editor-SRE

[ToastyX]

(03-21-2024 04:59 PM)JUZY Wrote:  I have an OMEN by HP 15-ax208no Laptop. I have recently replaced the original screen with a BOE NV156FHM-N4B 1920x1080 144hz.
The screen works as it should but when I installed it, only the 60hz (original screen hz) option came up.
I have tried different options via CRU but I can only get the screen to come up to 72hz. If I set it to 144hz, the screen splits in two and stutters. If I set it to 75hz, the color is washed out, almost making it black and white.
Anything above 75hz results in the screen splitting in two and stuttering.

I wonder if there is any way to solve this or if it is the screen that is wrong or the laptop?

Seems like either it's the wrong panel, or it only supports 144 Hz with specific timing parameters, which would be in the data sheet.