<![CDATA[Monitor Tests Forum - Monitors & Video Cards]]> https://www.monitortests.com/forum/ Wed, 08 Apr 2026 04:09:26 +0000 MyBB <![CDATA[Blank screen on monitor when tv is plugged into soundbar earc]]> https://www.monitortests.com/forum/Thread-Blank-screen-on-monitor-when-tv-is-plugged-into-soundbar-earc Mon, 06 Apr 2026 14:47:03 +0000 https://www.monitortests.com/forum/Thread-Blank-screen-on-monitor-when-tv-is-plugged-into-soundbar-earc Lg ultrawide 49GR85DC-B
Samsung qn90f
Jbl Bar 1000 mk1
5080 + 14700k

Hi guys I’m trying to get this system set up so I can have it all plugged into and run atmos through the bar. I already have the pc set up to run like that it’s hooked up with hdmi from the gpu using a phantom monitor that way and it works well.
I only have one hdmi output from my gpu so I have to manually disconnect it from the soundbar and reconnect to the tv.
I already tested the atmos from the tv with atmos it worked well.
I don’t mind disconnecting things I had to do it with my previous soundbar.
The problem is when the tv is plugged into the soundbar with earc. If it’s plugged in like that and the tv is off the post screen comes up on the monitor which is plugged in with display port then the monitor goes to black screen.
I’m pretty good at stuff like this but this one I can’t work out. The only way is to have the tv unplugged from the soundbar if I want to use pc. It’s very frustrating.
Any help would be greatly appreciated]]> Lg ultrawide 49GR85DC-B
Samsung qn90f
Jbl Bar 1000 mk1
5080 + 14700k

Hi guys I’m trying to get this system set up so I can have it all plugged into and run atmos through the bar. I already have the pc set up to run like that it’s hooked up with hdmi from the gpu using a phantom monitor that way and it works well.
I only have one hdmi output from my gpu so I have to manually disconnect it from the soundbar and reconnect to the tv.
I already tested the atmos from the tv with atmos it worked well.
I don’t mind disconnecting things I had to do it with my previous soundbar.
The problem is when the tv is plugged into the soundbar with earc. If it’s plugged in like that and the tv is off the post screen comes up on the monitor which is plugged in with display port then the monitor goes to black screen.
I’m pretty good at stuff like this but this one I can’t work out. The only way is to have the tv unplugged from the soundbar if I want to use pc. It’s very frustrating.
Any help would be greatly appreciated]]> <![CDATA[Request for Help Creating a Working Custom EDID (1440p / 144 Hz / HDMI 2.1 / FreeSync]]> https://www.monitortests.com/forum/Thread-Request-for-Help-Creating-a-Working-Custom-EDID-1440p-144%E2%80%AFHz-HDMI-2-1-FreeSync Sun, 05 Apr 2026 06:59:18 +0000 https://www.monitortests.com/forum/Thread-Request-for-Help-Creating-a-Working-Custom-EDID-1440p-144%E2%80%AFHz-HDMI-2-1-FreeSync
I tried using CRU to create a custom EDID, but the fuser won’t accept it — the screen just goes blank. I need help creating a custom EDID that the fuser will actually work with.

I do have an EDID from another 1440p monitor that works, but the problem is that the other monitor is G‑Sync, so FreeSync doesn’t work when using that EDID.

If anyone can help me build a proper custom EDID for the fuser, I’d really appreciate it. It needs to support:

- HDMI 2.1
- 1440p
- 144 Hz
- FreeSync

I can share my current EDID files if needed.]]>
I tried using CRU to create a custom EDID, but the fuser won’t accept it — the screen just goes blank. I need help creating a custom EDID that the fuser will actually work with.

I do have an EDID from another 1440p monitor that works, but the problem is that the other monitor is G‑Sync, so FreeSync doesn’t work when using that EDID.

If anyone can help me build a proper custom EDID for the fuser, I’d really appreciate it. It needs to support:

- HDMI 2.1
- 1440p
- 144 Hz
- FreeSync

I can share my current EDID files if needed.]]> <![CDATA[CRU]]> https://www.monitortests.com/forum/Thread-CRU--1934 Fri, 13 Mar 2026 10:23:28 +0000 https://www.monitortests.com/forum/Thread-CRU--1934
Background: I cannot get my LG OLED55BXFNA and LG 43UM7800GNA TVs to show 3840x2160@60 in HDR. They show 3840x2160@30 HDR fine.

I have checked all the specs of my laptop (Samsung Notebook 2 750XEE) and 2 TVs and they can support 3840x2160@60. I have done everything AI suggested like turned on the HDR Deep Color for the HDMI ports, renamed the HDMI ports as PC rather than HDMI, checked the HDMI cable (it is UHD, so HDMI 2.1), and the ports on the TVs are HDMI 2.0.

I have updated all of my drivers directly from Intel.

I was really worried about using this software from your website in case there were tonnes of bugs as well as messing something important up, but eventually plucked up the courage to try it out. I made some changes and ran the CRU software after consulting with AI. I was gutted as it didn't work...

I attach some screenshots showing what I did in the software. Did I do something wrong?
.png  Screenshot 2026-03-08 155943.png (Size: 77.1 KB / Downloads: 36)
.png  Screenshot 2026-03-08 155917.png (Size: 96.69 KB / Downloads: 36)
.png  Screenshot 2026-03-08 155851.png (Size: 156.31 KB / Downloads: 36) ]]>
Background: I cannot get my LG OLED55BXFNA and LG 43UM7800GNA TVs to show 3840x2160@60 in HDR. They show 3840x2160@30 HDR fine.

I have checked all the specs of my laptop (Samsung Notebook 2 750XEE) and 2 TVs and they can support 3840x2160@60. I have done everything AI suggested like turned on the HDR Deep Color for the HDMI ports, renamed the HDMI ports as PC rather than HDMI, checked the HDMI cable (it is UHD, so HDMI 2.1), and the ports on the TVs are HDMI 2.0.

I have updated all of my drivers directly from Intel.

I was really worried about using this software from your website in case there were tonnes of bugs as well as messing something important up, but eventually plucked up the courage to try it out. I made some changes and ran the CRU software after consulting with AI. I was gutted as it didn't work...

