Why Does Windows Dynamic Refresh Rate Keep Changing? DRR Mechanism, Power vs Smoothness & Misdiagnosis Guide
重點摘要
When a display refresh rate jumps between 60 Hz and 120 Hz, it is not necessarily a fault. This guide explains how Windows Dynamic Refresh Rate works, when switching is normal, and how to separate genuine display problems from power-saving behaviour, one display at a time.
A Jumping Refresh Rate: Ask Three Questions First
A display settings page that moves from 60 Hz to 120 Hz and then falls back again often alarms its owner. Under Windows 11 Dynamic Refresh Rate, known as DRR, that movement can itself be normal behaviour. Before reaching any conclusion, three questions should be answered: which display is changing, under what activity is it changing, and is any visible display fault accompanying the change. Without those three facts, any verdict is guesswork.
Refresh rate means how many times per second a display redraws its picture. A 60 Hz display redraws 60 times per second, and a 120 Hz display redraws 120 times per second. A higher rate usually makes scrolling, animation and pen input look smoother, while a lower rate means less redrawing work per second, which is kinder to battery life on a laptop. DRR is designed to choose between those two automatically: a higher rate when smoothness matters, and a lower rate when it does not, without the owner changing the setting by hand each time.
The key point is that DRR is not a display acting on its own, and it is not a graphics card changing settings at random. It is a Windows 11 strategy that runs on a qualifying display: it observes what the owner is doing and decides whether the moment calls for the lower or the higher rate. Once that strategy is understood, most cases of a rate that appears to change by itself can be explained. The cases that cannot be explained, especially those accompanied by a visible fault, are the ones worth investigating as faults.
DRR, a Fixed Rate, and VRR: Three Different Things
Three terms are often confused, yet they belong to different layers. A fixed refresh rate is the simplest mode: one value is used throughout, such as 60 Hz all day or 120 Hz all day. Its advantage is predictability, since the rhythm never changes. Its cost is that a high fixed rate keeps redrawing a static picture at full speed, which is wasteful for power, while a low fixed rate sacrifices smoothness during interaction.
Variable Refresh Rate, or VRR, is the underlying capability: the display and graphics system can adjust the refresh rate in step with content, rather than being locked to a single value. That capability is commonly associated with game synchronisation, and it belongs to the hardware and driver layer. DRR is a Windows-level strategy built on that capability: Windows decides when to use the lower rate and when to use the higher rate, mainly for everyday scrolling and pen interaction. In short, VRR answers whether the display can adjust on the fly, while DRR answers when Windows asks it to adjust.
That boundary matters. A DRR change is not the same as a game synchronisation fault, and the detailed treatment of game synchronisation belongs to a separate guide, so it is not rewritten here. Likewise, panel type differences, Overdrive and ULMB are separate topics with their own guides, and they are not expanded here.
| Mode | How it works | Advantage | Cost or limit |
|---|---|---|---|
| Fixed refresh rate | One value is used throughout | Predictable rhythm, no jumping | Static content still uses a high rate, or interaction is less smooth at a low rate |
| VRR capability | The display adjusts in step with content | Provides the foundation for on-the-fly adjustment | It is only a capability, not a Windows policy for everyday use |
| DRR strategy | Windows switches between a lower and a higher rate by activity | Power saving when static, smoothness when interacting, no manual switching | Only appears on qualifying displays, and switching itself is often mistaken for a fault |
Why Some Machines Have DRR and Others Do Not
DRR is not available on every Windows machine. Every requirement must be met at once, and if any one is missing, the DRR control will simply not appear in settings. That fact must be stated plainly, because otherwise an owner may assume the setting is hidden, the driver is damaged, or a third-party tool is needed to force it on.
First, the system must run Windows 11. Windows 10 does not offer DRR, whatever display is attached. Second, the display must support VRR and must reach at least 120 Hz. A display limited to 60 Hz, or one without VRR support, does not qualify. Third, the graphics driver must support the driver model DRR requires, and the panel firmware must expose VRR support and multiple refresh-rate options to Windows. If any link in that chain does not expose support, Windows will not offer DRR.
The main setting is a laptop built-in panel. DRR support on an external display arrived later and carries stricter conditions, so a high-refresh external display should never be assumed to carry DRR. When several displays are connected, each one must be checked in turn: a built-in panel having DRR says nothing about an external display, and an external display lacking DRR says nothing about the built-in panel. Treating the two as if they shared one setting is the most common checking error.
One further detail is easily missed: not every rate listed in settings applies at the current resolution. Some listed options may carry a note that choosing them changes the resolution. When checking DRR, the owner should first confirm which display is selected and what the current resolution is, and only then judge whether the DRR control exists, rather than deciding from a single number alone.
When Switching Happens: Static Content, Scrolling, and Interaction
DRR switching follows the owner's activity. When content is mostly static, Windows leans toward the lower rate, for example while reading email, reading a document, or looking at a page that is not moving. In those moments the picture barely changes, so redrawing it at a high rate adds almost nothing to how it looks, while still costing power.
When interaction needs smooth motion, switching occurs. Fast scrolling through a document or a web page, dragging a window, writing with a pen, or touch interaction all belong to this group. Windows raises the rate so that the motion looks continuous, and once the interaction ends and the picture settles again, the rate falls back. That rhythm, falling back when still and rising when interacting, is what normal DRR operation looks like.
Power state also affects the judgement. A laptop running on battery leans toward saving power, while a laptop plugged in tolerates power use more freely. The same machine can therefore behave differently on battery and on mains power, and that difference alone does not mean the setting was changed by someone else. Any comparison should record whether the machine was plugged in or on battery at the time, because results from the two states cannot be compared directly.
| Situation | DRR tendency | Reason |
|---|---|---|
| Still reading a document or email | Lower rate | The picture barely changes, so a high rate adds almost nothing |
| Fast scrolling through a document or web page | Higher rate | Motion needs continuity, and a low rate makes it look broken up |
| Pen writing or touch interaction | Higher rate | How closely the stroke follows the hand depends on the rate |
| Ordinary typing or still operation | Lower rate | Content changes little, so a high rate is not needed throughout |
| Full-screen application or game | Depends on that application's own behaviour | An application may have its own rate or full-screen behaviour, which must be compared separately |
The Power Versus Smoothness Trade-Off
The trade-off can be stated in one line: save power when still, stay smooth when interacting. The saving comes from not redrawing a static picture far more often than needed, and the smoothness comes from still having the higher rate available the moment interaction begins. The owner is spared a constant choice between locking the rate high all day and locking it low all day, and that is the value of DRR.
That trade-off has clear limits. First, DRR is not a battery-life guarantee. Screen brightness, power mode, background activity, and processor and graphics load usually matter more to how long a laptop lasts. A machine running at high brightness under heavy load will not gain an ideal battery life from DRR alone. Blaming DRR for a short battery life, or presenting DRR as a cure for one, are both misjudgements.
Second, higher is not always better. Locking the highest rate permanently only adds needless redrawing while the picture is static. Locking the lowest rate permanently sacrifices smoothness during interaction. DRR exists precisely to avoid either extreme. Third, the saving only appears in everyday use where static periods exist. If most of the time is spent under heavy load or continuous interaction, the rate will sit high for long stretches, and the room for saving is naturally small. That is not DRR failing; it is the shape of that workload.
Fourth, sensitivity to switching varies between people. Some owners notice the moment of switching, while others notice nothing at all. That difference in sensitivity is not itself a fault, and it is not evidence of panel damage. The judgement should rest on whether switching follows the rhythm of activity and whether picture content is damaged, not only on whether switching was felt.
Normal Switching Versus a Fault: How to Tell
The distinction is not whether the number jumps, but whether the jumping follows activity and whether it is accompanied by a visible fault. Normal switching has three marks: it follows activity, falling back when still and rising when interacting; picture content stays intact, with text, images and window positions undisturbed; and it settles after switching rather than bouncing back and forth for no reason.
The warning signs are different. First, persistent flicker: the picture flickers repeatedly, unrelated to activity, even while nothing is moving. Second, repeated black screens or picture loss: the picture disappears for a long stretch during switching, or blacks out frequently before returning. Third, settings that will not stay: a chosen dynamic or fixed value reverts to another value after a restart or a power-state change, and does so every time. Fourth, damaged picture content: ghosting, misalignment or colour faults appear after switching, rather than only a change in the rate number.
One misunderstanding needs care here. At the instant of switching, an individual panel may show a brief change in how bright it feels. That brief feeling is different from persistent flicker: the first appears only at the switching instant and then settles, while the second persists, appears even when still, and is unrelated to activity. Treating a single brief feeling as panel damage is a misjudgement, and dismissing persistent flicker as normal DRR behaviour is equally a misjudgement. The right record is: how long the flicker lasted, under what activity it appeared, whether it appeared while still, and whether it disappeared when a fixed rate was chosen.
| Observation | Points toward normal switching | Points toward further investigation |
|---|---|---|
| Timing of the jump | Follows activity, falling back when still and rising when interacting | Unrelated to activity, repeatedly jumping while still |
| Picture content | Intact, with no damage | Ghosting, misalignment or colour faults |
| Flicker | Brief feeling at the switching instant, then settled | Persistent flicker, present even while still |
| Black screen | No black screen, or only a fleeting switching feeling | Repeated black screens or a long loss of picture |
| Settings retention | Chosen value stays, with power-state changes explainable | Reverts to another value for no reason, every time |
Checking Steps: Change One Variable at a Time
Checking a DRR problem should start at display settings and work outward, changing one variable at a time and recording whether the result changed. Changing settings, power mode and driver options all at once may make a symptom disappear, but nobody will know which step mattered, and the next occurrence will have to be investigated from scratch.
Step one is to check each display in turn. Open display settings, then advanced display settings, select the correct display first, and confirm whether the DRR control exists for that display, whether dynamic or a fixed value is currently chosen, and what the current resolution is. With several displays connected, this step must be repeated for each one, and one display's result must never be used to judge another.
Step two is to compare the graphics driver control panel. The driver control panel also carries refresh-rate settings, which may interact with the Windows setting. Both settings should be recorded, so that any conflict or overwriting between them can be seen. After changing one side, the Windows settings page should be watched to see whether its number follows, or whether the two sides stay independent.
Step three is to check power mode. Open the power and battery settings and confirm the current power mode, energy-saver state, and whether the machine is plugged in or on battery. The two power states should be recorded separately, to see whether the problem appears in only one of them. A problem only on battery points toward the power-saving side, while a problem in both states points away from power mode itself.
Step four is to check the computer maker's own power or display tools. Some laptops ship with a maker tool that can overwrite the refresh rate or power behaviour. Such a tool should be checked for any power-saving display, fixed-rate or similar option, and for any conflict with the Windows setting. This step names only the direction to check; it does not present the maker tool as the sole cause.
Step five is to compare full-screen application and game behaviour. Open a full-screen application or game and watch how the rate number changes inside and outside the application. An application's own rate behaviour may differ from DRR, so the two must be recorded separately: recovery after leaving the application points toward the application layer, while persistence after leaving it points elsewhere. Frame-rate cap settings belong to a separate guide, article 225, which is pointed to here in a single sentence and is not expanded into cap values in this article.
Step six is to review recent changes: system updates, driver updates, a newly connected display, a power-mode change, or a maker-tool installation. Settings often revert after such changes: an update restores a default, a new display carries a different default, or a maker-tool update overwrites an older setting. Reviewing changes is not about blaming one update, but about finding which variable changed just before the problem began.
If the steps above still do not separate normal switching from a fault, or if the problem involves persistent flicker, repeated black screens or settings that will not stay, checking should pause rather than continue by repeatedly changing settings. Repeated setting changes can themselves create new variables and make later judgement harder.
When Switching DRR Off Is Reasonable
Switching DRR off is not an admission of defeat, and it is not a repair. It is a trade-off choice, and in several situations it is entirely reasonable.
First, for an owner who is highly sensitive to rate changes and finds the switching feeling a constant distraction in everyday use. Switching off and locking a fixed value removes the jumping rhythm, at the cost of giving up the static power-saving trade-off.
Second, for situations where motion must stay consistent and predictable, such as recording, capture, comparison work, or repeated checks of the same motion effect. A fixed rate keeps test conditions identical, so results can be compared meaningfully.
Third, as a comparison during investigation. When DRR is suspected, switching it off and locking a fixed value is a clean comparison: if the symptom disappears, the evidence points toward the DRR side, and if the symptom remains, the evidence points elsewhere. After the comparison, the owner can decide whether to leave it off or on for the long term.
Fourth, when a game or full-screen application needs a fixed high rate and DRR switching interferes with that application's own rhythm. Game synchronisation and dark-scene flicker each have their own guides; VRR dark-scene flicker is article 205, pointed to here in a single sentence, and game synchronisation settings are not expanded in this article.
There is also a case where switching DRR off should not be expected to help. If the real problem is settings being reset, power mode overwriting, or a maker tool in conflict, simply switching DRR off will not fix the resetting itself, and the next update or power-state change may change the setting again. Before switching off, the owner should confirm whether the problem truly comes from switching itself, or from the settings-retention side.
Common Myths, Dismantled
Myth: A jumping number means the display is broken. DRR normally jumps by design, falling back when still and rising when interacting. A number alone is not a fault; the rhythm and any accompanying picture fault are what matter.
Myth: An external display without DRR means the driver is broken. External display DRR conditions are stricter, and each display must be checked in turn. A built-in panel having DRR does not promise it on an external display, and its absence there may simply mean the requirements are not met.
Myth: Turning DRR on guarantees a large battery improvement. Brightness, power mode, background activity and load usually matter more to battery life. DRR is one part of the power trade-off, not a battery-life guarantee.
Myth: Locking the highest rate is always best. A static picture redrawn at the highest rate all day only adds needless work. DRR exists to avoid extremes, saving power when still and staying smooth when interacting.
Myth: A changing game frame rate means DRR is at fault. Game frame rate depends on the game itself, scene load and synchronisation, which sit on a different layer from everyday DRR switching. The two must be compared separately.
Myth: A setting that reverts must mean a system fault. Power-state changes, energy-saver mode, maker-tool overwriting, and defaults restored after a system or driver update can all change a setting. The changed variable should be found first, rather than assuming a system fault.
Myth: A brightness feeling at the switching instant means panel damage. A brief feeling at the switching instant differs from persistent flicker. Persistent flicker, present even while still and accompanied by content damage, is what points toward further investigation.
What This Guide Deliberately Does Not Repeat
Display topics with their own guides are pointed to here rather than rewritten. Bandwidth, EDID and DSC causes of a display locked at 60 Hz belong to article 110. Panel type differences belong to article 226. Overdrive settings belong to article 214. ULMB technology belongs to article 220. Multi-display standby, flicker and no-signal-after-wake belong to article 138. Keeping those boundaries clear stops the reader from circling between articles.
Frequently Asked Questions (FAQ)
Why does my rate keep falling back from 120 Hz to 60 Hz? That is very likely normal DRR operation: a lower rate while reading still content saves power, and a higher rate while scrolling or interacting restores smoothness. First check whether the jumping follows activity and whether picture content stays intact; a rhythm that follows activity with intact content points toward normal switching, not a fault.
Why does my machine have no DRR option at all? Check each display in turn first, to confirm whether the built-in panel or an external display is being viewed. DRR requires Windows 11, VRR support, a maximum rate of at least 120 Hz, and a supporting graphics driver and panel firmware exposing that support. If any requirement is missing, the option will not appear, and that means the requirements are not met, not that the setting is hidden.
My external display supports a high rate, so why does it have no DRR? External display DRR conditions are stricter, and a high rate alone does not promise DRR. The external display itself must be selected in advanced display settings and confirmed there, rather than judged from the built-in panel's result.
The picture flashes when the rate switches. Is the panel faulty? Not necessarily. A brief feeling at the switching instant differs from persistent flicker. A brief feeling that settles at once with intact content points toward normal switching, while persistent flicker, present even while still and accompanied by content damage, points toward further investigation.
The rate behaves differently on battery and on mains power. Has the setting been changed? Not necessarily. Power state itself affects the power-saving trade-off, so behaviour on battery and on mains power can differ. The two states should be recorded separately, to see whether the problem appears in only one of them before judging which side it points to.
I switched DRR off, but the problem is still there. What does that mean? It means the evidence points away from DRR switching itself. Switching off is a clean comparison: disappearance after switching off points toward the DRR side, while persistence after switching off means the investigation should move to power mode, maker tools, the driver control panel, or settings retention.
When is it reasonable to leave DRR off for the long term? When switching feels constantly distracting, when recording or comparison work needs a consistent motion rhythm, or when a game or full-screen application needs a fixed high rate. Leaving it off is a choice with a cost, namely giving up the static power-saving trade-off, not a repair.
When to Seek Professional Help
If the comparisons above still do not separate normal switching from a fault, or if the problem involves persistent flicker, repeated black screens, or settings that will not stay, a professional inspection can separate a settings problem from a hardware problem before parts are replaced unnecessarily.
HK GPU Fix is located at Dali Plaza, Room 1209, Shek Mun. For graphics or display-related inspection, call 2186 8010 or reach us on WhatsApp at 6558 6806.