GPU HDR Looks Washed Out, Black, or Wrong Colours: HDR, Colour Gamut, and Monitor Settings Troubleshooting

2026-10-20 ｜ GPU Repair ｜ 14 min read ｜ HK GPU Fix Editorial

Key Takeaways

Washed-out HDR is usually a mapping mismatch, not a faulty graphics card. HDR involves three layers — Windows, the monitor's on-screen menu, and the game or player — and any disagreement between them can distort colour. Match the SDR brightness, RGB range, and gamut mode first, then check cables, drivers, and the monitor's actual HDR capability.

Start by Naming the Symptom

Complaints after switching on HDR all sound similar — "the picture is wrong" — but the underlying mechanisms are completely different. The first step in troubleshooting is not to try controls at random. It is to pin down which kind of wrong the picture is, because each symptom points at a different layer.

The governing principle is that HDR is not a single switch. At any moment at least three layers of switches interact — the Windows system layer, the monitor's on-screen display and firmware layer, and the content or in-game layer. If any one layer disagrees with the others, the picture can look wrong. Troubleshooting must confirm each layer in turn, rather than assuming that switching HDR on in Windows means HDR is on everywhere.

HDR Is Three Switches, Not One

The Windows layer

The path is Settings, then System, then Display, then HDR. On a multi-monitor system, select the correct monitor first, because HDR settings are independent for each display.

Windows lists the display's capabilities, including whether it supports playing HDR games and apps and streaming HDR video. If that page reports no support, the cause is usually that HDR is not switched on in the monitor's on-screen menu, the cable or interface does not support it, the driver is outdated, or the monitor's EDID is not reporting correctly. It does not by itself prove that the graphics card is faulty.

Windows 10 and Windows 11 describe the HDR page in slightly different words, but the logic is the same: the system switch only permits HDR output. It does not guarantee that content will actually be presented in HDR.

A common misunderstanding is that switching HDR on in Windows should make the whole desktop look better. Most of the desktop is SDR content, and switching HDR on actually creates extra work mapping that SDR content into HDR output.

The monitor layer

Many monitors require HDR, or an HDR mode, to be switched on in the on-screen display (OSD) before Windows detects any HDR capability. Some monitors offer several HDR modes, such as cinema, gaming, or a standard HDR mode, or a manufacturer-specific dynamic brightness mode. Different modes can behave very differently in tone mapping and brightness.

In HDR mode, some monitors lock brightness adjustment, or hand brightness control to the HDR signal. That is not a fault. It is how HDR works: peak brightness is decided by the content's metadata and the monitor's tone mapping, not by a traditional SDR brightness control.

Some monitors also have ambient-light sensing or dynamic brightness features that change picture brightness with room light. During troubleshooting, tell that apart from an HDR fault: automatic brightness follows room light, while an HDR fault normally lines up with switching HDR on or off, changing content, or changing to fullscreen.

A useful check is to look at the monitor's current picture mode in the OSD while HDR content is playing. If the OSD still shows an SDR mode, the HDR signal never reached the monitor, and the problem is upstream — Windows, the game, the cable, or the interface. Do not waste time adjusting colour temperature in the OSD in that situation. Note that OSD names differ between brands, so the general rule is to look for the HDR or picture-mode control in the OSD, not to memorise one brand's button name.

The game and content layer

Most games need HDR switched on separately in the game's own graphics or display settings. Switching HDR on in Windows alone leaves the game outputting SDR.

Streaming platforms and players work the same way: the content itself must have an HDR version, the player or browser must support HDR, and the subscription, content-protection, and decoding conditions must all be met. Do not read "that title has no HDR" as "the graphics card's HDR is broken."

Some games include an HDR calibration screen asking for peak brightness, black level, paper white, and a tone-mapping midpoint. If those values are far from the monitor's real capability, the result is blown highlights, crushed blacks, or a washed-out picture.

The recommended order is: confirm the Windows switch, then confirm the OSD shows an HDR mode, then confirm the game or player has HDR on, and only then adjust calibration values. Skipping any earlier step and jumping to calibration only makes the picture harder to untangle.

"HDR is on but the picture looks no different"

That can mean the content itself is SDR, so the system is only mapping SDR into HDR output and the visual change is limited. It can mean the monitor accepts an HDR signal but its panel's peak brightness and contrast are too low for the effect to be obvious. It can mean the game is using Auto-HDR rather than native HDR. Or it can mean the browser or player is not taking the HDR path at all, so the picture is still SDR.

Why SDR Content Looks Washed Out in HDR Mode

The basic mechanism

SDR content was designed for a traditional display range: white level, black level, and gamma curve all assume a relatively narrow brightness range. HDR mode uses a different brightness and colour system, built around a much wider range.