I attach some screenshots showing what I did in the software. Did I do something wrong?
.png  Screenshot 2026-03-08 155943.png (Size: 77.1 KB / Downloads: 36)
.png  Screenshot 2026-03-08 155917.png (Size: 96.69 KB / Downloads: 36)
.png  Screenshot 2026-03-08 155851.png (Size: 156.31 KB / Downloads: 36) ]]> <![CDATA[Enabling G-Sync in already compatibile monitor]]> https://www.monitortests.com/forum/Thread-Enabling-G-Sync-in-already-compatibile-monitor Sun, 08 Mar 2026 22:59:12 +0000 https://www.monitortests.com/forum/Thread-Enabling-G-Sync-in-already-compatibile-monitor
Recently I bought Lenovo Legion 5(Ryzen 7 260 and RTX5060) with built in 15,1 OLED screen. At this moment I know it officialy does not support G-Sync nor Freesync but I can see that in CRU there is Freesync block(by default, I didnt add it), so it seems like this screen supports VRR in some form but its not enabled. How can I make it to work? For now I dont have any G-sync option in Nvidia control panel and Freesync on AMD integrated graphics is greyed out. Also, I can set any refresh rate in range from 40 to 165Hz in custom resolution tool in Nvidia control panel and it simply works. So, from my perspective (though I'm no expert), this panel should fully support VRR.

Im including screenshot from cru.

.png  Zrzut ekranu 2026-03-08 234540.png (Size: 197.08 KB / Downloads: 41) ]]>
Recently I bought Lenovo Legion 5(Ryzen 7 260 and RTX5060) with built in 15,1 OLED screen. At this moment I know it officialy does not support G-Sync nor Freesync but I can see that in CRU there is Freesync block(by default, I didnt add it), so it seems like this screen supports VRR in some form but its not enabled. How can I make it to work? For now I dont have any G-sync option in Nvidia control panel and Freesync on AMD integrated graphics is greyed out. Also, I can set any refresh rate in range from 40 to 165Hz in custom resolution tool in Nvidia control panel and it simply works. So, from my perspective (though I'm no expert), this panel should fully support VRR.

Im including screenshot from cru.

.png  Zrzut ekranu 2026-03-08 234540.png (Size: 197.08 KB / Downloads: 41) ]]> <![CDATA[You're my last hope - NVIDIA driver broke my HDMI 2.1 EDID on Samsung TV - please!]]> https://www.monitortests.com/forum/Thread-You-re-my-last-hope-NVIDIA-driver-broke-my-HDMI-2-1-EDID-on-Samsung-TV-please Mon, 23 Feb 2026 10:45:53 +0000 https://www.monitortests.com/forum/Thread-You-re-my-last-hope-NVIDIA-driver-broke-my-HDMI-2-1-EDID-on-Samsung-TV-please
First of all, NVIDIA said they couldn't replicate the issue which is just a slap into my face. I sent them dispdiay, dxdiag, everything. Maybe you can help?

Short version first:

The issue is driver-related and has existed since 577.00 up to the current 591.74.
Starting with driver 577.00, it is physically impossible to properly connect a Samsung TV with Game Mode enabled via HDMI.

- With driver 577.00, everything works fine (HDMI 2.1 Game Port and Samsung Game Mode Enabled).
- With driver newer than 577.00 (eg. 591.74), Samsung Game Mode doesn't work with Game Port 2.1 HDMI.
- The same TV worked perfectly on an RX 9070 XT on all drivers.
- TV: Samsung The Frame 2024 75", connected via HDMI 2.1.

----------

Longer version:

I did some deeper testing and I think the results might be genuinely useful for NVIDIA to reproduce this HDMI/EDID. Before each driver install I removed the previous driver in Windows Safe Mode (clean uninstall), and I also did that before switching HDMI ports.

What I found (three scenarios)

----------

Driver 577.00 (clean install) + OneConnect “gamepad” port + Game Mode ON

- Everything works perfectly
- TV is detected properly
- Proper EDID / CRU shows a full, correct configuration (multiple extension blocks)
- 4K works correctly, games get native resolution
- Aspect ratio is correct
- VRR Game Mode behaves as expected

----------

Driver 591.74 (clean install) + OneConnect “gamepad” port + Game Mode ON

- TV becomes basically unusable
- In NVIDIA Control Panel the display shows up as a generic “Digital Monitor”
- Windows can’t properly detect the display (no native resolution, resolution options are broken)
- CRU “active” looks empty / no proper EDID data (as if there’s no real EDID handshake)
- Random “unsupported resolution” errors on the TV
- G-Sync not working
- No native 4K option in games
- Games rendering in wrong aspect ratios (e.g. widescreen)
- On reboot with both monitor and TV connected, the screen just flickers

----------

Driver 591.74 (clean install) + switching HDMI from “gamepad” HDMI 2.1 port to another OneConnect HDMI port (2.0) + Game Mode ON

- Moving the same HDMI cable from the dedicated “gamepad” port (HDMI 2.1) to a different port (e.g. HDMI 3 2.0) makes the TV work again
- 4K and 120 Hz works, VRR/Game Mode works
- BUT: output format becomes limited (YCbCr 4:2:0 + Limited range),
- In CRU the “active” EDID/extension block structure is different (simpler) compared to the gamepad port on 577.00

----------

This strongly suggests the bug is tied to the EDID/CTA extension handling or HDMI 2.1 handshake path when Samsung Game Mode is enabled on the dedicated gaming port (HDMI 2.1). The same TV + OneConnect worked flawlessly on an AMD GPU (RX 9070 XT) across drivers, including Game Mode. With NVIDIA, the problem appears after driver 577.00 and persists to newest.

I'd love to see some input here.]]>
First of all, NVIDIA said they couldn't replicate the issue which is just a slap into my face. I sent them dispdiay, dxdiag, everything. Maybe you can help?

Short version first:

The issue is driver-related and has existed since 577.00 up to the current 591.74.
Starting with driver 577.00, it is physically impossible to properly connect a Samsung TV with Game Mode enabled via HDMI.

- With driver 577.00, everything works fine (HDMI 2.1 Game Port and Samsung Game Mode Enabled).
- With driver newer than 577.00 (eg. 591.74), Samsung Game Mode doesn't work with Game Port 2.1 HDMI.
- The same TV worked perfectly on an RX 9070 XT on all drivers.
- TV: Samsung The Frame 2024 75", connected via HDMI 2.1.

----------

Longer version:

I did some deeper testing and I think the results might be genuinely useful for NVIDIA to reproduce this HDMI/EDID. Before each driver install I removed the previous driver in Windows Safe Mode (clean uninstall), and I also did that before switching HDMI ports.

What I found (three scenarios)

----------

Driver 577.00 (clean install) + OneConnect “gamepad” port + Game Mode ON

- Everything works perfectly
- TV is detected properly
- Proper EDID / CRU shows a full, correct configuration (multiple extension blocks)
- 4K works correctly, games get native resolution
- Aspect ratio is correct
- VRR Game Mode behaves as expected

----------

Driver 591.74 (clean install) + OneConnect “gamepad” port + Game Mode ON

- TV becomes basically unusable
- In NVIDIA Control Panel the display shows up as a generic “Digital Monitor”
- Windows can’t properly detect the display (no native resolution, resolution options are broken)
- CRU “active” looks empty / no proper EDID data (as if there’s no real EDID handshake)
- Random “unsupported resolution” errors on the TV
- G-Sync not working
- No native 4K option in games
- Games rendering in wrong aspect ratios (e.g. widescreen)
- On reboot with both monitor and TV connected, the screen just flickers

----------

Driver 591.74 (clean install) + switching HDMI from “gamepad” HDMI 2.1 port to another OneConnect HDMI port (2.0) + Game Mode ON

- Moving the same HDMI cable from the dedicated “gamepad” port (HDMI 2.1) to a different port (e.g. HDMI 3 2.0) makes the TV work again
- 4K and 120 Hz works, VRR/Game Mode works
- BUT: output format becomes limited (YCbCr 4:2:0 + Limited range),
- In CRU the “active” EDID/extension block structure is different (simpler) compared to the gamepad port on 577.00

----------

This strongly suggests the bug is tied to the EDID/CTA extension handling or HDMI 2.1 handshake path when Samsung Game Mode is enabled on the dedicated gaming port (HDMI 2.1). The same TV + OneConnect worked flawlessly on an AMD GPU (RX 9070 XT) across drivers, including Game Mode. With NVIDIA, the problem appears after driver 577.00 and persists to newest.

I'd love to see some input here.]]> <![CDATA[Adrenalin 26.1.1 vs 26.2.1 - VERY strange behavior]]> https://www.monitortests.com/forum/Thread-Adrenalin-26-1-1-vs-26-2-1-VERY-strange-behavior Sat, 21 Feb 2026 16:49:28 +0000 https://www.monitortests.com/forum/Thread-Adrenalin-26-1-1-vs-26-2-1-VERY-strange-behavior
26.1.1 my 184Hz Back Porch Horizontal = 1
26.2.1 my 184Hz Back Porch Horizontal = 43 ( had to increase because artifacts jagged picture )

HOWEVER

my 284Hz Back Porch Horizontal = 1 remains working


specs > https://pastebin.com/SpqMpJkY


make it make sense

.png  1.png (Size: 47.73 KB / Downloads: 79)

.png  2.png (Size: 47.06 KB / Downloads: 63) ]]>
26.1.1 my 184Hz Back Porch Horizontal = 1
26.2.1 my 184Hz Back Porch Horizontal = 43 ( had to increase because artifacts jagged picture )

