Monitor Tests Forum

(06-07-2025 10:28 PM)ToastyX Wrote: [ -> ]That's an NVIDIA driver bug. I'm not sure what triggers it, but it seems to be happening more with 5000-series GPUs.

I made additional changes to the EDID:

Added extension override data block.
HDMI data block: Max TMDS clock should be 340 MHz.
HDMI 2.1 data block: Max TMDS character rate should be 600 Mcsc.
Deleted 4:2:0 capability map data block since that ties with the TV resolutions data block.
Set the preferred flag in the detailed resolution.

Try importing this:

If that doesn't help, what if you keep 640x480 @ 60 Hz enabled under established resolutions?

Your file worked I have 144hz only now and the Nvidia Control Panel is fully functional. It seems whatever was breaking the Nvidia driver must have been in those changes you did because those are the only things different.

Also I added 2880x2160 under the DisplayID 1.3 detailed resolution block, and that triggers a signal change only one time per boot then for subsequent resolution changes GPU integer scaling works to keep sending 3840x2160 144hz to the monitor at all times so no more signal swap black screens and broken monitor settings. Super happy now, thanks so much for your help. That's a game changer for this monitor!

Hi,

Having issues with my Samsung QN90B connected to PC with an GigaByte 7900 XTX via HDMI 2.1.

The HDR output to Windows 11 reports peak brightness as 830 Nits, and using the HDR calibration I can see the shape vanishes at 830 so its reporting correctly.

The TV is supposed to be rated to 2000 and in SDR mode looks obviously brighter, I have tried quite a few times to fix this but no joy so I picked up CRU to try and change the metadata for the max luminance:



Tried these settings and other values with the HDR tick for traditional gamma on and off and nothing makes the reported peak brightness change, did the recomended steps of: open CRU change values, use the restart64, even then reboot the PC, but still reports wrong.

Oddly it only ever shifts to report 817 or 830 and cant figure out why it changes.

Tried:
Different Adreneline drivers
Different Ports
Windows/card at latest drivers
HDR appears to work correctly for my playstation also connected to TV though cant check directly
Samsung TV HDR settings to off basic and advances for HDR tone mapping make no diff.
Samsung TV's have a Game HDR mode which is basically HGIG but this cant be toggled for PC connections for some reason, unsure why

Am I missing something with CRU settings? It really bugs me that I either have to choose between a poorly calibrated but bright SDR picture or an accurate but not as bright as it could be HDR for just my PC.

(06-09-2025 02:17 PM)Sadarak12 Wrote: [ -> ]Hi,

Having issues with my Samsung QN90B connected to PC with an GigaByte 7900 XTX via HDMI 2.1.

The HDR output to Windows 11 reports peak brightness as 830 Nits, and using the HDR calibration I can see the shape vanishes at 830 so its reporting correctly.

The TV is supposed to be rated to 2000 and in SDR mode looks obviously brighter, I have tried quite a few times to fix this but no joy so I picked up CRU to try and change the metadata for the max luminance:

https://i.imgur.com/QF10NPf.png

Tried these settings and other values with the HDR tick for traditional gamma on and off and nothing makes the reported peak brightness change, did the recomended steps of: open CRU change values, use the restart64, even then reboot the PC, but still reports wrong.

Oddly it only ever shifts to report 817 or 830 and cant figure out why it changes.

Tried:
Different Adreneline drivers
Different Ports
Windows/card at latest drivers
HDR appears to work correctly for my playstation also connected to TV though cant check directly
Samsung TV HDR settings to off basic and advances for HDR tone mapping make no diff.
Samsung TV's have a Game HDR mode which is basically HGIG but this cant be toggled for PC connections for some reason, unsure why

Am I missing something with CRU settings? It really bugs me that I either have to choose between a poorly calibrated but bright SDR picture or an accurate but not as bright as it could be HDR for just my PC.

AMD's driver might be using the HDR information in the FreeSync data block instead, but CRU doesn't have the ability to edit that yet. Run reset-all.exe and restart. Then run this and post the edid-test.txt here: https://www.monitortests.com/edid-test.zip

(06-09-2025 07:53 PM)ToastyX Wrote: [ -> ]AMD's driver might be using the HDR information in the FreeSync data block instead, but CRU doesn't have the ability to edit that yet. Run reset-all.exe and restart. Then run this and post the edid-test.txt here: https://www.monitortests.com/edid-test.zip