When Windows HDR is on, the desktop and most apps are still SDR content, and the system must map that SDR content into HDR output. If the mapping parameters are wrong, SDR white lands at the wrong brightness position, and the whole desktop looks washed out, grey, and low-contrast.

A second common cause is paper white — the SDR white level — not being set correctly. Paper white is the brightness that white in SDR content should map to. Set it too high, and white backgrounds blow out and glare. Set it too low, and the desktop looks dark and grey. Higher is not better; the value has to suit the monitor's real brightness and the viewing environment.

There is a related mechanism worth knowing. In SDR mode, Windows assumes the display is fully sRGB. In HDR mode, Windows reads the display's colour profile and maps app colours into the range the display supports. If the display's gamut mode does not change along with it, colour consistency between SDR and HDR suffers. SDR looking oversaturated and HDR looking relatively flat can be two faces of the same gamut-mapping problem, not a sign that HDR itself got worse.

The Windows SDR brightness control

Windows provides an SDR content brightness slider that adjusts how bright SDR content appears in HDR mode. It does not change the peak brightness of HDR content. It only moves the white position of SDR content inside HDR output.

The troubleshooting logic is straightforward: if the desktop looks washed out after switching HDR on, try this slider first. If the desktop becomes normal and HDR games and video stay normal, the problem was paper-white mapping, not hardware. If adjustment never helps, check the OSD gamut mode, the ICC profile, and whether the GPU control panel is adding its own colour interference.

Do not confuse this slider with the monitor's OSD brightness control. The former is system-level SDR mapping; the latter is monitor-level overall brightness and HDR tone mapping. Adjusting both at random makes it very hard to trace which one was the source of the problem.

Tone mapping: why the same HDR content looks different on different monitors

HDR content is commonly mastered for a relatively high peak brightness target, such as 1,000 nits. Many consumer monitors have a much lower real peak brightness. When content brightness exceeds what the monitor can do, the monitor must tone-map: compress the out-of-range brightness back into the range it can display while keeping as much highlight detail as possible.

Good tone mapping keeps highlight detail, avoids crushed blacks, and keeps contrast natural. Poor tone mapping, or wrong parameters, blows highlights into flat white, crushes shadows into black, or flattens the whole picture.

Useful distinctions:

• Blown highlights with no detail usually mean peak brightness is set too high, or tone mapping is pushing highlights beyond the monitor's capability.
• Crushed blacks with no shadow detail usually mean the black level or minimum brightness is set too low, or the contrast curve is compressing the shadows too hard.
• Grey, hazy shadows and a foggy picture usually mean a raised black floor, an RGB range mismatch, or a monitor that cannot control its black level, such as an LCD with no local dimming.

In-game HDR settings commonly include peak brightness, paper white, and a tone-mapping midpoint. The calibration rule is to enter values that match the monitor's real capability, not the aspirational figure on the packaging. Entering a peak brightness far above the monitor's real peak makes tone mapping compress on a false assumption, and the result is worse, not better. Do not expect a single correct number to apply to every model, because models differ.

The Windows HDR Calibration app exists to build an HDR colour profile for that specific monitor, covering minimum brightness, peak brightness, full-screen peak brightness, and saturation. During calibration, follow the patterns to the point where they just disappear, and do not push past that point. Before calibrating, it helps to restore the monitor's default HDR mode and switch off dynamic contrast, black enhancement, and similar features that would interfere with calibration.

HDR looking too dark is not always a fault

The average picture brightness of HDR content can be lower than SDR, because HDR reserves its brightness budget for highlights — the sun, lamps, explosions — instead of pushing the whole picture brighter. In the same scene, HDR shadows can be darker than SDR while highlights are brighter. That darker-overall-but-brighter-highlights character is normal HDR behaviour, not evidence that something broke.

If HDR content is so dark that detail is invisible while SDR is fine, check the game or player's HDR brightness setting, the monitor's OSD HDR mode, whether the Windows HDR calibration profile is stale or wrong, and whether a dynamic brightness or power-saving setting is holding brightness down.

Colour Gamut: sRGB, DCI-P3, and Rec.2020

What each gamut is for

sRGB and Rec.709 are the standard gamuts for traditional SDR content, covering the narrowest range. Most desktop apps, web pages, SDR games, and SDR video assume sRGB.

DCI-P3 is the digital cinema standard, wider than sRGB, extending further in red and green. Much HDR content, HDR streaming, and wide-gamut monitors use DCI-P3 as a reference.

Rec.2020, also called BT.2020, is the ultra-high-definition and HDR broadcast standard, wider still than DCI-P3. HDR10 and similar HDR formats use Rec.2020 as their container gamut. Very little content uses the whole Rec.2020 range, and very few consumer monitors can cover it fully.