HOWEVER

my 284Hz Back Porch Horizontal = 1 remains working


specs > https://pastebin.com/SpqMpJkY


make it make sense

.png  1.png (Size: 47.73 KB / Downloads: 79)

.png  2.png (Size: 47.06 KB / Downloads: 63) ]]> <![CDATA[NVIDIA DSR on Ultrawide monitor (Black Screen)]]> https://www.monitortests.com/forum/Thread-NVIDIA-DSR-on-Ultrawide-monitor-Black-Screen Sat, 21 Feb 2026 13:16:57 +0000 https://www.monitortests.com/forum/Thread-NVIDIA-DSR-on-Ultrawide-monitor-Black-Screen
I recently purchased a new widescreen monitor to replace my old widescreen monitor.

The resolution of both monitors is 3440x1440.
On my first monitor, the Asrock PG34WQ15R2B, NVIDIA DSR works well, multiplying the 3440x1440 resolution to get a resolution of 6880x2880. However, on my new monitor, the TCL 34R83Q, I encountered a problem. The maximum resolution without enabling DSR can be set to 3840x2160 instead of 3440x1440 as on the Asrock monitor. Because of this, NVIDIA DSR multiplies the resolution based on 3840x2160, not 3440x1440. This results in an 8K resolution with black bars, not the 6880x2880 resolution that a widescreen monitor should have.

I just registered on this forum today and learned about this wonderful program called CRU.
After trying to remove the resolution following the instructions on the website, I got a black screen and Windows froze. The only solution is reset-all.exe.
Please help me remove the 3840x2160 resolution from my ultrawide monitor so I can properly increase the resolution using NVIDIA DSR.

.png  Screenshot_2.png (Size: 727.42 KB / Downloads: 55)

.png  Screenshot_1.png (Size: 184.53 KB / Downloads: 54)

.png  Screenshot_3.png (Size: 40.44 KB / Downloads: 52) ]]>
I recently purchased a new widescreen monitor to replace my old widescreen monitor.

The resolution of both monitors is 3440x1440.
On my first monitor, the Asrock PG34WQ15R2B, NVIDIA DSR works well, multiplying the 3440x1440 resolution to get a resolution of 6880x2880. However, on my new monitor, the TCL 34R83Q, I encountered a problem. The maximum resolution without enabling DSR can be set to 3840x2160 instead of 3440x1440 as on the Asrock monitor. Because of this, NVIDIA DSR multiplies the resolution based on 3840x2160, not 3440x1440. This results in an 8K resolution with black bars, not the 6880x2880 resolution that a widescreen monitor should have.

I just registered on this forum today and learned about this wonderful program called CRU.
After trying to remove the resolution following the instructions on the website, I got a black screen and Windows froze. The only solution is reset-all.exe.
Please help me remove the 3840x2160 resolution from my ultrawide monitor so I can properly increase the resolution using NVIDIA DSR.

.png  Screenshot_2.png (Size: 727.42 KB / Downloads: 55)

.png  Screenshot_1.png (Size: 184.53 KB / Downloads: 54)

.png  Screenshot_3.png (Size: 40.44 KB / Downloads: 52) ]]> <![CDATA[Most energy efficient resolution, 1440x900 or just scaling on 2880x1800 OLED ?]]> https://www.monitortests.com/forum/Thread-Most-energy-efficient-resolution-1440x900-or-just-scaling-on-2880x1800-OLED Wed, 04 Feb 2026 19:25:50 +0000 https://www.monitortests.com/forum/Thread-Most-energy-efficient-resolution-1440x900-or-just-scaling-on-2880x1800-OLED I'm new here and want some opinions and possibly advice on how to proceed.
I'm curious if I should make a new stretched custom resolution or just use scaling?
Does one scaling look better than the other?
Which method gives the best battery life?

Sorry about the long text, tried condesing with spoiler tags but must have forgotten how they work Wink

Lenovo laptop with the following specs:
Computer: LENOVO 83JR
CPU: AMD Ryzen AI 7 350 (Krackan1, KRK1-A0)
AMD AGESA Version: StrixKrackanPI-FP8 1.1.0.0d
Chipset: AMD Promontory/Bixby FCH
Memory: 32768 MBytes LPDDR5 SDRAM 7500MT/s
4x MT62F2G32D4DS-023 WT
Graphics: AMD Krackan - Internal GPU [Lenovo]
AMD Radeon 860M, 512 MB LPDDR5 SDRAM
Internal DAC(400MHz)
Video BIOS Version: 023.010.001.022

Display connections: HDMI2.1 CONN, eDP CONN, DP1 CONN
Display: OLED 2880x1800 LEN140WQ+ / LEN8AC3
Drive: SKHynix_HFS001TEM4X182N, 1000.2 GB, NVMe

Code:
Driver Manufacturer:                    Advanced Micro Devices, Inc.
  Driver Description:                     AMD Radeon(TM) 860M Graphics
  Driver Provider:                        Advanced Micro Devices, Inc.
  Driver Version:                         32.0.22029.9039 (Radeon Software Adrenalin 25.12.1)
  AMD Driver Package Version:             25.20.29.09-251203a-196284C-AMD-Software-Adrenalin-Edition
  AMD Catalyst Driver Version:            15.8
  AMD Software Driver Version:            25.12.1
Code:
Lenovo [Unknown Model: LEN8AC3] -------------------------------------------

[General Information]
  Monitor Name:                           Lenovo [Unknown Model: LEN8AC3]
  Monitor Name (Manuf):                   LEN140WQ+    
  Serial Number:                          Unknown
  Date Of Manufacture:                    Week: 0, Year: 2024
  Monitor Hardware ID:                    Monitor\LEN8AC3
  Max. Vertical Size:                     19 cm
  Max. Horizontal Size:                   30 cm
  Horizontal Frequency:                   230 - 230 kHz
  Vertical Frequency:                     30 - 120 Hz
  Maximum Pixel Clock:                    710 MHz
[Advanced parameters]
  Input Signal:                           Digital
  Color Bit Depth:                        10 Bits per Primary Color
  Digital Video Interface Standard Supported: DisplayPort
  Gamma Factor:                           2.20
[DPMS Modes]
  Standby:                                Not Supported
  Suspend:                                Not Supported
  Active Off:                             Not Supported
  Standard Colour Space (sRGB) Default:   Not Supported
  Preferred Timing Mode:                  Supported
  Default GTF (Continuous Frequency):     Supported
  DFP 1.x Compatible:                     Yes
[Supported Video Modes]
[Chromaticity Coordinates]
  Red [x,y]:                               0.6807, 0.3184
  Green [x,y]:                             0.2197, 0.7246
  Blue [x,y]:                              0.1426, 0.0391
  White [x,y]:                             0.3135, 0.3291
[Color Gamut]
  sRGB Coverage:                          154.991 %
  AdobeRGB Coverage:                      114.898 %
  DCI-P3 Coverage:                        114.255 %
  NTSC Coverage:                          109.777 %
  BT.2020 Coverage:                       81.970 %
  HDR Support:                            Supported
  HDR10+ Support:                         Not Supported