Thanks and ill post the result of that log below, but I have also partially resolved the issue myself since this post so I will pop what I did here for future google searches:

AMD Driver seems to default to 10bc for Colour Depth and YCbCr 4:4:4 for pixel format. Changing these to 12bc and RGB 4:4:4 immediately put the peak brightness to 970 Nit's with a noticeable change in how washed out the image was looking under HDR. Its still not as high as it should be but its the first time I have been able to make the reported peak nits change since the issue began at least.

Result of the log:

DISPLAY\SAM71FB\7&AA3BF57&2&UID521 (active):
00 FF FF FF FF FF FF 00 4C 2D FB 71 00 0E 00 01
01 20 01 03 80 6F 3E 78 0A B3 61 AB 4F 46 A8 27
0B 50 54 BD EF 80 71 4F 81 C0 81 00 81 80 95 00
A9 C0 B3 00 D1 C0 08 E8 00 30 F2 70 5A 80 B0 58
8A 00 50 1D 74 00 00 1E 6F C2 00 A0 A0 A0 55 50
30 20 35 00 50 1D 74 00 00 1A 00 00 00 FD 00 18
78 0F FF 8F 00 0A 20 20 20 20 20 20 00 00 00 FC
00 51 42 51 39 30 0A 20 20 20 20 20 20 20 01 30
02 03 75 F0 E2 78 03 5A 61 60 65 66 75 76 DA DB
10 1F 04 13 05 14 20 21 22 40 3F 5D 5E 5F 62 64
03 12 2F 0D 57 07 09 07 07 15 07 50 57 07 01 67
54 03 83 0F 00 00 E2 00 4F E3 05 C3 01 6E 03 0C
00 30 00 B8 44 28 00 80 01 02 03 04 6D D8 5D C4
01 78 80 6B 02 30 90 C1 34 05 E3 06 0D 01 E2 0F
FF E5 01 8B 84 90 69 6D 1A 00 00 02 0B 30 90 00
04 81 05 77 0F 00 00 00 00 00 00 00 00 00 00 BA
02 03 04 F0 58 4D 00 B8 A1 38 14 40 F8 2C 45 00
00 00 00 00 00 1E 5C C1 00 E4 A2 38 AA 40 24 2C
45 80 00 00 00 00 00 1E CF CB 00 80 F5 40 3A 60
20 A0 3A 50 00 00 00 00 00 1C 1A 68 00 A0 F0 38
1F 40 30 20 3A 00 00 00 00 00 00 1A 74 D6 00 A0
F0 38 40 40 30 20 3A 00 00 00 00 00 00 1A 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2C
70 12 79 00 00 03 01 64 59 87 00 08 7F 07 9F 00
2F 80 1F 00 37 04 4C 00 02 00 04 00 51 2C 02 08
FF 0E 2F 02 F7 80 1F 00 6F 08 59 00 4B 00 07 00
EA B7 00 08 FF 09 AB 00 07 80 1F 00 37 04 75 00
3E 00 07 00 86 94 01 08 FF 0E 67 01 93 80 1F 00
3F 06 71 00 63 00 07 00 1D FF 00 08 FF 0E 4F 00
07 80 1F 00 37 04 4C 00 3E 00 07 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 90

(06-09-2025 09:13 PM)Sadarak12 Wrote: [ -> ]Thanks and ill post the result of that log below, but I have also partially resolved the issue myself since this post so I will pop what I did here for future google searches:

AMD Driver seems to default to 10bc for Colour Depth and YCbCr 4:4:4 for pixel format. Changing these to 12bc and RGB 4:4:4 immediately put the peak brightness to 970 Nit's with a noticeable change in how washed out the image was looking under HDR. Its still not as high as it should be but its the first time I have been able to make the reported peak nits change since the issue began at least.

Result of the log:

DISPLAY\SAM71FB\7&AA3BF57&2&UID521 (active):
00 FF FF FF FF FF FF 00 4C 2D FB 71 00 0E 00 01
01 20 01 03 80 6F 3E 78 0A B3 61 AB 4F 46 A8 27
0B 50 54 BD EF 80 71 4F 81 C0 81 00 81 80 95 00
A9 C0 B3 00 D1 C0 08 E8 00 30 F2 70 5A 80 B0 58
8A 00 50 1D 74 00 00 1E 6F C2 00 A0 A0 A0 55 50
30 20 35 00 50 1D 74 00 00 1A 00 00 00 FD 00 18
78 0F FF 8F 00 0A 20 20 20 20 20 20 00 00 00 FC
00 51 42 51 39 30 0A 20 20 20 20 20 20 20 01 30
02 03 75 F0 E2 78 03 5A 61 60 65 66 75 76 DA DB
10 1F 04 13 05 14 20 21 22 40 3F 5D 5E 5F 62 64
03 12 2F 0D 57 07 09 07 07 15 07 50 57 07 01 67
54 03 83 0F 00 00 E2 00 4F E3 05 C3 01 6E 03 0C
00 30 00 B8 44 28 00 80 01 02 03 04 6D D8 5D C4
01 78 80 6B 02 30 90 C1 34 05 E3 06 0D 01 E2 0F
FF E5 01 8B 84 90 69 6D 1A 00 00 02 0B 30 90 00
04 81 05 77 0F 00 00 00 00 00 00 00 00 00 00 BA
02 03 04 F0 58 4D 00 B8 A1 38 14 40 F8 2C 45 00
00 00 00 00 00 1E 5C C1 00 E4 A2 38 AA 40 24 2C
45 80 00 00 00 00 00 1E CF CB 00 80 F5 40 3A 60
20 A0 3A 50 00 00 00 00 00 1C 1A 68 00 A0 F0 38
1F 40 30 20 3A 00 00 00 00 00 00 1A 74 D6 00 A0
F0 38 40 40 30 20 3A 00 00 00 00 00 00 1A 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2C
70 12 79 00 00 03 01 64 59 87 00 08 7F 07 9F 00
2F 80 1F 00 37 04 4C 00 02 00 04 00 51 2C 02 08
FF 0E 2F 02 F7 80 1F 00 6F 08 59 00 4B 00 07 00
EA B7 00 08 FF 09 AB 00 07 80 1F 00 37 04 75 00
3E 00 07 00 86 94 01 08 FF 0E 67 01 93 80 1F 00
3F 06 71 00 63 00 07 00 1D FF 00 08 FF 0E 4F 00
07 80 1F 00 37 04 4C 00 3E 00 07 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 90

The monitor doesn't include any luminance data in the HDR static metadata data block, so it's using the FreeSync data block. The FreeSync data block is not documented publicly, so I haven't added support for editing anything other than the range. I have an idea where the luminance data is, so I plan to add that eventually, but my focus has been on CRU 2.0 lately.

On the 16th line of data where it shows 04 81 05 77 0F at the beginning, the 81 is the max luminance, and the 05 is the min luminance. There's another luminance profile after it (77 0F), but I'm not sure what it's for. You can edit the values and import the text file into CRU if you want to experiment.

Here is an example with the max luminance set to at least 2000 cd/m²: [attachment=1587]

Edit: added color in the quote so you can see where the luminance data is.

I wonder if EDID override works for anyone using a DisplayPort (DP) display with recent Nvidia drivers.
Any change I make to my DP 1.2 display triggers the Nvidia Control Panel bug.

My HDMI 2.1 display works fine, as long as I disable VRR in the display settings

(06-10-2025 12:32 AM)ToastyX Wrote: [ -> ]

(06-09-2025 09:13 PM)Sadarak12 Wrote: [ -> ]Thanks and ill post the result of that log below, but I have also partially resolved the issue myself since this post so I will pop what I did here for future google searches:

AMD Driver seems to default to 10bc for Colour Depth and YCbCr 4:4:4 for pixel format. Changing these to 12bc and RGB 4:4:4 immediately put the peak brightness to 970 Nit's with a noticeable change in how washed out the image was looking under HDR. Its still not as high as it should be but its the first time I have been able to make the reported peak nits change since the issue began at least.

Result of the log:

DISPLAY\SAM71FB\7&AA3BF57&2&UID521 (active):
00 FF FF FF FF FF FF 00 4C 2D FB 71 00 0E 00 01
01 20 01 03 80 6F 3E 78 0A B3 61 AB 4F 46 A8 27
0B 50 54 BD EF 80 71 4F 81 C0 81 00 81 80 95 00
A9 C0 B3 00 D1 C0 08 E8 00 30 F2 70 5A 80 B0 58
8A 00 50 1D 74 00 00 1E 6F C2 00 A0 A0 A0 55 50
30 20 35 00 50 1D 74 00 00 1A 00 00 00 FD 00 18
78 0F FF 8F 00 0A 20 20 20 20 20 20 00 00 00 FC
00 51 42 51 39 30 0A 20 20 20 20 20 20 20 01 30
02 03 75 F0 E2 78 03 5A 61 60 65 66 75 76 DA DB
10 1F 04 13 05 14 20 21 22 40 3F 5D 5E 5F 62 64
03 12 2F 0D 57 07 09 07 07 15 07 50 57 07 01 67
54 03 83 0F 00 00 E2 00 4F E3 05 C3 01 6E 03 0C
00 30 00 B8 44 28 00 80 01 02 03 04 6D D8 5D C4
01 78 80 6B 02 30 90 C1 34 05 E3 06 0D 01 E2 0F
FF E5 01 8B 84 90 69 6D 1A 00 00 02 0B 30 90 00
04 81 05 77 0F 00 00 00 00 00 00 00 00 00 00 BA
02 03 04 F0 58 4D 00 B8 A1 38 14 40 F8 2C 45 00
00 00 00 00 00 1E 5C C1 00 E4 A2 38 AA 40 24 2C
45 80 00 00 00 00 00 1E CF CB 00 80 F5 40 3A 60
20 A0 3A 50 00 00 00 00 00 1C 1A 68 00 A0 F0 38
1F 40 30 20 3A 00 00 00 00 00 00 1A 74 D6 00 A0
F0 38 40 40 30 20 3A 00 00 00 00 00 00 1A 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2C
70 12 79 00 00 03 01 64 59 87 00 08 7F 07 9F 00
2F 80 1F 00 37 04 4C 00 02 00 04 00 51 2C 02 08
FF 0E 2F 02 F7 80 1F 00 6F 08 59 00 4B 00 07 00
EA B7 00 08 FF 09 AB 00 07 80 1F 00 37 04 75 00
3E 00 07 00 86 94 01 08 FF 0E 67 01 93 80 1F 00
3F 06 71 00 63 00 07 00 1D FF 00 08 FF 0E 4F 00
07 80 1F 00 37 04 4C 00 3E 00 07 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 90

The monitor doesn't include any luminance data in the HDR static metadata data block, so it's using the FreeSync data block. The FreeSync data block is not documented publicly, so I haven't added support for editing anything other than the range. I have an idea where the luminance data is, so I plan to add that eventually, but my focus has been on CRU 2.0 lately.

On the 16th line of data where it shows 04 81 05 77 0F at the beginning, the 81 is the max luminance, and the 05 is the min luminance. There's another luminance profile after it (77 0F), but I'm not sure what it's for. You can edit the values and import the text file into CRU if you want to experiment.

Here is an example with the max luminance set to at least 2000 cd/m²:

Edit: added color in the quote so you can see where the luminance data is.

Cheers I might have a go I'm guessing launch CRU and 'Import' then locate the .txt and that's it for the import?

(06-10-2025 11:29 AM)Sadarak12 Wrote: [ -> ]Cheers I might have a go I'm guessing launch CRU and 'Import' then locate the .txt and that's it for the import?

Yes. You'll have to change the file type in the import dialog to see the file.

(06-10-2025 04:43 AM)DevilInDisguise Wrote: [ -> ]I wonder if EDID override works for anyone using a DisplayPort (DP) display with recent Nvidia drivers.
Any change I make to my DP 1.2 display triggers the Nvidia Control Panel bug.

My HDMI 2.1 display works fine, as long as I disable VRR in the display settings

EDID overrides should work with DisplayPort. Show me what changes you're making that is causing the problem. Export a file with the changes and post it here.

(06-10-2025 03:22 PM)ToastyX Wrote: [ -> ]EDID overrides should work with DisplayPort. Show me what changes you're making that is causing the problem. Export a file with the changes and post it here.

For example, I removed the 75Hz resolutions from the "Established Resolutions" section in the left pane, and the bug was triggered immediately after reset — just like with any other changes I tried.
I'm using CRU version 1.5.3.

On a side note, a few months ago, my HDMI 2.1 display also triggered the bug in some unclear situations.
Today following your earlier suggestion to delete the 4:2:0 capability map seems to have helped—I was able to remove all the resolutions I didn't need without triggering the bug.