GPU VRR Flicker in Dark Scenes? Why G-Sync and FreeSync Brightness Flickers, Gamma Shift & VRR Range Explained
重點摘要
Dark scenes flicker under G-Sync or FreeSync because a panel's gamma is tuned for one fixed refresh rate, and variable refresh moves away from it. This guide explains the gamma shift, the VRR floor, the Low Framerate Compensation boundary, and frame-time spikes, then covers frame caps, per-game settings, and firmware checks that reduce flicker.
The Short Answer First
If dark game scenes brighten and dim in waves while G-Sync or FreeSync is switched on, and the waves calm down or stop when variable refresh rate (VRR) is switched off in the same scene, the most likely explanation is not a dying graphics card. It is the panel's brightness response shifting as the refresh rate itself shifts. That distinction matters, because it changes what counts as a fix: the goal is usually to make the refresh rate steadier, not to replace hardware.
This article covers one situation only: a single monitor, VRR already switched on, and brightness oscillation in dark scenes. If your flicker only appears with a second monitor connected, read article #138 instead. If the picture is splitting horizontally or stuttering rather than changing brightness, article #155 is the right guide. If the flicker only appears with HDR switched on, article #139 covers that boundary. Those are different problems with different causes, and mixing their fixes together wastes time.
The Core Mechanism: Gamma Tuned for One Refresh Rate
A monitor panel's gamma response — the curve that decides how bright each shade from black to white should appear — is normally tuned to look its best at one fixed refresh rate, usually the panel's native maximum. Under VRR, the refresh rate no longer stays at that point. It follows the frame rate of the game, rising and falling as the scene changes. As the refresh rate moves away from the tuned point, the gamma curve drifts with it, and brightness shifts slightly.
Two features of that drift explain what you actually see on screen. First, the effect is strongest in dark and mid-dark shades, which is why bright daylight scenes can look perfectly steady while a night scene or a dark corridor seems to breathe. Second, it is the change in refresh rate that triggers the visible shift, not any particular refresh rate on its own. A steady refresh rate, high or low, does not flicker in this way. A refresh rate that jumps around does — and the larger and more irregular the jumps, the easier the brightness change is to notice. Switching between two very different frame-rate caps, for example a high cap and a much lower one, can make the dark-shade brightness difference directly visible.
On OLED panels, the same gamma drift has a more specific description: as gamma moves away from its tuned point, the panel's subpixels can be overcharged or misfired, producing a visible brightness change. That description belongs to OLED behaviour. It should not be applied as a blanket explanation to every LCD panel, where the underlying panel technology differs even though the visible symptom — brightness moving with refresh rate — can look similar.
The Second Mechanism: Voltage Sensitivity
There is a second, separate mechanism worth knowing about, because it changes which panels are most affected and which fixes help. Some panels are sensitive to voltage fluctuation as the refresh rate changes. This voltage-sensitive flicker is most often reported on VA panels, and occasionally on IPS panels, though less commonly. It is a panel response to the electrical side of a changing refresh rate, rather than a gamma-curve drift, and the two mechanisms can both be present.
This distinction is also why a G-Sync module is not a guarantee against flicker. A hardware G-Sync module generally provides finer voltage regulation and tuning, and that can remove the voltage-sensitive kind of flicker. It does not remove the gamma-shift kind. The Dell Alienware AW3423DW is a documented example of this: even with a G-Sync module fitted, gamma-type flicker under VRR has been reported for that model. The lesson is general, not a verdict on one model: do not buy or judge a monitor on the assumption that a module makes it immune, and do not assume that flicker on a module-equipped monitor means the module is faulty.
A related background point helps explain why low refresh rates are involved at all. When the refresh rate falls substantially, the voltage that holds each pixel in its intended state decays between refreshes, which can push gamma further from its tuned point. This is a supporting explanation for low-rate flicker, not a single cause that replaces the gamma and voltage mechanisms above.
The VRR Floor and the LFC Boundary
Every VRR monitor has an effective range, written in the form of a lower and an upper refresh rate — for example, a range written as 48–144Hz. That pair of numbers is used here only to illustrate how a range is written; it is not the specification of any particular model. Always read the range from your own monitor's specification sheet. Below the lower end of the range, the monitor can no longer follow the game's frame rate with a variable rhythm.
That is where Low Framerate Compensation (LFC) comes in. LFC repeats each frame two or three times so that the rhythm sent to the panel falls back inside the monitor's range. A game running below the floor still appears, because the panel is being fed repeated frames at a rate it can handle. LFC is a useful mechanism, and it is also a flicker source in its own right: the moment the system crosses into or out of LFC, the refresh rate jumps, and gamma jumps with it.
Some LFC implementations use a "sticky" design, staying in LFC for a while after a brief dip below the floor instead of switching in and out repeatedly. That reduces repeated flicker at the boundary, but it does not remove the boundary itself. If a game's frame rate hovers around the floor — dipping below it, recovering, and dipping again — the repeated crossings can produce repeated brightness jumps. Repeated crossings of the floor are one reason a game whose frame rate hovers around the floor can show repeated brightness jumps; whether a given game flickers visibly depends on its frame-time pattern and the panel.
FreeSync tiers matter here too. FreeSync Premium requires LFC and a refresh rate of at least 120Hz at Full HD resolution, while basic FreeSync does not guarantee LFC at all. Do not assume from a badge alone that a monitor has LFC; check the model's specification. A wider VRR range also tends to give LFC an easier job, because there is more room between the floor and the ceiling for repeated frames to land in — but range alone does not settle whether a particular monitor flickers, since panel tuning and the game's frame behaviour matter just as much.
Frame-Time Spikes: The Amplifier
Even with the gamma mechanism understood, most flicker needs a trigger, and the usual trigger is unstable frame timing. When a game's frame time spikes — a single frame taking much longer than its neighbours, or a burst of uneven frames — the refresh rate under VRR follows that spike, and the brightness follows the refresh rate. Watching a frame-rate readout beside a real-time frame-time graph while the flicker happens often shows the two moving together: brightness wobbles line up with frame-time spikes.
That is why flicker concentrates in particular moments rather than spreading evenly through a game. Menus, loading screens, and scene transitions are classic hotspots, because the frame rate there can swing from very high to very low and back again in a short time. A large scene change, or a background program grabbing resources mid-game, can do the same thing. Flicker that appears only in menus or loading screens is consistent with this mechanism; it does not mean the whole system is faulty, and it should not be diagnosed as though every scene flickered.
A frame-rate cap works on this mechanism, not by magic. Capping the frame rate inside the VRR range, and keeping it steady, reduces the size of refresh-rate swings and therefore the size of gamma jumps. That is also why a cap is a reduction technique rather than a cure: as long as frame-time spikes can still occur, a sharp spike can still produce a visible brightness jump. The cap narrows the swings; it does not remove the panel's gamma behaviour.
Is It VRR Brightness Flicker? A Differential Table
Before changing anything, run the comparison that separates VRR brightness flicker from lookalike problems. Play the same game, in the same dark scene, with VRR on and then with VRR off. If the flicker disappears or drops sharply with VRR off, the problem is VRR-related. If it does not change, stop working on VRR settings and look elsewhere.
| What you see | What it points to | Where to go |
|---|---|---|
| Dark-scene brightness rises and falls; present with VRR on, gone with VRR off | VRR brightness flicker | This article |
| Picture splits horizontally or the top and bottom halves misalign | Tearing, not flicker | Article #155 |
| Motion stutters or frame pacing feels uneven | Stutter or frame-pacing problem | Articles #155 and #136 |
| Flicker only when two monitors are connected; gone when one is unplugged | Multi-monitor coordination problem | Article #138, second section |
| Flicker only with HDR on, or a black flash when HDR switches | HDR signal renegotiation or the HDR plus VRR boundary | Article #139 |
| Flicker only in one game, or only in one menu | That game's frame-time behaviour interacting with VRR | Edge case in this article; use that game's frame cap or per-game VRR off |
| No VRR option appears at all, or VRR has no effect | Adapter, protocol, or bandwidth problem | Article #176 |
| Flicker continues with VRR off at a fixed refresh rate | Not VRR flicker; check cable, port, panel, driver, or backlight | Article #105 and driver checks |
| A whole bright scene suddenly dims, especially on OLED | Possibly an automatic brightness-limiting protection mechanism, not VRR flicker | Article #139 |
| Smearing or pale edges trailing moving objects | Ghosting or overdrive behaviour, not brightness flicker | Do not treat overdrive settings as a flicker fix |
Two of those rows deserve emphasis because they are the most common misroutes. Flicker at a fixed refresh rate, with VRR off, cannot be gamma-shift flicker by definition — the refresh rate is not varying — so continuing to adjust VRR settings in that case only burns time. And a sudden dimming of a whole bright image, rather than an oscillation in dark shades, belongs to a different mechanism; treat it as a different diagnosis rather than forcing it into this article's framework.
Diagnosis, One Change at a Time
Work through these steps in order, changing one thing at a time and re-checking the same dark scene after each change. Changing several settings at once makes it impossible to tell which one helped, and the next driver or game update can silently undo an unidentified fix.
- Confirm VRR is genuinely on in both places: the monitor's on-screen display setting for VRR or Adaptive-Sync, and the graphics driver's G-Sync or FreeSync setting. Note the monitor's specified VRR range from its specification sheet at the same time.
- Run the VRR on/off comparison described above, in the same game and the same dark scene. If the flicker does not follow VRR, stop here and use the differential table to redirect.
- Unplug any second monitor temporarily and re-check. If the flicker goes with the second monitor, the problem belongs to article #138.
- Switch HDR off and re-check. If the flicker follows HDR, the problem belongs to article #139.
- Turn on a frame-rate readout and a frame-time graph, and watch whether brightness wobbles line up with frame-rate drops or frame-time spikes. Note whether the flicker concentrates in menus, loading screens, or scene changes.
- Set a frame-rate cap inside the VRR range. A common approach is to cap a few frames per second below the monitor's maximum refresh rate — for example, a cap around 141 on a 144Hz monitor is a widely described method, offered here as a method example rather than a guaranteed value. Watch whether the brightness swings narrow. Note that a cap set too low can push the frame rate below the VRR floor and into repeated LFC crossings, which makes things worse rather than better.
- Switch VRR off for one game only, using the per-game setting in the graphics driver, and compare that game with VRR on. This isolates the trade-off to the game that actually flickers instead of giving up VRR everywhere.
- Compare fullscreen and windowed or borderless modes for the same game. VRR engagement can differ between display modes, so a mode change is a legitimate diagnostic step before concluding anything about the panel.
- Check for a monitor firmware update from the monitor maker, and read the update notes for any mention of VRR or flicker fixes. Do not assume an update will fix gamma behaviour; note the current driver version before updating a driver, so you can return to it if the update makes things worse.
- As a final exclusion step, try a different known-good cable, a different port, and a direct connection without any adapter. This step excludes signal-interruption flicker. It is not a treatment for gamma flicker, and a cable change should not be presented as one.
Fixes and Their Trade-Offs
No single setting removes gamma-shift flicker on an existing panel, so every fix below is a trade-off. The right choice depends on which compromise bothers you least in the game that flickers.
| Approach | What it helps | Cost or limit |
|---|---|---|
| Frame-rate cap inside the VRR range, kept steady | Narrows refresh-rate swings, so gamma jumps shrink and flicker becomes less noticeable | Not a cure; sharp frame-time spikes can still show through |
| VRR off for one game only | That game's brightness returns to fixed-refresh stability | Tearing may return in that game; weigh flicker against tearing per game |
| Fixed refresh rate plus VSync | Brightness stays stable | Input latency and tearing trade-offs; see article #155; not an upgrade |
| Driver or firmware update | Helps only if the maker actually fixed a related issue | An update does not guarantee a fix; record versions before updating |
| Lower game settings for a steadier frame rate | Reduces large frame-rate swings where the game itself is unstable | Visual quality cost; only helps when frame-rate instability is the trigger |
| A different monitor at next purchase | Lets you choose a model whose published reviews discuss VRR flicker behaviour | Not a fix for a panel you already own; no model can be promised flicker-free |
The frame-rate cap deserves one more caution. A cap is not "the lower, the better." A cap that holds the frame rate steady just inside the range helps; a cap that drags the frame rate down to the floor, or below it, invites LFC crossings and can make flicker more frequent. Stability inside the range is the target, not the lowest number you can set.
Six Misconceptions, Corrected
"Flicker means the graphics card is failing." No. VRR brightness flicker is a characteristic of how a panel's gamma interacts with a changing refresh rate. It is not, on its own, a fault signal from the graphics card. Flicker at a fixed refresh rate, or flicker accompanied by corrupted images or loss of signal, is a different matter and should be investigated as a hardware problem.
"A higher refresh-rate monitor solves it." No. A higher ceiling does not change the fact that gamma drifts as refresh rate moves. Reports on high-refresh OLED monitors describe flicker behaviour broadly similar to lower-refresh OLED monitors, because the mechanism is the same even when the numbers are bigger.
"A G-Sync module means immunity." No, as the AW3423DW example shows. A module improves voltage regulation and can remove voltage-type flicker, but gamma-type flicker can still appear.
"Changing the cable fixes it." No. Cable problems typically cause signal interruption, black screens, or no signal — not a smooth brightness oscillation in dark scenes. A cable swap is an exclusion step, not a treatment for gamma flicker.
"Updating the driver always fixes it." No. A driver update can improve some situations, but panel gamma behaviour is not something a driver rewrites. Treat an update as a check, not a certainty.
"VRR is all or nothing." No. VRR can be switched off per game, and a frame-rate cap can narrow swings without abandoning VRR entirely. The sensible question is per game: in this game, does flicker or tearing bother you more?
Edge Cases Worth Recognising
Flicker only in menus or loading screens fits the frame-time mechanism and should not be treated as a whole-system fault. Flicker in only one game points to that game's frame-time behaviour interacting with VRR; handle it with that game's cap or per-game VRR setting first. A frame rate that sits below the VRR floor for long periods will keep crossing the LFC boundary; the direction of travel there is a steadier frame rate inside the range, achieved by lowering settings or accepting a cap, not by pushing the cap higher.
Flicker that appears only when HDR and VRR are on together belongs to article #139; this article's main line covers standard dynamic range and general game dark scenes, and only flags the HDR boundary here. Flicker that appears only while a second monitor is connected belongs to article #138 and is not expanded here. And if windowed and fullscreen modes behave differently for the same game, run the mode comparison before drawing conclusions about the panel, since VRR engagement differs by mode.
The Honest Limit
Stated plainly: on an existing panel, gamma-type VRR flicker cannot be completely eliminated. What the steps in this article do is reduce it to the point where it stops being noticeable — usually by keeping the refresh rate from swinging widely, which means limiting VRR's own range of action in practice. That is a real improvement, and it is also a limit worth knowing before spending money. No cable, driver, or setting turns a panel's gamma behaviour into something it is not, and no monitor should be bought on a promise of being flicker-free.
The same honesty applies to variation between users of the same model. Screen, graphics card, game, scene, settings, and actual frame rate all affect whether flicker is visible and how strong it is. One person's invisible flicker can be another person's obvious one on the same model, and neither report is wrong. Judge your own setup by the on/off comparison in your own dark scenes, not by someone else's verdict on the model name.
When Inspection Is Warranted, and What to Prepare
If flicker continues with VRR off at a fixed refresh rate, or it arrives with corrupted images, persistent black screens, or loss of signal, the problem has moved outside this article's scope and into hardware diagnosis. Before seeking inspection, record the pattern: which game and scene, whether VRR on or off changes it, the monitor's specified VRR range, the frame-rate cap if any, and the driver version. That record lets an inspection start from evidence rather than from scratch.
HK GPU Fix is at Room 1209, Dali Plaza, Shek Mun. Telephone 2186 8010, WhatsApp 6558 6806. Repair pricing uses the published HK$400–2,800 tiers, with the actual quote given after inspection. There is no on-site or home service; inspection is at the Shek Mun workshop.
FAQ
Does VRR flicker mean my graphics card is broken?
Not on its own. Brightness oscillation in dark scenes that appears with VRR on and disappears with VRR off points at the panel's gamma shifting with refresh rate, which is a panel characteristic rather than a graphics-card fault signal. Flicker that continues at a fixed refresh rate, or that comes with corrupted images or no signal, is a different problem and should be investigated as hardware trouble.
Why do only dark scenes flicker?
Gamma drift shows most in dark and mid-dark shades, so bright scenes can look steady while a night scene or dark corridor visibly brightens and dims. The refresh rate is moving in both cases; the brightness change is simply much easier to see where shades are dark.
Will a frame-rate cap completely fix it?
No. A cap inside the VRR range steadies the refresh rate and shrinks gamma jumps, which usually makes flicker far less noticeable. It does not remove the panel's gamma behaviour, so a sharp frame-time spike can still show through, and a cap set too low can cause repeated LFC crossings at the VRR floor.
Should I switch VRR off entirely?
Try per-game switching first. If only one game flickers badly, switching VRR off for that game alone keeps VRR's benefits elsewhere. Switching it off everywhere trades flicker for the tearing that VRR was suppressing, so the choice is per game: which artefact bothers you more in that game?
Does a G-Sync module monitor never flicker?
No. A module generally improves voltage regulation and can remove voltage-sensitive flicker, but gamma-type flicker can still appear, as documented for the AW3423DW. Judge a monitor by its VRR flicker behaviour in reviews and by your own on/off comparison, not by the presence of a module alone.
My flicker only happens in menus and loading screens. Is that normal for this problem?
It fits this problem well. Menus and loading screens often swing the frame rate from very high to very low and back, which is exactly the kind of refresh-rate movement that makes gamma shift visible. Flicker concentrated there, with steady gameplay scenes unaffected, points at frame-time behaviour rather than a whole-system fault.
What should I check before concluding the panel is at fault?
Run the VRR on/off comparison in the same dark scene, unplug any second monitor, switch HDR off, and check whether brightness wobbles line up with frame-time spikes. If flicker survives all of those separations — still present with VRR off at a fixed refresh rate — it is not VRR brightness flicker, and the next steps are cable, port, panel, and driver checks rather than more VRR adjustments.