Custom Resolution Utility (CRU)

[ArtMov]

Hoping for a hint from toasty, I bought a noname monitor with a very good 2k 300hz innolux ips igzo panel, the monitor body has speaker outputs, the edid also configures the sound, frequency, location, the nvidia panel also shows that the monitor has sound. But the problem is that there is no sound, I tried everything, in the monitor settings there is also a setting for the level of sound and mute off. There is one note in the settings of the sound device in windows (nvidia high defnition) the connector is stated as “left and right hdmi connector”, , maybe this is the answer? Does it think it is connected via hdmi, or is audio output enabled only for hdmi, although I only tried it with the display port?
upd hdmi no sound too

[jeffeh12133]

(06-25-2024 09:26 PM)ToastyX Wrote:  

(06-25-2024 05:40 PM)jeffeh12133 Wrote:  also off topic but i think i found a bug. when i use restart64.exe, device manager adds a ghost entry in device manager Monitors section (the same Generic PnP Monitor) but its greyed out. when i load moninfo to check my monitor details, under [real-time] display, everything is fine, but under [registry-active], it fails to load the EDID, Filter Driver shows "(Data Unavailable) for the registry-active display with the ghost monitor not deleted. However when i delete the ghost monitor from device manager monitors tab, then reload MonInfo to re-enumerate monitor details, the [registry-active] display info shows properly, loads the resolutions, and shows Filter Driver: EDID Override properly.

That's weird. Is that with "Show hidden devices" enabled in the "View" menu in Device Manager, or is it showing that by default? Running restart.exe is the same as disabling and then enabling the GPU in Device Manager to restart the graphics driver, so it's normal to have another grayed out monitor in the list because that's what is used by the basic display driver while the graphics driver is restarting, but normally Device Manager doesn't show grayed out monitors unless "Show hidden devices" is enabled, so if you're seeing that by default, then that indicates a driver issue somewhere. I haven't ever seen "(Data Unavailable)" in MonInfo, so I don't know what that means or why that would happen. Normally MonInfo doesn't list the monitor at all if there is no data for it. If you can use RegEdit to export HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY to a file while it's happening and post it here, I can check if anything weird going on.

yea basically if i restart64.exe after editing the EDID via CRU as normal, what happens is the [real-time] listing of the monitor in MonInfo shows the changes properly. whatever change i made, is shown here. BUT, BELOW [real-time], there are two other listings (which is normal), listed as [registry-active] and [registry]. these settings don't list properly, because im assuming they are reading the ghost-monitor's EDID (from during the restart using restart64.exe).

i think it's a ranking error, because this issue is immediately solved as soon as i delete the ghost monitor that shows up after using restart64.exe. im guessing windows thinks that the basic display device is the original and proper monitor, and uses that as the active registry for the display. it's weird because the real-time display shows properly, whereas the other two listings for registry do not (unless the ghost monitor is deleted).

-somewhat unrelated-
i also noticed that disabling my monitor's ddc/ci from (enabled) to (disabled) then refreshing MonInfo program, no longer lists [real-time] monitor information, as extracted from the ddc/ci (which is normal), but only shows the [registry-active] and [registry] entries of the monitor for Generic PnP Monitor. why does disabling ddc/ci with an EDID override cause seemingly smoother responsiveness to my display? and do you recommend disabling ddc/ci when using an EDID override?

[ToastyX]

(07-03-2024 09:45 AM)jeffeh12133 Wrote:  i also noticed that disabling my monitor's ddc/ci from (enabled) to (disabled) then refreshing MonInfo program, no longer lists [real-time] monitor information, as extracted from the ddc/ci (which is normal), but only shows the [registry-active] and [registry] entries of the monitor for Generic PnP Monitor. why does disabling ddc/ci with an EDID override cause seemingly smoother responsiveness to my display? and do you recommend disabling ddc/ci when using an EDID override?

Nothing you said should be happening. DDC/CI should not affect the EDID or the responsiveness. DDC/CI is for controlling monitor settings such as brightness through software.

[ToastyX]

(07-01-2024 12:01 PM)ArtMov Wrote:  Hoping for a hint from toasty, I bought a noname monitor with a very good 2k 300hz innolux ips igzo panel, the monitor body has speaker outputs, the edid also configures the sound, frequency, location, the nvidia panel also shows that the monitor has sound. But the problem is that there is no sound, I tried everything, in the monitor settings there is also a setting for the level of sound and mute off. There is one note in the settings of the sound device in windows (nvidia high defnition) the connector is stated as “left and right hdmi connector”, , maybe this is the answer? Does it think it is connected via hdmi, or is audio output enabled only for hdmi, although I only tried it with the display port?
upd hdmi no sound too

I don't see how the driver could think it's HDMI if it's plugged into DisplayPort. Maybe the monitor doesn't actually have speakers, or it's not connected properly inside.

