Threaded Mode | Linear Mode

***ToastyX*** · 11-29-2020, 02:24 PM

(11-29-2020 09:43 AM)mlleemiles Wrote: I seem to have trouble using the tool with new nvidia drivers (past 436.30).

If I create a new resolution that worked on previous drivers, system will crash immediately after a reboot or driver restart. My GPU is GTX660.

I have also tried to override EDID with registry, same result. Installing a monitor driver with EDID will fail and cause a BSOD as well. I'm trying to fix corrupted EDID on my monitor but it seems nvidia has blocked EDID override once and for all..

That sounds like a driver bug. Export a file with the changes you made and post it here.

mlleemiles · 11-29-2020, 03:00 PM

(11-29-2020 02:24 PM)ToastyX Wrote:
(11-29-2020 09:43 AM)mlleemiles Wrote: I seem to have trouble using the tool with new nvidia drivers (past 436.30).

If I create a new resolution that worked on previous drivers, system will crash immediately after a reboot or driver restart. My GPU is GTX660.

I have also tried to override EDID with registry, same result. Installing a monitor driver with EDID will fail and cause a BSOD as well. I'm trying to fix corrupted EDID on my monitor but it seems nvidia has blocked EDID override once and for all..
That sounds like a driver bug. Export a file with the changes you made and post it here.

Here is the changes I have made - simply adding 1440x900@60hz for standard resolution, everything else is empty/unchanged.

***ToastyX*** · 11-29-2020, 03:31 PM

(11-29-2020 03:00 PM)mlleemiles Wrote: Here is the changes I have made - simply adding 1440x900@60hz for standard resolution, everything else is empty/unchanged.

What monitor is this? This looks like a generic EDID that CRU creates if the driver can't read the EDID. You need at least one detailed resolution.

mlleemiles · 11-29-2020, 05:48 PM

(11-29-2020 03:31 PM)ToastyX Wrote:
(11-29-2020 03:00 PM)mlleemiles Wrote: Here is the changes I have made - simply adding 1440x900@60hz for standard resolution, everything else is empty/unchanged.
What monitor is this? This looks like a generic EDID that CRU creates if the driver can't read the EDID. You need at least one detailed resolution.

Yeah - I mentioned that my monitor EDID is corrupted thus no EDID is provided at all. I can add one standard resolution and it works fine in older drivers. But in newer ones, no matter what resolution type i add, driver will crash.

***ToastyX*** · 11-29-2020, 06:20 PM

(11-29-2020 05:48 PM)mlleemiles Wrote: Yeah - I mentioned that my monitor EDID is corrupted thus no EDID is provided at all. I can add one standard resolution and it works fine in older drivers. But in newer ones, no matter what resolution type i add, driver will crash.

Does that happen with a detailed resolution? The EDID standard requires at least one detailed resolution. Is the monitor connected using VGA, DVI, or HDMI?

mlleemiles · 11-29-2020, 06:30 PM

(11-29-2020 06:20 PM)ToastyX Wrote:
(11-29-2020 05:48 PM)mlleemiles Wrote: Yeah - I mentioned that my monitor EDID is corrupted thus no EDID is provided at all. I can add one standard resolution and it works fine in older drivers. But in newer ones, no matter what resolution type i add, driver will crash.
Does that happen with a detailed resolution? The EDID standard requires at least one detailed resolution. Is the monitor connected using VGA, DVI, or HDMI?

Yes, adding anything will crash driver unfortunately. My monitor is connected via VGA to DVI connector.

AchillesBoi · 11-30-2020, 09:32 PM

(11-23-2020 06:52 PM)ToastyX Wrote:
(11-23-2020 11:33 AM)AchillesBoi Wrote: A new driver version came out recently and I clean-installed it but the bug is still present. I downgraded to several older versions from months ago to try to find one that works but the bug is present in all driver versions. The only way to avoid the bug is to use reset-all.exe then restart-64.exe (or reboot) and then not use CRU at all.
In Radeon Settings, under Settings (cogwheel at the top-right), Graphics, Advanced (at the bottom), do you have an option for 10-bit pixel format? If so, try enabling it.

I think the last driver that didn't have this issue was 19.2.1, but Windows 10 will automatically upgrade to a newer driver if you install a version that's too old.

I always install the latest version of my GPU drivers, straight from AMD's website and not from the Windows Store/Update. I do not have the 10-bit pixel format enabled from within Graphics -> Advanced because all my games take a massive performance hit when I enable it. I do have 10 bpc enabled on the Display tab since my monitor is compatible with 10 bpc, and I would like to continue using 10 bpc.

It seems to me that the bug here is caused by editing the EDID, maybe something CRU is doing is conflicting with the way Windows (or the GPU) reads that data? Allowing Windows to build the EDID from scratch shows no issues, but presenting Windows with an edited EDID creates the issue.

easterhands · 12-01-2020, 12:11 AM

Hello there, Is it possible to create HDMI 2.1 spec custom resolutions? I'm having trouble figuring it out if so. I have an LG B9 with an RTX 3080 and am trying to create an ultrawide 3840x1620 resolution that will support HDR and 12 bit color at 120hz.

***ToastyX*** · 12-01-2020, 04:22 AM

(12-01-2020 12:11 AM)easterhands Wrote: Hello there, Is it possible to create HDMI 2.1 spec custom resolutions? I'm having trouble figuring it out if so. I have an LG B9 with an RTX 3080 and am trying to create an ultrawide 3840x1620 resolution that will support HDR and 12 bit color at 120hz.

That depends on the driver. What happens when you add 3840x2160 @ 120 Hz with CRU?

***ToastyX*** · 12-01-2020, 04:22 AM

(11-30-2020 09:32 PM)AchillesBoi Wrote: It seems to me that the bug here is caused by editing the EDID, maybe something CRU is doing is conflicting with the way Windows (or the GPU) reads that data?

No, it's an AMD driver bug. It's probably applying an 8-bit gamma table to 10-bit color, causing 1/4th the brightness.