⏱ 12 min read  ·  ✅ Updated Oct 2026

If you want to overclock 120Hz monitor to 144Hz, first determine whether 144Hz is already a supported mode. A connection or setting may be holding the display at 120Hz. A genuinely 120Hz-limited monitor may reject 144Hz or accept the signal while skipping frames. This guide explains how to identify your situation, attempt a controlled increase when appropriate, verify the result, and recover if the picture disappears.

Can you overclock 120Hz monitor to 144Hz?

Sometimes, but there is no universal setting that makes every 120Hz panel operate correctly at 144Hz. The monitor, its input electronics, the graphics output, and the connection must all accommodate the requested mode.

Start by separating three situations:

What you discover What it means Appropriate next step
The manual lists 144Hz at your resolution and input Your display is running below a supported mode Fix the connection or select 144Hz normally
The manual documents an overclock mode reaching 144Hz Higher refresh requires a manufacturer-provided setting Follow that exact model’s instructions
The manual specifies a 120Hz maximum without a higher mode A 144Hz custom timing exceeds the documented specification Keep 120Hz or accept the risks of an unsupported experiment

A fourth possibility is that 120Hz is itself the monitor’s advertised overclock ceiling. Do not assume that an already overclocked display has another 24Hz available.

NVIDIA warns that operation beyond the display manufacturer’s advertised specifications can cause permanent damage and may void warranty coverage. A successful driver test does not cancel that warning or establish long-term reliability.

The procedure below assumes a Windows 11 PC and an external monitor. Internal laptop panels require separate OEM guidance; the presence of a gaming GPU does not establish that the built-in screen supports custom refresh rates.

Understand what the extra 24Hz can deliver

The move from 120Hz to 144Hz increases refresh frequency by 20%. The time between refreshes falls from approximately 8.33 milliseconds to 6.94 milliseconds, a difference of about 1.39 milliseconds.

Those numbers describe refresh intervals, calculated as 1,000 divided by refresh rate. They are not measured end-to-end input latency, pixel response times, or guaranteed gaming improvements.

Refresh rate Calculated time per refresh Increase over 120Hz
120Hz 8.33 ms Baseline
125Hz 8.00 ms About 4.2%
130Hz 7.69 ms About 8.3%
144Hz 6.94 ms 20%

These intermediate rates are mathematical examples, not promised supported modes.

Changing the display timing also does not make the GPU render more frames. If a game struggles to maintain 80 frames per second, selecting 144Hz will not make it render at 144 fps. The most useful comparison is your actual game at stable settings, with the same resolution and synchronization configuration.

For an unsupported overclock, a small theoretical improvement may be outweighed by flicker, missing frames, or unreliable wake behavior. Decide beforehand which compromises would make you return to 120Hz.

Check the monitor and connection before changing anything

Identify the exact model and input limits

Read the complete model number from the monitor’s label or information menu, including any suffix. Open that model’s official manual and locate the supported timing table.

Look for the combination of resolution, refresh rate, and input. A maximum vertical-frequency range alone is less useful than an explicit supported mode. Similarly, a family’s marketing page may cover several variants with different capabilities.

Record these details:

  • The native resolution and documented maximum refresh rate.
  • Whether 144Hz requires a particular input or monitor menu setting.
  • Any restrictions involving HDR, adaptive sync, or other display features.
  • The manufacturer’s instructions for undoing an overclock setting.

A monitor advertised for 144Hz can still be limited to 120Hz in a particular configuration. Solve that supported-mode problem before creating custom timings.

Trace the complete signal path

Write down how the image reaches the screen: graphics output, cable, any adapter or dock, and monitor input. On a desktop with a discrete graphics card, confirm which physical output you are using.

For the initial check, simplify the route to a direct connection when practical. A dock or adapter adds another compatibility requirement, making it harder to identify why a mode is unavailable.

Do not buy a cable solely because it says “gaming” or “144Hz.” Its suitability depends on the resolution and signal format as well as refresh rate. Use the capabilities specified for both endpoints and the exact connection.

At unchanged resolution, color format, and timing structure, moving from 120Hz to 144Hz increases the refresh-related data requirement by approximately 20%. Actual link requirements also involve timing overhead and signal format, so this percentage is not a complete bandwidth calculation.

Record a clean 120Hz baseline

Save open work and close unnecessary applications. Confirm that the display is stable at its existing supported mode before experimenting.

Record the current resolution, refresh rate, HDR state, adaptive-sync setting, and monitor overdrive setting. Photograph the monitor menu if that helps you restore it later.

Use a familiar game or motion scene to establish what normal behavior looks like. If the monitor already blacks out at 120Hz, resolve that problem first. Otherwise, a preexisting cable or configuration fault could be mistaken for an overclocking limit.

Prepare a recovery route before testing

Keep these changes within software and the monitor’s documented menus. There is no reason to open the monitor, modify its electronics, or flash unofficial firmware for this task.