[AMD FreeSync]
  AMD FreeSync Support:                   Supported
  Native Color Space Set:                 Supported
  Local Dimming:                          Supported
  Gamma 2.2 EOTF:                         Not Supported
  Replay Mode:                            Not Supported
  Fast Transport:                         Not Supported
  PQ EOTF:                                Supported
  Panel Type:                             OLED
  Refresh rate:                           30 - 120 Hz
  NVIDIA G-Sync Support:                  Not Supported
  HDMI AdaptiveSync Support:              Not Supported
[DisplayPort]
  VESA AdaptiveSync Support:              Supported
  Refresh rate:                           30 - 120 Hz
[Driver Information]
  Driver Manufacturer:                    Lenovo
  Driver Description:                     Lenovo HDR Monitor
  Driver Provider:                        Lenovo
  Driver Version:                         5.0.0.10
  Driver Date:                            29-May-2025
Code:
00 FF FF FF FF FF FF 00 30 AE C3 8A 00 00 00 00
00 22 01 04 B5 1E 13 78 03 66 85 AE 51 38 B9 24
0A 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 FD 00 1E 78 E6
E6 47 01 0A 20 20 20 20 20 20 00 00 00 FE 00 4C
45 4E 4F 56 4F 0A 20 20 20 20 20 20 00 00 00 FC
00 4C 45 4E 31 34 30 57 51 2B 0A 20 20 20 02 DB
02 03 23 00 E3 05 80 00 E6 06 05 01 8F 6A 01 73
1A 00 00 03 0B 1E 78 00 A0 8F 01 6A 02 78 00 00
00 00 8D 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 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 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 B2
70 20 79 02 00 20 00 0C BA 41 59 03 42 00 00 00
00 00 18 00 21 00 1D CA 0B 5E 07 40 0B 08 07 00
E5 7A 51 85 A3 B9 4A 02 0A 02 45 54 D0 5F 4C 64
18 10 23 78 22 00 28 00 D4 0A 05 3F 0B C7 00 07
00 1F 00 07 07 77 00 4F 00 0F 00 00 D4 0A 85 3F
0B C7 00 07 00 1F 00 07 07 F7 07 CF 07 0F 00 2B
00 0C 27 00 1E 77 00 00 27 00 1E 3B 00 00 2E 00
06 18 10 D0 5F 4C 64 00 00 00 00 00 00 00 12 90
]]> I'm new here and want some opinions and possibly advice on how to proceed.
I'm curious if I should make a new stretched custom resolution or just use scaling?
Does one scaling look better than the other?
Which method gives the best battery life?

Sorry about the long text, tried condesing with spoiler tags but must have forgotten how they work Wink

Lenovo laptop with the following specs:
Computer: LENOVO 83JR
CPU: AMD Ryzen AI 7 350 (Krackan1, KRK1-A0)
AMD AGESA Version: StrixKrackanPI-FP8 1.1.0.0d
Chipset: AMD Promontory/Bixby FCH
Memory: 32768 MBytes LPDDR5 SDRAM 7500MT/s
4x MT62F2G32D4DS-023 WT
Graphics: AMD Krackan - Internal GPU [Lenovo]
AMD Radeon 860M, 512 MB LPDDR5 SDRAM
Internal DAC(400MHz)
Video BIOS Version: 023.010.001.022

Display connections: HDMI2.1 CONN, eDP CONN, DP1 CONN
Display: OLED 2880x1800 LEN140WQ+ / LEN8AC3
Drive: SKHynix_HFS001TEM4X182N, 1000.2 GB, NVMe

Code:
Driver Manufacturer:                    Advanced Micro Devices, Inc.
  Driver Description:                     AMD Radeon(TM) 860M Graphics
  Driver Provider:                        Advanced Micro Devices, Inc.
  Driver Version:                         32.0.22029.9039 (Radeon Software Adrenalin 25.12.1)
  AMD Driver Package Version:             25.20.29.09-251203a-196284C-AMD-Software-Adrenalin-Edition
  AMD Catalyst Driver Version:            15.8
  AMD Software Driver Version:            25.12.1
Code:
Lenovo [Unknown Model: LEN8AC3] -------------------------------------------

[General Information]
  Monitor Name:                           Lenovo [Unknown Model: LEN8AC3]
  Monitor Name (Manuf):                   LEN140WQ+    
  Serial Number:                          Unknown
  Date Of Manufacture:                    Week: 0, Year: 2024
  Monitor Hardware ID:                    Monitor\LEN8AC3
  Max. Vertical Size:                     19 cm
  Max. Horizontal Size:                   30 cm
  Horizontal Frequency:                   230 - 230 kHz
  Vertical Frequency:                     30 - 120 Hz
  Maximum Pixel Clock:                    710 MHz
[Advanced parameters]
  Input Signal:                           Digital
  Color Bit Depth:                        10 Bits per Primary Color
  Digital Video Interface Standard Supported: DisplayPort
  Gamma Factor:                           2.20
[DPMS Modes]
  Standby:                                Not Supported
  Suspend:                                Not Supported
  Active Off:                             Not Supported
  Standard Colour Space (sRGB) Default:   Not Supported
  Preferred Timing Mode:                  Supported
  Default GTF (Continuous Frequency):     Supported
  DFP 1.x Compatible:                     Yes
[Supported Video Modes]
[Chromaticity Coordinates]
  Red [x,y]:                               0.6807, 0.3184
  Green [x,y]:                             0.2197, 0.7246
  Blue [x,y]:                              0.1426, 0.0391
  White [x,y]:                             0.3135, 0.3291
[Color Gamut]
  sRGB Coverage:                          154.991 %
  AdobeRGB Coverage:                      114.898 %
  DCI-P3 Coverage:                        114.255 %
  NTSC Coverage:                          109.777 %
  BT.2020 Coverage:                       81.970 %
  HDR Support:                            Supported
  HDR10+ Support:                         Not Supported
[AMD FreeSync]
  AMD FreeSync Support:                   Supported
  Native Color Space Set:                 Supported
  Local Dimming:                          Supported
  Gamma 2.2 EOTF:                         Not Supported
  Replay Mode:                            Not Supported
  Fast Transport:                         Not Supported
  PQ EOTF:                                Supported
  Panel Type:                             OLED
  Refresh rate:                           30 - 120 Hz
  NVIDIA G-Sync Support:                  Not Supported
  HDMI AdaptiveSync Support:              Not Supported
[DisplayPort]
  VESA AdaptiveSync Support:              Supported
  Refresh rate:                           30 - 120 Hz
[Driver Information]
  Driver Manufacturer:                    Lenovo
  Driver Description:                     Lenovo HDR Monitor
  Driver Provider:                        Lenovo
  Driver Version:                         5.0.0.10
  Driver Date:                            29-May-2025