[ItsBihx]

Trying to display scale my 380hz monitor to 1750x1080 @380hz but it goes red and doesnt let you apply the res at anything past 286. the resolution 1750x1080 works fine gpu scaling but so its not like the res isnt possible. any fixes?

[ToastyX]

(07-03-2024 09:20 PM)ItsBihx Wrote:  Trying to display scale my 380hz monitor to 1750x1080 @380hz but it goes red and doesnt let you apply the res at anything past 286. the resolution 1750x1080 works fine gpu scaling but so its not like the res isnt possible. any fixes?

https://www.monitortests.com/forum/Threa...tility-CRU

[DzigiBau]

@ToastyX

Would you please give me a hand here, I am not fully sure what is going on. I use CRU since my VRAM clock stucks at maximum and I used your settings from page 1 to make it work. My card here is GigaByte AMD/ATI R9 280 WindForce, which I connect to Asus monitor by passive MiniDisplay to HDMI adapter (DP 1.2 to HDMI 2.0 with HDMI 2.0 cable) and to my television using HDMI 1.4 cable. Resolution is 1920x1080 at 59.940 which I prefer as my favorite as a matter of taste.

1. In your instruction you say that we need to setup TMDS clock for AMD/ATI GPUs and I did it by clicking in Extension Blocks Field, CTA-861, HDMI and TDMS Clock was unticked, I enable it and it gives me 225Mhz as maximum. If I try to put higher value, it becomes grey and I cannot put anything. I change display mode to television only and there I check TDMS Clock and left 225Mhz. Is this normal or I need to do something more to increase it? For DP to HDMI connection to my Monitor, it is the same, but if I select it, after restart64.exe implementation it becomes unstable and returns back to unticked TDMS Clock, which I left that way.

2. For making VRAM drop down in idle, I use CVT-RB2 standard mode and it works for certain time, I have some desktop widget to follow GPU and VRAM clocks, but after a while it stucks again on VRAM maximum clock. My GPU has 300Mhz for GPU and 150Mhz for VRAM in idle, but it brings it to 510Mz for GPU and maximum 1250Mhz for VRAM which uses more power 30W additional, which I do not want. I do not play games, using computer for typing, browsing and youtube videos only. What can I do more to make VRAM goes to minimum 150Mhz and stopping using more power in idle mode? I use Windows 11 with latest 22.6.1 AMD driver for my GPU, there is no newer one. Old GPU, I know.

3. This one sounds very ridiculous. When I turn on PC, it sends same video signal to both, monitor and television, with old booting sequence, you remember white letters on black background and then start to load Windows. On monitor everything goes correctly, but on television I have vertical blue lines (instead of black background) which lasts until Windows loads and it becomes normal. If I open AMD Radeon Software (Adrenalin) and restart PC, then I have correct situation on television during booting, white letters on black background. What is the problem, I am not sure, cable is HDMI 1.4, newer one, good one, but booting sequence has vertical blue lines, some version of corrupted signal, low voltage or something if I do not open AMD Radeon Software settings. Is it possible to solve this one using one of your softwares?

Thank you for your work and time.

[ToastyX]

(07-04-2024 12:33 PM)DzigiBau Wrote:  @ToastyX

Would you please give me a hand here, I am not fully sure what is going on. I use CRU since my VRAM clock stucks at maximum and I used your settings from page 1 to make it work. My card here is GigaByte AMD/ATI R9 280 WindForce, which I connect to Asus monitor by passive MiniDisplay to HDMI adapter (DP 1.2 to HDMI 2.0 with HDMI 2.0 cable) and to my television using HDMI 1.4 cable. Resolution is 1920x1080 at 59.940 which I prefer as my favorite as a matter of taste.

1. In your instruction you say that we need to setup TMDS clock for AMD/ATI GPUs and I did it by clicking in Extension Blocks Field, CTA-861, HDMI and TDMS Clock was unticked, I enable it and it gives me 225Mhz as maximum. If I try to put higher value, it becomes grey and I cannot put anything. I change display mode to television only and there I check TDMS Clock and left 225Mhz. Is this normal or I need to do something more to increase it? For DP to HDMI connection to my Monitor, it is the same, but if I select it, after restart64.exe implementation it becomes unstable and returns back to unticked TDMS Clock, which I left that way.

2. For making VRAM drop down in idle, I use CVT-RB2 standard mode and it works for certain time, I have some desktop widget to follow GPU and VRAM clocks, but after a while it stucks again on VRAM maximum clock. My GPU has 300Mhz for GPU and 150Mhz for VRAM in idle, but it brings it to 510Mz for GPU and maximum 1250Mhz for VRAM which uses more power 30W additional, which I do not want. I do not play games, using computer for typing, browsing and youtube videos only. What can I do more to make VRAM goes to minimum 150Mhz and stopping using more power in idle mode? I use Windows 11 with latest 22.6.1 AMD driver for my GPU, there is no newer one. Old GPU, I know.

