Your monitor box promises 144 Hz or 240 Hz, yet Windows 11 sits at 60 Hz and every mouse flick feels like it drags through syrup. It is the most common display mistake on new builds, and the fix usually takes under five minutes once you know where Windows hides the setting. This tutorial shows how to change monitor refresh rate on Windows 11 in 13 steps, then verifies the result, fixes the cases where the option is missing, and ends with a PowerShell auditor that logs what your system really runs.
Microsoft made Windows 11 version 26H2 generally available on September 29, 2026, and the route to the setting is still Settings, System, Display, Advanced display. The list of rates you see there depends on the monitor, the cable, the GPU, the driver, the resolution, and the selected display mode, so no single top value exists for every PC. That is why a rate can be missing even when the panel supports it, and why the first half of this guide checks hardware before it touches a menu.
If you already know your panel supports more than Windows offers and you want rates beyond the factory spec, read our walkthrough on overclocking a monitor after you finish here. Start with the safe path first. A correct standard rate fixes most complaints, and it gives you a clean baseline for everything else.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What You Need Before You Change Anything
This is a short tutorial with a small toolkit. You need a monitor that actually advertises a rate above 60 Hz, a cable and port that can carry it, an up-to-date graphics driver, and Windows 11 with the display adapter recognized. The table below lists each requirement with the current version as of October 28, 2026 and the reason it matters.
| Requirement | Current version or spec | Why it matters |
|---|---|---|
| Windows 11 | Version 26H2, generally available September 29, 2026 | Hosts the Advanced display page where the rate list lives. Eligible 24H2 and 25H2 PCs receive 26H2 through a small enablement package |
| NVIDIA GeForce driver | Game Ready Driver 621.01 WHQL | Newest confirmed GeForce driver. Older drivers can hide modes on new monitors |
| AMD Software: Adrenalin Edition | 26.10.1 WHQL, last updated October 20, 2026 | Current Radeon driver listed on AMD’s release notes page |
| Graphics card | Any recent card. Newest flagships are GeForce RTX 5090 and Radeon RX 9070 XT | Older cards work, but their ports set the ceiling |
| Monitor | A panel rated above 60 Hz at your target resolution | Windows can only offer what the monitor reports |
| Cable | DisplayPort or HDMI cable rated for your resolution and rate | The cheapest cable is the most common cause of a missing option |
| Admin rights | Local administrator | Needed for driver installs and the scheduled task in the project |
You do not need extra software for the main steps. Windows Settings and your GPU vendor’s control panel are enough. The project later in this article uses PowerShell, which ships with Windows 11, and needs no downloads.
Two warnings before you start. First, note your current resolution and rate so you can return to them if a change goes wrong. Second, if you run a laptop, plug in the charger before testing high rates, because the system may cap the rate on battery to save power.
How Refresh Rate Works and Why Windows Shows a Short List
Refresh rate counts how many times per second the panel redraws the image, measured in hertz. At 60 Hz the screen updates every 16.67 milliseconds, and at 240 Hz it drops to 4.17. Faster updates mean smoother motion, lower perceived input delay, and less blur during fast pans. They also mean more work for the GPU and more data across the cable.
That data load explains most missing options. A display mode is the combination of resolution, rate, color depth, and signal format. The connection has a fixed bandwidth budget, and every mode must fit inside it. When you raise the resolution the available rates fall, and when you raise the rate the available resolutions fall. The standards bodies make this clear. The DisplayPort standard and HDMI each define link speeds, and the label on a port tells you the generation, not the exact capability of that specific port.
Treat the labels with suspicion. A DisplayPort 2.1 sticker does not guarantee any particular refresh rate, and it does not prove every port on the card supports the same link class. HDMI 2.1 works the same way. According to HP’s monitor connectivity glossary, HDMI 2.1 offers 48 Gbps of bandwidth with example support for 4K at 120 Hz, 8K at 60 Hz, and variable refresh rate, but a given device may implement only part of that feature set.
| Connection | What usually limits the rate | What to check first |
|---|---|---|
| DisplayPort (any version) | Cable quality and the port’s link class | Use the cable shipped with the monitor and confirm the monitor’s on-screen menu allows the higher DisplayPort mode |
| HDMI 2.1 | Whether both ends and the cable support the full feature set | Check the monitor manual for the exact HDMI port that carries the top rate |
| Older HDMI | Bandwidth ceiling reached at lower resolutions | Lower the resolution or switch to DisplayPort |
| USB-C with DisplayPort alt mode | Dock or adapter bandwidth, shared USB lanes | Plug the monitor straight into the GPU as a test |
| Adapters (HDMI to DisplayPort and similar) | Active versus passive conversion | Remove the adapter to confirm it is the cause |
| Laptop internal panel | Power plan, hybrid graphics routing | Connect the charger and check the vendor panel |
One more rule matters for variable refresh. AMD’s current FreeSync documentation says the technology needs a compatible display, a compatible GPU or APU, and a current graphics driver, and that FreeSync can run over HDMI without HDMI 2.1. So a missing HDMI 2.1 port does not automatically rule out adaptive sync, which we cover in Step 10.
Steps 1 to 3: Identify Your Monitor, Cable and Driver
Resist the urge to open Settings first. Ten minutes of fact-finding saves an hour of guessing, and Steps 1 to 3 give you the three numbers every later step depends on.
Step 1: Find your monitor’s real maximum. Read the model number on the back label or in the on-screen menu, then open the maker’s spec page and note the top rate at your native resolution. Many monitors list several rates, such as a lower rate at 4K and a higher one at 1440p, or a higher rate only on one specific port. Write down both the rate and the port that supports it. If the spec says 144 Hz over DisplayPort and 120 Hz over HDMI, you now know which cable to use.
Step 2: Confirm which cable and port you actually use. Look at the back of the PC. If the monitor connects to the motherboard video output instead of the graphics card, the integrated graphics is driving the screen and the rate list will be short. This mistake is common on new builds. Move the cable to the graphics card and reboot. Then check the cable itself. Dell’s DisplayPort FAQ is a good primer on what the port does, and the short version is that the cable must match the standard your monitor and card use. When in doubt, swap in the cable that came in the monitor box.
Step 3: Install the current graphics driver. Open the vendor app or website and install the latest driver for your card. On GeForce hardware the newest confirmed Game Ready Driver is 621.01 WHQL from October 20, 2026. On Radeon hardware, AMD lists Adrenalin Edition 26.10.1 WHQL, last updated October 20, 2026. Pick the clean install option if the vendor offers it. If the new driver makes things worse, you can roll back the NVIDIA driver without reinstalling Windows.
Now record your baseline. Open PowerShell and run this command to see what Windows currently reports for each video controller.
Get-CimInstance Win32_VideoController |
Select-Object Name, DriverVersion, CurrentHorizontalResolution, CurrentVerticalResolution, CurrentRefreshRate |
Format-ListThe output below is an example. Your adapter name, driver version, and numbers will differ, but the shape is what you should expect.
Name : NVIDIA GeForce RTX 5090
DriverVersion : 32.0.16.2101
CurrentHorizontalResolution: 2560
CurrentVerticalResolution : 1440
CurrentRefreshRate : 60If CurrentRefreshRate reads 60 and your monitor is rated higher, you have confirmed the problem. If the adapter name shows a generic or integrated device while a discrete card is installed, go back to Step 2 and move the cable.
Steps 4 to 6: Change the Rate in Windows 11 Settings
Windows Settings is the safest place to change the rate because it talks to the driver through the standard display stack. These steps match the documented route for Windows 11 as of October 2026.
Step 4: Open Advanced display. Press the Windows key, type Settings, and open it. Go to System, then Display. Scroll to the Related settings area and click Advanced display. A right-click on the desktop followed by Display settings gets you to the same page faster.
Step 5: Choose the monitor, then the rate. At the top of Advanced display, use the dropdown to pick the correct monitor if you have more than one. Below the monitor details you will see a row called Choose a refresh rate. Open its dropdown and read the list. Pick the highest rate that your Step 1 research says the panel supports at this resolution. Windows shows a confirmation box with a countdown. Click Keep changes before the timer ends. If you do nothing, Windows reverts the change, which is a useful safety net when a mode turns the screen black.
Step 6: Handle a second monitor. Each display carries its own rate. Select the other monitor in the dropdown and repeat Step 5 for it. If you run a dual-monitor gaming setup with panels of different speeds, set each one to its own maximum instead of matching them. Windows handles mixed rates on modern drivers, although a few setups show brief stutter on the slower display. If you see that, drop the faster monitor to a rate that divides evenly, such as 120 Hz next to a 60 Hz companion, and check whether the stutter disappears.
A quick success check helps here. Drag a window quickly across the desktop or wiggle the mouse in a circle. At 60 Hz you see a trail of discrete cursor images with large gaps between them. At 144 Hz and above the gaps shrink so much that the trail looks nearly continuous. You will verify this properly in Step 12, but your eyes will tell you something has changed immediately.
Steps 7 to 9: Set the Rate in NVIDIA, AMD and Intel Software
Windows Settings is enough for most people. The vendor control panels matter when a rate is missing from Windows, when you need a custom resolution, or when you want to check which mode the driver thinks is active. Menu labels shift between driver releases, so treat the names below as a guide and search the panel if a label differs.
Step 7: NVIDIA Control Panel or NVIDIA app
Open the NVIDIA Control Panel from the desktop context menu or the Start menu, then go to the Display section and pick Change resolution. Select your monitor and look at the Refresh rate dropdown. This list comes from the driver, so a rate that appears here but not in Windows Settings usually points to a stale Windows display profile. Choose the rate, click Apply, and confirm. The NVIDIA app on newer driver packages also shows display information, though the classic panel remains the quickest place to compare the full mode list. Remember that the list can include rates for other resolutions, so filter by the resolution you actually use.
Step 8: AMD Software Adrenalin Edition
Open AMD Software: Adrenalin Edition, click the gear icon, and go to the Display tab. Here you can see the active display, the current rate, and Radeon options for adaptive sync. According to AMD’s release notes, Adrenalin 26.10.1 covers the Radeon RX 9070, RX 9060 and RX 9050 series, and AMD’s compatibility list reaches back to older RX families. If you see no display options, confirm you installed the full Adrenalin package and not a bare driver.
Step 9: Intel Graphics settings and integrated displays
Systems that rely on Intel graphics, including many thin laptops, expose rate controls in the Intel Graphics Software or the standard Windows page. Be careful with port assumptions here. One third-party listing describes the Arc B580 as reaching UHBR13.5 on its best DisplayPort output and UHBR10 on the others, and Intel’s own pages do not confirm that for the whole product family. The lesson is practical. Try each output on your card if one will not offer the rate you want.
When you finish a vendor-panel change, go back to Windows Settings and confirm it reports the same value. If the two disagree, the vendor panel has applied a custom profile, and you should pick one source of truth. Use Windows Settings for everyday use and the vendor panel only for custom modes.
Steps 10 and 11: Turn On Variable Refresh Rate and Match Your Games
Raising the maximum rate is only half the job. Variable refresh rate lets the monitor follow the GPU’s frame output instead of forcing the GPU to wait for a fixed tick. The result is less tearing without the delay of classic vertical sync.
Step 10: Enable adaptive sync for your hardware. Turn it on in two places. First, open the monitor’s on-screen menu and enable its adaptive sync option, which some makers label FreeSync, G-Sync Compatible, or Adaptive-Sync. Second, enable it in the GPU software. In the NVIDIA Control Panel the setting sits under Display, in the section for setting up G-SYNC. In AMD Software it appears as a FreeSync toggle on the Display tab. Our deeper guide on setting up G-Sync and FreeSync walks through compatibility checks and the common flicker problems on some panels. Over HDMI, check that the monitor’s HDMI port supports the feature, since support varies by port even on one monitor.
Step 11: Match in-game settings to the panel. Windows can show 144 Hz while a game quietly runs at 60. Open each game’s video settings and look for a refresh rate field in the display mode area. Set it to the same rate as the desktop. Choose borderless or exclusive fullscreen depending on the game, and avoid windowed mode for competitive play when you can. Then cap the frame rate a few frames below the monitor’s maximum, such as 141 on a 144 Hz panel, if you use adaptive sync with vertical sync enabled in the driver. That keeps the frame pace inside the variable range and avoids the delay that appears when frames spill past the limit.
Games are the place where the rate setting is most often lost. Many titles read the list of modes at launch and select the first entry, which is often 60 Hz. If a game ignores your preference, check whether it keeps a separate config file and edit the refresh rate there. A short note in the game’s forum usually names the exact line.
| Refresh rate | Frame time | Typical use |
|---|---|---|
| 60 Hz | 16.67 ms | Office work, video playback, laptop battery saver |
| 75 Hz | 13.33 ms | Entry gaming monitors |
| 120 Hz | 8.33 ms | Console modes, 4K gaming, smooth desktop |
| 144 Hz | Not listed | Common competitive baseline |
| 165 Hz | Not listed | Mid-range gaming panels |
| 240 Hz | 4.17 ms | Fast esports and high-end OLED |
| 360 Hz | Not listed | Specialist esports panels |
Higher rates demand more from the PC. If your GPU only produces 90 frames per second in a heavy game, a 240 Hz panel will not make it feel like 240. It will, however, show those 90 frames with lower latency than a 60 Hz panel would. For a sense of what current premium panels offer, see our comparison of 4K 240Hz OLED gaming monitors.
Steps 12 and 13: Verify the Change and Make It Stick
Step 12: Verify with an independent test. Trust but check. Open a motion test page such as the UFO test, which draws moving objects at your rate and shows trails on screen. Run it in a browser and compare how many images the camera or your eye records at 60 versus your new setting. The browser also needs to run at the right rate, so close extra tabs and make sure hardware acceleration is on. For a numeric check, rerun the PowerShell command from Step 3. CurrentRefreshRate should now show your target.
Get-CimInstance Win32_VideoController | Select-Object Name, CurrentRefreshRateName CurrentRefreshRate
---- ------------------
NVIDIA GeForce RTX 5090 144While you test, watch the heat. Higher rates and heavier frame output raise load, so spend a minute checking GPU temperature after a long session to be sure nothing runs hotter than expected.
Step 13: Make it stick. Windows stores the rate per monitor, but several events can reset it. A driver update, a monitor firmware change, a cable swap, or a docking station can all trigger a fresh detection that falls back to 60 Hz. After any of those, repeat Step 5. If you want a safety net, run the project script from the next section at every logon so you get a record and an early warning when the rate slips. Also write down the cable and port you use, because moving the cable to a different port restarts the detection process.
Finally, save a screenshot of the Advanced display page showing the correct rate, and keep it with your build notes. If you ever need to rebuild, you will know the target within seconds.
Worked Example: A 1440p Monitor Stuck at 60 Hz
Theory is easier to trust after you watch it solve a real case, so here is a typical session from start to finish. The numbers are illustrative, and the pattern is the one most readers hit. A new build has a 1440p monitor rated for 144 Hz. Windows Settings lists only 60 Hz, and the Step 3 command reports a refresh rate of 60.
First pass: the cable. The owner looks at the back of the case and finds the monitor plugged into the motherboard video output. That output belongs to the integrated graphics, which explains the short list. Moving the cable to the graphics card and rebooting adds more entries, but the top one is still 120 Hz and the monitor spec promises 144.
Second pass: the monitor menu. The on-screen menu has a setting for the DisplayPort mode that ships on an older option. Switching it to the newer mode makes the panel report its full capability. After a restart, the Choose a refresh rate dropdown now includes 144 Hz. The owner selects it, clicks Keep changes, and runs the PowerShell auditor. The log row changes from BELOW-MAX to OK.
Third pass: the game. The first shooter the owner launches still feels slow. A look at the video settings shows the game set to 60 Hz in exclusive fullscreen. Changing it to 144 Hz and capping frames just under the limit fixes the feel. Total time was well inside the 25 minutes this guide promises, and none of it needed a driver reinstall.
The lesson from the example is the order of attack. Check the cheap physical causes first, then the monitor’s own menu, then software, and last the individual games. Every step you skip adds guesswork.
Complete Working Project: A PowerShell Refresh Rate Auditor
The steps above fix the immediate problem. This project keeps it fixed. It is a single PowerShell script that lists every mode your primary display accepts, reports the current mode, compares it with the best rate at the current resolution, logs the result to a CSV file, and optionally switches rate for you. It talks to Windows through the same display API that Settings uses, so it needs no extra tools. The script handles the primary display only, so run it on the monitor you care about most.
Save the file as RefreshAudit.ps1 in a folder such as C:\Tools. The listing below is the whole thing. Read through it before you run it, since it changes display settings when you pass the switch option.
param(
[int]$SetHz = 0,
[string]$LogPath = "$env:USERPROFILE\Documents\refresh-audit.csv"
)
Add-Type -TypeDefinition @'
using System;
using System.Runtime.InteropServices;
[StructLayout(LayoutKind.Sequential, CharSet = CharSet.Unicode)]
public struct DEVMODE {
[MarshalAs(UnmanagedType.ByValTStr, SizeConst = 32)] public string dmDeviceName;
public short dmSpecVersion;
public short dmDriverVersion;
public short dmSize;
public short dmDriverExtra;
public int dmFields;
public int dmPositionX;
public int dmPositionY;
public int dmDisplayOrientation;
public int dmDisplayFixedOutput;
public short dmColor;
public short dmDuplex;
public short dmYResolution;
public short dmTTOption;
public short dmCollate;
[MarshalAs(UnmanagedType.ByValTStr, SizeConst = 32)] public string dmFormName;
public short dmLogPixels;
public int dmBitsPerPel;
public int dmPelsWidth;
public int dmPelsHeight;
public int dmDisplayFlags;
public int dmDisplayFrequency;
public int dmICMMethod;
public int dmICMIntent;
public int dmMediaType;
public int dmDitherType;
public int dmReserved1;
public int dmReserved2;
public int dmPanningWidth;
public int dmPanningHeight;
}
public static class DisplayApi {
[DllImport("user32.dll", CharSet = CharSet.Unicode)]
public static extern bool EnumDisplaySettings(string deviceName, int modeNum, ref DEVMODE devMode);
[DllImport("user32.dll", CharSet = CharSet.Unicode)]
public static extern int ChangeDisplaySettingsEx(string deviceName, ref DEVMODE devMode, IntPtr hwnd, uint flags, IntPtr lParam);
}
'@
function New-DevMode {
$dm = New-Object DEVMODE
$dm.dmSize = [int16][System.Runtime.InteropServices.Marshal]::SizeOf([type][DEVMODE])
return $dm
}
function Get-CurrentMode {
$dm = New-DevMode
[void][DisplayApi]::EnumDisplaySettings($null, -1, [ref]$dm)
[pscustomobject]@{ Width = $dm.dmPelsWidth; Height = $dm.dmPelsHeight; Hz = $dm.dmDisplayFrequency }
}
function Get-DisplayModes {
$modes = @()
$i = 0
$dm = New-DevMode
while ([DisplayApi]::EnumDisplaySettings($null, $i, [ref]$dm)) {
if ($dm.dmBitsPerPel -ge 32) {
$modes += [pscustomobject]@{ Width = $dm.dmPelsWidth; Height = $dm.dmPelsHeight; Hz = $dm.dmDisplayFrequency }
}
$i++
}
$modes | Sort-Object Width, Height, Hz -Unique
}
function Set-RefreshRate([int]$Hz) {
$dm = New-DevMode
[void][DisplayApi]::EnumDisplaySettings($null, -1, [ref]$dm)
$dm.dmDisplayFrequency = $Hz
$dm.dmFields = 0x80000 -bor 0x100000 -bor 0x400000
$test = [DisplayApi]::ChangeDisplaySettingsEx($null, [ref]$dm, [IntPtr]::Zero, 0x2, [IntPtr]::Zero)
if ($test -ne 0) { throw "Windows rejected $Hz Hz at the current resolution (code $test)." }
$apply = [DisplayApi]::ChangeDisplaySettingsEx($null, [ref]$dm, [IntPtr]::Zero, 0x1, [IntPtr]::Zero)
if ($apply -ne 0) { throw "Applying $Hz Hz failed (code $apply)." }
}
if ($SetHz -gt 0) {
Set-RefreshRate -Hz $SetHz
Start-Sleep -Seconds 2
}
$gpu = Get-CimInstance Win32_VideoController | Select-Object -First 1
$current = Get-CurrentMode
$modes = Get-DisplayModes
$maxHz = ($modes | Where-Object { $_.Width -eq $current.Width -and $_.Height -eq $current.Height } |
Measure-Object Hz -Maximum).Maximum
$row = [pscustomobject]@{
Time = Get-Date -Format s
Adapter = $gpu.Name
Driver = $gpu.DriverVersion
Width = $current.Width
Height = $current.Height
CurrentHz = $current.Hz
MaxHzAtThisResolution = $maxHz
Status = if ($current.Hz -lt $maxHz) { 'BELOW-MAX' } else { 'OK' }
}
$row | Export-Csv -Path $LogPath -Append -NoTypeInformation
$row | Format-ListHere is how it works. The DEVMODE structure is the Windows description of a display mode. EnumDisplaySettings with index minus one returns the current mode, and counting upward through the indexes returns every mode the driver will accept. ChangeDisplaySettingsEx then applies a new mode. The script first calls it with the test flag, which asks Windows whether the mode would work without changing anything. Only when the test passes does it call again with the update-registry flag so the choice persists across restarts.
Run it in a normal PowerShell window. The first command audits and logs. The second asks for 144 Hz and then audits.
powershell -NoProfile -ExecutionPolicy Bypass -File C:\Tools\RefreshAudit.ps1
powershell -NoProfile -ExecutionPolicy Bypass -File C:\Tools\RefreshAudit.ps1 -SetHz 144A typical run on a 1440p monitor that has slipped back to 60 Hz looks like the output below. The values are illustrative, so your adapter and driver will differ.
Time : 2026-10-28T19:42:07
Adapter : NVIDIA GeForce RTX 5090
Driver : 32.0.16.2101
Width : 2560
Height : 1440
CurrentHz : 60
MaxHzAtThisResolution : 144
Status : BELOW-MAXBELOW-MAX is the signal you want. It tells you the panel accepts a higher rate at this resolution, so you can pass the switch option or repeat Step 5. If the status reads OK but the number is still lower than the box promised, the limit sits in the cable, the port, or the monitor menu, and the troubleshooting section below applies.
To run the audit at every sign-in, register a scheduled task. Use a path you control, and only use the bypass flag with a script you wrote or reviewed yourself.
schtasks /create /tn "RefreshAudit" /sc onlogon /rl limited /tr "powershell.exe -NoProfile -ExecutionPolicy Bypass -File C:\Tools\RefreshAudit.ps1"After a week, open refresh-audit.csv in a spreadsheet. A run of OK rows with a sudden BELOW-MAX entry after a driver update tells you exactly which update reset the setting. That small log turns a vague complaint into a dated record you can attach to a bug report.
Seven Common Pitfalls That Waste an Evening
These mistakes account for most of the support threads on the topic. Check them before you try anything exotic.
- Plugging into the motherboard, not the graphics card. The integrated output drives the screen, and the rate list shrinks to what it supports. Move the cable to the GPU and reboot.
- Trusting a version label. A DisplayPort 2.1 or HDMI 2.1 sticker does not guarantee a given rate, and it does not prove every port on a card has the same capability. Read the monitor manual for the exact port that carries the top mode.
- Using the wrong cable. A cable that carries 1080p happily can fail at 1440p and 144 Hz. Use the one from the monitor box, or buy one certified for your standard.
- Changing the rate in Windows but not in the game. The desktop reads 144 Hz while the game runs at 60. Set the game’s own field.
- Ignoring the monitor’s menu. Many panels ship with a high-speed or overdrive option off by default, and some hide their top DisplayPort mode behind a setting. Open the on-screen menu once and read every entry.
- Missing the Keep changes box. Windows reverts the change when the countdown ends. If you clicked too late, you will think the change failed.
- Stacking adapters and docks. Every adapter is another point where bandwidth drops. Test with a direct cable first.
A related trap is chasing a higher number than your content needs. Video at 24 or 30 frames per second looks best when the display rate is a clean multiple, so a 120 Hz setting often plays film cleaner than 144 Hz. If playback looks uneven, test both.
Troubleshooting: 10 Fixes When the Rate Is Missing or Resets
Work through this list in order. Most problems fall to the first four items.
- Only 60 Hz appears in the list. Swap the cable for the one in the monitor box, then move it to a different port on the card. Reboot with the monitor on. If the list grows, the old cable or port was the limit.
- The monitor shows as a generic device. Windows could not read the display’s identification data. Try a different cable, then unplug the monitor for a minute and reconnect. If a driver or INF file is available from the maker, install it.
- The panel’s own menu blocks the mode. Look for a DisplayPort version, high refresh, or overdrive setting in the on-screen menu and enable it. Some monitors need this before they report their top modes.
- The rate resets after a reboot. Another program may be applying a profile at startup. Check the GPU vendor software for a saved custom mode or a game profile, and check startup apps from a monitor utility. Run the project script at logon to spot the moment it changes.
- The screen goes black after a change. Wait for the countdown to finish so Windows reverts. If it does not, press Windows, Ctrl, Shift and B together to restart the graphics driver, or boot into Safe Mode and pick a lower rate.
- A game locks to 60 Hz. Set the refresh rate inside the game, switch between borderless and exclusive fullscreen, and check for a config file that stores the rate.
- High rate but washed-out color or lower detail. At the edge of a link’s bandwidth, the system may drop color depth or use compression. Try one step lower in rate or resolution and compare. This is a bandwidth symptom, not a defect.
- Flicker with adaptive sync. Some panels flicker when frame rates swing widely. Lower the maximum rate a little, cap frames, or turn off adaptive sync in the monitor menu to test.
- The driver looks corrupted. Use the vendor installer’s clean option. If the problem started with a new release, roll back to the previous driver, then wait for the next one.
- Remote sessions and virtual machines. A remote desktop or a virtual display adapter often reports a fixed rate. Check the rate on the physical machine and not inside the session.
If none of these work, test the monitor with another PC or a laptop. If the second machine also cannot reach the rated mode, the monitor, its firmware, or its cable is at fault and the fix is a warranty claim, not a setting.
Advanced Tips for Multi-Monitor, KVM and Laptop Setups
Once the basics work, a few extra habits keep the setup healthy. Start with a baseline of calibration. Rate does not change color, but a new rate often prompts you to revisit picture settings, so it is a good time to calibrate the panel and save the profile.
- Use KVM switches carefully. A KVM can cap the rate because it sits in the signal path. If your rate drops after you add one, test without it first, then look for a model rated for your resolution and rate. Our guide to a KVM switch dual-monitor setup covers the compatibility checks.
- Watch overdrive and ghosting. Raising the rate changes the pixel response behavior, and some overdrive modes cause trailing on the new setting. If you see it, read how to fix monitor ghosting and adjust the overdrive level.
- Protect OLED panels. A high rate does not harm an OLED, but static desktop elements still can. Review OLED burn-in prevention if your new panel uses that technology.
- Pair the rate with your mouse. A fast display shows off a fast pointer. Raise the mouse polling rate to match, using our guide to gaming mouse DPI and polling rate.
- Lower the rate for battery and noise. A laptop on battery often runs better at 60 Hz or 120 Hz. Reserve the top rate for when you are plugged in.
- Mac and Linux notes. If you share a monitor with a Mac, macOS lists the rate in its Displays settings, and Linux desktops expose it in their display settings or through the xrandr command. The cable and port rules from earlier apply to every operating system.
For more guides in this area, browse the hardware section, where we keep the monitor, GPU, and storage walkthroughs together.
Custom Modes, EDID and Why You Should Not Force Them
Every monitor describes itself to the PC through a small block of data called EDID. Windows and the driver read it to build the list you see in Advanced display. If the list is wrong, the cause is usually a bad cable, a faulty handshake, or a monitor firmware quirk. The tempting shortcut is to force a mode by writing a custom resolution in the vendor panel or with a third-party utility. That works for some monitors, and it can also cause a blank screen, flicker, or an unstable link that only shows up after hours of play.
Treat custom modes as the last resort and use a simple order of operations. Fix the cable and the port. Update the driver. Check the monitor menu. Only then try a custom rate, and raise it in small steps while you watch for artifacts such as flickering lines, sparkles, or sudden black frames. Our overclocking guide linked in the introduction covers that process, including how to back out of a bad mode, so use it if you decide to go that route. Keep a note of the last good value so you can return to it quickly.
One more detail helps. If you run through a KVM or an HDMI capture device, the handshake data may come from that box and not from the monitor. A short list in that case means the accessory is presenting a limited profile. Try the monitor directly to confirm.
Refresh Rate, Power Draw and When Lower Is Better
A higher rate costs power. The GPU renders more frames, the panel redraws more often, and the link moves more data. On a desktop the cost is small, but on a laptop it shows up in battery life and fan noise. Many tutorials simply say pick the highest number. That is rarely the best advice for a machine you carry around.
A sensible split looks like this. Use the top rate while you play or draw with a pen, because the smoothness is the whole point. Use a mid rate such as 120 Hz for browsing and video, since it keeps motion smooth without the full cost. Use 60 Hz on battery when you only need text and a low-power state. Your laptop may handle some of this on its own, so check the power settings before you build a manual routine.
The project script from earlier makes switching cheap. Pass 60 for battery work and your top rate for plugged-in sessions, and let the CSV tell you how often you actually changed it. After a month, the log shows whether the high rate earns its keep in your daily routine.
Frequently Asked Questions
How do I change monitor refresh rate on Windows 11? Open Settings, go to System, then Display, then Advanced display. Pick your monitor, open the Choose a refresh rate dropdown, select the highest supported value, and click Keep changes before the countdown ends. If the list is short, check the cable, port, and driver first.
Why is my monitor stuck at 60 Hz? The most frequent causes are a cable plugged into the motherboard output, a cable or port that cannot carry the mode, a missing graphics driver, or a monitor menu option that is off. Work through the troubleshooting list in order.
Does a DisplayPort 2.1 or HDMI 2.1 label guarantee a certain refresh rate? No. The label names the generation of the standard, not the exact capability of that port, cable, or device. Check the monitor manual for the rate each specific port supports.
Can I run two monitors at different refresh rates? Yes. Windows stores the rate per display, so set each panel to its own maximum. A few setups show stutter on the slower screen, and dropping the faster screen to a clean multiple often cures it.
Is a higher refresh rate always better? Not always. Higher rates cost power and need a GPU that can feed them. They help most in fast games and smooth scrolling, while a lower rate suits battery use and some video content.
Will FreeSync work over HDMI? According to AMD’s current FreeSync documentation, FreeSync can run over HDMI without HDMI 2.1, as long as the display, GPU, and driver all support it. Support varies by port, so confirm your exact input.
Is it safe to use a script to change the rate? The project script tests the mode first and only applies it if Windows accepts it, so it will not push your monitor to an unsupported state. Read any script before you run it and keep the Windows revert timer in mind when you test.
Which driver version should I install in October 2026? The newest confirmed GeForce Game Ready Driver is 621.01 WHQL from October 20, 2026. On Radeon, AMD lists Adrenalin Edition 26.10.1 WHQL, last updated October 20, 2026. Check the vendor site, since newer releases may appear after this article.
