Most gaming monitors ship with more refresh rate hiding inside the panel than the box admits. A 144Hz screen will often run cleanly at 165Hz or higher once you stop letting the factory spec sheet cap it, and the ceiling keeps climbing: LG’s UltraGear 25G590B, a 25-inch FHD IPS panel that launched at $999 in August 2026, ships with a native 1000Hz refresh rate and an officially rated 1100Hz overclocked mode — what LG calls the world’s first native 1000Hz gaming monitor. That process is called monitor overclocking, and unlike most hardware tuning, it costs nothing beyond about 45 minutes of careful testing.
Overclocking a monitor doesn’t touch voltage or thermal limits the way GPU or RAM overclocking does. You’re not pushing silicon past its rated speed, you’re unlocking a refresh rate the panel could likely already handle but the manufacturer never validated or advertised. That distinction is why the process is comparatively low-risk, and why it deserves its own guide alongside our existing walkthroughs for overclocking RAM and overclocking a GPU.
This tutorial covers how to overclock a monitor safely in 2026 using the built-in Nvidia Control Panel and AMD Software Adrenalin tools, using ToastyX’s CRU (Custom Resolution Utility) for any GPU including Intel, verifying the result is actually stable rather than just “selected” in a menu, and knowing exactly when to stop. Tech Insider’s own July 2026 tutorial timed the full process at roughly 45 minutes across the 13 steps laid out below, and that’s the pace this guide follows. By the end, you’ll have a tested, documented refresh rate ceiling for your specific monitor, plus a troubleshooting reference for when a step doesn’t go as planned.
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 Is Monitor Overclocking, and Why Bother in 2026?
A monitor’s refresh rate is how many times per second it redraws the image, measured in hertz (Hz). A 60Hz panel redraws 60 times a second; a 165Hz panel redraws 165 times. Higher refresh rates make fast motion look smoother and can shave a few milliseconds off the delay between an input and the frame that shows it, which is why competitive shooters, fighting games, and racing titles benefit the most from chasing extra Hz.
Monitor overclocking pushes that number past whatever is printed on the box, using software instead of any hardware modification. The reason there’s headroom to find at all comes down to how panels are validated. A manufacturer buys a batch of display panels rated for, say, 144Hz, tests them at that speed, and ships them labeled 144Hz. Many of those same panels would run cleanly at 155Hz or 165Hz, but validating and marketing a higher number costs money and risks returns from the small percentage of units that can’t handle it. So vendors pick a conservative, guaranteed number and stop there. That gap between “guaranteed” and “actually capable” is exactly what Nvidia’s control tools, AMD Software Adrenalin, and CRU exploit.
The 2026 monitor market makes this a slightly different conversation than it was a few years ago. Flagship esports panels have pushed refresh rates to extremes: TFTCentral’s 2026 recommended gaming monitor roundup lists the 24-inch Asus ROG Strix Ace XG248QSG at 610Hz and the BenQ Zowie XL2586X+ at 600Hz, while 27-inch 1440p OLED panels such as the Asus ROG Swift PG27AQDP now reach 480Hz. Asus itself kept pushing through the summer, previewing a 27-inch 4K OLED in August 2026 that runs natively at 240Hz but adds QHD and FHD overclocked modes rated at 400Hz and 488Hz respectively, alongside a 24.5-inch OLED shown the same month with a native 720Hz refresh rate and a 0.02ms response time. Even 4K OLED gaming monitors are catching up: PCWorld’s 2026 gaming monitor coverage notes a 26.5-inch 4K OLED panel running at 240Hz out of the box, TechTimes’ June 2026 review clocked the Asus ROG Strix OLED XG34WCDMTG at 240Hz with a 0.03ms response time, and Engadget covered the ViewSonic VX2738 2K OLED hitting that same 240Hz/0.03ms combination when it showed at CES 2026. Rtings’ July 2026 rankings now put the Asus ROG Swift OLED PG32UCDM Gen3 at the top of its 240Hz OLED picks, a verdict OfZenAndComputing’s July 2026 update echoes by naming the PG32UCDM the best 2026 4K OLED gaming monitor outright.
If you’re shopping in 2026, you can often buy your way to a higher native refresh rate outright. That doesn’t make overclocking pointless, though. Most gaming monitors in active use today aren’t this year’s flagship; they’re 60Hz, 75Hz, 144Hz, or 165Hz panels bought over the last several years, and a free 10 to 30Hz bump costs nothing but the time it takes to test it properly. It’s also a useful diagnostic before you spend money: if your current monitor overclocks cleanly to 180Hz, you may not need to upgrade at all this year.
The performance case for chasing extra Hz is measurable, not just a feeling. Refresh rate and input lag are closely linked, since a monitor generally can’t display a frame faster than it redraws the panel. Our own testing on the gaming monitor vs TV comparison measured 5.5ms of input lag on a dedicated gaming monitor against 6.8ms on a TV in game mode — a gap that’s driven in large part by refresh rate and processing overhead. Overclocking doesn’t change your panel’s underlying response time (the pixel transition speed is a hardware property CRU can’t touch), but a higher, verified-stable Hz does reduce the theoretical minimum delay between a frame being rendered and it appearing on screen, and it makes fast camera movement look noticeably less smeared. That’s the entire value proposition in one sentence: smoother motion and a small, real latency improvement, in exchange for about 45 minutes of testing.
Prerequisites: What You Need Before You Start
Monitor overclocking is a Windows-centric process. macOS offers essentially no user-facing custom resolution support for this, and Linux users need a different tool chain built around xrandr rather than CRU. Everything below assumes Windows 10 (version 2004 or later) or Windows 11.
- Operating system: Windows 10 (2004+) or Windows 11. CRU, Nvidia Control Panel, and AMD Software Adrenalin all assume a current Windows display driver stack.
- GPU driver: the latest WHQL-certified driver for your card — current guidance points to NVIDIA driver 595.76 or later, or the newest AMD Adrenalin build. Older drivers occasionally reject custom resolutions that newer ones accept.
- Cable and port: DisplayPort 1.4 or newer, or HDMI 2.1, rated for the resolution and Hz combination you’re targeting. We cover exactly how much bandwidth each standard provides further down.
- CRU (Custom Resolution Utility): free, portable, no installer required, distributed by developer ToastyX through the Monitor Tests forum.
- A verification tool: Blur Busters’ free browser-based TestUFO frame-skipping test, and optionally a longer stress test loop such as Unigine Heaven or 3DMark.
- 15 to 45 minutes uninterrupted, plus a phone or second device on hand in case you need to look up recovery steps with the monitor temporarily blank.
- Your exact monitor model number and native panel specs (resolution, factory-rated refresh rate, panel type) noted down before you touch a single setting.
One more thing worth setting expectations on: this guide is specifically about refresh rate overclocking, not GPU core/memory overclocking. If you also want to push clock speeds on an Nvidia or AMD card, that’s a separate process covered in our MSI Afterburner overclocking guide.
How Much Extra Refresh Rate Can You Realistically Expect?
Results vary by individual panel, not just by model, so treat every number below as a community-reported range rather than a guarantee. A support guide from monitor maker KTC puts it plainly when describing the standard workflow.
In the NVIDIA Control Panel or AMD Software, create a custom resolution and incrementally raise the refresh rate by 1 Hz at a time.
KTC Play, Safe Monitor Overclocking Guide — ktcplay.com
That cautious, incremental approach is exactly why headroom is expressed as a range rather than a fixed number. Here’s what to expect based on where your panel currently sits.
| Native Refresh Rate | Common Panel Types | Typical Reported Ceiling | Notes |
|---|---|---|---|
| 60Hz | TN, VA, IPS | 75–100Hz | The most common overclock target; usually the easiest and most noticeable win |
| 75Hz | IPS, VA | 85–100Hz | Smaller absolute jump but still improves motion clarity |
| 100Hz | IPS, VA | 110–120Hz | Diminishing returns start to show up here |
| 144Hz | IPS, TN | 165–180Hz | The classic “sweet spot” overclock most guides reference |
| 165Hz | IPS, Fast VA | 180–200Hz | Cable and port bandwidth start to matter as much as the panel itself |
| 240Hz | TN, Fast IPS, OLED | 245–260Hz | Minimal headroom left; the panel is already close to its real ceiling |
| 480Hz+ (2026 flagship) | OLED, TN | Little to none | Vendors already validate close to the panel’s true limit at this tier |
Notice the pattern: the lower your starting Hz, the more room you typically have, both in absolute terms and as a percentage. That said, headroom doesn’t disappear entirely at the high end — a May 2025 KitGuru review documented a Philips Evnia gaming monitor overclocking from 360Hz to 390Hz through its own OSD menu, and a May 2025 YouTube buyer’s guide highlighted a 240Hz esports monitor pushed to 360Hz using the same kind of incremental approach. Manufacturers are now publishing their own overclock headroom out of the box, too: Philips’ 27M2N5500X launched in July 2026 rated for 400Hz native and 425Hz overclocked, and KTC’s 24M1, announced the same month, ships at 240Hz native with a 260Hz overclocked mode built in — both a roughly 6 to 8 percent factory-sanctioned bump. That’s part of why overclocking remains relevant even as native 480Hz and 600Hz-plus panels hit the market — the installed base of 60Hz to 165Hz monitors is enormous, and that’s where most of the free performance is still sitting unclaimed.
Steps 1–3: Audit Your Cable, Port, and GPU Before You Touch Any Settings
Step 1: Confirm Your Cable and Port Support the Bandwidth You Need
Every refresh rate overclock is ultimately a bandwidth question. Higher resolution, higher Hz, and higher color depth all multiply the data rate your cable and port have to carry. A 1080p monitor has bandwidth to spare on almost any modern DisplayPort or HDMI connection, but pushing 1440p or 4K to a much higher Hz can hit the ceiling of an older DisplayPort 1.2 or HDMI 2.0 cable and port. We break down the exact numbers in the bandwidth section below — for now, just confirm you’re using the cable that shipped with the monitor (if it’s DisplayPort) or a certified high-bandwidth cable if you’re attempting a large jump.
Step 2: Update Your GPU Driver and Check DSC Support
Install the latest WHQL driver before doing anything else. You can confirm what’s currently installed, along with your active display mode, from PowerShell:
Get-CimInstance Win32_VideoController | Select-Object Name, DriverVersion, CurrentRefreshRate, CurrentHorizontalResolution, CurrentVerticalResolutionWhile you’re in there, check whether both your GPU and monitor support Display Stream Compression (DSC). DSC lets a lower-bandwidth connection carry a signal that would otherwise need more raw bandwidth than the cable technically provides, which matters a lot if you’re trying to overclock a 1440p or 4K panel rather than a 1080p one.
Step 3: Record a Stock Baseline Before Changing Anything
Run the TestUFO frame-skipping test at your current, factory-rated refresh rate and note the result. Take a screenshot of your current Windows Display Settings. This baseline is what you’ll compare against once you start pushing the Hz higher, and it’s your rollback reference if anything goes wrong later.
Steps 4–6: Overclock With Nvidia Control Panel
If you have an Nvidia GPU, this is the fastest path and doesn’t require installing anything extra.
Step 4: Open the Custom Resolution Creator
Right-click the desktop, open NVIDIA Control Panel, and go to Display > Change Resolution > Customize. Check the box for “Enable resolutions not exposed by the display,” then click Create Custom Resolution.
Step 5: Raise the Refresh Rate in Small Increments
Enter your monitor’s current resolution and timing standard, then increase only the refresh rate field. The conservative approach, and the one most safety-focused guides recommend, is 1Hz at a time — Tech Insider’s own July 2026 overclocking guidance narrows that further, recommending 1–5Hz steps specifically when working inside the Nvidia Control Panel. HowToGeek’s own guide, updated in May 2026, gives the same advice, recommending 5Hz increments specifically through NVIDIA Control Panel custom resolutions. iTechGuides’ August 2026 advice is even more cautious, suggesting you start at just 1–3Hz above your panel’s rated refresh rate before deciding how far to push. DisplayNinja’s June 2026 guide splits the difference, recommending an initial 5Hz jump followed by 1Hz steps from there. If you’d rather move faster and don’t mind re-testing more carefully near the ceiling, 5Hz steps are common in community guides too — just slow down to 1–3Hz increments once you’re within 10Hz of where problems start appearing.
Step 6: Test and Apply
Click Test. Nvidia’s tool displays the new mode and gives you roughly 15 seconds to confirm it before automatically reverting to the previous working setting — this auto-revert is your safety net, so don’t panic if the screen goes briefly blank during the test. If the image is clean, confirm the change. If it isn’t, let the countdown expire and try a smaller increment.
Steps 7–8: Overclock With AMD Software Adrenalin
Step 7: Create a Custom Resolution in Adrenalin
Open AMD Software Adrenalin, go to the Display tab, and find Custom Resolutions. Create a new entry using your monitor’s current resolution, then raise only the refresh rate field, following the same small-increment approach described above.
Step 8: Apply and Stress-Test
Save the custom resolution, select it under Windows Display Settings, and immediately run the TestUFO frame-skipping test before you trust the new number. AMD’s tool doesn’t always auto-revert as aggressively as Nvidia’s, so if the screen goes black and doesn’t recover within about 15 to 20 seconds, hold the power button for a hard reset and remove the bad entry afterward.
Steps 9–12: Overclock Any GPU (Including Intel) With CRU
CRU works regardless of GPU vendor and gives you far more granular control over the actual display timings than either Nvidia or AMD’s built-in tools. It’s also the more dependable option for Intel integrated graphics, where custom-resolution support inside Intel’s own control panel has historically been inconsistent across driver versions. Most in-depth overclocking guides, including the walkthrough on Tom’s Hardware’s community forum, default to CRU for exactly this reason. Its ceiling is also higher than most people assume: a Blur Busters forum thread from January 2026 documented manual CRU tuning pushing a Samsung OLED monitor toward a 500Hz overclock, well past anything the panel was ever marketed at.
Step 9: Download and Run CRU as Administrator
Download the current release of CRU from ToastyX’s official Monitor Tests forum thread — this is the canonical source, so avoid third-party mirrors. Extract the ZIP file, right-click CRU.exe, and choose Run as Administrator. If you have more than one display connected, use the dropdown at the top to select the correct one before making any changes.
Step 10: Add a Detailed Resolution With Your Target Refresh Rate
Under “Detailed resolutions” (not “Standard resolutions” — detailed gives you precise timing control), click Add. Enter your target refresh rate. For most first attempts, letting CRU auto-calculate standard timings is fine; once you’re pushing toward the edge of your cable’s bandwidth, switching the blanking type to CVT-RBv2 (reduced blanking) lowers the required pixel clock without changing the resolution or Hz you’re asking for. A detailed resolution entry looks roughly like this once filled in:
The distinction between “Standard” and “Detailed” resolutions inside CRU trips up a lot of first-time users, so it’s worth being explicit about it. Standard resolutions let Windows pick generic timings for you, which is fine for small, conservative bumps. Detailed resolutions expose every individual timing parameter — pixel clock, front porch, sync width, back porch — which is what lets you apply reduced-blanking math precisely instead of hoping the automatic calculation gets you close enough. If your monitor still ignores the new mode after following every step correctly, open CRU’s main window and check the “Extension blocks override” option; some panels report a limited EDID by default that CRU needs to explicitly override before it will offer refresh rates outside the factory-declared range.
Detailed resolution (illustrative example — your values will differ)
Pixel Clock: 533.250 MHz
Active Pixels: 2560 x 1440
Front Porch: 48 x 3
Sync Width: 32 x 5
Back Porch: 80 x 33
Blanking: CVT-RBv2 (reduced)
Target Refresh Rate: 172 HzStep 11: Restart the Graphics Driver With restart64.exe
Click OK to save the detailed resolution, then run the restart tool that ships in the same folder as CRU instead of rebooting the whole machine:
:: Run from the extracted CRU folder after saving your changes
:: Use restart32.exe instead if you're on a 32-bit build of Windows
restart64.exeYour screen will flash and go black for a few seconds while the driver restarts — that’s normal and not a sign of failure.
Step 12: Select the New Refresh Rate in Windows Display Settings
Go to Settings > System > Display > Advanced Display, and pick the new Hz value from the refresh rate dropdown. If it isn’t listed, the driver restart didn’t fully apply — run restart64.exe again, and if it still doesn’t show up, do a full reboot.
Step 13: Verify Your Overclock Is Actually Stable
Windows displaying “172 Hz” in the settings menu is not proof of anything — it just means the mode was accepted, not that every frame is actually landing on screen without being dropped. This is the step most rushed guides skip, and it’s the one that actually tells you whether your new number is real.
Open TestUFO’s frame-skipping test and watch the moving block for at least a minute. You can automate opening it for repeat testing with a one-line batch file:
:: Opens the Blur Busters frame-skipping test in your default browser
start https://www.testufo.com/frameskippingA clean result shows a single moving block with no duplicate or trailing ghost image. A failing result shows visible stutter, or a faint second block trailing just behind the first — that’s your monitor or GPU silently dropping frames at the new refresh rate, even though Windows reports it as working. If you see that, step back down by 5Hz and retest. For extra confidence, especially before you commit to a setting long-term, run a demanding game or a synthetic loop such as Unigine Heaven for 15 to 20 minutes with the on-screen refresh counter visible, watching for any drop back to the old number.
Complete Working Example: Taking a 144Hz Monitor to 172Hz
Here’s the entire process end to end, using one of the most common real-world cases: a 27-inch, 1440p IPS monitor factory-rated for 144Hz, connected over DisplayPort 1.4.
- Baseline recorded at 144Hz: TestUFO frame-skipping test clean, no dropped frames.
- Opened CRU, added a detailed resolution at 150Hz using standard timings. Applied with restart64.exe. TestUFO clean.
- Increased to 158Hz. Applied. TestUFO clean, no visible artifacts.
- Increased to 165Hz — the community-reported ceiling for this panel class. Applied. TestUFO clean, matched expectations from the headroom table above.
- Pushed further to 170Hz to find the real limit rather than stopping at the “expected” number. Applied. TestUFO clean.
- Pushed to 175Hz. Faint flicker appeared at the edges of the panel during fast motion, and single-pixel sparkling was visible in bright scenes — the classic sign of being past the stable ceiling.
- Backed off 1Hz at a time: 174Hz still showed occasional sparkle, 173Hz was borderline, 172Hz was completely clean across a 20-minute stress loop.
- Switched the blanking type to CVT-RBv2 at 172Hz to reduce the pixel clock and leave more DisplayPort 1.4 bandwidth headroom for stability margin, then re-verified with another full TestUFO pass.
The final, verified configuration for this specific unit ended up here:
Monitor: 27-inch 1440p IPS, factory-rated 144 Hz
Cable: DisplayPort 1.4
Method: CRU detailed resolution + restart64.exe
Tested past the point of failure: 175 Hz (edge flicker, pixel sparkle)
Stable setting applied: 172 Hz
Frame-skipping test: 0% dropped frames over a 20-minute loopThat’s a 28Hz gain, roughly 19% over the factory rating, for zero additional hardware cost. Your own ceiling will land somewhere else depending on the individual panel, the cable in your hand, and which GPU is driving it — but this is the exact repeatable process to find it.
DisplayPort vs HDMI Bandwidth and DSC: Your Real Ceiling
At lower resolutions, the panel itself is usually the limiting factor. At 1440p and especially 4K, the cable and port frequently become the limit first, before the panel electronics even get tested. DisplayPort 2.1’s UHBR20 mode is changing that math for the newest panels: Tech Insider’s own July 2026 guide notes that its 80Gbps of raw bandwidth is enough to enable 4K overclocks at 240Hz and beyond, and KTC’s May 2026 safe-overclocking guide goes further, stating that HDMI and DP 2.1 ceilings now let many 1440p panels reach 360Hz in practice. Firmware plays a role here too — Acer’s Predator X27U picked up firmware v1.07 back in March 2025, and a guide published in June 2026 by Alibaba Electronics confirms that update is what unlocks the full 240Hz over HDMI 2.1b on that panel, rather than the port’s raw bandwidth alone doing the work. Gigabyte’s own support documentation for the MO27Q28GR OLED, updated in February 2026, adds a practical wrinkle: its firmware-based refresh tools require a single USB cable connected directly to the monitor before the higher timings will apply. Here’s how much headroom each current standard actually provides.
| Standard | Raw Bandwidth | Effective Throughput | Typical Practical Ceiling |
|---|---|---|---|
| DisplayPort 1.2 | 21.6 Gbps | ~17.28 Gbps | 1440p at 144Hz, 8-bit color |
| DisplayPort 1.4 | 32.4 Gbps | ~25.9 Gbps | 4K at 120Hz, or 1440p well past 240Hz, without DSC |
| DisplayPort 1.4 with DSC | 32.4 Gbps (compressed stream) | Effectively much higher | 4K at 144–240Hz using visually lossless compression |
| DisplayPort 2.1 (UHBR20) | 80 Gbps | ~77.4 Gbps | 4K at 240Hz or higher without needing DSC |
| HDMI 2.0 | 18 Gbps | ~14.4 Gbps | 4K at 60Hz, or 1440p at 144Hz |
| HDMI 2.1 | 48 Gbps | ~42.6 Gbps (FRL) | 4K at 120Hz, or 1440p well past 240Hz |
Display Stream Compression (DSC) is the detail most overclocking guides gloss over. It’s a visually lossless compression scheme, standardized by VESA, that lets a connection carry a signal that would otherwise exceed its raw bandwidth. If both your GPU and monitor support DSC over the cable you’re using, a refresh rate that looks mathematically impossible on paper can still work in practice. If either end doesn’t support it, you’re limited to the raw, uncompressed bandwidth figures in the table above — which is exactly why the same overclock might work perfectly on one PC and fail immediately on another using nominally similar hardware. Adapters are catching up too: Cable Matters shipped firmware 7.02.120 for its 8K HDMI-to-DisplayPort adapters in July 2026, and the update enables VRR passthrough across four adapter models that previously blocked variable refresh entirely — worth checking if your overclocked signal is routing through one of them.
The other lever, as mentioned in Step 10, is reduced blanking. Standard timings include padding around the active image that made sense for old CRT electronics but serves no purpose on a modern LCD or OLED panel. CVT-RBv2 strips most of that padding out, which lowers the pixel clock required for a given resolution and refresh rate, in turn easing the load on your cable and port without changing anything you actually see on screen. The gains from getting this right can be substantial on newer connections — KTC’s May 2026 guidance puts it directly, stating that DisplayPort 2.1 can carry a 1440p signal from 240Hz up to 360Hz once you’re using CVT-RBv2 timings instead of standard ones.
Cable labeling is worth a specific warning here, because it’s the single most common reason an otherwise correct overclock fails. Not every cable sold as “DisplayPort” or “HDMI” actually supports the full bandwidth its connector shape implies — a lot of budget cables are built to the minimum spec for their connector, not the maximum. Look for explicit certification language such as “DisplayPort 1.4 certified” or “Ultra High Speed HDMI” (the official label for HDMI 2.1-rated cables) rather than assuming any cable with the right plug will do. If a mode fails at the port and driver level but the math in the table above says it should work, swapping the cable first is faster than troubleshooting anything in CRU.
5 Common Pitfalls When Overclocking a Monitor
- Jumping in large increments instead of small steps. Going straight from 144Hz to 180Hz skips right past the point where problems first appear, so you never actually learn where your real, stable ceiling is — you just find out where it fails completely.
- Not checking cable and port bandwidth first. It’s easy to blame “a bad panel” when the real bottleneck is an old HDMI 2.0 cable that shipped in the box five years ago. Rule out the cable before you conclude the monitor itself won’t overclock.
- Trusting the Windows refresh rate readout instead of running an actual test. As covered in Step 13, the display settings menu will happily report a number that isn’t holding up frame by frame. Always confirm with TestUFO or a similar frame-skipping test.
- Skipping the recovery plan. Before applying any untested mode, know how you’ll recover if the screen goes blank and doesn’t come back — whether that’s CRU’s auto-revert, a second monitor to fix settings from, or Safe Mode.
- Ignoring what the overclock does to your VRR range. G-Sync and FreeSync ranges are calibrated against the display’s original certified maximum. Changing your fixed refresh rate without checking variable refresh behavior afterward can produce stutter that has nothing to do with the overclock itself being unstable.
- Applying the same process to a laptop’s built-in panel. External monitor logic doesn’t always transfer. Many embedded laptop displays are locked at the firmware or embedded DisplayPort level and will simply ignore a custom resolution CRU sends them.
Troubleshooting: 9 Problems You’ll Actually Run Into
These cover the vast majority of issues reported across CRU’s own documentation, Blur Busters’ forums, and community overclocking guides.
| Problem | Likely Cause | Fix |
|---|---|---|
| Screen goes black or shows “no signal” right after applying a custom mode | The display couldn’t sync to the new timing | Wait about 15 seconds for Windows or Nvidia to auto-revert; if it doesn’t, reboot and remove the bad entry in CRU |
| New refresh rate doesn’t appear in Windows or in-game settings | The driver was never restarted after the CRU change | Run restart64.exe (or restart32.exe) again, or do a full reboot |
| Screen flickers or shows faint horizontal lines at the new Hz | You’re past the panel’s real stability ceiling | Drop the refresh rate by 5Hz, then step down by 1Hz until the flicker stops |
| CRU changes don’t persist after a reboot | The detailed resolution wasn’t saved correctly, or a driver update reset it | Reopen CRU, re-add the detailed resolution, and re-run restart64.exe |
| Refresh rate silently reverts to the factory number after a Windows update | Windows Update reset or replaced the GPU driver | Reapply the CRU or GPU-panel custom resolution after any major Windows update |
| Overclock works at 1080p but fails at 1440p or 4K on the same monitor | You’ve hit a cable or port bandwidth ceiling, not a panel limit | Use a certified DisplayPort 1.4/2.1 or HDMI 2.1 cable, enable DSC if both ends support it, or switch to CVT-RBv2 timings |
| G-Sync or FreeSync stops working correctly after the overclock | The variable refresh rate range is tied to the display’s original certified maximum | Manually update the VRR range in CRU or in the GPU driver’s adaptive sync settings |
| Random single-pixel sparkling or dots appear at the new Hz | Early warning sign that you’re right at the edge of a stable ceiling | Back off 1–2Hz immediately — this is the most common early symptom, not a sign of damage |
| A laptop’s built-in display ignores the custom resolution entirely | Many embedded panels are locked at the firmware or embedded DisplayPort level | Accept the native refresh rate, or look for a manufacturer-specific overclocking utility for that exact model |
Advanced Tips: Getting the Last Few Hz Safely
Once the basic process is working, a few refinements separate a “good enough” overclock from one that’s actually squeezed as far as the hardware allows.
Use CVT-RBv2 whenever you’re bandwidth-constrained. The difference in required pixel clock can be the deciding factor between a mode that works and one that doesn’t, especially at 1440p and 4K:
Standard timing at 1440p / 172 Hz: pixel clock approx. 600 MHz (tight against DP 1.4 headroom)
CVT-RBv2 reduced blanking at 1440p / 172 Hz: pixel clock approx. 533 MHz (comfortable margin within DP 1.4)Watch for per-application refresh rate overrides. Some games and launchers force their own refresh rate on startup regardless of your Windows default, which can make a perfectly stable overclock look broken inside one specific title. Check the game’s display settings before assuming the overclock itself failed.
Recalibrate your VRR range after settling on a final Hz. G-Sync and FreeSync ranges are typically anchored to the panel’s original certified maximum. After a successful overclock, revisit the adaptive sync settings in CRU or your GPU driver so the top of the VRR window matches your new ceiling rather than the old factory number. On Linux, ArchWiki’s July 2026 documentation covers the equivalent move in more depth, walking through an EDID override that extends the FreeSync range on a DP-2 port so variable refresh keeps working past the display’s original certified ceiling — the same underlying idea as the Windows-side VRR recalibration described here.
Treat every panel as its own silicon lottery result. Two identical monitor models, even from the same batch, can land on different stable ceilings. If you’re overclocking a multi-monitor setup, verify each display independently with its own TestUFO pass rather than assuming one result applies to both.
Compare against strobe backlight modes if motion clarity, not raw Hz, is the actual goal. Blur Busters’ own testing has found that strobe backlight technology, such as LightBoost, can produce noticeably less motion blur than a 180Hz overclock delivers on its own. If your real objective is the clearest possible motion rather than the highest number, it’s worth testing your monitor’s strobe mode before — or alongside — an Hz overclock.
Don’t expect the same results on gaming handhelds and gaming laptops. Devices like the Steam Deck, ROG Ally, and Legion Go use integrated panels driven over an embedded interface rather than external DisplayPort or HDMI, and most ship with the refresh rate ceiling already tuned close to what the panel and battery budget can sustain. A handful of handhelds expose a refresh-rate override in their own first-party software rather than through CRU, so check the manufacturer’s settings app before assuming CRU is the right tool for a handheld or laptop screen — treat external monitors and built-in panels as two separate problems with two different toolsets.
Is Monitor Overclocking Safe? Risks and Warranty Reality
Compared with GPU or RAM overclocking, this is a genuinely low-risk process. You aren’t increasing voltage or current draw, which is the mechanism that creates real risk of hardware degradation in other types of overclocking. You’re asking the panel to accept a faster timing than the one it shipped validated for, and the realistic failure mode is a blank screen or visible artifacts that clear up the moment you back off the setting, not permanent damage.
That said, “low-risk” isn’t “zero-risk,” and it’s worth being precise about where the actual risk sits:
- Warranty: most manufacturers don’t have a technical way to detect that you overclocked the refresh rate, since it’s a Windows-side display mode setting rather than a firmware change. Still, policies vary by manufacturer. If you ever need warranty service, revert to the factory refresh rate first to avoid it complicating an unrelated diagnosis.
- Data safety: there’s no risk to files or the OS itself. Worst case, you’re looking at a blank screen you need to recover from, not data loss.
- When to actually stop: flickering, horizontal lines, inverse ghosting, or random black screens are your signal to back off immediately rather than push through them. None of these are “push past it and it’ll be fine” situations.
As one community walkthrough on Tom’s Hardware’s forum puts it, the actual mechanics of applying a new setting can be as simple as changing a number and clicking OK — it’s the testing and verification around that single click that determines whether the result is safe and repeatable. Independent coverage from outlets including How-To Geek, DisplayNinja, and Digital Trends all converge on the same core guidance: move in small increments, verify with a real test, and stop the moment you see artifacts.
Frequently Asked Questions
Does overclocking a monitor void the warranty?
Most manufacturers don’t explicitly void the warranty over refresh-rate overclocking, since it’s a software-side timing change rather than a hardware or firmware modification. Policies still vary, so if you ever need warranty service, revert to the factory settings first to keep the diagnosis simple.
Can monitor overclocking damage my display?
It’s considered low-risk compared with GPU or RAM overclocking because you aren’t raising voltage or current. The realistic failure mode is a blank screen or visible artifacts that clear up as soon as you lower the refresh rate again, not permanent hardware damage. Start conservative and increase gradually regardless.
How much can I really overclock my monitor?
It depends heavily on your individual panel, not just the model name. Community-reported ranges suggest 60Hz panels often reach 75–100Hz, 144Hz panels often land around 165–180Hz, and 165Hz panels may reach 180–200Hz — but treat these as starting expectations, not guarantees, since results vary by unit, cable, and GPU. Even at the flagship end, manufacturers are now baking a similar margin in from the factory: LG’s $999 UltraGear 25G590B, launched in August 2026 with Motion Blur Reduction Pro, ships with a native 1000Hz refresh rate and an official 1100Hz overclocked mode — a roughly 10 percent factory-sanctioned bump that mirrors the percentages regular panels see in community testing.
Does every monitor support overclocking?
No. Some panel and firmware combinations simply reject any refresh rate outside their advertised range. Laptop-integrated panels are especially likely to ignore custom resolutions, since they’re often driven over embedded DisplayPort with limits set at the firmware level.
Is CRU safe to download and use?
CRU is a long-established, widely used freeware tool from developer ToastyX, distributed through the Monitor Tests forum. It’s portable, requires no installation, and doesn’t modify anything beyond Windows’ own display mode list — which is exactly why the bundled restart64.exe tool can undo changes without needing a driver reinstall.
Why did my screen go black after I applied a custom resolution?
The display couldn’t sync to the new timing. Windows and Nvidia’s built-in custom resolution tool auto-revert after roughly 15 seconds if you don’t confirm the mode. With CRU, if it doesn’t revert automatically, boot into Safe Mode or connect a second monitor to remove the problematic entry.
Do I need a new cable to overclock my monitor?
Only if you’re bandwidth-limited. A 1080p monitor has spare capacity on almost any current DisplayPort or HDMI cable. Pushing 1440p or 4K to a much higher Hz can hit the ceiling of an older DisplayPort 1.2 or HDMI 2.0 connection, in which case a DisplayPort 1.4, DisplayPort 2.1, or HDMI 2.1-rated cable and port removes that bottleneck.
Nvidia Control Panel, AMD Software, or CRU — which should I use?
Nvidia Control Panel and AMD Software Adrenalin are the fastest options if you’re only chasing a modest bump and want to stay inside a simple GUI. CRU gives more granular control over the underlying timings, which matters for reduced-blanking modes, and it works identically across Nvidia, AMD, and Intel — which is why most in-depth guides default to it.
Will overclocking my monitor improve my FPS in games?
No. Refresh rate overclocking changes how often the display can redraw the image, not how many frames your GPU renders per second. If your GPU is already producing more frames than your factory refresh rate can show, a higher Hz lets you see more of that existing performance — but it won’t make a GPU-bound game render faster on its own. Pair it with your GPU’s own headroom, covered in our GPU overclocking guide, if you’re also frame-rate limited.
What’s the difference between monitor overclocking and GPU overclocking?
They target completely different bottlenecks. GPU overclocking, covered in our MSI Afterburner guide, raises core and memory clocks to render more frames per second, and it does involve real voltage and thermal considerations. Monitor overclocking only changes how fast the display refreshes what it’s shown; it doesn’t touch the GPU at all and carries none of the thermal or power-delivery risk that comes with silicon-level overclocking.
Related Coverage
- How to Overclock RAM: 10 Steps, 90 Min [2026]
- How to Overclock a GPU: 12 Steps, 60 Min [2026]
- MSI Afterburner: Overclock GPU in 12 Steps, 30 Min [2026]
- Ryzen Master: Undervolt Your CPU in 12 Steps, 40 Min [2026]
- Gaming Monitor vs TV 2026: 5.5ms vs 6.8ms Input Lag [Tested]
- How to Build a Gaming PC in 12 Steps, 90 Min [2026]
- More hardware coverage
