Hello,
I've been using CRU for a while on my 240hz monitor but i recently upgraded to a 360hz Alienware 2523HF and i cant figure out how to do it, is there any chance i can get a detailed explanation on how to do it? my GPU is a 3060ti, thanks.
Hi! When using a Philips Oled 2024 TV (55OLED809/12) connected via hdmi 2.1 to a PC, there is such a problem that when the TV is turned off, every hour (constant) this display reconnects to Windows (with the appropriate sound of the device connection, but the most problematic thing at this moment is the system freeze for 3 seconds) when the TV is turned on ( doesn't matter what happens on it) there is no such problem, but it is worth turning it off, it is redefined hourly in Windows. I've already tried everything possible, installed a clean Windows, reset to default settings TV,updated the TV firmware, turned off all possible energy-saving settings in both TV and Windows, turned off the HDMI-CEC on the TV, deleted the drivers via DDU, turned off HDCP, rearranged the hdmi cable to different TV ports. Nothing gave any results, anyway, if the TV is turned off, it reconnects every hour, and several device setup manager event 131 errors occur at the same time when viewing Windows events. When searching for a similar problem, I found no solutions except how to disconnect the hdmi cable from the TV or de-energize the TV itself (this naturally gives the result, since the TV disappears from the devices in Windows completely and no longer reconnects), but this solution is not very convenient. Of the options that could solve this, it is most likely to connect the TV via a DP adapter to HDMI, but with this connection, the VRR will most likely stop working. So, maybe someone knows at least some solution to this problem, or maybe something needs to be turned on/off in the HDMI 2.1 settings in the CRU? Before that, I used a cheaper cable that worked poorly at 48 Gbps (the picture disappeared at a random moment, I solved the 40 Gbps limit in the CRU) I thought there was a reconnection problem with the TV turned off in this cable, but no, by buying a more expensive cable that works fine with standard settings, everything is the same. I used Windows 11 23H2, and also tried to upgrade to 24H2. RTX 4080 graphics card
(12-31-2024 08:47 AM)Alex4467 Wrote: [ -> ]Hi! When using a Philips Oled 2024 TV (55OLED809/12) connected via hdmi 2.1 to a PC, there is such a problem that when the TV is turned off, every hour (constant) this display reconnects to Windows (with the appropriate sound of the device connection, but the most problematic thing at this moment is the system freeze for 3 seconds) when the TV is turned on ( doesn't matter what happens on it) there is no such problem, but it is worth turning it off, it is redefined hourly in Windows. I've already tried everything possible, installed a clean Windows, reset to default settings TV,updated the TV firmware, turned off all possible energy-saving settings in both TV and Windows, turned off the HDMI-CEC on the TV, deleted the drivers via DDU, turned off HDCP, rearranged the hdmi cable to different TV ports. Nothing gave any results, anyway, if the TV is turned off, it reconnects every hour, and several device setup manager event 131 errors occur at the same time when viewing Windows events. When searching for a similar problem, I found no solutions except how to disconnect the hdmi cable from the TV or de-energize the TV itself (this naturally gives the result, since the TV disappears from the devices in Windows completely and no longer reconnects), but this solution is not very convenient. Of the options that could solve this, it is most likely to connect the TV via a DP adapter to HDMI, but with this connection, the VRR will most likely stop working. So, maybe someone knows at least some solution to this problem, or maybe something needs to be turned on/off in the HDMI 2.1 settings in the CRU? Before that, I used a cheaper cable that worked poorly at 48 Gbps (the picture disappeared at a random moment, I solved the 40 Gbps limit in the CRU) I thought there was a reconnection problem with the TV turned off in this cable, but no, by buying a more expensive cable that works fine with standard settings, everything is the same. I used Windows 11 23H2, and also tried to upgrade to 24H2. RTX 4080 graphics card
That's a firmware issue that Philips needs to fix. The only way around it is to use an EDID emulator.
Forgive me if this has been answered elsewhere, I have done a lot of searching and come up with nothing specific.
I have been using CRU for probably 15 years now (I love it!), so I'm pretty familiar with it.
I currently have the following setup:
Windows 10 Pro 22H2
Gigabyte Aorus Elite X570 + Ryzen 7 5800X3D
Asus TUF RTX 3080 10GB
Nvidia 537.58 Driver (running this old version for testing, but later ones have the same issues)
Dual matching monitors:
2x KTC H27E22 (240Hz 2560x1440 FastHVA, Freesync\Gsync compatible, connected via DP 1.4 with name brand cables; one display in landscape, one in portrait)
Since going dual-monitor a few months ago I have noticed that if I make any changes to their configuration with CRU (deleting an unwanted resolution) and leave both displays enabled when I reboot, I will almost always get stuck at a blank\black screens with a hung startup (keyboard LED toggles don't even respond) right when the login screen should be showing.
It is normal to get stuck at this point when setting incompatible resolutions, but I have never seen this happen when simply modifying ANY resolutions with CRU. It seems very odd and it is a bit frustrating since there are some changes I need to make to my setup that only CRU can do.
This is a 2024 model of monitor, and despite the lesser known brand name these are absolutely fantastic displays (FastHVA is a sight to behold for those who hate IPS glow), so I hope it isn't just a display firmware problem. I am inclined to think it is display driver or even CRU related... as if some kind of incompatible data is being presented to the displays.
If anyone has any suggestions, please let me know.
If there is any extra information I can provide to help diagnose this, I will do so ASAP. This monitor has lots of extension blocks, and data blocks within them: DisplayID 1.3, CTA-861, HDR, Colorimitry, etc. Maybe something there is getting messed up in the process of trying to save\apply the edits from CRU, and the monitor is freaking out when it tries to load at startup.
... but again, it seems to mainly happen when both displays are enabled. It never ever gives a black screen when I delete\reset the changes from CRU.
Thanks for your time everyone.
(01-02-2025 02:22 AM)ozzuneoj Wrote: [ -> ]Since going dual-monitor a few months ago I have noticed that if I make any changes to their configuration with CRU (deleting an unwanted resolution) and leave both displays enabled when I reboot, I will almost always get stuck at a blank\black screens with a hung startup (keyboard LED toggles don't even respond) right when the login screen should be showing.
This is an NVIDIA driver bug. I've been telling people affected by the bug to report it to NVIDIA, but it's been almost three years and they still haven't fixed it. The problem only seems to happen with multiple monitors connected, and even then it doesn't always happen. It's not an issue with the monitor or anything specific in the EDID. It happens when any EDID override is present.
(01-02-2025 02:47 AM)ToastyX Wrote: [ -> ] (01-02-2025 02:22 AM)ozzuneoj Wrote: [ -> ]Since going dual-monitor a few months ago I have noticed that if I make any changes to their configuration with CRU (deleting an unwanted resolution) and leave both displays enabled when I reboot, I will almost always get stuck at a blank\black screens with a hung startup (keyboard LED toggles don't even respond) right when the login screen should be showing.
This is an NVIDIA driver bug. I've been telling people affected by the bug to report it to NVIDIA, but it's been almost three years and they still haven't fixed it. The problem only seems to happen with multiple monitors connected, and even then it doesn't always happen. It's not an issue with the monitor or anything specific in the EDID. It happens when any EDID override is present.
Man, I was afraid of that. Thank you so much for the speedy reply and all the years of working on and supporting this awesome utility.
Crazy idea here... what if we had some kind of startup\shutdown script that would apply the EDID overrides after the login screen has displayed and then revert them at shutdown to prevent the black screen on startup issue? I believe that is the only time it occurs, so if Nvidia is unwilling to fix it, perhaps we could just work around it in this way for the time being. Running restart64 to initialize the overrides without a reboot has never caused any serious issues for me, and I think if it happened very early in the post-login-screen startup process, like before any GPU or fan monitoring tools have loaded, it wouldn't interfere with those either.
As far as the source of the problem, have there been any specific posts or threads that have narrowed the issue down to anything in particular? For example, any situations where it does or doesn't happen with dual monitors, or specific combinations of drivers, hardware, OS, etc. that don't have the issue? I don't mind throwing a bit of effort at it to see if I can add any information to the pool of knowledge myself.
Thanks again for your time.
Also, it's worth mentioning that my main reasons for using CRU are the following:
1. I like to use DLDSR for super smooth scaling in older games, but it seems the wonderfully made Nvidia drivers will provide high resolution DSR modes while limiting them to 60Hz on a 240Hz display. Like... why? Why is customizing DLDSR refresh rates not a setting in the control panel? Why isn't it just sending a native 2560x1440@240hz signal to the display when using DLDSR? I can override it with CRU by deleting absolutely all other resolutions that aren't 240Hz and it works totally fine. Why can't nvidia just make this the default behavior? The mind boggles...
2. There is yet another known bug with nvidia drivers that causes the OS to freeze\hang briefly when certain applications or windows load. The issue is pretty widely discussed in these threads:
https://www.reddit.com/r/nvidia/comments...ering_fix/
https://www.reddit.com/r/overclocking/co...a_windows/
As far as I can tell, the latest information points to certain GUI elements for some reason "considering" (for lack of a better term) all of the resolutions available to the driver and the system before loading. So if lots of unused resolutions are available, it adds significantly to this slow down. It seems a bit weird to me that that would be the cause, but I used SRE to delete most resolutions and I believe it did help. It was recommended to use CRU to delete more of them, buuuttt... I can't, without it causing the black screen on startup.
(01-02-2025 03:16 AM)ozzuneoj Wrote: [ -> ]Crazy idea here... what if we had some kind of startup\shutdown script that would apply the EDID overrides after the login screen has displayed and then revert them at shutdown to prevent the black screen on startup issue? I believe that is the only time it occurs, so if Nvidia is unwilling to fix it, perhaps we could just work around it in this way for the time being. Running restart64 to initialize the overrides without a reboot has never caused any serious issues for me, and I think if it happened very early in the post-login-screen startup process, like before any GPU or fan monitoring tools have loaded, it wouldn't interfere with those either.
In theory that could be done, but it's tricky to implement because it has to run as admin, and there isn't an easy way to control or determine the order of startup items, so I'm not sure about the timing. Task Scheduler can run a script as admin on startup or when logging in, but running a script on shutdown is trickier and requires a group policy, which isn't officially available on Home editions of Windows. You can export an .exe file using CRU to create a self-contained EDID installer, and you can call that in a batch file using the command line options listed in the first post. Then you can have one batch file that installs the EDID and restarts the driver, and another batch file that resets the EDID.
(01-02-2025 03:16 AM)ozzuneoj Wrote: [ -> ]As far as the source of the problem, have there been any specific posts or threads that have narrowed the issue down to anything in particular? For example, any situations where it does or doesn't happen with dual monitors, or specific combinations of drivers, hardware, OS, etc. that don't have the issue? I don't mind throwing a bit of effort at it to see if I can add any information to the pool of knowledge myself.
The problem doesn't always happen even on the same system where the problem has happened before with the same exact EDID override. I haven't found any particular trigger other than multiple monitors. Some have reported that changing a setting in the NVIDIA control panel such as the resolution or color depth can sometimes fix the problem, but I haven't been able to verify that.
(01-02-2025 03:16 AM)ozzuneoj Wrote: [ -> ]1. I like to use DLDSR for super smooth scaling in older games, but it seems the wonderfully made Nvidia drivers will provide high resolution DSR modes while limiting them to 60Hz on a 240Hz display. Like... why? Why is customizing DLDSR refresh rates not a setting in the control panel? Why isn't it just sending a native 2560x1440@240hz signal to the display when using DLDSR? I can override it with CRU by deleting absolutely all other resolutions that aren't 240Hz and it works totally fine. Why can't nvidia just make this the default behavior? The mind boggles...
DSR is supposed to have the same refresh rates as the native resolution. Where is it limited to 60 Hz? That might be another driver bug.
(01-02-2025 05:32 AM)ToastyX Wrote: [ -> ] (01-02-2025 03:16 AM)ozzuneoj Wrote: [ -> ]Crazy idea here... what if we had some kind of startup\shutdown script that would apply the EDID overrides after the login screen has displayed and then revert them at shutdown to prevent the black screen on startup issue? I believe that is the only time it occurs, so if Nvidia is unwilling to fix it, perhaps we could just work around it in this way for the time being. Running restart64 to initialize the overrides without a reboot has never caused any serious issues for me, and I think if it happened very early in the post-login-screen startup process, like before any GPU or fan monitoring tools have loaded, it wouldn't interfere with those either.
In theory that could be done, but it's tricky to implement because it has to run as admin, and there isn't an easy way to control or determine the order of startup items, so I'm not sure about the timing. Task Scheduler can run a script as admin on startup or when logging in, but running a script on shutdown is trickier and requires a group policy, which isn't officially available on Home editions of Windows. You can export an .exe file using CRU to create a self-contained EDID installer, and you can call that in a batch file using the command line options listed in the first post. Then you can have one batch file that installs the EDID and restarts the driver, and another batch file that resets the EDID.
(01-02-2025 03:16 AM)ozzuneoj Wrote: [ -> ]As far as the source of the problem, have there been any specific posts or threads that have narrowed the issue down to anything in particular? For example, any situations where it does or doesn't happen with dual monitors, or specific combinations of drivers, hardware, OS, etc. that don't have the issue? I don't mind throwing a bit of effort at it to see if I can add any information to the pool of knowledge myself.
The problem doesn't always happen even on the same system where the problem has happened before with the same exact EDID override. I haven't found any particular trigger other than multiple monitors. Some have reported that changing a setting in the NVIDIA control panel such as the resolution or color depth can sometimes fix the problem, but I haven't been able to verify that.
(01-02-2025 03:16 AM)ozzuneoj Wrote: [ -> ]1. I like to use DLDSR for super smooth scaling in older games, but it seems the wonderfully made Nvidia drivers will provide high resolution DSR modes while limiting them to 60Hz on a 240Hz display. Like... why? Why is customizing DLDSR refresh rates not a setting in the control panel? Why isn't it just sending a native 2560x1440@240hz signal to the display when using DLDSR? I can override it with CRU by deleting absolutely all other resolutions that aren't 240Hz and it works totally fine. Why can't nvidia just make this the default behavior? The mind boggles...
DSR is supposed to have the same refresh rates as the native resolution. Where is it limited to 60 Hz? That might be another driver bug.
Thanks for the suggestion about automating CRU. If it comes to that at least I know where to start.
Regarding the DLDSR refresh rate issue, it has done this on my machine for a very long time. I think it has done it since I first got an RTX 3060 Ti capable of using DLDSR.
I just ran DDU to remove all traces of nvidia drivers and monitor left-overs from my system, I installed the latest nvidia drivers (566.36) and even with that clean slate this is what happens:
In nvidia control panel, go to 3D settings, click "DSR-Factors" , select 1.78x DL (5880x2880), click apply. Monitors flicker a bit, then come back.
Go to either the "Change Resolution" screen in Nvidia control panel or the Windows "Display Settings" screen. Select new DLDSR resolution, apply... and my main monitor (windows calls it 2, but nvidia calls it 1) is at 60Hz. Nvidia control panel allows me to select 60, 59, 50, 30 and 29Hz at that res. Windows advanced display settings only allow 60Hz.
For some reason it has always been this way for me unless I use CRU to remove all 60Hz resolutions. It was like this on my BenQ XL2720Z (1080P 120Hz), LG 27GR83Q (1440P 240Hz) as well as my current KTC monitors. I have been using Displayport for all of them since getting a 3060 Ti and then a 3080.
I have found posts about this for years too. It's baffling that things like this can so reliably plague some people across multiple GPUs, drivers and monitors, yet others never experience this. I would love to find a fix that doesn't require CRU, of course... so I tinker with it every once in a while, but I always just go back to CRU. Now that doing EDID overrides causes the blank screen on startup, I would love to find a solution to either of these issues.
EDIT: Here is a reddit post about the 60Hz DLDSR issue:
https://www.reddit.com/r/nvidia/comments...s_cap_fix/
I had a glimmer of hope when I stumbled upon posts stating that an old program called "ForceFix" would allow you to override refresh rates in DX9 games and it was the only other thing that worked for them aside from CRU.
I found it here:
https://sourceforge.net/projects/forcefi...p/download
... but since it's 10 years old it has a cap of 200Hz on the custom refresh rate, and it doesn't seem like it will help with applications that are in a full screen window mode (since the desktop refresh rate will be unaffected). Ugh... so annoying.
(12-31-2024 03:26 PM)ToastyX Wrote: [ -> ] (12-31-2024 07:23 AM)wheo9x Wrote: [ -> ]I've been using CRU for a while on my 240hz monitor but i recently upgraded to a 360hz Alienware 2523HF and i cant figure out how to do it, is there any chance i can get a detailed explanation on how to do it? my GPU is a 3060ti, thanks.
How to do what?
How to get stretched resolution using the CRU method with a 360hz monitor? it wont allow me to do it.