The important idea is that a wider gamut does not automatically mean better-looking colour. Whether colour looks right depends on whether the content's gamut assumption matches the gamut the display actually outputs. If the content is sRGB but the display outputs its native wide gamut with no conversion, colours get stretched and become oversaturated.

Why a wide-gamut monitor makes SDR content look oversaturated

The mechanism is direct. The panel's native gamut may be close to DCI-P3 or wider, but SDR content's colour values are defined for sRGB. If the system or monitor does not convert, the sRGB values are mapped straight onto the native wide gamut. Reds get redder, greens get greener, skin tones lean red or orange, and the whole picture looks harsh.

This shows most in apps with no colour management: some image viewers, browser configurations, and interface elements do not colour-manage, so content is shown as if it were native wide gamut. Apps with proper colour management, such as full colour-managed photo editors, convert sRGB content correctly into the display gamut and look normal.

A related mechanism appears in HDR mode. In HDR mode Windows reads the display colour profile and maps correctly; in SDR mode, if the display stays in its native wide-gamut mode, SDR colours get stretched to the panel's native gamut and become oversaturated. The practical answer is to use an sRGB mode for SDR and a native, wide-gamut, or HDR mode for HDR, so each mode matches its content.

Oversaturation is therefore often a gamut-mode mismatch, not a broken monitor or a broken graphics card.

Gamut clamping and sRGB simulation modes

Gamut clamping limits output to a target gamut, such as sRGB, so colours do not get pulled beyond it. For everyday SDR use, clamping to sRGB usually produces the most natural-looking colour.

There are several ways to get there:

• The monitor's OSD sRGB simulation or sRGB mode clamps the gamut in the monitor hardware. The advantage is that it applies to the whole system and does not depend on whether each app colour-manages. The drawback is that on some models the sRGB mode locks brightness or contrast, or its colour accuracy is not strong, so check that model's manual.
• Windows 11 Automatic Color Management (ACM) uses the display's ICC profile to convert SDR content into the display gamut automatically. It is aimed at SDR accuracy on wide-gamut displays. It does not replace HDR, and it does not turn SDR into HDR. It needs a newer Windows 11 version, a wide-gamut display with a valid ICC profile, and a supported GPU and driver, and it must be switched on manually. Do not write it up as if every Windows computer has it.
• Some driver-level gamut clamping tools exist. One GPU maker's driver offers a related option, and third-party tools can use EDID primary data for clamping. No single third-party tool should be presented as the only answer, and any tool should be checked for source and system compatibility rather than installed blindly from a troubleshooting article.

Clamping cannot add gamut coverage the monitor does not have. It can only narrow output to the target gamut. If the monitor's own coverage is short, clamping will not conjure wider colour.

One boundary case matters: people doing photo or design work in fully colour-managed professional software do not have a problem with a wide-gamut monitor as such. Their problem only appears in apps without colour management. For those users, the answer is to separate colour-managed apps from non-colour-managed apps, not to declare that wide gamut is bad.

Common gamut misunderstandings

• "Higher gamut coverage percentage is always better." Coverage is only one measure. Colour accuracy, whether the gamut mode matches the content, and whether brightness and contrast are sufficient all matter. A display covering all of DCI-P3 with the wrong gamut mode can look worse on SDR than an accurate sRGB display.
• "Turning saturation down is the same as calibrating." Lowering saturation can make oversaturation less obvious, but it does not make colour accurate. The real fix is matching the gamut mode and colour management.
• "HDR content always uses Rec.2020, so a display must cover the whole of Rec.2020 to count as HDR." Rec.2020 is the container. The content's actual colour distribution and the display's actual coverage are separate questions. Do not confuse the container gamut with real coverage.

HDR Certification: DisplayHDR Ratings and the Limits of Entry-Level HDR

What DisplayHDR is

DisplayHDR is a display certification from VESA, the Video Electronics Standards Association, graded on peak brightness, black level, gamut, bit depth, local dimming, and related conditions. It is a hardware capability certification, not a signal format. HDR10 is a signal format; DisplayHDR 400 is a display certification. The two should not be confused: a DisplayHDR 400 monitor can accept an HDR10 signal without having the hardware capability to fully present HDR10 content's dynamic range.

What the tiers mean in practice

Higher tiers exist above these, but bigger numbers are not an absolute rule. Local dimming, black level, and gamut have to be considered together.

Be careful with labels that are not part of the official standard. Claims such as DisplayHDR 2000 have circulated in the market. Check certification against the official VESA listing rather than trusting the number printed on the box.

How panel technology shapes HDR

