Custom Resolution Utility (CRU)

[kristianity1977]

I just imported that into cru and my tv has gone blank. I did a couple of restart of my pc and now I’m getting no image whatsoever on my Samsung tv? after my pc boots

EDIT

After another restart nvidia app asked me to reinstall my driver for the 4090 so i did that. I restarted and its all fine agian, and the 165hz has gone from Windows!!

Thank you so much!

[kristianity1977]

As a quick side note to yesterday where now my PC is not showing 165hz (which is great). Ive noticed a side effect of this is that HDR has stopped functioning. Is this a side effect of the EnableTiledDisplay registry edit? And is there a workaround?

[EeK]

(01-26-2026 08:51 PM)MUC Wrote:  The raw EDID shows that this TV already contains a Video Timing Data Block (VTDB) for 3840 x 1600 @ 144 Hz (CVT-RB @ 987.25 MHz) in the second CTA-861 block. However, CRU doesn't display this, only the VTDB for 60 Hz, which is also present there. The Nvidia driver is actually supposed to offer 3840 x 1600 @ 144 Hz as an option without CRU on this TV. Strange. If I assign your S90F EDID to my Nvidia card externally (without CRU) using an emulator, I can easily select 3840 x 1600 @ 144 Hz in the driver. But if it works for you now the way you did it, all the better. For modes with pixel clock frequencies above 655 MHz and without VICs, using a DisplayID via HDMI is certainly a good option.

That's odd. If I check the second CTA-861 block using CRU, it has 4 detailed resolutions, none of which are 3840x1600 @ 144 Hz:

3840x1600 @ 59.963 Hz
3840x1080 @ 59.968 Hz
3840x1080 @ 119.973 Hz
1920x1080 @ 143.981 Hz

Additionally, 3840x1600 @ 144 Hz never showed up by default in the Nvidia Control Panel with any of the drivers I tried.

What are VICs?

Quote:DSC wouldn't be the problem here. On GeForce RTX 30 or 40 series cards, Nvidia DSR only disappears if the needed pixel clock of the output signal is higher than 1350 MHz. This is not related to DSC. Please also see this:

https://tftcentral.co.uk/news/nvidia-dsr...-sometimes
https://tftcentral.co.uk/articles/loads-...nd-updates

I tested the GeForce RTX 50 series with CRU and it works up to almost exactly twice the pixel clock (2700 MHz). Even with DSC, because there's simply no other option for 4K @ 275 Hz via HDMI 2.1.

Ah, I don't actually use DSR or DLDSR. I mentioned trying to avoid DSC mainly for two reasons:

1. Never deal with the issue of Nvidia's driver ignoring EDID overrides when DSC is active and the maximum resolution and refresh rate combination exceeds the GPU's single-head pixel clock limit, since I have a 4000 series card.

2. Minimize the long intervals of black screens while switching resolutions/refresh rates and moving between full screen apps when DSC is active and multiple displays are connected.

I believe DSC is active at my display's maximum resolution and refresh rate combination (3840x2160 @ 144 Hz) with Full RGB 10-bit (necessary for HDR). The goal was to create a new ultrawide resolution (1600p) still running at 144 Hz with Full RGB 10-bit, but without the need for DSC.

I also ran into another issue when tring to enable Atmos (posted here). My current workaround is to simply run a single HDMI cable from the TV to the GPU most of the time, and connect the second cable (DP-to-HDMI), from the GPU to the AVR, whenever I play an Atmos-certified game - and only after I'm already logged in to Windows, as to prevent the other Nvidia bug that causes the OS to hang during boot when an EDID override present with multiple displays connected, since I could never get these scripts to work).

Quote:Yes, you can easily export the current EDID and use it later. The binary format (BIN) is universal. If you save it as a BIN file, you can also use it with other EDID editors.

Awesome, thanks for letting me know!

[MUC]

(Yesterday 06:47 PM)kristianity1977 Wrote:  Ive noticed a side effect of this is that HDR has stopped functioning.

I can't confirm that. I did the following test:

• I advertised the yesterday's EDID to my RTX 50 graphics card using an external emulator.
• When I then also imported the EDID into CRU, there were no changes, meaning the graphics driver read the EDID correctly from the HDMI port’s DDC (Display Data Channel).
  

