If the 240Hz option is not showing, check the selected monitor and resolution in Windows, then confirm that the connected input supports that exact mode. Test a direct connection before changing drivers or creating custom timings. On high-resolution displays, also verify any Display Stream Compression requirements. A 240Hz label on the box does not establish support through every port and configuration.
- 240Hz option not showing: Start with the supported mode
- Define exactly which 240Hz mode you want
- Select the correct display and refresh rate in Windows
- Check DSC without disabling a necessary feature
- Test the physical connection before replacing components
- 240Hz option not showing with multiple monitors
- Investigate drivers and firmware using the change history
- Recover safely if the option appears but the image fails
- Verify the complete result and prepare a support report
- Frequently asked questions
- Restore the mode the complete connection supports
240Hz option not showing: Start with the supported mode
On Windows 11, open Settings, System, Display, and Advanced display. Select the intended monitor and inspect Choose a refresh rate. If 240Hz appears, apply it only when the resulting resolution and picture are correct.
If the option is missing, work through three questions: Does this input support 240Hz at the intended resolution? Can the source and complete connection carry that mode? Is the graphics software correctly exposing the supported combination?
These symptoms call for different next steps:
| What you see | First investigation |
|---|---|
| Only 120Hz or 144Hz is available | Monitor timing table, connected input, and source output |
| 240Hz appears at a lower resolution | Requirements for the original resolution and feature combination |
| 240Hz disappears through a dock or KVM | Intermediary device and multi-display arrangement |
| The option exists, but selecting it loses signal | Mode compatibility and connection stability |
| Windows applies 240Hz, but a game reports lower fps | Application configuration and rendering performance |
This guide assumes an external display connected to a Windows PC. It restores an advertised supported mode; it does not turn a lower-rated monitor into a 240Hz model through overclocking.
Define exactly which 240Hz mode you want
Record resolution, color settings, and the input
Write down the monitor’s full model number, current resolution, connected input, source output, and any adapters or docks. Include HDR and output color depth when relevant.
“240Hz” alone leaves out the signal’s size. Full HD, QHD, and 4K place very different demands on the connection. The following calculations illustrate the difference using uncompressed RGB with 8 bits per channel:
| Resolution at 240Hz | Calculated active image data |
|---|---|
| 1920 × 1080 | Approximately 11.94 Gbps |
| 2560 × 1440 | Approximately 21.23 Gbps |
| 3840 × 2160 | Approximately 47.78 Gbps |
These figures exclude blanking intervals, transport overhead, and compression. They are not cable requirements or proof that a specific port supports the mode. Their purpose is to explain why the same refresh rate can require a different connection strategy at another resolution.
Color depth changes the calculation, too. At the same resolution and rate, RGB with 10 bits per channel uses 30 active bits per pixel instead of 24, a 25% increase before compression and transport overhead. That does not mean enabling HDR always raises traffic by exactly 25%; the actual output format, bit depth, and compression determine the signal.
For diagnosis, record what the graphics driver actually outputs. A display accepting HDR is not enough information to calculate its connection requirements. Likewise, an 8-bit comparison that exposes 240Hz answers a narrower question than whether your preferred HDR and color configuration works at 240Hz.
Check the monitor’s timing table by port
Find the exact manufacturer’s supported resolution-and-refresh combinations. Read the conditions for the input you actually use rather than relying on a general maximum-refresh specification.
For example, Dell specifies the Alienware AW2721D at 2560 × 1440 with 240Hz over DisplayPort and 144Hz over HDMI. An owner using HDMI can therefore encounter a legitimate lower ceiling on a monitor marketed for 240Hz.
That example does not mean HDMI is universally unsuitable for 240Hz. It means this model’s input support determines the correct route. Other displays have different limits, and even closely related model names can refer to different hardware.
Check whether a monitor-side mode is required
Read the manual for any documented high-refresh setting, input bandwidth option, compression requirement, or approved overclock mode involved in reaching the advertised maximum.
Some monitors expose their maximum without an overclock toggle; others require a specific setting. Do not assume every gaming display uses the same menu. Pixel overdrive and picture presets are not substitutes for enabling a supported input mode.
Record the existing on-screen display settings before changing them. Follow the exact model’s instructions, then inspect the Windows mode list again.
Select the correct display and refresh rate in Windows
Use Advanced display for the intended screen
- Save open work and close fullscreen games.
- Open Settings, System, and Display.
- Use Identify if multiple screens are attached.
- Set the intended display resolution.
- Open Advanced display and select that monitor.
- Inspect Choose a refresh rate and select 240Hz when available.
Confirm a readable image and recheck the applied resolution. Microsoft notes that asterisk-marked refresh choices require a resolution change. Selecting a faster rate with fewer pixels is not the same result as restoring 240Hz at the original resolution.
On Windows 10, use Advanced display settings. Depending on the interface, check its Refresh rate list or Display adapter properties, Monitor, and Screen refresh rate.
Compare the graphics software’s mode list
For NVIDIA systems with display controls available, open NVIDIA Control Panel, Display, and Change resolution. Select the target monitor and compare the available resolution and refresh combinations with Windows.
ZOWIE’s setup instructions advise its NVIDIA users to choose the intended resolution under PC rather than Ultra HD, HD, SD. This is a relevant manufacturer-documented interface check, not a way to override a port limitation.
AMD’s current display guidance directs refresh selection through Windows. On systems with multiple graphics adapters, establish which adapter drives the connected output before treating a missing vendor control as an error.
Keep refresh rate separate from game performance
If Windows already applies 240Hz, a game’s 120 fps counter does not mean the option is missing. Check the game’s selected screen, frame cap, resolution, and refresh setting where available.
Rendering more frames requires the PC to process the game faster; changing the display mode alone does not guarantee 240 fps. Conversely, lowering graphics settings will not normally expose an absent Windows display mode.
Record which readout shows the lower number before choosing a troubleshooting branch. This prevents a game limit from being mistaken for a connection failure.
Be careful with a monitor’s live refresh counter during adaptive-sync operation. Depending on the implementation, it may follow changing frame delivery rather than display a constant configured maximum. A fluctuating number during gameplay is therefore different evidence from Windows omitting 240Hz entirely.
For a useful comparison, first inspect the configured Windows mode, then note the game fps and monitor readout during the same scene. If the desktop mode remains correct but behavior changes between applications, investigate application settings before replacing the cable or modifying the monitor’s supported modes.
Check DSC without disabling a necessary feature
Understand what Display Stream Compression does
Display Stream Compression, or DSC, reduces the data required to transport a display signal. VESA describes it as a low-latency, visually lossless compression standard. A high-resolution, high-refresh mode may depend on DSC where uncompressed transport would exceed the available link capacity.
Not every 240Hz mode requires DSC, and a DSC-capable monitor does not establish that every source supports the required mode. Read the monitor and GPU documentation for the specific connection.
If the manual requires DSC for your target, leave the necessary support enabled. Turning it off simply to reveal another software control can remove the very mode you are trying to restore.
Verify source support for the connection you use
NVIDIA documents DisplayPort DSC support on Turing-class GeForce RTX 20-series and GTX 16-series GPUs and later generations. Its HDMI DSC guidance identifies Ampere-class GeForce RTX 30-series hardware. These are DSC-support distinctions, not universal guarantees of every 240Hz resolution and color combination.
NVIDIA also notes that compatible DSC operation can activate automatically. Some monitors change compression availability through an input-link setting rather than a separately labeled DSC switch.
Follow the exact documentation instead of toggling DisplayPort compatibility modes randomly. A lower link mode can change available capabilities even though the cable remains in the same socket.
Compare the intended feature combination
If documentation indicates bandwidth-dependent limits, test the supported mode with HDR off or another supported output color depth. Keep other settings unchanged and record the result.
If 240Hz appears, you have narrowed the issue to a configuration-dependent restriction. Investigate whether another documented connection preserves both the refresh target and the image features you need.
Do not silently accept reduced resolution, degraded text, or lost HDR as a complete fix. Judge the entire configuration, then choose the trade-off deliberately if the hardware cannot provide everything together.
Test the physical connection before replacing components
Use a direct source-to-monitor path
Temporarily remove a dock, KVM switch, converter, capture device, or extension when a direct connection is possible. Use an output and input documented for your target resolution and rate.
If 240Hz appears, reconnect the intermediary device with only that display attached. Then restore other devices separately. This establishes which arrangement changes the mode list without assuming a particular component is broken.
For laptops, verify the external output specifications separately from the built-in screen. A fast internal panel or powerful discrete GPU does not establish every port’s external display capabilities.
Check the cable with a controlled substitution
Confirm that the connectors are seated properly, then try another known-good cable suitable for the target connection. Keep the computer output, monitor input, resolution, and feature settings constant during the comparison.
Check the replacement cable’s actual capabilities and certification rather than relying on a “gaming” description. A cable cannot add a capability missing from the source or monitor input.
If a port change is also necessary, test it separately and record both results. Making several changes together can produce a working picture while leaving the original cause unclear.
Verify the dock or converter’s complete requirements
Look for a support table that covers the host connection, number of displays, resolution, and refresh rate. A dock advertising 4K output does not automatically establish QHD 240Hz or 4K 240Hz support.
For converters, verify the signal direction and target mode explicitly. A connector that fits is not evidence that the conversion preserves high-refresh capability.
Intel documents that intermediary devices can also affect reading a display’s capability information, called EDID. A direct comparison can help isolate that problem; it does not prove EDID corruption or justify an override file.
240Hz option not showing with multiple monitors
Test one display, then restore the arrangement
If the desktop is duplicated, press Windows + P and test Extend. For a simpler baseline, disconnect other screens and recheck the target monitor’s refresh options.
If the mode returns, reconnect the second display while keeping the first connection unchanged. Record the resolutions, refresh rates, and graphics outputs used when the option disappears.
Do not conclude that every monitor must run at the slowest screen’s rate. The relevant limit can depend on the source hardware, duplicated mode, dock, or combined display configuration.
Consider graphics-resource limits on DSC configurations
NVIDIA notes that some high-pixel-rate DSC modes can consume additional internal display resources, affecting multi-monitor arrangements. The applicable limit depends on the GPU and modes involved.
If each monitor works alone but the complete arrangement fails, preserve that comparison and consult the GPU’s display-support guidance. Do not assume adding another cable or disabling compression will resolve a resource limitation.
This is especially relevant when troubleshooting several demanding displays. The success of one screen at its maximum does not prove every connected screen can simultaneously use its maximum mode.
Investigate drivers and firmware using the change history
Establish whether 240Hz ever worked in this setup
For a first installation, verify documented compatibility before trying old drivers. For a previously working arrangement, list recent changes: cable, input, GPU, monitor settings, dock, driver, or additional display.
Restore the previous physical arrangement where practical. An input change can look like a software regression when it happens around the same time as an update.
Record the driver version and operating-system version before changing software. Repeat the same test after each intervention so the comparison remains meaningful.
Install an appropriate supported graphics driver
Obtain the package from the PC manufacturer or GPU vendor and verify support for the exact hardware and operating system. On laptops, consult the computer manufacturer’s recommendations for the adapters serving the external connection.
If Device Manager shows Microsoft Basic Display Adapter, investigate the absent manufacturer driver. Microsoft identifies that entry as its generic graphics driver, not the GPU manufacturer’s full driver package.
If the problem began immediately after a driver update, a supported rollback can provide a useful comparison. Avoid third-party driver-download sites and unrelated registry changes.
Use firmware and monitor files only when applicable
Check official support for relevant monitor, dock, or graphics firmware instructions. Apply only updates intended for the exact model and follow the manufacturer’s procedure.
A monitor INF file may be a relevant support step in some configurations, but it is not a universal 240Hz unlock. Neither an INF file nor a color profile expands a port’s documented transport capability.
Do not begin by reinstalling Windows or stacking custom-resolution utilities. Restore the ordinary supported mode through the documented path first.
Recover safely if the option appears but the image fails
Do not confirm an unreadable temporary display change. Allow the confirmation period to expire and return to the previous working mode. Keep a stable supported refresh rate while investigating the connection.
If the unusable setting persists, another working monitor or alternative input may let you restore it. Windows Startup Settings offers low-resolution video and Safe Mode recovery options when necessary.
After recovery, check whether the failed mode changed resolution, color settings, or another feature. Test another appropriate cable and source where available. A listed 240Hz entry does not establish that an unstable signal should be kept.
Verify the complete result and prepare a support report
Confirm the intended resolution and approximately 240Hz in Windows, then check the monitor’s incoming-signal information where available. Restart, test sleep and wake, and repeat the original failure condition.
Restore the features and accessories you actually use. If the setting works only with HDR disabled or a second display disconnected, record that limitation rather than declaring the entire setup fixed.
Send support the exact monitor, GPU or laptop, connected ports, cable or converter, dock, resolution, output color settings, driver version, and available refresh rates. Include controlled comparison results and whether the target mode previously worked.
Frequently asked questions
Does HDMI support 240Hz?
It can on suitable source-and-display combinations. The exact resolution, input implementation, color settings, and compression requirements determine support. Do not replace a model-specific timing table with a blanket claim about the connector.
Will a faster GPU automatically expose 240Hz?
No. A GPU change helps only when the existing output capability is the limit. It cannot remove a monitor input restriction or repair an unsuitable intermediary device. Verify the missing capability before buying hardware.
Should I create a custom 240Hz resolution?
Not as the first fix for an advertised mode. Confirm support and diagnose the normal connection first. Use custom timing instructions only when justified by model-specific support; a manually added entry does not certify the display path.
Restore the mode the complete connection supports
Define the exact 240Hz target, verify each endpoint, and preserve required features such as DSC. Use a direct connection and controlled software comparisons to locate the restriction.
Keep the result only when the intended resolution, image features, and normal display arrangement remain stable. If documented support exists but the option stays unavailable, escalate with the evidence rather than forcing unsupported timings.