Code:
00 FF FF FF FF FF FF 00 30 AE C3 8A 00 00 00 00
00 22 01 04 B5 1E 13 78 03 66 85 AE 51 38 B9 24
0A 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 FD 00 1E 78 E6
E6 47 01 0A 20 20 20 20 20 20 00 00 00 FE 00 4C
45 4E 4F 56 4F 0A 20 20 20 20 20 20 00 00 00 FC
00 4C 45 4E 31 34 30 57 51 2B 0A 20 20 20 02 DB
02 03 23 00 E3 05 80 00 E6 06 05 01 8F 6A 01 73
1A 00 00 03 0B 1E 78 00 A0 8F 01 6A 02 78 00 00
00 00 8D 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 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 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 B2
70 20 79 02 00 20 00 0C BA 41 59 03 42 00 00 00
00 00 18 00 21 00 1D CA 0B 5E 07 40 0B 08 07 00
E5 7A 51 85 A3 B9 4A 02 0A 02 45 54 D0 5F 4C 64
18 10 23 78 22 00 28 00 D4 0A 05 3F 0B C7 00 07
00 1F 00 07 07 77 00 4F 00 0F 00 00 D4 0A 85 3F
0B C7 00 07 00 1F 00 07 07 F7 07 CF 07 0F 00 2B
00 0C 27 00 1E 77 00 00 27 00 1E 3B 00 00 2E 00
06 18 10 D0 5F 4C 64 00 00 00 00 00 00 00 12 90
]]> <![CDATA[MacBook Pro 2019 adding FreeSync range possible?]]> https://www.monitortests.com/forum/Thread-MacBook-Pro-2019-adding-FreeSync-range-possible Mon, 02 Feb 2026 17:02:06 +0000 https://www.monitortests.com/forum/Thread-MacBook-Pro-2019-adding-FreeSync-range-possible
I am trying to add FreeSync support with CRU on Windows 10 to the built-in MacBook Pro display: https://everymac.com/systems/apple/macbo...specs.html

The range I have set is 48-60 Hz (48 Hz is the lowest value supported by macOS, so this is what I am starting with).

But I still cannot set FreeSync enabled in the AMD GPU panel. Is this because what I am trying to do is:

- impossible on this hardware?
- not supported by the current driver version?
- should use another method like installing some modified INF file or rewriting EDID: https://forums.blurbusters.com/viewtopic...e0bf779714 ?

Regards]]>
I am trying to add FreeSync support with CRU on Windows 10 to the built-in MacBook Pro display: https://everymac.com/systems/apple/macbo...specs.html

The range I have set is 48-60 Hz (48 Hz is the lowest value supported by macOS, so this is what I am starting with).

But I still cannot set FreeSync enabled in the AMD GPU panel. Is this because what I am trying to do is:

- impossible on this hardware?
- not supported by the current driver version?
- should use another method like installing some modified INF file or rewriting EDID: https://forums.blurbusters.com/viewtopic...e0bf779714 ?

Regards]]> <![CDATA[CRU on 360Hz]]> https://www.monitortests.com/forum/Thread-CRU-on-360Hz Mon, 02 Feb 2026 09:45:00 +0000 https://www.monitortests.com/forum/Thread-CRU-on-360Hz <![CDATA[Help with DisplayPort Monitor Voltage, Resistance Readings]]> https://www.monitortests.com/forum/Thread-Help-with-DisplayPort-Monitor-Voltage-Resistance-Readings Sat, 24 Jan 2026 15:00:10 +0000 https://www.monitortests.com/forum/Thread-Help-with-DisplayPort-Monitor-Voltage-Resistance-Readings
Can anyone look at the readings I've taken from my monitor and tell me if they're abnormal or could be causing issues in my graphics card? I'm looking for someone to take some measurements on their DisplayPort monitor.

I'm getting a resistance reading of 100 kΩ on pin 16 of my DisplayPort cable connected to an unpowered monitor (Dell U2212HM). Pin 16 is supposedly the ground for the AUX channel (pins 15, 17). It also does not have continuity with the monitor's metal chassis. This looks like unusual behavior for a ground pin to me.

Ground pins 2, 5, 8, 11, and even 19 (DP_PWR RETURN) have continuity with the metal chassis.

Checking the ground pins on two different unplugged DisplayPort cables themselves show that opposite ends of pin 16-16 and 19-19 are connected to each other while 2, 5, 8, 11 are not. I assume 2, 5, 8, 11 are common grounds while 16 is a dedicated ground. Pin 20 on my cable is not wired and does not carry voltage while powered.

Measuring resistance of pin 16 vs 18 (Hotplug detect) gives a resistance of 200 kΩ, while HPD vs metal shield gives 100 kΩ ohms on its own. There seems to be a series connection between pin 16 and 18.

While the monitor is powered on and searching for a video signal, there is a constant 2.9 V on pin 16, the only ground pin showing voltage. I don't think a ground should carry voltage.

Voltage on pin 18 (HPD) is 0 V.

To make sure this voltage on pin 16 was not EMI, I attached a 10 kΩ resistor using wires. This triggered the monitor to think it is attached to a PC and autodetected DisplayPort, but then entered standby since there was no signal. The voltage dropped to a steady 0.3 V during these logic changes reacted by the monitors firmware. This firmware behavior is what's normal whenever a GPU is connected to the monitor through DisplayPort but the PC is not powered (the monitor immediately enters standby instead of searching for a signal for 5 minutes). So I guess the GPU only really sees 0.3 V most of the time on ground pin 16.

This autodetect on my 10 kΩ load was glitchy and random upon connecting it, the monitor was seemingly confused by it. If the monitor didn't enter the autodetect/standby state, voltage across the 10 kΩ stood at a steady 2.9 V.

My GPU has been randomly failing to initialize (zombie state) on fresh boots and reboots. Whenever the issue occurs, I get a black screen/no display from the point of the BIOS loading screen but the system POSTs successfully and loads into Windows. Windows logs a WHEA error pointing to my Intel PEG 460D PCIe express root port where a secondary device is not visible. Concurrently, an amduw23g driver loading failure is also logged. One crash has occured since this issue has been occuring for 2 months.

Furmark stress test for 30+ minutes and 1 hour OCCT VRAM test passes with no issues. Hotspot 91 C, VRAM 78 C. Prime95 CPU 63 C.

Driver not found event with every black screen: https://pastebin.com/8dYiv3vt
(the binary in this event translates to [PSP]: Driver Status Reported at FW 1, with version 0x548E2990 status 0x2. FW load failed)

WHEA error: https://pastebin.com/grfBF66W

Minidump: https://pastebin.com/iLkX4mWg

I've tried every BIOS tweak out there and done multiple OS reinstalls and DDU wipes. The display even went out once during system restarts initiated by the Windows installation sequence. Reseated the GPU, cleaned the pins with IPA, driver rollbacks (drivers that didn't give me issues before give me these issues now), buying a Unitek C1628GY01 cable, CMOS resets and default BIOS.

Unplugging the monitor from the GPU for a week while the GPU is still installed, powered, and enabled, I have shifted to the iGPU and connected the monitor using VGA in a dual GPU setup. The errors on my discrete GPU have completely stopped and I can load the drivers and access my metrics in AMD adrenalin flawlessly. The moment I plugged the monitor back in, the GPU started randomly misbehaving again. Sometimes hotplugging DP multiple times leads to a permanent no display from the GPU when there was initially a display, on for example the 3rd or 4th hotplug.

On VGA, the monitor showed up as Generic PnP monitor and the maximum resolution is 1024x768 despite having iGPU drivers installed. The monitor can still identify as a Dell U2212HM on DisplayPort (when it works). Possible EDID failure on VGA?

My theory is that because DisplayPort pin 16 is an AUX ground which handles EDID, intermittent link training failures are being caused on the GPU which cause it to zombie out or activate protection circuits. But I'm not sure as I don't have access to a spare monitor or PC. Please help.

System specifications:
Windows 11 Pro 25H2
Intel Core i3 12100
Gigabyte H610M H V2 DDR4 REV 1.0 (BIOS F34)
Corsair cmk16gx4m2e3200c16 RAM 2x8 GB
ID Cooling SE 214 XT
Lexar NM620 1 TB NVMe
ADATA SU650 120 GB
Seagate Barracuda 1 TB 7200 RPM
Gigabyte UD750GM PSU
PowerColor Fighter RX 7600