I can select up to 4K @ 120 Hz RGB 10-bit with HDR and VRR (see attachment).

According to general understanding, EnableTiledDisplay = ZERO only prevents the graphics driver from offering settings that would result in the output signal having a pixel clock of more than 1350 MHz (RTX 30 and 40) or 2700 MHz (RTX 50). This actually has nothing to do with HDR.

Perhaps you made a careless mistake during the import process. It's almost always advantageous to select the "Import complete EDID" checkbox when importing an EDID into CRU to avoid ending up with an undefined mix-up in the registry. Did you do that? If not, you should probably do it. When experimenting with CRU, always make sure you know how to boot the system into safe mode in case of an emergency. This prevents Windows from loading the Nvidia graphics driver, which, with an EDID incompatible with the display, would then fail to show a signal.

[kristianity1977]

(Yesterday 09:26 PM)MUC Wrote:  

(Yesterday 06:47 PM)kristianity1977 Wrote:  Ive noticed a side effect of this is that HDR has stopped functioning.

I can't confirm that. I did the following test:

• I advertised the yesterday's EDID to my RTX 50 graphics card using an external emulator.
• When I then also imported the EDID into CRU, there were no changes, meaning the graphics driver read the EDID correctly from the HDMI port’s DDC (Display Data Channel).
  

I can select up to 4K @ 120 Hz RGB 10-bit with HDR and VRR (see attachment).

According to general understanding, EnableTiledDisplay = ZERO only prevents the graphics driver from offering settings that would result in the output signal having a pixel clock of more than 1350 MHz (RTX 30 and 40) or 2700 MHz (RTX 50). This actually has nothing to do with HDR.

Perhaps you made a careless mistake during the import process. It's almost always advantageous to select the "Import complete EDID" checkbox when importing an EDID into CRU to avoid ending up with an undefined mix-up in the registry. Did you do that? If not, you should probably do it. When experimenting with CRU, always make sure you know how to boot the system into safe mode in case of an emergency. This prevents Windows from loading the Nvidia graphics driver, which, with an EDID incompatible with the display, would then fail to show a signal.

Sorry. What I mean is, im getting the same message as you in that windows is showing that HDR is supported, but its not actually working even though windows reports that it is.