• LCD with edge lighting or global dimming: with no local dimming, HDR shadows easily turn grey, because the backlight must brighten for highlights and cannot dim shadows independently.
• LCD with full-array local dimming or Mini-LED: more dimming zones mean finer bright and dark control and smaller halos. With a limited number of zones, small bright points on dark backgrounds still show halo. That is a physical limit, not a settings error.
• OLED: each pixel emits its own light, black is close to fully black, contrast is extremely high, and HDR shadow performance is the strongest of the three. OLED panels also have automatic brightness limiting and related protection mechanisms: when a large area of the picture goes bright, the system lowers brightness automatically to protect the panel and control power. A full-white picture suddenly going dim can be that protection mechanism, not an HDR fault.
• Variable refresh rate (VRR) with HDR: on some panels, HDR plus VRR can flicker, especially when the frame rate fluctuates heavily. This is a boundary case where panel, driver, and VRR interact. Temporarily switching VRR off is a valid comparison test to see whether the flicker follows VRR.

Why HDR can look worse than SDR

If the monitor is DisplayHDR 400 class with no local dimming, switching HDR on re-maps content and the result can be lower contrast and greyer shadows. In that situation, switching HDR off and using SDR mode can be the more sensible everyday choice. It is not a failure.

HDR is not "on means better." It is good only when display capability, content, and settings all line up. If the hardware capability is not there, leaving HDR off is a rational choice.

Auto-HDR in Games

What Auto-HDR is

Auto-HDR is a Windows 11 feature that converts a game that was originally SDR into HDR output. It is not the game's native HDR. It is a system-level SDR-to-HDR conversion.

Auto-HDR first appeared on Xbox consoles and was later brought to Windows 11. It works by taking the brightness information already present in the SDR image and expanding it into the HDR range along a consistent tone curve. It does not invent shadow or highlight detail that was never there.

System requirements follow Microsoft's official documentation: Windows 11, HDR switched on, an HDR display, and a newer GPU with a compatible driver. The Windows HDR Calibration app also has GPU generation thresholds. Requirements change with Windows versions, so treat the official Microsoft documentation as the reference rather than memorising one GPU generation as the minimum.

Why Auto-HDR sometimes looks good and sometimes looks wrong

Auto-HDR quality depends on whether the Windows calibration profile is accurate. If the profile's peak brightness and black level are far from the monitor's real capability, the conversion comes out blown out, crushed, or oversaturated.

The game's own brightness and gamma settings also feed into Auto-HDR. Auto-HDR does not automatically correct a game whose brightness is already set too high. If the game is too bright, Auto-HDR magnifies the error.

Game native HDR quality also varies. If a game's native HDR implementation is poor — wrong tone mapping, blown highlights — Auto-HDR can look more natural, because it follows Windows' uniform rules instead of the developer's flawed rules. If native HDR is done well, native HDR usually wins over Auto-HDR.

The troubleshooting test is simple: switch Auto-HDR off and see whether native HDR or SDR looks normal. If switching it off fixes the picture, the problem is in the Auto-HDR conversion layer, not in the graphics card hardware.

Strength and triggering

Windows 11 provides an Auto-HDR intensity control through the Xbox Game Bar. Too high, and highlights blow out and colours look unnatural. Too low, and the picture looks much like SDR. There is no single correct intensity number; moderation is the principle.

Auto-HDR does not work in every game. Some games only trigger it in specific rendering or display modes. Common checks are trying exclusive fullscreen, confirming the game uses a supported DirectX version, and updating the GPU driver. If a game does not support it, Auto-HDR will not force itself on, and that is not a fault.

Do not confuse Auto-HDR with in-game "fake HDR" filters or post-processing effects. Those effects only adjust the SDR picture's brightness and colour. They are not true HDR output.

Black Screen, Flicker, or No Signal When Switching HDR

Why switching causes a black screen

Switching HDR forces the system to re-negotiate the signal: resolution, refresh rate, bit depth, chroma subsampling, HDR metadata, and related parameters all have to be confirmed again. That process normally makes the picture go black or flicker briefly. A short black screen during re-negotiation is normal.

A normal black screen is brief, usually recovering within a few seconds, with a normal picture afterwards. A black screen that persists, needs the cable unplugged and reconnected to recover, or flickers repeatedly is abnormal and worth investigating.

Directions for abnormal black screens and flicker