Know how to return to the recorded 120Hz mode. A second working display can make recovery easier, but it does not prove the experimental display will accept a higher rate.

Driver tests may briefly blank the screen. NVIDIA’s documentation says a failed custom-mode test should return the previous picture after a few seconds. Do not confirm an unreadable mode or assume every kind of monitor-side change has the same automatic rollback.

A setting stored in the monitor’s own menu may need to be undone there. Review its controls before starting, especially if menu navigation becomes difficult without an incoming picture.

Small increases are an editorial recommendation for isolating failures, not a guarantee of safety. Stop if the driver rejects a mode, the monitor reports an unsupported signal, or visual problems appear. Repeated attempts at the same failing setting provide little useful information.

How to overclock a 120Hz monitor to 144Hz in order

Select an existing supported mode first

  1. Open Settings, then System, Display, and Advanced display.
  2. Select the intended monitor if more than one is connected.
  3. Check the current resolution and refresh information.
  4. Look for 144Hz under Choose a refresh rate.
  5. If the manual supports that mode on your connection, select it and confirm only after the image returns correctly.

Microsoft notes that an asterisk beside a refresh option means choosing it will change the resolution. Check that you have not traded native resolution for a higher number.

If 144Hz is missing despite official support, recheck the input, cable path, and required monitor settings. A custom resolution should not be the first response to an incorrectly configured supported mode.

Use a documented monitor overclock setting when available

  1. Open the monitor’s on-screen display using its physical controls.
  2. Locate the overclock option described in the exact-model manual.
  3. Follow any feature restrictions or connection prerequisites.
  4. Enable the documented setting and choose the permitted refresh target.
  5. Select the resulting mode in Windows and verify its behavior.

ASUS documents this general approach for applicable monitors, including input requirements and model-dependent menu behavior. Its example is not evidence that every ASUS monitor, or every 120Hz screen, includes that feature.

Do not select a higher value simply because the menu exposes one. Stay within the model’s instructions and restore the previous setting if the result is unstable.

Create a small increase with NVIDIA Control Panel

Use this branch only when NVIDIA controls the connected display and the custom-resolution controls are available.

  1. Open NVIDIA Control Panel and choose Display, then Change resolution.
  2. Select the correct monitor.
  3. Choose Customize, then Create Custom Resolution.
  4. Review the displayed warning before proceeding.
  5. Retain the native pixel dimensions and progressive scan setting.
  6. For an unsupported experiment, begin with a small increase such as 122Hz or 125Hz rather than jumping directly to 144Hz.
  7. Leave timing parameters at their existing or automatic values for the initial attempt.
  8. Select Test and save only if the picture is clear and the test succeeds.

Apply the saved mode if needed, then perform the verification checks below before increasing it again. If one candidate passes, another small increase can identify whether additional headroom exists. There is no mandatory sequence of rates.

If Customize is unavailable, investigate the display routing and feature support for your system. Do not assume that a grayed-out button is permission to bypass driver restrictions with another utility.

Create a candidate mode with AMD Software

AMD’s documented workflow uses Custom Resolutions in AMD Software: Adrenalin Edition. Controls can differ by installation and hardware.

  1. Open AMD Software, search for Custom, and select Custom Resolution.
  2. Select the intended display.
  3. On first use, review the license agreement and proceed only if you accept it.
  4. Choose Create New to populate a profile with the current settings.
  5. Preserve the native resolution and enter a small refresh increase.
  6. Choose Create and allow the compatibility check to complete.
  7. If accepted, select the saved mode through Windows display settings or an applicable game menu.

AMD provides a trash icon for deleting custom profiles. A compatibility pass establishes that the profile was accepted; you still need to examine actual display behavior.

Treat Intel systems and internal screens separately

Do not follow an old tutorial that assumes every Intel Graphics Command Center installation has a custom-resolution button. Intel’s current support article says the latest IGCC uses Windows display settings and lacks that editor; it describes a Beta workaround for the product covered by the article.

That does not establish universal refresh-overclock support. Intel also documents limitations for internal displays. Check the exact GPU, driver, laptop, and display path before attempting a model-specific method. Custom Scaling changes apparent display size and is not a refresh-rate overclock control.

Verify that the higher rate displays real frames

Confirm the active signal and preserve image quality

Check Windows Advanced display again after applying the candidate. Also inspect the monitor’s signal-information page if available. Confirm the intended resolution remains active.

A label such as 143.98Hz instead of an exact 144.00Hz is not, by itself, evidence of failure. More important questions are whether the intended mode is active and whether the screen displays it correctly.

Compare small text, familiar images, and motion against the baseline. Look for newly introduced lines, sparkling pixels, intermittent blackouts, or motion trails. Avoid changing overdrive and refresh simultaneously, because that makes the comparison harder to interpret.

If HDR or adaptive sync was disabled for troubleshooting, restore features individually after the basic fixed-refresh test. A useful result needs to work in the configuration you actually intend to use.