P.S DisplayPort male pin layouts are difficult to find on the web because the male connector is a 180 degree translation of the female. Wikipedia has the female connector. My Dell U2212HM's manual (available as a PDF on the web) has the male layout. DisplayPort 1.2 documentation: https://glenwing.github.io/docs/DP-1.2.pdf]]>
Can anyone look at the readings I've taken from my monitor and tell me if they're abnormal or could be causing issues in my graphics card? I'm looking for someone to take some measurements on their DisplayPort monitor.

I'm getting a resistance reading of 100 kΩ on pin 16 of my DisplayPort cable connected to an unpowered monitor (Dell U2212HM). Pin 16 is supposedly the ground for the AUX channel (pins 15, 17). It also does not have continuity with the monitor's metal chassis. This looks like unusual behavior for a ground pin to me.

Ground pins 2, 5, 8, 11, and even 19 (DP_PWR RETURN) have continuity with the metal chassis.

Checking the ground pins on two different unplugged DisplayPort cables themselves show that opposite ends of pin 16-16 and 19-19 are connected to each other while 2, 5, 8, 11 are not. I assume 2, 5, 8, 11 are common grounds while 16 is a dedicated ground. Pin 20 on my cable is not wired and does not carry voltage while powered.

Measuring resistance of pin 16 vs 18 (Hotplug detect) gives a resistance of 200 kΩ, while HPD vs metal shield gives 100 kΩ ohms on its own. There seems to be a series connection between pin 16 and 18.

While the monitor is powered on and searching for a video signal, there is a constant 2.9 V on pin 16, the only ground pin showing voltage. I don't think a ground should carry voltage.

Voltage on pin 18 (HPD) is 0 V.

To make sure this voltage on pin 16 was not EMI, I attached a 10 kΩ resistor using wires. This triggered the monitor to think it is attached to a PC and autodetected DisplayPort, but then entered standby since there was no signal. The voltage dropped to a steady 0.3 V during these logic changes reacted by the monitors firmware. This firmware behavior is what's normal whenever a GPU is connected to the monitor through DisplayPort but the PC is not powered (the monitor immediately enters standby instead of searching for a signal for 5 minutes). So I guess the GPU only really sees 0.3 V most of the time on ground pin 16.

This autodetect on my 10 kΩ load was glitchy and random upon connecting it, the monitor was seemingly confused by it. If the monitor didn't enter the autodetect/standby state, voltage across the 10 kΩ stood at a steady 2.9 V.

My GPU has been randomly failing to initialize (zombie state) on fresh boots and reboots. Whenever the issue occurs, I get a black screen/no display from the point of the BIOS loading screen but the system POSTs successfully and loads into Windows. Windows logs a WHEA error pointing to my Intel PEG 460D PCIe express root port where a secondary device is not visible. Concurrently, an amduw23g driver loading failure is also logged. One crash has occured since this issue has been occuring for 2 months.

Furmark stress test for 30+ minutes and 1 hour OCCT VRAM test passes with no issues. Hotspot 91 C, VRAM 78 C. Prime95 CPU 63 C.

Driver not found event with every black screen: https://pastebin.com/8dYiv3vt
(the binary in this event translates to [PSP]: Driver Status Reported at FW 1, with version 0x548E2990 status 0x2. FW load failed)

WHEA error: https://pastebin.com/grfBF66W

Minidump: https://pastebin.com/iLkX4mWg

I've tried every BIOS tweak out there and done multiple OS reinstalls and DDU wipes. The display even went out once during system restarts initiated by the Windows installation sequence. Reseated the GPU, cleaned the pins with IPA, driver rollbacks (drivers that didn't give me issues before give me these issues now), buying a Unitek C1628GY01 cable, CMOS resets and default BIOS.

Unplugging the monitor from the GPU for a week while the GPU is still installed, powered, and enabled, I have shifted to the iGPU and connected the monitor using VGA in a dual GPU setup. The errors on my discrete GPU have completely stopped and I can load the drivers and access my metrics in AMD adrenalin flawlessly. The moment I plugged the monitor back in, the GPU started randomly misbehaving again. Sometimes hotplugging DP multiple times leads to a permanent no display from the GPU when there was initially a display, on for example the 3rd or 4th hotplug.

On VGA, the monitor showed up as Generic PnP monitor and the maximum resolution is 1024x768 despite having iGPU drivers installed. The monitor can still identify as a Dell U2212HM on DisplayPort (when it works). Possible EDID failure on VGA?

My theory is that because DisplayPort pin 16 is an AUX ground which handles EDID, intermittent link training failures are being caused on the GPU which cause it to zombie out or activate protection circuits. But I'm not sure as I don't have access to a spare monitor or PC. Please help.

System specifications:
Windows 11 Pro 25H2
Intel Core i3 12100
Gigabyte H610M H V2 DDR4 REV 1.0 (BIOS F34)
Corsair cmk16gx4m2e3200c16 RAM 2x8 GB
ID Cooling SE 214 XT
Lexar NM620 1 TB NVMe
ADATA SU650 120 GB
Seagate Barracuda 1 TB 7200 RPM
Gigabyte UD750GM PSU
PowerColor Fighter RX 7600

P.S DisplayPort male pin layouts are difficult to find on the web because the male connector is a 180 degree translation of the female. Wikipedia has the female connector. My Dell U2212HM's manual (available as a PDF on the web) has the male layout. DisplayPort 1.2 documentation: https://glenwing.github.io/docs/DP-1.2.pdf]]> <![CDATA[Raising Pixel Clock safe or not?]]> https://www.monitortests.com/forum/Thread-Raising-Pixel-Clock-safe-or-not Mon, 12 Jan 2026 16:06:00 +0000 https://www.monitortests.com/forum/Thread-Raising-Pixel-Clock-safe-or-not and it sets the G.Pixel Clock (KHz) - 452500

CRU reports a max pixel clock of 330 Mhz for my monitor. Is it safe / ok?

I have an Asus VG278q monitor and i did this because it looks like the setup is stuck in a low bandwidth mode (Display port 1.1 - Current Link Settings - 2.7 Gbps x 4). After this change it finally shows Current Link Settings - 5.4 Gbps x 4]]> and it sets the G.Pixel Clock (KHz) - 452500

CRU reports a max pixel clock of 330 Mhz for my monitor. Is it safe / ok?

I have an Asus VG278q monitor and i did this because it looks like the setup is stuck in a low bandwidth mode (Display port 1.1 - Current Link Settings - 2.7 Gbps x 4). After this change it finally shows Current Link Settings - 5.4 Gbps x 4]]> <![CDATA[Cant configure NVIDIA Surround]]> https://www.monitortests.com/forum/Thread-Cant-configure-NVIDIA-Surround Sat, 03 Jan 2026 11:05:55 +0000 https://www.monitortests.com/forum/Thread-Cant-configure-NVIDIA-Surround
When i configure surround i get 7680X1440 refresh rate 180. However if i closed down or reboot the monitors will go to the default settings of 5760X1080 refresh rate 60.
Here are the specs for the monitor. https://au.aoc.com/product/CQ32G4E

Somebody suggested to use CRU to get a custom res for NVIDIA surround. However i am not sure what res i need to put into CRU?]]>
When i configure surround i get 7680X1440 refresh rate 180. However if i closed down or reboot the monitors will go to the default settings of 5760X1080 refresh rate 60.
Here are the specs for the monitor. https://au.aoc.com/product/CQ32G4E

Somebody suggested to use CRU to get a custom res for NVIDIA surround. However i am not sure what res i need to put into CRU?]]> <![CDATA[Custom Resolution Utility (CRU) Work in Progress]]> https://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU-Work-in-Progress Wed, 31 Dec 2025 23:30:08 +0000 https://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU-Work-in-Progress
Download: cru-test-2026-01.zip

