Screen tearing shows up as a horizontal split in a moving image, one half of the frame slightly out of step with the other, and it is still one of the most common complaints in PC and console gaming forums heading into the back half of 2026. The cause has not changed in over a decade: your GPU is pushing frames to the display faster or slower than the panel can draw them, so the monitor ends up rendering two frames in a single scan. What has changed is the toolkit for fixing it. NVIDIA and AMD have folded adaptive sync deeper into their driver stacks, Windows 11 now defaults Hardware-Accelerated GPU Scheduling to on for most systems, and Microsoft’s KB5079391 preview build, shipped in March 2026, added official support for refresh rates above 1,000Hz (with refresh handling tested internally up to 5,000Hz), meaning the display-timing math behind tearing now has to account for panels far outside the old 60-360Hz range. Handhelds like the Steam Deck and ROG Xbox Ally X ship with their own frame-pacing quirks that desktop guides rarely cover.
This guide walks through 12 steps to diagnose and eliminate screen tearing on Windows, SteamOS, and Linux gaming handhelds, using only free, official tools: V-Sync, G-Sync, FreeSync, frame-rate caps, driver settings, and (for advanced users) Custom Resolution Utility. Budget about 40 minutes if you work through every step, or 5 minutes if you just need the one setting that fixes your specific case.
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 Causes Screen Tearing on PC, Consoles, and Handhelds
A monitor redraws its screen from top to bottom at a fixed interval set by its refresh rate. A 60Hz panel redraws 60 times a second, a 165Hz panel does it 165 times a second, and so on. Your GPU, meanwhile, renders frames as fast as the game engine and hardware allow, which is rarely a clean multiple of the monitor’s refresh rate. When the GPU finishes a new frame in the middle of the monitor’s scan, and the display isn’t told to wait, the top portion of the screen shows the old frame while the bottom portion shows the new one. That visible seam is the tear line, and if the frame rate keeps drifting relative to the refresh rate, the tear line drifts too, which is why it looks like it’s scrolling.
Three conditions make tearing worse. First, an uncapped frame rate that swings well above or below your refresh rate gives the GPU more chances to hand off a half-finished frame mid-scan. Second, a cable or port running below its rated bandwidth (an HDMI 2.0 cable on an HDMI 2.1 display, for instance) can force a display to drop to a lower effective refresh rate without warning the OS, throwing off the sync math. Third, some games render internally in exclusive fullscreen while Windows composites in borderless, and switching between those modes changes which layer is responsible for buffering frames, occasionally reintroducing tearing that a driver-level fix had already solved.
The fix in every case is the same idea in different clothing: make the GPU’s frame delivery match the monitor’s draw cycle, either by forcing the GPU to wait (V-Sync), letting the monitor’s refresh rate stretch to match the GPU (G-Sync/FreeSync), or keeping the frame rate below the refresh rate so there’s headroom either way (a frame cap).
Buffering, Frame Pacing, and Why Averages Lie
A GPU averaging 165fps on a 165Hz monitor still tears constantly if the frame times behind that average swing wildly, say from 4ms to 9ms and back, because the panel needs a steady cadence, not just a matching long-run average. This is why two systems with the same benchmark average fps can behave completely differently on the same monitor. Double buffering, the default in most engines, swaps a finished “back buffer” frame into the “front buffer” the display reads from as soon as it’s ready, with no regard for where the scan currently sits. Triple buffering adds a second back buffer so the GPU always has somewhere to write while the display finishes reading, which smooths out frame pacing without the input-lag penalty of classic V-Sync, though not every engine implements it, and some implementations still tear at extreme frame rate mismatches. If two fixes in this guide both technically apply to your situation and one still tears more than the other, frame pacing consistency, not raw average fps, is usually the reason.
Prerequisites: What You Need Before You Start
- Operating system: Windows 11 (recommended) or Windows 10 22H2, SteamOS 3.6 or later for Steam Deck, or a current Linux distro with KWin/Mutter for handhelds like the ROG Ally or Legion Go.
- GPU driver: Latest NVIDIA Game Ready or Studio driver via the NVIDIA app, or the latest AMD Software: Adrenalin Edition. Both ship monthly updates in 2026, so check for one before troubleshooting further.
- A VRR-capable display (optional but strongly recommended): Any monitor certified G-Sync, G-Sync Compatible, FreeSync, FreeSync Premium, or FreeSync Premium Pro.
- The right cable: DisplayPort 1.4 (or 2.1 for the newest 4K/240Hz+ panels) or HDMI 2.1 for high-refresh, high-resolution setups. A generic HDMI cable pulled from a drawer is the single most common hidden cause of intermittent tearing.
- RivaTuner Statistics Server (RTSS): free, bundled with MSI Afterburner, used for frame-rate capping.
- Custom Resolution Utility (CRU) by ToastyX: free, only needed for the advanced step near the end of this guide.
- About 40 minutes and admin rights on your PC.
Step 1: Confirm You’re Actually Seeing Screen Tearing
Before changing any settings, rule out other causes. Stuttering, ghosting, and input lag all get misdiagnosed as tearing, and each has a different fix. The cleanest way to confirm tearing is Blur Busters’ TestUFO, a free browser-based motion test. Open it in your browser at your monitor’s native resolution, load the “Frame Skipping” or standard UFO motion test, and watch the object move horizontally across the screen. A horizontal split in the moving object, with the two halves briefly out of alignment, is a genuine tear. If you instead see the object skip or jump instead of gliding smoothly, that’s frame pacing or a low frame rate, not tearing, and you should check Step 6 (frame capping) before anything else.
Take a screen recording with your phone at 60fps or higher if you want to review the tear in slow motion. It’s easier to spot in fast horizontal camera pans in games like racing titles or first-person shooters than in slower strategy games, so test with something that has consistent lateral motion.
Step 2: Check Your Refresh Rate, Cable, and Port
Open Windows Settings, go to System, then Display, then Advanced Display, and confirm the refresh rate shown matches what your monitor is actually rated for. It’s common for a 165Hz monitor to silently default to 60Hz after a driver update, a cable swap, or a Windows update, and gaming at 60Hz on a variable refresh panel with G-Sync disabled is a textbook tearing setup. You can also check this from PowerShell, which is faster if you’re troubleshooting across multiple displays.
Get-CimInstance -Namespace root\wmi -ClassName WmiMonitorID | ForEach-Object {
$name = ($_.UserFriendlyName -notmatch 0 | ForEach-Object {[char]$_}) -join ""
Write-Output $name
}
Get-CimInstance -ClassName Win32_VideoController | Select-Object Name, CurrentRefreshRate, CurrentHorizontalResolution, CurrentVerticalResolutionIf CurrentRefreshRate is lower than expected, reset it in Display Settings first. Next, check the cable. HDMI 2.0 tops out around 18Gbps, which is enough for 4K at 60Hz but not 4K at 120Hz or higher with full chroma, so a display that can’t get enough bandwidth will often silently step down its refresh rate or color depth, which throws off sync. HDMI 2.1 (48Gbps) and DisplayPort 1.4 (32.4Gbps) or DisplayPort 2.1 are the safer choices for anything above 4K/60. Also try a different port on the GPU itself. It sounds trivial, but some cards route certain ports through a different internal controller, and one port can behave differently from another on the same card.
Step 3: Turn On V-Sync the Right Way
V-Sync is the oldest fix and still the most reliable fallback when a display doesn’t support adaptive sync. It forces the GPU to hold a completed frame until the monitor is ready for it, which eliminates tearing completely but can introduce input lag and, on older implementations, stutter when the frame rate drops below the refresh rate. Enable it in one place, not three. Turning on V-Sync in the game, in the NVIDIA app or AMD Software, and in Windows all at once is a common mistake that stacks latency without adding any benefit.
The recommended order in 2026 is to enable V-Sync inside the game itself first, since most engines pace frames more intelligently than a blanket driver override. If the game doesn’t offer the option, or if tearing persists, set it at the driver level instead: in the NVIDIA app, go to Graphics, select your game’s profile, and set Vertical Sync to On. In AMD Software: Adrenalin Edition, open Gaming, select the game, and toggle Vertical Refresh under the Display section. Avoid enabling V-Sync in more than one layer at a time.
Step 4: Enable NVIDIA G-Sync or G-Sync Compatible
If your monitor supports G-Sync or G-Sync Compatible, this is a better fix than V-Sync because it eliminates tearing without the input lag penalty, by letting the monitor’s refresh rate vary to match the GPU’s frame output instead of forcing the GPU to wait. Open the NVIDIA app (or the legacy NVIDIA Control Panel if you haven’t migrated), go to Display, then Set Up G-SYNC, and confirm the checkbox for “Enable G-SYNC, G-SYNC Compatible” is checked for your specific monitor. Many G-Sync Compatible monitors, which are non-NVIDIA-certified displays validated by NVIDIA to work with the feature, ship with this off by default. NVIDIA’s January 2026 GeForce driver update alone validated 63 new G-SYNC Compatible displays as part of the same driver stack that introduced DLSS 4.5, so it’s worth rechecking the list even if your monitor wasn’t on it a year ago.
Underneath that toggle, you’ll also see an option for “Enable settings for the selected display model” and, separately, a per-application toggle for whether G-Sync applies in windowed and borderless modes. For 2026-era games that default to borderless fullscreen, make sure “Enable for windowed and full screen mode” is checked, or G-Sync will only activate in true exclusive fullscreen, which fewer titles use by default now than they did five years ago. If you’re shopping for a new panel rather than tuning an existing one, NVIDIA’s newer G-SYNC Pulsar monitors, which pair VRR with backlight-strobing motion blur reduction, began shipping from Acer, AOC, ASUS, and MSI on January 7, 2026, with AOC’s AGON Pro AG276QSG2 landing at £559 in February 2026 as one of the first models on shelves.
Step 5: Enable AMD FreeSync or FreeSync Premium
AMD FreeSync works on the same variable refresh rate principle as G-Sync and, on most modern monitors, is enabled through both the monitor’s own on-screen display and the AMD driver. Open the monitor’s OSD menu first and confirm FreeSync (sometimes labeled Adaptive-Sync, AMD FreeSync Premium, or simply VRR) is turned on there. Then open AMD Software: Adrenalin Edition, go to Display, and toggle AMD FreeSync to On. If the toggle is grayed out, the monitor connection isn’t reporting FreeSync support, which usually means the wrong port or cable, so revisit Step 2.
FreeSync Premium adds low-framerate compensation, which keeps the sync window stable even when your frame rate drops well below the display’s minimum refresh, and FreeSync Premium Pro adds HDR requirements on top of that. None of the tiers require anything different from you as a user beyond the same on/off toggle, the naming just tells you what the panel is capable of.
Step 6: Cap Your Frame Rate Below Your Refresh Rate
Even with G-Sync or FreeSync enabled, most panels still tear if the frame rate exceeds the top of the display’s variable refresh range, because the sync window has an upper bound. The standard fix is to cap your frame rate a few frames below your monitor’s max refresh rate, giving the adaptive sync window room to work. RTSS (RivaTuner Statistics Server), installed alongside MSI Afterburner, is the most precise free tool for this on Windows, because it caps at the frame-presentation level rather than relying on the game engine’s own limiter, which is often less consistent.
| Monitor Refresh Rate | Recommended Frame Cap | Why |
|---|---|---|
| 60Hz | 58 fps | Keeps frame delivery inside the sync window with margin for frame time variance |
| 75Hz | 72 fps | Standard for budget FreeSync monitors |
| 144Hz | 141 fps | The most common competitive-gaming refresh rate in 2026 |
| 165Hz | 162 fps | Common on mid-range IPS gaming monitors |
| 240Hz | 237 fps | Needs a strong GPU to hit consistently, pair with DLSS/FSR upscaling if needed |
| 360Hz | 355 fps | Esports-tier panels, where the frame cap matters more than raw Hz |
To set this in RTSS, launch the app, select your game’s executable from the dropdown (or use the Global profile), and enter your target number in the Framerate limit field. RTSS applies the cap the next time you launch the game. Both the NVIDIA app and AMD Software also include their own built-in frame limiters now (NVIDIA calls it Max Frame Rate under the 3D Settings/Graphics tab, AMD calls it Frame Rate Target Control under Gaming) if you’d rather not install a third-party tool.
Step 7: Update GPU Drivers and Windows Display Settings
Outdated GPU drivers are a recurring, boring, and frequently overlooked cause of tearing, especially after a game patch changes how it presents frames to the OS. Update through the NVIDIA app or AMD Software’s built-in updater rather than relying on Windows Update, which often lags weeks behind the vendor’s own release. After updating, do a clean install if you’re coming from a driver more than two major versions old. Both NVIDIA and AMD include a “Clean Installation” or “Factory Reset” checkbox in their installer that wipes old, conflicting profile settings, worth using if you’ve been fighting tearing across multiple driver versions without success. As of June 2026, AMD’s latest WHQL branch is Adrenalin 26.5.1 (driver version 26.10.07.01), with the follow-up Adrenalin 26.6.2 release the same month adding official FSR 4.1 support for RDNA 3 GPUs, a rendering path that also helps stabilize frame delivery, so RDNA 3 owners still seeing tearing should confirm they’re on at least that build.
While you’re in Windows Settings, also check System, then Display, then Graphics, and review any per-app “High Performance” vs “Power Saving” GPU assignments. On laptops with both integrated and discrete GPUs, a game accidentally running on the integrated GPU while the display is wired to the discrete GPU’s output is a classic and confusing tearing cause, because the two GPUs pace frames independently. Force the game to the discrete GPU explicitly under Graphics settings if you have a hybrid laptop.
Step 8: Check Hardware-Accelerated GPU Scheduling and Game Mode
Hardware-Accelerated GPU Scheduling (HAGS) hands frame-queue management from the CPU to a dedicated processor on the GPU, and Windows 11 now defaults it to on for most current systems. For most setups this reduces latency and helps sync, but on a small number of GPU and driver combinations it introduces micro-stutter that can look like tearing. Microsoft’s KB5101684 preview, released in July 2026, is the latest in a string of Windows 11 updates that touch display timing and VRR behavior under the hood, so if tearing appears right after a Windows update, check whether that build (or a newer one) is installed before assuming it’s a GPU-side regression. It’s worth toggling HAGS off as a diagnostic step if nothing else in this guide has worked. Go to Settings, System, Display, Graphics, then Default Graphics Settings, and flip Hardware-accelerated GPU scheduling off, restart, and retest with TestUFO.
# Toggle Hardware-Accelerated GPU Scheduling from an elevated PowerShell prompt
# 2 = enabled, 1 = disabled (requires a restart to take effect)
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\GraphicsDrivers" -Name "HwSchMode" -Value 1
Restart-Computer -ConfirmAlso check Windows Game Mode (Settings, Gaming, Game Mode). It’s generally beneficial, but on systems with background capture software like Xbox Game Bar recording actively running, it can compete for GPU resources in a way that destabilizes frame pacing. If you record gameplay and see tearing only during recorded sessions, this is the setting to check first.
Step 9: Rule Out Cable and Port Bandwidth Limits
This deserves its own step beyond the quick check in Step 2, because bandwidth-limited tearing is intermittent and easy to misdiagnose as a software problem. A 4K/240Hz signal over DisplayPort 1.4, for example, needs Display Stream Compression (DSC) to fit inside the available bandwidth, and DSC support is not universal across every GPU, cable, and monitor combination. If your monitor supports DSC but your cable is a generic or overly long unbranded one, the signal can intermittently drop bits, which some monitors handle by silently dropping frames.
The fix is a certified cable rated for your exact bandwidth needs (look for “DisplayPort 1.4 certified” or “HDMI 2.1 Ultra High Speed” labeling, not just the connector shape) and a cable under 2 meters where possible, since signal integrity degrades with length at these bandwidths. If you’re using a USB-C to DisplayPort adapter for a handheld or laptop dock, confirm it explicitly supports DisplayPort Alt Mode at the bandwidth your resolution and refresh rate require, since many budget adapters cap out well below what the port physically supports.
Step 10: Fix Screen Tearing on Steam Deck, ROG Ally, and Linux Handhelds
Handhelds add a wrinkle desktop guides skip: the compositor. On SteamOS, Valve’s Gamescope compositor manages frame pacing and VRR for you, and it’s generally reliable, but tearing can still show up in Desktop Mode, which runs the KDE Plasma desktop’s own compositor instead of Gamescope. If tearing only appears in Desktop Mode, open System Settings, go to Display and Monitor, then Compositor, and confirm “Allow tearing” is unchecked and VSync is enabled for the compositor. In Gaming Mode itself, tearing usually means the in-game frame cap is set above the panel’s refresh rate, so check the Performance overlay (the “…” Quick Access menu) and cap the frame rate there instead of leaving it uncapped.
# On SteamOS Desktop Mode or a Linux handheld running KDE Plasma, check the connected
# display and force a compositor re-init from a terminal (Konsole)
xrandr --query | grep -w connected
kwriteconfig6 --file kwinrc --group Compositing --key Backend "OpenGL"
qdbus org.kde.KWin /Compositor org.kde.kwin.Compositing.reinitializeOn the ROG Xbox Ally X and Legion Go 2, which run full Windows rather than SteamOS, the fix set is the same as the rest of this guide: enable VRR in the handheld’s own Armoury Crate or Legion Space overlay, and set a frame cap a few fps below the panel’s native refresh rate. Both devices ship with an in-app FPS limiter specifically because their small high-refresh panels tear noticeably at the edges of their sync range.
Step 11: Fine-Tune With Custom Resolution Utility (Advanced)
If every earlier step still leaves occasional tearing, and you’re comfortable with a bit more risk, Custom Resolution Utility (CRU) by ToastyX lets you edit the EDID timing your GPU driver reports for the display, which can smooth out edge-case refresh rates that neither the driver’s default nor the monitor’s advertised spec handle cleanly. Download CRU, run it as Administrator, select your monitor from the dropdown, and under Detailed Resolutions click Add. Adjust the refresh rate in 1Hz increments rather than jumping straight to a target number, testing stability at each step with TestUFO before moving to the next.
After each change, run restart64.exe (bundled with CRU) to reload the display driver without a full reboot. If a change produces a black screen or the display drops signal, wait 15 seconds for Windows to auto-revert, or run reset.exe from Safe Mode to strip all EDID overrides and start over. Treat CRU as a last resort, not a first step. It edits how your GPU understands the display’s own timing spec, and pushing it too far can produce an unstable image that looks worse than the tearing you started with.
Step 12: Build Your Complete Tear-Free Setup
With every individual toggle covered, here is the full working configuration that eliminates tearing for the overwhelming majority of Windows gaming setups in 2026, combining the pieces from Steps 3 through 8 into one checklist you can apply top to bottom on a fresh install.
- Confirm the correct refresh rate is active in Windows Display Settings (Step 2).
- Use a certified DisplayPort 1.4/2.1 or HDMI 2.1 cable rated for your resolution and refresh rate (Steps 2 and 9).
- Enable G-Sync/G-Sync Compatible or AMD FreeSync in the driver app, matched to your monitor (Steps 4 and 5).
- Leave in-game V-Sync off if adaptive sync is active, only enable V-Sync as a fallback on non-VRR displays (Step 3).
- Set an RTSS or driver-level frame cap 3 to 5 fps below your monitor’s max refresh rate (Step 6).
- Keep GPU drivers current through the NVIDIA app or AMD Software’s built-in updater (Step 7).
- Leave Hardware-Accelerated GPU Scheduling on unless you’ve confirmed it causes stutter on your specific hardware (Step 8).
Save this as a driver profile per game where the software allows it, so a fresh Windows install or a new GPU doesn’t mean redoing every step from scratch. NVIDIA app profiles and AMD Adrenalin per-game profiles both export to a file you can back up.
You can also script a quick end-to-end verification after applying every step above, confirming the display is running at the expected resolution and refresh rate and that Hardware-Accelerated GPU Scheduling is in the state you intended, before you launch a game to do the visual TestUFO check from Step 1.
# Quick post-setup verification from an elevated PowerShell prompt
$display = Get-CimInstance -ClassName Win32_VideoController | Select-Object Name, CurrentRefreshRate
$hags = Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\GraphicsDrivers" -Name "HwSchMode" -ErrorAction SilentlyContinue
Write-Output "Active display mode:"
$display | Format-Table -AutoSize
Write-Output "HAGS state (2=on, 1=off):" $hags.HwSchModeReal 2026 Monitor Examples With Verified VRR Ranges
Knowing your specific panel’s certified VRR window matters more than knowing its headline refresh rate, because tearing at the edges of that window is normal, expected behavior rather than a bug to chase. A monitor rated “48-165Hz FreeSync Premium,” for example, will still tear below 48fps unless it also supports low-framerate compensation, since that’s simply outside the range the panel was built to stretch across. RTINGS’ refresh rate testing is a useful independent reference if your monitor’s box or product page doesn’t clearly list the actual VRR floor and ceiling, since manufacturer marketing sometimes only quotes the top number. Samsung’s lineup illustrates how fast this list moves: the company confirmed in February 2026 that its 2026 OLED TVs and monitors, including the S95H, S90H, S85H, and Odyssey G6 models (G60H and G61SH), are G-SYNC Compatible, and by August 2026 the newest Odyssey G6 shipped supporting both FreeSync Premium Pro and G-SYNC Compatible out of the box, covering the newest tear-free display tier from a single panel.
| Panel Type (2026) | Typical VRR Range | Tearing Risk Outside Range |
|---|---|---|
| Budget 1080p IPS, 75-100Hz | 48-100Hz FreeSync | High below 48fps without low-framerate compensation |
| Mid-range 1440p IPS, 144-165Hz | 48-165Hz FreeSync Premium / G-Sync Compatible | Moderate, most have LFC to smooth the low end |
| High-refresh esports IPS/TN, 240-280Hz | 1-240Hz or 1-280Hz G-Sync / FreeSync Premium Pro | Low across nearly the full range on flagship models |
| 4K OLED gaming panel, 240-360Hz | 48-240Hz or 20-360Hz, model-dependent | Low within range, OLED controllers are tightly tuned and rarely accept unofficial overclocks beyond it |
| Handheld OLED (Steam Deck OLED, ROG Ally X-class), 90-120Hz | 45-90Hz or 48-120Hz via Gamescope/driver VRR | Low when VRR is enabled system-side, higher if the in-app frame cap exceeds the panel’s ceiling |
On Linux desktops outside SteamOS, such as a Bazzite or Nobara gaming install, VRR support depends on the compositor and kernel version rather than a single driver toggle. Wayland sessions on a current kernel with Mutter (GNOME) or KWin (KDE Plasma) generally support VRR natively, and you can confirm it’s active from a terminal without opening any settings menu.
# Check whether variable refresh rate is exposed and active on a Linux desktop (X11)
xrandr --verbose | grep -A2 "connected primary" | grep -i "vrr\|Variable"
# On Wayland with GNOME, check the current session's VRR state
gsettings get org.gnome.mutter experimental-features
# On KDE Plasma (Wayland), query the active output's adaptive sync status
kscreen-doctor -o | grep -i "vrr\|adaptive"If VRR shows as unsupported on Linux despite your monitor and GPU both supporting it on Windows, check that you’re running a Wayland session rather than X11, since X11’s VRR support is inconsistent across GPU vendors, and update your kernel and Mesa (for AMD/Intel) or NVIDIA driver package to the latest version your distro offers.
Common Pitfalls When Fixing Screen Tearing
- Stacking multiple sync methods at once. Enabling V-Sync in the game, the driver, and Windows simultaneously adds input lag without fixing anything the driver-level toggle didn’t already fix on its own.
- Forgetting the monitor-side FreeSync toggle. AMD’s driver setting does nothing if the monitor’s own on-screen menu still has Adaptive-Sync or FreeSync switched off.
- Testing with the wrong content. Slow-moving menus and static UI won’t reveal tearing. Always test with fast horizontal motion, ideally TestUFO or a real game with camera panning.
- Using an uncertified cable at high bandwidth. A cable that “fits” the port physically doesn’t guarantee it carries the full signal a 4K/144Hz+ or 4K/240Hz+ setup needs.
- Applying a frame cap above your refresh rate instead of below it. A 144fps cap on a 144Hz display still allows frames to occasionally arrive mid-scan. Capping a few frames under gives the sync window breathing room.
- Chasing driver settings when the real problem is the game’s exclusive fullscreen mode. Some titles handle adaptive sync differently in borderless vs. exclusive fullscreen, so if a fix works in one game but not another, check that setting first.
Troubleshooting Screen Tearing Issues
| Symptom | Likely Cause | Fix |
|---|---|---|
| Tearing only in one specific game | Game-specific V-Sync or fullscreen mode setting overriding the driver | Check the game’s own display settings first, disable in-game V-Sync if driver-level sync is already active |
| G-Sync toggle is grayed out | Monitor connected via an unsupported port or an uncertified cable | Switch to a DisplayPort connection and a certified cable, then recheck the toggle |
| FreeSync works in some games but not others | Per-application VRR setting disabled, or exclusive fullscreen required by that engine | Enable “windowed and full screen mode” support in the driver’s sync settings |
| Tearing appears only after a Windows update | Windows Update reset the refresh rate or reinstalled a generic display driver | Reapply your refresh rate in Display Settings and reinstall the GPU vendor’s driver |
| Screen goes black after a CRU change | The new custom timing exceeded what the monitor or cable can handle | Wait 15 seconds for auto-revert, or boot into Safe Mode and run CRU’s reset.exe |
| Tearing on a laptop but not when docked | Game running on integrated GPU instead of the discrete GPU | Force the game to the discrete GPU under Windows Graphics settings |
| Frame cap in RTSS doesn’t seem to apply | RTSS profile set to a different executable, or Vulkan/DX12 hook not loading | Confirm the correct .exe is targeted and that RTSS’s “Application detection level” is set to High |
| Tearing only in Steam Deck Desktop Mode | KDE Plasma compositor tearing allowance enabled | Disable “Allow tearing” under System Settings, Display and Monitor, Compositor |
| Intermittent tearing that comes and goes | Cable or port bandwidth limit under sustained high-bitrate signal | Swap to a shorter, certified DisplayPort 1.4/2.1 or HDMI 2.1 cable and try a different GPU port |
Advanced Tips for Competitive and High-Refresh Gaming
Competitive players chasing the lowest possible input lag at 240Hz and 360Hz often skip V-Sync entirely and rely purely on a tight frame cap paired with G-Sync or FreeSync, since that combination avoids the buffering delay V-Sync can introduce even in its lowest-latency modes. NVIDIA’s Reflex and AMD’s Anti-Lag 2 technologies, both available as in-game toggles in most 2026 competitive titles, work alongside this setup by reducing the render queue depth further, and they stack well with a frame cap set 3fps below your refresh rate rather than the 5fps margin recommended for general use.
For multi-monitor setups, be aware that VRR only applies to the display it’s configured for. If you run a game across a single ultrawide but keep a second monitor active for chat or streaming software, confirm the second display isn’t set as the primary output in Windows, since some games query the primary display’s refresh rate for their internal frame pacing even when rendering on a different monitor.
Finally, if you’re troubleshooting a brand-new GPU alongside an older monitor, check whether the panel’s firmware has a pending update. Monitor manufacturers occasionally ship firmware updates that expand or correct the VRR range reported to the GPU, and a panel advertised as “48-165Hz FreeSync” can sometimes report an inaccurate lower bound to the driver until it’s updated, which shows up as tearing specifically at low frame rates during less demanding scenes.
Frequently Asked Questions
Does screen tearing damage my monitor or GPU?
No. Tearing is a visual artifact caused by frame timing, not a hardware fault, and it carries no risk of damage. It’s purely a synchronization issue between the GPU’s output and the display’s draw cycle.
Is G-Sync or FreeSync better for fixing tearing?
Both solve tearing the same way, by making the refresh rate variable. G-Sync requires an NVIDIA GPU and either a certified G-Sync module or G-Sync Compatible validation. FreeSync works with both AMD and NVIDIA GPUs on FreeSync-certified monitors, since it’s based on the open VESA Adaptive-Sync standard. If your monitor supports both labels, either works equally well for eliminating tearing.
Should I cap my frame rate even if I have G-Sync or FreeSync?
Yes. Adaptive sync only covers the range between the display’s minimum and maximum refresh rate. Frame rates above that maximum still cause tearing, so a small frame cap below your refresh rate keeps every frame inside the sync window.
Why does V-Sync sometimes cause more lag than it fixes?
Traditional V-Sync buffers a completed frame and holds it until the display is ready, which adds a delay equal to roughly one frame at your refresh rate. On a 60Hz display that’s up to 16.7ms of extra input lag, which is noticeable in fast-paced games. This is why adaptive sync (G-Sync/FreeSync) plus a frame cap is preferred over V-Sync wherever the hardware supports it.
Can screen tearing happen on a TV instead of a monitor?
Yes, and it’s actually more common on TVs used as gaming displays, because many TVs process the incoming signal through additional processing stages (motion smoothing, upscaling) that add latency and can desync frame delivery. Enabling the TV’s Game Mode, which bypasses most of that processing, resolves the majority of TV-related tearing.
Does screen tearing affect console gaming the same way?
Consoles use the same underlying principle, but with less user-facing control. Current-generation consoles support VRR over HDMI 2.1 when both the console and the TV support it, and enabling VRR in the console’s display settings fixes tearing the same way FreeSync or G-Sync does on PC.
Why does tearing appear only when I’m streaming or recording gameplay?
Capture software adds a second consumer of every rendered frame, and if it’s not properly synchronized with the game’s own frame delivery, it can reveal tearing that wasn’t visible on the primary display, or introduce new tearing in the recorded output specifically. Disabling Windows Game Mode or switching your capture software’s hook method, if it offers more than one, often resolves this.
Is Custom Resolution Utility safe to use?
It’s safe when used carefully and incrementally, one Hz at a time, with testing between each change. CRU edits how your GPU driver interprets the display’s timing, not the monitor’s own firmware, so a bad setting is reversible through Windows’ automatic revert or the tool’s own reset function. It carries more risk than the driver-level toggles earlier in this guide, which is why it’s listed as an advanced, optional step.
Why does my frame rate cap sometimes get ignored after a game update?
Game patches occasionally reset internal engine settings, including any built-in frame limiter, back to their defaults. If you rely on the in-game cap rather than RTSS or a driver-level limiter, check it after every major patch. Setting the cap in RTSS or your GPU vendor’s software instead avoids this, since those tools apply the limit outside the game’s own settings file.
Do I need adaptive sync if I already have a very fast GPU?
Not strictly, if you can hold a rock-steady frame rate above your monitor’s refresh rate and keep V-Sync on, but that’s a narrow, demanding condition to maintain across every scene in every game. A frame cap plus G-Sync or FreeSync is more forgiving, because it stays tear-free through the frame rate dips that even a high-end GPU has during demanding scenes, explosions, or dense crowds.