• Cable and interface: a cable that cannot carry the signal, a cable that is too long, a loose connector, or an adapter or switch that does not support HDR can all make re-negotiation fail. Test with another known-good cable, another port, and a direct connection with no adapter. Do not assume that a cable which worked for SDR will necessarily work for HDR, because HDR mode demands more from the signal.
• Monitor firmware and drivers: outdated monitor firmware, a driver bug, or a driver behaviour change after a Windows update can all cause black screens when switching HDR. Update the GPU driver, check whether the monitor maker offers a firmware update, and if needed try a clean driver install as a comparison.
• Refresh rate and resolution combinations: high refresh rate plus high resolution plus HDR together place the highest demand on bandwidth and signal stability. For troubleshooting, lower the refresh rate or resolution as a comparison. If the black screen goes away, the problem leans toward bandwidth, signal, or cable rather than a faulty panel. Detailed bandwidth and compression calculations belong with high-refresh-rate 4K troubleshooting and are not repeated here.
• VRR, G-Sync, and FreeSync: user reports describe black screens and flicker with HDR plus high refresh rate plus VRR all on together. Temporarily switching VRR off is a valid comparison test.
• Audio and HDMI handshaking: there are reports of black screens when adjusting volume in HDR mode, particularly over HDMI with ARC or a soundbar, possibly related to a brief HDMI handshake interruption. Treat this as a boundary case, not as proof that a soundbar is faulty.
• EDID reporting: the monitor tells the graphics card what modes it supports through EDID. If EDID is wrong or the monitor does not report correctly, Windows can output HDR with wrong parameters and the screen can go black. Restarting the monitor, reseating the cable, and resetting the monitor's OSD settings can force EDID to re-negotiate.

Telling normal from faulty

Normal: a black screen of a few seconds when switching HDR, entering a game, or changing to fullscreen, with a normal picture afterwards and no ongoing flicker.

Worth investigating: a black screen lasting well beyond ten seconds, needing the cable reseated to recover, flickering every few seconds, resetting resolution or refresh rate after switching, or coming with a system crash or restart.

Avoid absolute rules such as "a black screen of a certain number of seconds always means a fault," because re-negotiation time differs between monitors. The rule is that a brief black screen is common, while a persistent or repeating black screen deserves investigation.

Extra complexity with two monitors

In a multi-monitor setup, HDR settings are independent per monitor. If one monitor supports HDR and the other does not, or the two use different HDR modes, switching can leave one monitor black, make colours inconsistent, or reset HDR settings. Identify which monitor has the problem rather than mixing the two monitors' symptoms together. If needed, disconnect the second monitor and test with a single monitor to see whether the problem follows the multi-monitor combination.

Bit Depth, Chroma Subsampling, and RGB Full Versus Limited

Bit depth: 8-bit, 10-bit, and 8-bit plus FRC

8-bit colour gives 256 levels per channel, about 16.77 million colours in total. 10-bit gives 1,024 levels per channel, about 1.07 billion colours. HDR content generally needs 10-bit or better, because the HDR brightness range is wide and 8-bit gradients easily show banding.

8-bit plus FRC, or Frame Rate Control, means the panel itself is 8-bit but uses dithering to simulate a 10-bit result. DisplayHDR 400 accepts 8-bit plus FRC. The simulation can reduce banding, but it is not native 10-bit. Do not describe FRC as true 10-bit.

A common misunderstanding is that converting 8-bit content into a 10-bit container turns it into true 10-bit. Converting the container does not restore colour data that was already lost, and it does not fully remove banding.

For troubleshooting: if gradients show banding, first confirm that the GPU control panel's bit-depth setting is 10-bit, or the highest value the monitor supports, and that the cable and interface support that combination. If the monitor itself only supports 8-bit, forcing 10-bit has no real effect.

Chroma subsampling: 4:4:4, 4:2:2, and 4:2:0

4:4:4 keeps full chroma information with no subsampling compression, and is kindest to text, fine lines, and interface edges.

4:2:2 compresses colour information horizontally. It is usually hard to notice in video playback, but text edges can show coloured fringing.

4:2:0 compresses both horizontally and vertically. It is usually acceptable for video playback, but desktop text and spreadsheets are where blurred colour edges show most.

Human vision is more sensitive to brightness than to colour, so chroma subsampling compression is hard to spot in video but easy to spot in desktop text and small fonts. That is why "video looks fine, text looks wrong" can be a subsampling issue rather than a faulty graphics card.

Bit depth and chroma subsampling are independent ideas. Bit depth decides how many levels each colour has. Subsampling decides how much colour information is kept. Do not mix the two together.

HDMI and DisplayPort versions, in brief

HDMI 2.0 has about 18 Gbps of bandwidth and supports 4K at 60 Hz, with HDR support added from HDMI 2.0a onward. With high resolution plus high refresh rate plus HDR plus 10-bit plus 4:4:4 all on together, bandwidth runs short, and the fix is to lower subsampling, such as to 4:2:2, or lower the refresh rate.

HDMI 2.1 has about 48 Gbps and supports 4K at 120 Hz, 8K at 60 Hz, and dynamic HDR, with far less bandwidth pressure at high-specification combinations.