Important differences:
  • Descriptors such as "Name" and "Range limits" are now edited from the "Detailed resolutions and descriptors" list in the main window. Use the "Edit..." button under the list and not the button at the top of the window.
  • Standard resolution descriptors are no longer added automatically. To add more than 8 standard resolutions, add a "Standard resolutions" descriptor manually, or add a "VTB-EXT" extension block.
  • YCbCr 4:2:2/4:4:4 for HDMI is now in the CTA-861 extension block window. For DisplayPort, use the "Edit..." button at the top of the main window.
  • "TV resolutions" data block has been renamed to "Video resolutions" to align with CTA terminology.
  • Interlaced detailed resolutions vertical timing parameters are now per frame to avoid confusing resolution changes and for consistency with DisplayID. For EDID detailed resolutions, the vertical active resolution, front porch, and sync width must be even, and the back porch, blanking, and total must be odd.
Major changes:
  • The display list now only contains active displays and inactive displays with overrides
  • The "Edit..." button at the top now contains EDID properties such as product identification, display parameters, and color characteristics
  • All detailed resolution fields can now be edited (use the triangle button to show all fields)
    • Sync type should always be "Digital separate" even with CRT monitors
    • Borders are only supported by NVIDIA
    • Added OVT standard
  • All descriptors are now supported
    • Range limits now supports all timing definitions
    • CVT and Established III resolutions are not commonly used and only work with EDID 1.4 (normally used with DisplayPort only)
    • Color point and color management are not commonly used and have no effect in Windows
  • Extension blocks are now readable with all GPUs including Intel
  • Extension block header fields can now be edited
  • FreeSync data block HDR profiles can now be edited
  • HDMI data block 3D fields can now be edited
  • HDR static metadata data block now shows actual luminance values along with the raw values
  • New CTA-861 data blocks:
    • G-SYNC
    • HDR dynamic metadata
    • HDR10+
    • Microsoft head-mounted and specialized displays
    • Native video resolution
    • Product information
    • Vendor-specific
    • Video format preference
    • Video format resolutions
  • New DisplayID data blocks
  • VTB extension blocks now support CVT resolutions (not commonly used)
  • Import will now always import the complete EDID
  • Dark mode is now supported
]]>
Download: cru-test-2026-01.zip

Important differences:
  • Descriptors such as "Name" and "Range limits" are now edited from the "Detailed resolutions and descriptors" list in the main window. Use the "Edit..." button under the list and not the button at the top of the window.
  • Standard resolution descriptors are no longer added automatically. To add more than 8 standard resolutions, add a "Standard resolutions" descriptor manually, or add a "VTB-EXT" extension block.
  • YCbCr 4:2:2/4:4:4 for HDMI is now in the CTA-861 extension block window. For DisplayPort, use the "Edit..." button at the top of the main window.
  • "TV resolutions" data block has been renamed to "Video resolutions" to align with CTA terminology.
  • Interlaced detailed resolutions vertical timing parameters are now per frame to avoid confusing resolution changes and for consistency with DisplayID. For EDID detailed resolutions, the vertical active resolution, front porch, and sync width must be even, and the back porch, blanking, and total must be odd.
Major changes:
  • The display list now only contains active displays and inactive displays with overrides
  • The "Edit..." button at the top now contains EDID properties such as product identification, display parameters, and color characteristics
  • All detailed resolution fields can now be edited (use the triangle button to show all fields)
    • Sync type should always be "Digital separate" even with CRT monitors
    • Borders are only supported by NVIDIA
    • Added OVT standard
  • All descriptors are now supported
    • Range limits now supports all timing definitions
    • CVT and Established III resolutions are not commonly used and only work with EDID 1.4 (normally used with DisplayPort only)
    • Color point and color management are not commonly used and have no effect in Windows
  • Extension blocks are now readable with all GPUs including Intel
  • Extension block header fields can now be edited
  • FreeSync data block HDR profiles can now be edited
  • HDMI data block 3D fields can now be edited
  • HDR static metadata data block now shows actual luminance values along with the raw values
  • New CTA-861 data blocks:
    • G-SYNC
    • HDR dynamic metadata
    • HDR10+
    • Microsoft head-mounted and specialized displays
    • Native video resolution
    • Product information
    • Vendor-specific
    • Video format preference
    • Video format resolutions
  • New DisplayID data blocks
  • VTB extension blocks now support CVT resolutions (not commonly used)
  • Import will now always import the complete EDID
  • Dark mode is now supported
]]> <![CDATA[Asus monitor CRU black screen]]> https://www.monitortests.com/forum/Thread-Asus-monitor-CRU-black-screen Sun, 28 Dec 2025 05:19:50 +0000 https://www.monitortests.com/forum/Thread-Asus-monitor-CRU-black-screen <![CDATA[60hz to 40hz on HP Elitebook 645 G11?]]> https://www.monitortests.com/forum/Thread-60hz-to-40hz-on-HP-Elitebook-645-G11 Fri, 26 Dec 2025 03:56:50 +0000 https://www.monitortests.com/forum/Thread-60hz-to-40hz-on-HP-Elitebook-645-G11 I can only see 60hz available listed on Windows 11 settings, also internet search tells me the manufacturer (LG) lists only 60hz as product specification.
I can only change to 40hz if I use Custom Resolution Utility (CRU) and set up a custom resolution with 40hz, but I am afraid to use it like this long term as I don't want to damage the screen permanently. Is there any possibility that the screen might be damaged if I lower the refresh rate and use it like this? I am fan of this refresh rate, but if it means to stess/strain the monitor then I won't use it.
I have found a PDF with info about the panel and uploaded it with this post. Could you take a look>

Please provide me with insight, thank you and happy holidays!

.pdf  LP140WU4-SPD1_Ver1.0_20240227_202505295843-compressed.pdf (Size: 1.89 MB / Downloads: 128) ]]> I can only see 60hz available listed on Windows 11 settings, also internet search tells me the manufacturer (LG) lists only 60hz as product specification.
I can only change to 40hz if I use Custom Resolution Utility (CRU) and set up a custom resolution with 40hz, but I am afraid to use it like this long term as I don't want to damage the screen permanently. Is there any possibility that the screen might be damaged if I lower the refresh rate and use it like this? I am fan of this refresh rate, but if it means to stess/strain the monitor then I won't use it.
I have found a PDF with info about the panel and uploaded it with this post. Could you take a look>

Please provide me with insight, thank you and happy holidays!

.pdf  LP140WU4-SPD1_Ver1.0_20240227_202505295843-compressed.pdf (Size: 1.89 MB / Downloads: 128) ]]> <![CDATA[Hisense 55 A7GQ & Nvidia RGB full]]> https://www.monitortests.com/forum/Thread-Hisense-55-A7GQ-Nvidia-RGB-full Sat, 08 Nov 2025 12:12:44 +0000 https://www.monitortests.com/forum/Thread-Hisense-55-A7GQ-Nvidia-RGB-full My Hisense 55 A7GQ TV (4K@60, IPS, QLED) is connected via HDMI to a PC with an Nvidia 5070 graphics card.
The TV is in Game Mode.
In the Nvidia panel, the native resolution is set to 4K x 2K, 3840 x 2160 at 60Hz (located in the Ultra HD, HD, SD section; the PC section only lists resolutions of 1280 x 1024 and below).

When using the YCbCr444 color format, the image displays correctly, pixel for pixel.
When switching the color format to RGB, the image displays incorrectly, either full or limited.
This is especially noticeable with colored fonts, thin lines, calibration images for gamma adjustments, etc.
The image also displays incorrectly with YCbCr444 when Game Mode is disabled.