3. This one sounds very ridiculous. When I turn on PC, it sends same video signal to both, monitor and television, with old booting sequence, you remember white letters on black background and then start to load Windows. On monitor everything goes correctly, but on television I have vertical blue lines (instead of black background) which lasts until Windows loads and it becomes normal. If I open AMD Radeon Software (Adrenalin) and restart PC, then I have correct situation on television during booting, white letters on black background. What is the problem, I am not sure, cable is HDMI 1.4, newer one, good one, but booting sequence has vertical blue lines, some version of corrupted signal, low voltage or something if I do not open AMD Radeon Software settings. Is it possible to solve this one using one of your softwares?

Thank you for your work and time.

If you're using multiple monitors, all monitors need to be using the same resolution and refresh rate with the same exact timing parameters so the vertical blanking periods are synchronized. The R9 280 also has a special mode called UVD that's used when video acceleration is active, such as when playing videos in a browser, and the clocks will stay in this mode if anything is running with video acceleration active. Google "UVD clock bug" for more information. Sometimes it will also change the memory clock when it shouldn't, causing one or both of the screens to display garbage, which might be what's happening when it's booting. Honestly I consider that a design flaw with the first generation GCN GPUs. Newer GPUs don't have these issues, but you still have to make sure the monitors are synchronized. I don't know what you're talking about with the TMDS clock because CRU would never put in 225 MHz if it wasn't enabled already, and that has nothing to do with your issues anyway. That only affects what resolutions the driver will accept, but you don't need to do anything special for 1920x1080 @ 59.94 Hz since that's less than 165 MHz pixel clock.

[nikif002]

I am having an issue where custom resolutions stopped "taking" for me. I am on Windows 11, Dell XPS 9510 laptop. Hooked up to a Dell U3011 through HDMI and a Dell USB-C multiport adapter.

The monitor has never properly exposed its native 2560x1600 resolution as long as I remember, and I have always had to use CRU.

Now I am newly unable to add resolutions. I can add the detailed resolution as before (screenshot attached), however no matter how many times I run restart.exe, the asterisk remains indicating it has not been saved, and Windows won't let me choose the new resolution.

Formerly I have had this exact problem when installing the Intel "Arc" or "Iris XE" drivers or whatever, but it was always fixed by uninstalling those drivers and reverting to using the default drivers from Windows. This is no longer the case. I have tried everything I can think of -- actual restarts, re-installing and uninstalling the latest Intel drivers, I tried the beta Intel Graphics Control Panel to change the resolution (that has never really worked). Any ideas? I would love to understand more about what is happening here so I can fix it not just this time, but if it ever happens again in the future.

EDIT: It works with 30hz instead of 60. Am I just high and that's what I've always used? I swear it used to work with 60hz. I wish I hadn't wiped my old resolutions in an attempt to fix this.

[ToastyX]

(07-04-2024 06:07 PM)nikif002 Wrote:  I am having an issue where custom resolutions stopped "taking" for me. I am on Windows 11, Dell XPS 9510 laptop. Hooked up to a Dell U3011 through HDMI and a Dell USB-C multiport adapter.

The monitor has never properly exposed its native 2560x1600 resolution as long as I remember, and I have always had to use CRU.

Now I am newly unable to add resolutions. I can add the detailed resolution as before (screenshot attached), however no matter how many times I run restart.exe, the asterisk remains indicating it has not been saved, and Windows won't let me choose the new resolution.

Formerly I have had this exact problem when installing the Intel "Arc" or "Iris XE" drivers or whatever, but it was always fixed by uninstalling those drivers and reverting to using the default drivers from Windows. This is no longer the case. I have tried everything I can think of -- actual restarts, re-installing and uninstalling the latest Intel drivers, I tried the beta Intel Graphics Control Panel to change the resolution (that has never really worked). Any ideas? I would love to understand more about what is happening here so I can fix it not just this time, but if it ever happens again in the future.

EDIT: It works with 30hz instead of 60. Am I just high and that's what I've always used? I swear it used to work with 60hz. I wish I hadn't wiped my old resolutions in an attempt to fix this.

Ideally you should use DisplayPort to avoid having to add 2560x1600 manually because the monitor doesn't officially support 2560x1600 with HDMI even though it will work if you can add it. The * means it is saved. It would say "(restart required)" if it wasn't taking effect. The GPU is definitely capable, so the driver is ignoring the resolution for some reason. I don't know if Intel listens to this, but check the maximum TMDS clock in the HDMI data block in the CTA-861 extension block. It should be high enough to accommodate the pixel clock for the resolution you want. I recommend just putting 340 MHz because that's the standard maximum for HDMI 1.4.