DisplayPort 1.4 has about 32.4 Gbps and supports Display Stream Compression. At high resolution plus high refresh rate plus HDR, DisplayPort 1.4 commonly relies on that compression.

The key troubleshooting rule is not to look at the "HDMI 2.1" or "DisplayPort 1.4" label alone. Check whether the graphics card port version, the cable version, and the monitor port version all support the combination you need. Any one older link can be the bottleneck. Adapter cables count too: an active DisplayPort-to-HDMI adapter has its own bandwidth, HDR, and VRR limits. Do not assume an adapter equals a direct connection.

RGB Full versus Limited: one of the most common causes of a washed-out picture

RGB Full means 0 to 255, the PC monitor standard. 0 is the darkest black and 255 is the brightest white.

RGB Limited means 16 to 235, the television and video standard. 16 is the darkest black and 235 is the brightest white.

If the graphics card outputs Limited (16 to 235) but the display interprets it as Full (0 to 255), black level 16 is read as dark grey, and the whole picture looks washed out and low-contrast.

Conversely, if the graphics card outputs Full but the display interprets it as Limited, shadows get crushed to dead black and highlights blow out, losing detail.

HDMI is especially prone to this. Some GPU drivers default to Limited on HDMI connections, because HDMI was designed for televisions and the driver assumes a television is on the other end. DisplayPort connections usually default to Full. That is a common reason why "DisplayPort looks fine, HDMI looks washed out."

The fix is to make both ends agree. In the GPU control panel, confirm the output dynamic range is Full — the NVIDIA control is output dynamic range, the AMD control is pixel format RGB 4:4:4 Full, and the Intel control is quantisation range Full. At the same time, confirm the monitor or television OSD black-level or HDMI black-level setting matches the GPU (on a television, the setting may be labelled Full, High, or Normal depending on the brand). Change both sides to match; changing only one side leaves the mismatch in place.

One exception: if the display is a television, the television may expect Limited. In that case, "both sides Full" is not necessarily the right answer. The correct principle is that both sides agree, not that Full is always right. Do not present Full as universally correct when a television is the display.

YCbCr versus RGB

RGB is most common for PC desktops, text, and interface content, carrying colour and brightness together, and it suits pixel-accurate content.

YCbCr is common for video and television, separating brightness from colour so it can work with chroma subsampling compression. For video playback, YCbCr can be a reasonable choice. For desktop text, RGB 4:4:4 is usually sharper.

Do not treat YCbCr itself as a fault. The question is whether the content type, output format, and display interpretation match. If text looks blurred in YCbCr 4:2:0, try RGB 4:4:4 as a comparison. If video looks fine, there is no need to force RGB.

Drivers, Windows Settings, and Colour Management

The GPU driver layer

The GPU control panel — NVIDIA Control Panel, AMD Software, or Intel Graphics Command Center — can override Windows HDR colour settings. Common interventions include output colour format, output dynamic range, bit depth, digital vibrance or saturation enhancement, and contrast or gamma adjustment.

The troubleshooting rule is: if driver interference is suspected, first restore the GPU control panel's colour settings to defaults — RGB, Full range, the highest bit depth, and no extra colour enhancement — and let Windows handle HDR tone mapping. Do not let the driver and Windows tone-map at the same time.

If a problem appeared after a driver update, consider rolling back to the previously stable driver as a comparison, or doing a clean install that removes old settings before installing the new driver. Do not immediately conclude that the new driver has a bug, because flicker can also come from cable or monitor firmware issues.

Registry edits that reset HDR tone mapping are sometimes mentioned as a fix. Treat them as a last resort, not a first step, and back up before touching the registry.

Windows colour management and ICC profiles

An ICC profile is a file describing a display's colour characteristics. Many manufacturer-supplied ICC profiles are made for SDR calibration, not for HDR.

A common problem is that a custom ICC profile for SDR stays applied in HDR mode, so Windows and the driver apply colour correction twice and the colours go wrong. Windows does not automatically switch ICC profiles when HDR is switched on or off.

Troubleshooting directions:

• In SDR mode, use the correct SDR ICC profile.
• In HDR mode, consider removing or disabling the custom ICC profile and using the profile the Windows HDR Calibration app generates instead.
• If removing the ICC profile makes the colours normal, the problem was at the profile layer, not in the hardware.

Windows 11 Automatic Color Management differs from traditional ICC management: ACM uses the display's ICC profile to understand the display's native characteristics and automatically converts SDR content into the correct gamut. It does not replace HDR, and it does not calibrate the display itself. If the display's factory calibration is itself inaccurate, ACM will not fix it automatically.