Another problem is that the TV's color adjustment doesn't work with YCbCr444, but it does with RGB.
And this TV really needs it due to poor default color calibration.

When selecting a signal source, the TV displays 8bit | BT709 | 16:9| YUV444 or 8bit | BT709 | 16:9| RGB when changing to RGB.

I tried changing the resolution, refresh rate, creating a custom resolution, and changing the scaling settings – nothing changed.

I read many different posts about CRU, tried changing settings, and adding resolutions – in most cases, I got a black screen after restart64.
In cases where restart64 or rebooting the PC was successful, nothing changed.

Maybe someone has encountered a similar problem and can help (if that's even possible).
I took screenshots of all the default settings.


.png  CRU default.png (Size: 251.35 KB / Downloads: 169) ]]> My Hisense 55 A7GQ TV (4K@60, IPS, QLED) is connected via HDMI to a PC with an Nvidia 5070 graphics card.
The TV is in Game Mode.
In the Nvidia panel, the native resolution is set to 4K x 2K, 3840 x 2160 at 60Hz (located in the Ultra HD, HD, SD section; the PC section only lists resolutions of 1280 x 1024 and below).

When using the YCbCr444 color format, the image displays correctly, pixel for pixel.
When switching the color format to RGB, the image displays incorrectly, either full or limited.
This is especially noticeable with colored fonts, thin lines, calibration images for gamma adjustments, etc.
The image also displays incorrectly with YCbCr444 when Game Mode is disabled.

Another problem is that the TV's color adjustment doesn't work with YCbCr444, but it does with RGB.
And this TV really needs it due to poor default color calibration.

When selecting a signal source, the TV displays 8bit | BT709 | 16:9| YUV444 or 8bit | BT709 | 16:9| RGB when changing to RGB.

I tried changing the resolution, refresh rate, creating a custom resolution, and changing the scaling settings – nothing changed.

I read many different posts about CRU, tried changing settings, and adding resolutions – in most cases, I got a black screen after restart64.
In cases where restart64 or rebooting the PC was successful, nothing changed.

Maybe someone has encountered a similar problem and can help (if that's even possible).
I took screenshots of all the default settings.


.png  CRU default.png (Size: 251.35 KB / Downloads: 169) ]]> <![CDATA[Black screen crash]]> https://www.monitortests.com/forum/Thread-Black-screen-crash Thu, 16 Oct 2025 14:10:23 +0000 https://www.monitortests.com/forum/Thread-Black-screen-crash <![CDATA[10 bit output HP ZBook Power 16 inch G11 RTX ADA 3000]]> https://www.monitortests.com/forum/Thread-10-bit-output-HP-ZBook-Power-16-inch-G11-RTX-ADA-3000 Sat, 13 Sep 2025 05:39:51 +0000 https://www.monitortests.com/forum/Thread-10-bit-output-HP-ZBook-Power-16-inch-G11-RTX-ADA-3000
I have a HP ZBook Power 16 inch G11 with RTX ADA 3000 connected through a HP G6 TB4 dock to a Barco 6530 medical display running 3280x2048 resolution. The display supports 10bit color and if I connect it to a MacBook Air over the same TB4 connection, I het 10 bit output. I also get 10 bit over DP from a HPz4 workstation, but I can only get 8 bit from the Zbook G11. I've also tried direct TB-DP cables. In display properties, it's connected to the intel iGPU and there is no option in windows, nvidia control panel or bios to force it to use the RTX.

I've also spent >90 mins on a single call with HP support.

My question is can I force it to use RTX ADA for 10 bit or can I get 10 bit from the iGPU?

Thanks for any help!]]>
I have a HP ZBook Power 16 inch G11 with RTX ADA 3000 connected through a HP G6 TB4 dock to a Barco 6530 medical display running 3280x2048 resolution. The display supports 10bit color and if I connect it to a MacBook Air over the same TB4 connection, I het 10 bit output. I also get 10 bit over DP from a HPz4 workstation, but I can only get 8 bit from the Zbook G11. I've also tried direct TB-DP cables. In display properties, it's connected to the intel iGPU and there is no option in windows, nvidia control panel or bios to force it to use the RTX.

I've also spent >90 mins on a single call with HP support.

My question is can I force it to use RTX ADA for 10 bit or can I get 10 bit from the iGPU?

Thanks for any help!]]> <![CDATA[Samsung G95NC Picture-by-Picutre -> 21:9 + 11:9 blurried?]]> https://www.monitortests.com/forum/Thread-Samsung-G95NC-Picture-by-Picutre-21-9-11-9-blurried Mon, 04 Aug 2025 11:54:01 +0000 https://www.monitortests.com/forum/Thread-Samsung-G95NC-Picture-by-Picutre-21-9-11-9-blurried
sorry to bother you but i'm really frustrated right now.

So i recently bougth the Samsung Odyssey Neo G9 G95NC as a "upgrade" from my Samsung Odyssey G9 G93SC (OLED) which i always used in PbP mode with 21:9 + 11:9 working perfectly fine.
But now the 21:9 part seems blurried and for the 11:9 part i can't select 120Hz in the windows display settings. If i switch to 2x 16:9, nothing is blurried and both parts can be used with 120Hz at the same time. So for me there is no limit in bandwidth at all.

Back to 21:9 + 11:9 windows says "(recommended)" for 3440x1440, also the nvcp, but desktop mode and active signal mode are both 5120x2160 but it still looks burried like 3440x1440. Also it is not zoomed, as it should be (?) if a lower resolution is used. If i disable pbp and use a custom resolution (via nvcp, yep that works dunno why) with 5120x2160@240Hz, it display in the middle with black bars on both sides perfectly fine.

Did some research and read ALL threads i've found but apparently no one has this problems or is using 21:9 + 11:9, asked perplexity ai and it said that my gpu could be the reason for the interpolation because 5120x2160 is not in the Detailed Timings Descriptor due to it's limit of 4,095 horizontal pixels so it is in a extension block (found it) and windows prefers the Detailed Timings Descriptor over the extension blocks IF using PbP.

Can anyone tell me how to fix this ??? Also the 60hz limitation of the 11:9 part.


Greets]]>
sorry to bother you but i'm really frustrated right now.

So i recently bougth the Samsung Odyssey Neo G9 G95NC as a "upgrade" from my Samsung Odyssey G9 G93SC (OLED) which i always used in PbP mode with 21:9 + 11:9 working perfectly fine.
But now the 21:9 part seems blurried and for the 11:9 part i can't select 120Hz in the windows display settings. If i switch to 2x 16:9, nothing is blurried and both parts can be used with 120Hz at the same time. So for me there is no limit in bandwidth at all.

Back to 21:9 + 11:9 windows says "(recommended)" for 3440x1440, also the nvcp, but desktop mode and active signal mode are both 5120x2160 but it still looks burried like 3440x1440. Also it is not zoomed, as it should be (?) if a lower resolution is used. If i disable pbp and use a custom resolution (via nvcp, yep that works dunno why) with 5120x2160@240Hz, it display in the middle with black bars on both sides perfectly fine.

Did some research and read ALL threads i've found but apparently no one has this problems or is using 21:9 + 11:9, asked perplexity ai and it said that my gpu could be the reason for the interpolation because 5120x2160 is not in the Detailed Timings Descriptor due to it's limit of 4,095 horizontal pixels so it is in a extension block (found it) and windows prefers the Detailed Timings Descriptor over the extension blocks IF using PbP.

Can anyone tell me how to fix this ??? Also the 60hz limitation of the 11:9 part.


Greets]]>