Custom Resolution Utility (CRU)

[witega]

I added that as a first detailed resolution:



Now I'm running into an issue where after restarting the driver (and not going into Recovery Mode) my monitor turns off and back on again after every 5 seconds or so. So I basically go back into my monitor's OSD, while the screen is still on, power it off, wait a few minutes then turn it on again. Then I restart the drivers until it's stable where I'm not encountering this issue.

Should I remove the extension block from the CRU application since it's identical to my first detailed, or does that not matter?

[ToastyX]

(06-13-2019 04:10 AM)witega Wrote:  Should I remove the extension block from the CRU application since it's identical to my first detailed, or does that not matter?

It's redundant so it doesn't need to be there, but it doesn't matter. Blinking on and off would indicate the monitor or cable can't handle the resolution or timing parameters you gave it. I would try the "LCD standard" and "LCD native" timing options to see if that improves anything.

[witega]

ToastyX, thanks for your replies.

When you said "Recovery Mode" applies the default settings until the next graphics driver restart, what do you mean by "default settings" here? The first detailed resolution I have or something else?

So now every time I do the restart.exe, run a benchmark, I keep getting these black line artifacts as I posted earlier in my videos. Yet, if I do restart.exe and then go into Recovery Mode, these artifacts are no longer present in the benchmark. They also are gone from games like PUBG.

This is kind of a head scratcher to me.

[ToastyX]

(06-14-2019 03:07 PM)witega Wrote:  When you said "Recovery Mode" applies the default settings until the next graphics driver restart, what do you mean by "default settings" here? The first detailed resolution I have or something else?

Default as in no override, as if you didn't change anything with CRU.

[xtcrefugee]

(06-12-2019 05:01 PM)ToastyX Wrote:  The driver is not handling EDID overrides correctly. Export a file from CRU and post it here. I will see if I can create an alternative method that works with Intel.

Just FYI I finally found a solution for the current Intel DCH drivers (tested with 26.20.100.6912 on my Surface Go). Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\SHP14A6 there were two keys that referred to the same display, one with the EDID_OVERRIDE key (presumably added by CRU) and one without. So I copied everything in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\SHP14A6\4&3291bf54&0&UID265988\Device Parameters\EDID_OVERRIDE to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\SHP14A6\1&8713bca&0&UID0\Device Parameters\EDID_OVERRIDE and rebooted, and afterwards my custom resolutions were again shown and usable in Windows display settings.

This is a relief as it looks like the DCH drivers are required for Windows 10 1903, the legacy drivers no longer have a control panel on this version.

[ToastyX]

(06-23-2019 03:40 PM)xtcrefugee Wrote:  Just FYI I finally found a solution for the current Intel DCH drivers (tested with 26.20.100.6912 on my Surface Go). Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\SHP14A6 there were two keys that referred to the same display, one with the EDID_OVERRIDE key (presumably added by CRU) and one without. So I copied everything in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\SHP14A6\4&3291bf54&0&UID265988\Device Parameters\EDID_OVERRIDE to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\SHP14A6\1&8713bca&0&UID0\Device Parameters\EDID_OVERRIDE and rebooted, and afterwards my custom resolutions were again shown and usable in Windows display settings.

CRU should list both entries in the monitor list, so you should be able to use the "Copy" and "Paste" buttons at the top instead of editing the registry directly. The solution doesn't make sense though. The second entry is added by the Microsoft Basic Display Adapter driver and shouldn't apply to Intel's driver. That seems like a bug in Intel's driver.

[scottroberts91]

I currently have a Samsung Q900RA 8K set, i can enable 8K 30HZ @ 4.2.0 Chroma in CRU but I've been unable to add 3840x2160 @ 120HZ @ 4.2.0

The TV does have a 120HZ panel and enough bandwidth for 4K 120 @ 4.2.0 but i cant add the resolution.

My GPU is a 1080TI

Regards
Scott

[Osahashi]

Hello,

can someone please help me with the HDMI support? I have a 27MU67-B and a PS4 Pro, without any HDMI at CEA-861 the console runs not at 4K, I already change the cable.

The monitor use HDMI 1.2, the Nvidia driver is patched (if it makes any different).

I can add 3840x2160 at HDMI resolutions, but only 24 hz, 25 hz and 30 hz, not 60 hz? I think because my PC connects via DP and not HDMI, I can add a custom one, but only with a code that I didn't know.

What is ACP/ISRC? 30-bit deep color (10 bcp) is 10-bit color code right? Where is RGB, there is only YCbCr?

Default TMDS is 340 MHz, is that ok?

Is there any FAQ for the CRU tool or Wiki?

Edit: I know now what's the problem is, it's the HDCP! If I turn it off at the PS4 Pro the HDMI signal works with 4k and deep color, turn it on no signal. The monitor has in the service menu the setting "load HDCP", default is NO, maybe it works if I turn it on...
Can't turn it on, if I set it to YES it goes back to NO.

[ToastyX]

(06-26-2019 11:09 AM)Osahashi Wrote:  can someone please help me with the HDMI support? I have a 27MU67-B and a PS4 Pro, without any HDMI at CEA-861 the console runs not at 4K, I already change the cable.

CRU creates software overrides. It does not affect the monitor, so it would not transfer over to the PS4. The manual for the monitor says Ultra HD Deep Color must be on to enable 4K @ 60 Hz.

For PC use, you should not need to edit anything with CRU to get 4K @ 60 Hz. It should already be defined, usually as a detailed resolution and/or in a TV resolutions data block in the extension block. If you're using DisplayPort, you should not need an HDMI data block.

ACP/ISRC is Audio Content Protection/International Standard Recording Code. 30-bit deep color is 10 bits per channel (bpc). HDMI always supports RGB. 4K @ 60 Hz with RGB or YCbCr 4:4:4 requires HDMI 2.0. HDMI 2.0 requires both the HDMI data block and the HDMI 2.0 data block. Both should already be there when using HDMI if the monitor supports HDMI 2.0. HDMI 2.0 monitors usually define 340 MHz TMDS for the HDMI data block and 600 Mcsc TMDS for the HDMI 2.0 data block. These basically define pixel clock limits.

[ToastyX]

(06-25-2019 12:18 PM)scottroberts91 Wrote:  I currently have a Samsung Q900RA 8K set, i can enable 8K 30HZ @ 4.2.0 Chroma in CRU but I've been unable to add 3840x2160 @ 120HZ @ 4.2.0

The TV does have a 120HZ panel and enough bandwidth for 4K 120 @ 4.2.0 but i cant add the resolution.

How are you adding the resolutions? If you're using a 4:2:0 resolutions data block, 4K @ 100/120 Hz and 8K/10K resolutions are newer and might not be fully supported by current drivers. They might have added support for 4:2:0 with 8K @ 30 Hz but not 4K @ 120 Hz. You'll have to ask NVIDIA about supporting 4:2:0 with 4K @ 120 Hz.