Keep three ideas separate: the ICC profile describes the display, the Windows HDR calibration profile holds HDR brightness and saturation settings, and ACM automatically converts SDR content into the display gamut. They are not interchangeable.

Screenshots and recordings can mislead

In HDR mode, a screenshot's colours can differ from what the eye sees, because the screenshot tool has to convert HDR to SDR. Some screenshot tools have an HDR screenshot colour-correction option, and whether it is on or off changes the screenshot's colours.

When judging HDR colour, look at the display directly. A screenshot opened on another SDR display has already been converted and does not equal what the eye sees on the HDR display.

Streaming and player conditions

HDR on a streaming service in Windows usually needs a specific playback environment, a subscription plan that supports HDR, a video extension for decoding, and content-protection-compatible hardware. Watching through a browser that does not support HDR can deliver high resolution in SDR with no HDR, and that should not be read as a graphics card problem.

HDR video on a video platform usually needs a supported browser with hardware acceleration switched on, plus a video that actually has an HDR version.

Local HDR files need a player that passes HDR metadata through or tone-maps correctly, or colours can look dull or washed out.

Streaming HDR carries extra content-protection, decoding, and browser conditions. Those conditions change over time, so this guide does not list any platform's subscription prices or version details.

The Diagnostic Sequence

Follow this order. Each step isolates one layer before moving on.

1. Record the symptom. Which content is affected — desktop, games, video, or everything? Which switch triggered it — Windows HDR, entering a game, changing to fullscreen? Is it constant or intermittent?
2. Confirm the three layers. Is Windows HDR on? Does the OSD show an HDR mode? Is HDR on inside the game or player?
3. Do the simplest comparison. Switch HDR off and check whether SDR is normal. If SDR is normal, the problem leans toward HDR mapping, settings, or the monitor's HDR capability, not a fully failed graphics card.
4. Adjust SDR white brightness. If the desktop looks washed out with HDR on, try the Windows SDR content brightness slider first.
5. Check RGB range. Confirm the GPU output dynamic range and the display black-level setting agree. PC monitors are usually Full on both sides; a television should be matched to what the television expects.
6. Check gamut mode. Use an sRGB mode for SDR and a native, wide-gamut, or HDR mode for HDR. If the monitor has an sRGB simulation mode, test whether SDR looks normal in it.
7. Check in-game and in-player settings. Are peak brightness, paper white, and tone-mapping midpoint entered to match the monitor's real capability? If needed, rebuild the HDR profile with the Windows HDR Calibration app.
8. Check bit depth and subsampling. For gradient banding or text fringing, confirm bit depth is 10-bit, or the highest value the monitor supports, and that subsampling is 4:4:4 for desktop text or a suitable video subsampling setting.
9. Check cable and interface. For black screens, flicker, or no signal, try another known-good cable, another port, and a direct connection with no adapter. Lower the refresh rate or resolution first as a comparison.
10. Check driver and ICC profile. Restore the GPU colour settings to defaults, remove any suspect custom ICC profile, and update or roll back the GPU driver as a comparison. If needed, switch VRR, Auto-HDR, and dynamic contrast off one at a time to isolate them.
11. Check monitor capability. If the monitor is DisplayHDR 400 class with no local dimming, limited HDR effect is expected. Do not try to force true HDR out of it with settings.

Common Misunderstandings

• "Switching HDR on always looks better." Wrong. HDR depends on display hardware capability plus content plus settings. On a display without enough capability, HDR can look worse than SDR.
• "A washed-out HDR picture means the graphics card is broken." Wrong. The most common causes are SDR mapping, paper white, RGB range mismatch, and gamut mode mismatch.
• "Turning brightness to maximum equals HDR." Wrong. HDR is about brightness range and contrast, not pushing the whole picture to maximum brightness. Pushing too bright only blows highlights and glares.
• "A wider gamut is always better." Wrong. Gamut has to match the content. An unmatched wide gamut only oversaturates SDR content.
• "DisplayHDR 400 means true HDR." Wrong. DisplayHDR 400 is an entry-level compatibility tier with no local dimming requirement. Do not confuse it with DisplayHDR 600, 1000, or True Black.
• "Auto-HDR equals native HDR." Wrong. Auto-HDR is an SDR-to-HDR conversion whose quality depends on calibration and the game's own settings.
• "Any black screen means a fault." Wrong. A brief re-negotiation black screen when switching HDR is normal. A persistent or repeating black screen is what deserves investigation.
• "A more expensive cable fixes everything." Wrong. Cable quality is one possible cause, but interface version, drivers, monitor OSD, RGB range, bit depth, and subsampling all have to be considered together.
• "A screenshot shows HDR colour accurately." Unreliable. A screenshot has been through HDR-to-SDR conversion and does not equal what the eye sees on the HDR display.
• "One set of settings works for every monitor." Wrong. Panel technology, DisplayHDR tier, and OSD mode all change which settings are correct.

