A 60Hz and 144Hz dual monitor setup can run each screen at its own supported refresh rate in an extended desktop. If the faster monitor appears limited to 60Hz, first check the display mode and per-screen refresh settings. If Windows still reports 144Hz but motion stutters, investigate game settings, background applications, and the connection path instead. These symptoms need different fixes; replacing the 60Hz monitor should not be your first step.
- The quick fix: Use Extend and configure each display separately
- Identify the actual symptom before changing more settings
- If the 144Hz option is missing
- If Windows shows 144Hz but the game runs at 60 FPS
- If a 60Hz and 144Hz dual monitor setup stutters during video
- Test presentation mode and adaptive sync carefully
- If screens flicker, disconnect, or lose signal
- If the problem started after an update
- Verify the fix and know when to escalate
- Final troubleshooting verdict
The quick fix: Use Extend and configure each display separately
Different refresh rates are supported in an extended desktop when the graphics hardware and connections support the required modes. AMD explicitly documents independent resolution and refresh settings for extended displays.
Start with this baseline:
- Save your work and close games.
- Press Windows + P and select Extend.
- Open Settings, System, Display, and use Identify to match the numbered displays to the physical screens.
- Open Advanced display and select the 144Hz monitor.
- Choose its intended resolution and 144Hz refresh rate.
- Select the other monitor and confirm its supported 60Hz mode.
- Reopen the application and repeat the activity that showed the problem.
Microsoft documents refresh selection through Advanced display. Available choices depend on the selected monitor and supported modes.
If this restores smooth operation, stop there. If not, record whether the failure is a missing mode, low game frame rate, uneven motion, or signal loss.
Why Duplicate can change the result
Duplicate mirrors the same desktop rather than creating independent workspaces.
AMD’s documented duplicate configuration uses a common supported resolution and refresh rate. Other hardware implementations can differ, but cloning is not the cleanest baseline for testing independent 60Hz and 144Hz operation.
Use Extend during diagnosis. If duplication is necessary for capture or presentation, verify the exact graphics driver and receiving device’s supported arrangement separately.
Identify the actual symptom before changing more settings
A refresh setting, a frame counter, and the appearance of motion measure different things. Compare them before choosing a troubleshooting branch.
| Symptom | First check | What it may indicate |
|---|---|---|
| Windows offers only 60Hz | Correct display, input, cable, and supported timings | Display-mode or connection limitation |
| Windows reports 144Hz but the game stays near 60 FPS | Game limits, V-Sync, selected monitor | Application configuration or rendering limit |
| Motion becomes uneven during secondary-screen video | Repeat with video paused | Interaction involving the application or graphics workload |
| Screen intermittently goes black | Direct connection and supported signal mode | Link, power, driver, or mode-switching issue |
| The problem appears after sleep | Recheck detected mode and connection | Reconnection or configuration issue |
| Cursor looks less smooth only on the second screen | Compare each screen separately | Expected difference between refresh rates |
Refresh rate is not game frame rate
A monitor set to 144Hz can refresh approximately every 6.94 milliseconds. A 60Hz display refreshes approximately every 16.67 milliseconds.
Those calculated intervals do not guarantee equivalent game frame rates. The game can render fewer frames than the display refreshes.
Likewise, a high FPS average does not prove evenly delivered frames. Brief interruptions can remain visible even when the counter looks healthy.
Understand variable refresh readouts
With variable refresh rate enabled, a monitor’s live refresh indicator may fluctuate.
That behavior is not automatically evidence that Windows has permanently changed the selected maximum mode. Compare the configured mode, the game’s frame delivery, and the monitor’s documented indicator behavior.
Avoid treating every changing on-screen refresh number as proof of a mixed-monitor fault.
If the 144Hz option is missing
Focus on the video connection and supported timing before investigating browser acceleration or gaming overlays.
Confirm the exact monitor and input
Check the model suffix and manufacturer timing table. Some monitors support their advertised maximum only through particular inputs or settings.
Select the intended native resolution first, then inspect the available refresh choices. A frequency range in a specification table is not a guarantee of every resolution-and-refresh combination.
Also confirm that the cable is connected to the monitor you selected in Windows. Similar display names can make this surprisingly easy to misidentify.
Remove intermediate devices
Temporarily bypass the dock, KVM, capture device, converter, or extension cable where practical.
Connect the fast monitor directly to a suitable video output, then check available modes again. Microsoft recommends isolating accessories and cables when troubleshooting external displays.
If 144Hz becomes available directly, investigate the removed device’s exact limits. Do not replace the monitor merely because one docked arrangement cannot expose its maximum mode.
Check the cable and source together
A connector’s shape does not establish the complete supported signal.
Verify the graphics output, cable, adapter, and monitor input at the intended resolution and refresh. For USB-C, confirm video-output support on the computer.
A basic HDMI splitter repeats a signal; it does not create two independent extended outputs. Microsoft specifically distinguishes this limitation from adding a suitable display connection.
Try the fast monitor alone
Disconnect the secondary display temporarily and retest.
If 144Hz is still unavailable, the 60Hz monitor is unlikely to be the immediate explanation. Continue checking the fast screen’s own path.
If the mode appears only with one screen connected, investigate simultaneous display limits, dock bandwidth, and driver behavior. Individual support for each screen does not establish support for every combined configuration.
If Windows shows 144Hz but the game runs at 60 FPS
Once the selected display mode is correct, investigate the game rather than repeatedly changing Windows refresh settings.
Check the game’s selected screen and limits
Confirm the game opens on the intended display. Make the fast screen the main display as a sensible baseline, while recognizing that this setting does not itself unlock bandwidth or remove every stutter.
Inspect resolution, refresh selection, V-Sync, and frame limits inside the game. Also check any application-specific limit in the graphics software.
Change one control at a time. A 60 FPS cap can remain active even when the desktop correctly operates at 144Hz.
Separate background limits from foreground performance
Some games reduce their frame rate when they lose focus.
Clicking a browser or chat window on the second screen may therefore change game behavior without changing the monitor’s refresh rate.
Return focus to the game and compare. If performance recovers, inspect the game’s background-frame setting rather than assuming the two monitors are synchronized incorrectly.
Rule out an ordinary rendering bottleneck
Repeat a consistent scene and temporarily lower a demanding graphics setting.
If frame rate improves, workload is part of the explanation. Do not expect the monitor setting to solve a game that cannot produce the desired frames.
Use the same scene, resolution, and foreground state for comparisons. Different locations or loading events can otherwise make an unrelated change appear successful.
If a 60Hz and 144Hz dual monitor setup stutters during video
This branch applies when the configured modes remain correct but a repeatable secondary-screen activity affects smoothness.
Establish a controlled comparison
Run the same game scene with the second screen showing a static desktop.
Then play the same video at the same size and quality. Pause it and repeat the comparison.
Record whether the game stutters, the video drops frames, or both occur. An improvement when playback stops implicates that workload or interaction; it does not prove that every 60Hz display causes the problem.
Isolate the application
Try the same content in another suitable player or browser, if available.
Disable browser extensions selectively or use a clean profile for comparison. Avoid changing the monitor settings and the playback application simultaneously.
If only one application triggers the symptom, prioritize its updates and configuration. If several trigger it, examine the shared driver, graphics path, and overall system workload.
Test hardware acceleration as a reversible experiment
If the affected application exposes a hardware-acceleration setting, note its original state, change it, restart the application, and repeat the same test.
Keep the change only if it improves your actual workload without creating another problem.
Disabling acceleration can shift work elsewhere in the system, so it is not a universal performance upgrade. If the comparison is inconclusive, restore the original setting.
Remove extra graphics activity
Temporarily close animated wallpapers, unused video streams, recording previews, and unnecessary overlays.
Add them back individually after establishing a stable baseline. A second display showing a static document is a different workload from one running several animated applications.
Do not assume that a GPU can handle every background task without affecting the foreground simply because its average utilization is below 100%.
Separate video cadence from a system-wide problem
A low-frame-rate video will not acquire additional native motion detail merely because the monitor refreshes more frequently.
Check whether the same scene looks uneven with the game closed. If it does, examine the source video, playback statistics where available, and the player before blaming the dual-monitor configuration.
Also distinguish buffering from rendering stutter. Playback pauses accompanied by a loading indicator suggest a different investigation from smoothly delivered audio with uneven pictures. Repeat with a suitable local file if available to reduce network-related uncertainty.
Do not compare different videos and conclude that changing a display setting fixed the issue. Keep the content, playback quality, and window size consistent.
Test presentation mode and adaptive sync carefully
Game presentation, variable refresh, and desktop composition can interact. The goal is to identify a useful configuration, not apply every available optimization.
Compare fullscreen and borderless
If the game offers both, test each with the same scene and settings.
Neither mode is universally superior across games, drivers, and Windows versions. Modern presentation behavior also means a menu label alone does not fully describe the underlying path.
If one mode consistently avoids the symptom, use it as a practical workaround and record the result for support.
Check Windows windowed-game optimizations
Microsoft documents Optimizations for windowed games for compatible DirectX 10 and DirectX 11 titles in Windows 11.
The control is under Settings, System, Display, Graphics. Its purpose includes improving presentation latency through a newer presentation model.
For an affected game, test the supported per-application setting, restart the game, and compare. Do not describe this as a blanket fix for every API or mixed-refresh configuration.
If Auto HDR affects whether the control can be changed, follow Microsoft’s related instructions rather than changing several graphics features blindly.
Limit G-SYNC testing to the affected configuration
For supported NVIDIA systems, check Set up G-SYNC in NVIDIA Control Panel.
NVIDIA offers fullscreen-only and windowed-plus-fullscreen operation. Its documentation specifically identifies fullscreen-only operation as an option when windowed applications cause difficulty.
Use that as a targeted test when relevant. Temporarily disabling G-SYNC can also help isolate the symptom, but an improvement identifies a setting interaction rather than proving the monitor is defective.
For FreeSync or other VRR arrangements, use the applicable manufacturer controls instead of following NVIDIA-specific instructions.
Use 120Hz only as a diagnostic comparison
If the fast monitor officially supports 120Hz, test it while leaving the secondary screen at 60Hz.
A better result can provide a useful workaround, but it does not establish a universal requirement for refresh rates to be exact multiples.
If nothing changes, restore 144Hz. Do not permanently reduce refresh simply because an online explanation claims all mixed-rate systems need matching ratios.
If screens flicker, disconnect, or lose signal
Signal loss deserves a separate investigation from uneven game motion.
Distinguish mode changes from random dropouts
A brief blank when switching inputs or display modes can differ from repeated blackouts during unchanged operation.
Record whether the problem occurs when entering a game, changing HDR, waking the computer, or simply moving through the desktop.
That trigger helps narrow the investigation. Do not treat every black screen as the same failure or immediately assume the graphics card is dying.
Test a conservative supported mode
Temporarily select a lower documented refresh rate. If relevant, compare with HDR disabled while keeping other settings stable.
If dropouts stop, investigate signal stability and the supported combination of resolution, refresh, and color settings. This is evidence for further diagnosis, not proof that one particular cable is faulty.
Swap one known-compatible cable or output at a time. Note which combination fails.
Check power and connections
Reseat external connectors gently and verify the monitor’s intended power arrangement. Save work and shut down equipment before handling connections that are awkward to access.
For a desktop, inspect where cables terminate. Graphics-card and motherboard outputs can belong to different display paths; motherboard video also depends on the system’s configuration.
Do not open the PC or move hardware just to follow a generic mixed-refresh workaround. Start with accessible connections and documented settings.
If the problem started after an update
A new symptom after a driver or system change makes the update relevant, but timing alone does not prove the cause.
Use a controlled driver change
Record the installed graphics driver version and the date the symptom began.
Check official support channels for an appropriate driver. Laptop owners should also consider the computer manufacturer’s guidance for hybrid graphics and external displays.
If a driver update clearly preceded the problem, a supported rollback is a reasonable comparison. Microsoft includes driver rollback in its external-display troubleshooting guidance.
Do not alternate repeatedly between unrelated drivers without preserving a reproducible test.
Recover from a transient display problem
Save work where possible and try a normal restart before making further configuration changes.
Microsoft also documents Windows + Ctrl + Shift + B as a graphics-driver reset shortcut that can help with some existing display issues. The screen may briefly change while it responds.
Treat this as recovery, not proof that the root cause is fixed. If the same trigger immediately brings the problem back, continue collecting evidence rather than repeating the shortcut indefinitely.
Avoid stacking low-level tweaks
Registry edits, disabled Windows graphics features, forced timings, and third-party driver cleanup can complicate diagnosis when applied together.
Keep the initial process to documented display modes, application settings, connection tests, and supported driver changes.
If a vendor identifies a specific workaround for your hardware and driver, record how to reverse it. Do not turn a version-specific fix into a permanent requirement for every dual-monitor PC.
Verify the fix and know when to escalate
A useful fix survives the real workload, not just a few seconds of cursor movement.
Repeat the original failure
Confirm the intended resolution and refresh for both screens, then rerun the exact game or desktop activity.
Test with secondary-screen playback if that originally triggered stutter. Check behavior after restarting and after sleep.
Keep only changes with a repeatable benefit. Restore experiments that did not help so the final configuration remains understandable.
Send support a reproducible report
Include the following:
- Both exact monitor models and selected resolutions.
- Graphics hardware, computer model, and driver version.
- Windows version and relevant build information.
- Cable types and every dock, adapter, or KVM involved.
- Extend or Duplicate mode.
- Game, browser, or player version.
- Whether the problem occurs with one monitor alone.
- Results from direct connections and presentation-mode tests.
- Whether the symptom is low FPS, uneven motion, flicker, or signal loss.
This information helps distinguish an unsupported configuration from a software regression or failing component. Replace hardware only when testing points to a specific limitation or fault.
Final troubleshooting verdict
Keep the 144Hz display at its supported rate and the secondary monitor at 60Hz in Extend mode unless testing identifies a specific reason to change them. Resolve missing refresh options through the connection path, investigate low FPS within the application, and isolate video-related stutter with controlled comparisons. Treat fullscreen, VRR, acceleration, and 120Hz tests as reversible diagnostic tools. Mixed refresh rates alone are not a reason to buy another monitor.
