Custom Resolution Utility (CRU)

[MUC]

(10-08-2026 06:56 PM)AssadFaszad Wrote:  I did try it, and it did work. I believe this was the first time I saw it running on any other bit depth than 8, as it went down to 6. I do have 180Hz working with 8bit though, but thank you. Do you by any chance have a color profile for this panel?

No, unfortunately, I don't have a color profile.

If the bit depth drops to 6 bpc based on my EDID, that indicates the DisplayPort interface is running only on the HBR2 protocol.

1440p @ 180 Hz RGB 8-bit CVT-RB = 107% HBR2 (768.68 MHz pixel clock)

The 180 Hz mode in your EDID is defined at 700 MHz, which corresponds to 97% HBR2. If it works that way, leave it as is.

---

I do not believe the Tiled Display Topology is necessary in your latest EDID. Please try the attachment. This comes as close as possible to the EDID compliance in the structure you selected.

[Qattos]

Hi everyone!

Before anything, thank you so much ToastyX for everything you do, I've been using CRU for a couple of years and it's been very useful on older monitors.
I have a question I think only the people over here might help with or at least explain its cause, I think it's beyond the scope of CRU because it happens before Windows boot.

I have a Lenovo LOQ 16APH8 with an RTX 4060 + AMD iGPU, my original display panel was B160UAN05.A 1920x1200 with G-Sync 144Hz, I upgraded it to a different panel N160GME-GTB 2560x1600 240Hz that only supports VRR.
This new panel is not supported by Lenovo, but it works perfectly once Windows is loaded, no issues whatsoever.
The issue happens when I switch to dGPU-only mode in BIOS, in the pre-Windows boot and in BIOS, the display looks distorted and static-y like the old TVs (see the video I attached), once Windows login page is loaded, the display is working perfectly as intended.
This issue is not present when I'm on Hybrid-mode/Switchable graphics, it only happens on dGPU-only mode.

My first thought was that my new panel's EDID data is probably corrupt or messed up, but I compared it to dumps from linux-hardware dot org for the same model of course, and it's an exact match, so nothing wrong there.
I'm now suspecting my Nvidia's vBIOS GOP version needs an update or something, I have no idea what's this, I used AI to try to troubleshoot this, could be wrong.

I looked up laptops with my exact GPU and new panel, found one Acer-PHN16-72, got its vBIOS and it seems to have a newer GOP version 7.0.0.19 compared to mine 7.0.0.13, I should note that this laptop I found has G-Sync even though N160GME-GTB doesn't support G-Sync.

Any ideas guys?


Link to video
   

  N160GME-GTB.bin (Size: 256 bytes / Downloads: 14)

[ToastyX]

(10-16-2026 07:27 PM)Qattos Wrote:  Hi everyone!

Before anything, thank you so much ToastyX for everything you do, I've been using CRU for a couple of years and it's been very useful on older monitors.
I have a question I think only the people over here might help with or at least explain its cause, I think it's beyond the scope of CRU because it happens before Windows boot.

I have a Lenovo LOQ 16APH8 with an RTX 4060 + AMD iGPU, my original display panel was B160UAN05.A 1920x1200 with G-Sync 144Hz, I upgraded it to a different panel N160GME-GTB 2560x1600 240Hz that only supports VRR.
This new panel is not supported by Lenovo, but it works perfectly once Windows is loaded, no issues whatsoever.
The issue happens when I switch to dGPU-only mode in BIOS, in the pre-Windows boot and in BIOS, the display looks distorted and static-y like the old TVs (see the video I attached), once Windows login page is loaded, the display is working perfectly as intended.
This issue is not present when I'm on Hybrid-mode/Switchable graphics, it only happens on dGPU-only mode.

My first thought was that my new panel's EDID data is probably corrupt or messed up, but I compared it to dumps from linux-hardware dot org for the same model of course, and it's an exact match, so nothing wrong there.
I'm now suspecting my Nvidia's vBIOS GOP version needs an update or something, I have no idea what's this, I used AI to try to troubleshoot this, could be wrong.

I looked up laptops with my exact GPU and new panel, found one Acer-PHN16-72, got its vBIOS and it seems to have a newer GOP version 7.0.0.19 compared to mine 7.0.0.13, I should note that this laptop I found has G-Sync even though N160GME-GTB doesn't support G-Sync.

Any ideas guys?

That's happening because the BIOS is using the wrong resolution, and laptop panels don't have scalers, so it doesn't display correctly. The graphics driver in Windows reads the EDID, so it uses the correct resolution, and lower resolutions are scaled by the GPU. I don't know why the BIOS would only use the wrong resolution with the dedicated GPU though.

[Qattos]

(10-17-2026 10:58 PM)ToastyX Wrote:  That's happening because the BIOS is using the wrong resolution, and laptop panels don't have scalers, so it doesn't display correctly. The graphics driver in Windows reads the EDID, so it uses the correct resolution, and lower resolutions are scaled by the GPU. I don't know why the BIOS would only use the wrong resolution with the dedicated GPU though.