Edge Cases Worth Leaving Open

• A television used as a PC display may expect Limited RGB, may have its own HDR modes for game, movie, and PC use, and may need an HDMI port's enhanced, Deep Color, or UHD Color setting switched on before it supports HDR. Follow the television's manual rather than applying PC monitor settings directly to a television.
• A laptop's built-in screen and an external monitor can have completely different HDR capabilities. HDR settings are independent per display, so do not assume both will behave the same.
• Two monitors with different HDR capability can show inconsistent colours, reset settings, or leave one monitor black when switching.
• Streaming HDR carries extra browser, app, subscription, decoding, and content-protection conditions. If any are missing, HDR will not appear.
• OLED protection mechanisms lower brightness when a large bright area is shown. That is a protection behaviour, not a fault.
• VRR plus HDR can flicker on some combinations. Temporarily switching VRR off is a valid comparison.
• In HDR mode, some OSD options become locked. That is normal design, not a broken OSD.
• Game HDR implementations vary in quality. The same monitor can show good HDR in one game and poor HDR in another because of the game's own implementation, not the graphics card.
• Older graphics cards and older interfaces may need lower subsampling or a lower refresh rate at high resolution plus high refresh rate plus HDR. That is an interface capability limit, not a fault.

When Settings Stop and Inspection Starts

Everything above belongs to the settings and troubleshooting side. The boundary for inspection is clear: if the same abnormal output appears on multiple known-good monitors and cables, and driver and settings factors have been ruled out layer by layer, the graphics card's own output may need hardware inspection.

Do not read every HDR problem as a repair job. Most HDR complaints are resolved by matching the three HDR layers, the RGB range, the gamut mode, and the cable and driver state.

If inspection is needed, pricing follows the published three tiers: Tier 1 HK$400–780, Tier 2 HK$480–1,380, Tier 3 HK$680–2,800, with a total range of HK$400–2,800 and the final quote after inspection. The service works on a No fix, no fee basis.

Visit Dali Plaza Room 1209, Shek Mun, or call 2186 8010. WhatsApp 6558 6806 is also available for enquiries.

FAQ

Why does the desktop look washed out as soon as I switch HDR on?

The desktop is mostly SDR content, and in HDR mode that content has to be mapped into a much wider brightness range. If the paper-white mapping is wrong, white lands at the wrong brightness and the desktop looks grey and flat. Try the Windows SDR content brightness slider first, then check the RGB range and gamut mode before suspecting hardware.

Why do colours look oversaturated in SDR but flat in HDR?

That pattern often points at a gamut-mode mismatch. If the display stays in its native wide gamut for SDR, SDR colours get stretched and look oversaturated. In HDR mode, Windows reads the display colour profile and maps more carefully, so HDR can look flatter by comparison. Use an sRGB mode for SDR and a native, wide-gamut, or HDR mode for HDR.

Is DisplayHDR 400 real HDR?

DisplayHDR 400 certifies that a display can accept HDR signals with at least 400 nits of peak brightness, but it does not require local dimming, so it is best described as an entry-level compatibility tier rather than true HDR. DisplayHDR 600 adds local dimming and a wider gamut, DisplayHDR 1000 is a high-end tier, and DisplayHDR True Black is the OLED branch where near-black blacks give high contrast at lower peak brightness.

Why does the screen go black for a moment when I switch HDR on?

Switching HDR forces the system to re-negotiate resolution, refresh rate, bit depth, subsampling, and HDR metadata, which normally blanks the picture briefly. A black screen of a few seconds that recovers to a normal picture is expected. A black screen that persists, needs the cable reseated, or flickers repeatedly deserves investigation, starting with the cable, port, driver, and VRR state.

Should I use RGB Full or RGB Limited?

Both sides of the connection must agree. For a PC monitor, Full on both sides is the usual answer. For a television, match whatever the television expects, which may be Limited. A mismatch is the problem: Limited output read as Full looks washed out, while Full output read as Limited crushes shadows and blows highlights.

Why does Auto-HDR look good in one game and bad in another?

Auto-HDR converts SDR games to HDR using the Windows calibration profile and the game's own brightness settings. If the calibration profile does not match the monitor's real capability, or the game's brightness is already set too high, the conversion magnifies the error. Switching Auto-HDR off is the quickest way to test whether the conversion layer is the source.

Why does a screenshot of my HDR screen look wrong on another display?

A screenshot has to be converted from HDR to SDR, and that conversion does not reproduce what the eye sees on the HDR display. Judge HDR colour by looking at the display directly, not by opening the screenshot on a different SDR display.