Check for frame skipping with a camera

A monitor can accept a timing without displaying every expected refresh. Use the TestUFO Frame Skipping Checker to investigate that distinction.

Let the test run smoothly on the target screen. Close unnecessary browser tabs and background workloads, and address any synchronization warnings before interpreting the result.

TestUFO instructs users to photograph the screen with an exposure of 1/10 second or longer so multiple illuminated squares appear. A screenshot cannot capture the panel’s physical refresh sequence.

Compare your photograph with the test’s good and frame-skipping examples. Gaps in the expected sequence warrant investigation. Repeat an unclear shot and compare the same procedure at the known-good 120Hz baseline; a poorly synchronized test or inadequate exposure can mislead you.

Do not call the overclock successful merely because Windows displays a larger number. Reject a candidate that reproducibly skips frames under a valid test.

Test daily transitions as well as a game

Try a familiar game, ordinary desktop use, a restart, and a sleep-and-wake cycle. Switch between desktop and full-screen modes if that reflects your normal routine.

As a practical screening session, allow roughly 20–30 minutes of varied use. This is a suggested observation period, not a manufacturer certification or proof of long-term stability.

Record the tested rate and any failures. If 144Hz produces intermittent blackouts while 120Hz remains reliable, the useful result is the stable mode. A lower custom rate is worth retaining only if it also passes your checks and justifies operating outside specification.

Troubleshoot an unsuccessful attempt

Symptom What to check Immediate action
Black screen during the test Rejected timing or lost signal Do not confirm; allow the test to revert
Unsupported or out-of-range message Monitor does not accept the candidate Restore the supported rate
Driver rejects profile creation Timing, connection, or driver restriction Stop increasing and review documented limits
Desktop works but motion skips Frame delivery and test validity Repeat a valid test; reject confirmed skipping
Flicker appears after adaptive sync returns Behavior with that feature enabled Compare with the original 120Hz configuration
Game returns to 120Hz Game display mode and refresh selection Check its settings and the selected monitor
Failure occurs after sleep or restart Persistence and reconnection behavior Restore the stable configuration

If a documented 144Hz mode fails, compare your setup with the manual and contact support with the exact model, input, resolution, GPU, and symptoms. A failure within a supported configuration deserves different investigation from rejection of an unsupported overclock.

Do not copy another person’s detailed porch, sync-width, or pixel-clock values merely because the screen size matches. Without exact-model evidence, those settings introduce additional unknowns.

Restore 120Hz if the picture remains unusable

If you can still access Windows, select the affected display in Advanced display and restore its known-good resolution and 120Hz rate. Then delete the experimental profile in the utility that created it.

If the monitor-side overclock option caused the problem, undo that setting using the manual’s recovery procedure. ASUS advises disconnecting the signal cable and using the monitor menu to lower the maximum refresh rate on applicable models. Follow your manufacturer’s instructions rather than assuming this applies universally.

For a persistent Windows display problem, Microsoft provides Enable low-resolution video through Windows Recovery Environment: Troubleshoot, Advanced options, Startup Settings, then Restart. Choose the low-resolution-video option to start with reduced resolution and refresh settings and reset the configuration. Have the BitLocker recovery key available if the device is encrypted.

Use a second working display to access recovery instructions when available. Avoid repeated forced shutdowns as an improvised troubleshooting routine. If the screen remains abnormal at its original supported mode, stop experimenting and seek manufacturer assistance.

Frequently asked questions

Will any 120Hz monitor reach 144Hz?

No. The same advertised refresh rate does not imply identical panel electronics, input support, or available headroom. Another owner’s success is not a guarantee for your unit.

Does lowering resolution guarantee that 144Hz will work?

No. It may reduce signal bandwidth, but it cannot establish that the monitor supports the higher refresh frequency. If a lower-resolution 144Hz mode is officially listed, evaluate that documented trade-off separately.

Should you use CRU after the driver rejects 144Hz?

Not as an automatic next step. Third-party display overrides require their own compatibility checks and recovery preparation. They do not prove the panel can operate correctly at the requested rate. For this workflow, rejection is a reason to reassess the limit.

Is stable 120Hz preferable to unstable 144Hz?

Yes. The theoretical refresh-interval improvement is about 1.39 milliseconds. Missing frames, blackouts, or lost features can outweigh that modest gain. Keep 144Hz only when the applicable mode works correctly and its risks and trade-offs are acceptable.

Choose the mode that survives verification

Begin with the manual and the connection. Select an existing supported 144Hz mode when available, or use the manufacturer’s documented overclock procedure. Treat custom timings beyond a stated 120Hz maximum as an optional, unsupported experiment.

The deciding evidence is consistent operation at the intended resolution, with complete frame delivery and your normal features enabled. If the display cannot provide that, restore 120Hz. A dependable screen is a better outcome than an impressive setting that fails during use.

Explore Our Guides & Free Tools