For example, with everything at default (so no Regedit, and no EDID import) then HDR, and RTX HDR are working as intended. (With RTX HDR I can see this as an option in Nvidia APP.

As soon as I do the regedit and import the EDID, HDR is showing as working still, but it isnt working in games and RTX HDR vanishes from the Nvidia APP and doesnt work in the Nvidia Overlay.

Resetting everything again to default makes it work again

On my attached image is the nvidia APP and where RTX Dynamic Vibrance is, under normal circumstances is RTX HDR. The second image shows my Nvidia App when everything is at default

Normal HDR in game, toggleing ON or OFF makes no difference to the image. So even though windows shows HDR as working, its not

[MUC]

(Yesterday 07:46 PM)EeK Wrote:  What are VICs?

VIC = Video Identification Code

These are numbers defined in the CTA-861 standard to define specific signal modes without requiring Detailed Timing Descriptors (DTDs).

For example, VIC #118 means 3840 x 2160 @ 120 Hz for the graphics driver (with specific predefined timing parameters). VICs are displayed in CRU as TV resolutions and can be added or removed as such. Anything not included in the CTA-861 standard cannot be added in the CTA-861 extension block if it would have a pixel clock higher than 655 MHz. This is why the input fields turn red when you attempt to define such a DTD in the CTA-861 extension.

(Yesterday 07:46 PM)EeK Wrote:  Never deal with the issue of Nvidia's driver ignoring EDID overrides when DSC is active and the maximum resolution and refresh rate combination exceeds the GPU's single-head pixel clock limit, since I have a 4000 series card.

As far as I could determine experimentally with an RTX 30 card, ignoring an EDID overwrite depends solely on this pixel clock limit (1350 MHz). DSC itself plays no role.

(Yesterday 07:46 PM)EeK Wrote:  I believe DSC is active at my display's maximum resolution and refresh rate combination (3840x2160 @ 144 Hz) with Full RGB 10-bit (necessary for HDR). The goal was to create a new ultrawide resolution (1600p) still running at 144 Hz with Full RGB 10-bit, but without the need for DSC.

The raw EDID of the S90F shows that 3840 x 2160 @ 144 Hz corresponds to the CVT-RB standard (1332.75 MHz). This works at 8-bit without DSC. It's a close call. However, it's true that the TV needs DSC if you want to output 10-bit (HDR). The interface shows a maximum of FRL5 (40 Gbps). At 10-bit, the signal would be at 112% of FRL5.

You can check it here: https://tomverbeure.github.io/video_timings_calculator

3840 x 1600 @ 144 Hz is no problem. The original EDID shows 987.25 MHz. That's also CVT-RB. At 10-bit, that means 83% of FRL5.

---

(Yesterday 09:38 PM)kristianity1977 Wrote:  As soon as I do the regedit and import the EDID, HDR is showing as working still, but it isnt working in games and RTX HDR vanishes from the Nvidia APP and doesnt work in the Nvidia Overlay.

Ah, okay, I see.

With the test setup described above and my RTX 50, I see "RTX HDR" both with the EDID override and with EnableTiledDisplay = ZERO.

The signal diagnostics of the LG TV I'm using for testing also show the reception of an HDR10 signal (see attachment). I can also see it visually. However, I'm not a gamer, so I can't test any games.

Unfortunately, I don't know why the Nvidia driver is behaving this way for you. Only Nvidia themselves can probably explain it in the context of games in full-screen mode. You can, of course, experiment with the EDID and, for example, remove unnecessary parts. That might make a difference.

[kristianity1977]

I am wondering now if I could possibly disable 165hz from the TV service menu and see if that helps.

Out of interest, Im not sure what importing the EDID is actually doing? As making the registry change alone is enough to remove the 165hz option. What does the EDID import add in addition?

I didnt mention this before but perhaps i should have. I am running Displayport from my 4090 to HDMI on my TV as my HDMI port in my GPU is damaged

[MUC]

(Yesterday 10:43 PM)kristianity1977 Wrote:  I am running Displayport from my 4090 to HDMI on my TV as my HDMI port in my GPU is damaged

Oh, that certainly makes a difference. Please link the adapter or cable you're using. If it's an adapter: What HDMI cable is attached to it and how long is it?

[kristianity1977]

(Yesterday 10:56 PM)MUC Wrote:  

(Yesterday 10:43 PM)kristianity1977 Wrote:  I am running Displayport from my 4090 to HDMI on my TV as my HDMI port in my GPU is damaged

Oh, that certainly makes a difference. Please link the adapter or cable you're using. If it's an adapter: What HDMI cable is attached to it and how long is it?

Its just a straight Displayport to HDMI cable and its 2m long. Its just a generic one from ebay. This is the description in the listing

8K DP to HDMI 2.1 Cables Audio Video Converter Unidirectional Adapter 8K@60Hz 4k@120Hz For HDTV Projector laptop Monitor


1. Support 8K@60Hz / 4K@120Hz Ultra high definition resolution brings the ultimate visual experience, suitable for professional design, high-end gaming, and home theater.

2. The gold-plated interface is resistant to oxidation and corrosion, ensuring more stable signal transmission and reducing screen flickering or black screen issues. Nylon weaving provides anti-interference and anti winding properties, enhancing durability

3. Supports synchronous audio transmission, solving video and audio needs with one cable

4. Supports dynamic HDR, VRR (variable refresh rate), ALLM (automatic low latency mode), and is compatible with gaming consoles such as PS5/Xbox

5. Wide compatibility: Suitable for RTX 30/40 series, AMD RX 6000/7000 graphics cards, as well as Samsung LG、 Sony 8K TV and Dell and Asus 4K monitors.

This is the listing if that helps

https://www.ebay.co.uk/itm/226726482888?...5894868057

[MUC]

(Yesterday 11:05 PM)kristianity1977 Wrote:  Its just a generic one from ebay.

Let's find out.

• Please download the attached file (VmmDPTool64.zip; this is a diagnostic tool for Synaptics chips, which is commonly found in 8K adapter cables. Tool version 9.1.7.0).
• Unzip the file.
• Run VmmDPTool64.exe. Right-click the file and select "Run as administrator". Either the message "Can not find Synaptics MST DP hub IC" appears, or a window opens.
• When a window opens, select the "Debug" tab.
• Click on "FW version" in the bottom left corner. What will then be displayed in the status window?