UPDATE:
I went ahead and flashed the Acer vBIOS I mentioned earlier, and now my issue is solved, my laptop is working perfectly fine after stress testing the gpu, I have yet to test the only HDMI port on my laptop but I don't use it that much anyway.

OLD post:
Thank you so much for clarifying this.
I assume there's not much I can do to resolve this? Besides modding Nvidia's vBIOS, even this seems impossible with how much Nvidia locked down their vBIOS.
I have a CH341A programmer to dump my BIOS file but I wouldn't know what to mod even if I was willing to risk it.
Either way, thanks again.

[TheBinarySon]

Hello! New person here, just trying to figure how to optimize my setup as best I can.

I am using an old RCA 4K UHD LED TV (RLDED5098-UHD) as my external and main monitor for my Framework 16 Laptop. I recently went through the settings to see if I had everything set up properly, and came across the option to select the EDID 2.0 (the tv was only using 1.4). This, a new usb-c to hdmi adapter, and a new hdmi cable led to me going from 1920x1080 at 60 Hz to 4K at 60 Hz.

However, I am running into 2 possible issues, and if they affect the display's ability to be the best it can be, then I'd like to fix them if possible: 1.) the laptop only recognizes the tv as "MSTAR Demo," and it only has the "Generic PnP Monitor" driver; and 2.) Despite some places saying that the TV supports HDR10 (though not everywhere, and the instruction manual doesn't appear to say anything about it either way), the laptop refuses to say that the tv does so, and I've tried uninstalling the monitor, trying two of the 4 hdmi ports (none of them say which are ARC/e-ARC or HDR), restarting the laptop and/or the TV, changing the pixel format in AMD Adrenalin from RGB 444 to YCbCr 422 or 420 in order to go from 8 bpc to 10 bpc, etc.

I came across your website during my research into these issues, so I wanted to see if there's any help or insight you folks could provide me. I don't see where in CRU you can override the laptop's insistence that the tv isn't HDR (though maybe it isn't and the places that say it's HDR10 are just wrong?), so before I go messing things up I wanted to ask you fine folks first. Any help would be appreciated.

Thanks!

[MUC]

(10-19-2026 04:23 AM)TheBinarySon Wrote:  Any help would be appreciated.

Please run edid-test.exe on the laptop while connected to the TV. A file named "edid-test.TXT" will be created in the same folder. This file contains the EDID currently detected by the laptop. Please attach that file here so we can verify it.

Please also post a link to the adapter used.

[TheBinarySon]

(10-19-2026 07:26 PM)MUC Wrote:  Please run edid-test.exe on the laptop while connected to the TV. A file named "edid-test.TXT" will be created in the same folder. This file contains the EDID currently detected by the laptop. Please attach that file here so we can verify it.

Please also post a link to the adapter used.

Thanks for the response! I've attached the TXT file, and the links to the cable and adapter I bought to improve my connection to the display and get 4k are below.

FYI, I did some troubleshooting and online research using the Google Search AI mode and the conclusion it got to was that the MStar Demo was only a superficial issue related only to the name, and that nothing was being missed. With respect to the HDR, the tv apparently is compatible with HDR10, which means it can process certain HDR playback formats without just showing a black screen, but that since its top brightness is only 300 nits, it's not real HDR and once again I'm not missing anything. All of that to say I appreciate any help I can get if folks think these conclusions are wrong, but I don't want to bother anyone to badly, and if the MStar thing is just a naming bug then I am fine with it.

Cable - https://www.amazon.com/dp/B08M9HND4F/?tag=mtests-20#ad
Adapter - https://www.amazon.com/dp/B08GC1K9TF/?tag=mtests-20#ad


  edid-test.txt (Size: 2 KB / Downloads: 7)

[mdrejhon]

(08-22-2026 03:58 PM)AssadFaszad Wrote:  Hi, I've got a laptop 1440p@165Hz GSync Compatible screen.

Laptops are extremely finicky. I have a Razer Blade. It uses uses NVIDIA Optimus between itself and the internal Radeon iGPU (AMD Ryzen HX 370).

If you're using a cheap USB4 adaptor, find one of those DP80 adaptors (USB-C to DP 80 Gbps), direct AltMode rather than other USB4 display protocols. I found it solved my problem.

The UGreen brand I found works fine. It passed everything including VRR but I really, really had to fiddle *both* the Radeon and NVIDIA settings to get the VRR puncturing out of the laptop to the external monitor without loss of protocol (converters like HDMI->DP can lose metadata, and sometimes DP->DP conversion occurs generically in cheap adaptors, losing some VRR PnP metadata along the way).

VRR out of a USB-C laptop port using NVIDIA Optimus = lots of hoop jumping.
Correct converter, correct cable, correct settings in AMD (or Intel), correct settings in NVIDIA, and correct settings in Windows.

Not only that...
Fiddling with two control panels on a dual-GPU laptop is necessary because often the game (rendered on dGPU) is displayed as a bordereless window on the iGPU. In a gaming laptop using dual GPU to an external monitor that can ONLY run on the iGPU *then* both the dGPU/iGPU needs to have VRR properly configured for the VRR to pass through sometimes, depending on your laptop capabilities. It SHOULD by default, but sometimes a hoop jump is needed, to get VRR working properly on an external monitor with a dual-GPU gaming laptop.

In addition to Windows DRR being annoyingly default ON even in a plugged-in gaming laptop, it's a lot of hoop jumping to get VRR working reliably in the first place, *lest* even before touching the VRR range remotely at all.
Nice thing is if DRR works, I know VRR works, then I can turn off DRR. Challenge is that the game framepaces properly to VRR instead of DWM/borderless/iGPU/dGPU interfering and mis-framepacing (making it look like VRR was not enabled).

Big headache... Layers upon layers of abstraction when dealing with custom modes from the USB-C port of a dual-GPU gaming laptop, especially those models with mandatory iGPU routing for external displays. On some models, render/output GPU can never be same GPU when your game is using the dGPU.

[AssadFaszad]

(10-20-2026 03:53 AM)mdrejhon Wrote:  

(08-22-2026 03:58 PM)AssadFaszad Wrote:  Hi, I've got a laptop 1440p@165Hz GSync Compatible screen.

Laptops are extremely finicky. I have a Razer Blade. It uses uses NVIDIA Optimus between itself and the internal Radeon iGPU (AMD Ryzen HX 370).

If you're using a cheap USB4 adaptor, find one of those DP80 adaptors (USB-C to DP 80 Gbps), direct AltMode rather than other USB4 display protocols. I found it solved my problem.

The UGreen brand I found works fine. It passed everything including VRR but I really, really had to fiddle *both* the Radeon and NVIDIA settings to get the VRR puncturing out of the laptop to the external monitor without loss of protocol (converters like HDMI->DP can lose metadata, and sometimes DP->DP conversion occurs generically in cheap adaptors, losing some VRR PnP metadata along the way).

VRR out of a USB-C laptop port using NVIDIA Optimus = lots of hoop jumping.
Correct converter, correct cable, correct settings in AMD (or Intel), correct settings in NVIDIA, and correct settings in Windows.

Not only that...
Fiddling with two control panels on a dual-GPU laptop is necessary because often the game (rendered on dGPU) is displayed as a bordereless window on the iGPU. In a gaming laptop using dual GPU to an external monitor that can ONLY run on the iGPU *then* both the dGPU/iGPU needs to have VRR properly configured for the VRR to pass through sometimes, depending on your laptop capabilities. It SHOULD by default, but sometimes a hoop jump is needed, to get VRR working properly on an external monitor with a dual-GPU gaming laptop.

In addition to Windows DRR being annoyingly default ON even in a plugged-in gaming laptop, it's a lot of hoop jumping to get VRR working reliably in the first place, *lest* even before touching the VRR range remotely at all.
Nice thing is if DRR works, I know VRR works, then I can turn off DRR. Challenge is that the game framepaces properly to VRR instead of DWM/borderless/iGPU/dGPU interfering and mis-framepacing (making it look like VRR was not enabled).

Big headache... Layers upon layers of abstraction when dealing with custom modes from the USB-C port of a dual-GPU gaming laptop, especially those models with mandatory iGPU routing for external displays. On some models, render/output GPU can never be same GPU when your game is using the dGPU.

Thank you for the write-up. Luckily I have a single screen for now and run on dGPU only. I have a friend who has a laptop with such routing. It was jarring to see. Glad you figured it out.

By any chance do you know if it's possible to have above 8bit color depth on laptops? I realize it'd involve dropping the refresh rate. But curiosity is getting the better of me.

[MUC]

(10-20-2026 02:57 AM)TheBinarySon Wrote:  I've attached the TXT file, and the links to the cable and adapter I bought to improve my connection to the display and get 4k are below.

The EDID indicates that the TV was manufactured in 2014 and supports 4K @ 60 Hz.

However, HDMI 2.0a — which includes HDR support — was not introduced until 2015. Therefore, I would venture to say that this TV does not support HDR. There is no mention of HDR support in the EDID. The USB-C to HDMI adapter contains an active protocol converter chip. It is theoretically possible that this chip lacks HDR support (there is no mention of it on Amazon) and, as a result, filters out the HDR information from the EDID before it reaches the graphics card driver. I consider this unlikely, however. I believe the TV is a standard HDMI 2.0 device - lacking the "a" specification — and therefore does not support HDR.

The EDID says:
Display Product Name: 'MStar Demo'

The manufacturer chose this name deliberately. Why, remains their secret. It has no bearing on the device's functions. It is just a name. You can also change it, if you wish.

---

(10-20-2026 10:29 PM)AssadFaszad Wrote:  By any chance do you know if it's possible to have above 8bit color depth on laptops?

In principle, yes. Provided the panel supports it. But the original EDID of your built-in laptop screen explicitly states: "Bits per primary color channel: 8". It can therefore be assumed that 10-bit is either not supported or would lead to undesirable results.