No signal, wrong resolution or stuck at 60 Hz? Find the limiting link
Find out why your monitor shows no signal or the wrong refresh rate, and whether your USB-C, DisplayPort, HDMI or dock connection can carry the mode you want — part by part, with sources.
Updated: 2026-10-18
Check your connection
The interactive check needs JavaScript. Everything else on this page — the bandwidth tables, the fix checklists and the sources — works without it.
How the solver decides
It splits the connection into parts — computer output, anything in between, cable and the monitor input — and checks each one. A connection is only as good as its weakest part.
- FAIL means a documented limit rules your mode out. Example: 3440×1440 at 165 Hz needs at least 19.62 Gbit/s of active pixels at 8-bit RGB, more than an HDMI 2.0-class link’s 18 Gbit/s [H1].
- UNKNOWN means nothing rules it out, but something needed is missing, often the monitor’s exact timing for that input or a cable certification.
- CONDITIONAL means the numbers fit with a full timing you supplied, and the listed checks still have to hold.
- PASS needs the exact monitor model to list your mode for that input, plus documented capability on every part. A quick check from spec-sheet classes never says PASS.
The numbers are separated on purpose. Raw link rate (32.4 Gbit/s for DisplayPort HBR3 over four lanes) is not the same as usable payload (25.92 Gbit/s) [V1] [V2]. And a cable label like “8K 60Hz” describes one mode on one standard; it is not a 60 Hz ceiling for your monitor.
Which links can carry common modes
Active pixels × refresh × bits per pixel gives the minimum bitrate. Real signals add blanking, so a “Not ruled out” cell can still fail with the monitor’s real timing. DisplayPort payloads are VESA figures [V1] [V3]; HDMI payloads are DERIVED from the published raw totals [H1] [H2].
| Mode | HDMI 2.0 class 18 Gbit/s | HDMI 2.1 FRL 48 Gbit/s | USB-C Alt Mode 2 lanes, DP 1.2 | USB-C Alt Mode 2 lanes, DP 1.4 | DP 1.2 HBR2 (4 lanes) | DP 1.4 HBR3 (4 lanes) | DP 2.x UHBR20 |
|---|---|---|---|---|---|---|---|
| Usable payload, Gbit/s | 14.40 (DERIVED) | 42.67 (DERIVED) | 8.64 | 12.96 | 17.28 | 25.92 | 77.37 |
| 1920×1080 @ 144 Hz needs ≥ 7.17 Gbit/s | Not ruled out | Not ruled out | Not ruled out | Not ruled out | Not ruled out | Not ruled out | Not ruled out |
| 1920×1080 @ 240 Hz needs ≥ 11.94 Gbit/s | Not ruled out | Not ruled out | FAIL: exceeds | Not ruled out | Not ruled out | Not ruled out | Not ruled out |
| 2560×1440 @ 144 Hz needs ≥ 12.74 Gbit/s | Not ruled out | Not ruled out | FAIL: exceeds | Not ruled out | Not ruled out | Not ruled out | Not ruled out |
| 2560×1440 @ 165 Hz needs ≥ 14.60 Gbit/s | UNKNOWN: over DERIVED payload | Not ruled out | FAIL: exceeds | FAIL: exceeds | Not ruled out | Not ruled out | Not ruled out |
| 2560×1440 @ 240 Hz needs ≥ 21.23 Gbit/s | FAIL: exceeds | Not ruled out | FAIL: exceeds | FAIL: exceeds | FAIL: exceeds | Not ruled out | Not ruled out |
| 3440×1440 @ 100 Hz needs ≥ 11.89 Gbit/s | Not ruled out | Not ruled out | FAIL: exceeds | Not ruled out | Not ruled out | Not ruled out | Not ruled out |
| 3440×1440 @ 144 Hz needs ≥ 17.12 Gbit/s | UNKNOWN: over DERIVED payload | Not ruled out | FAIL: exceeds | FAIL: exceeds | Not ruled out | Not ruled out | Not ruled out |
| 3440×1440 @ 165 Hz needs ≥ 19.62 Gbit/s | FAIL: exceeds | Not ruled out | FAIL: exceeds | FAIL: exceeds | FAIL: exceeds | Not ruled out | Not ruled out |
| 3840×2160 @ 60 Hz needs ≥ 11.94 Gbit/s | Not ruled out | Not ruled out | FAIL: exceeds | Not ruled out | Not ruled out | Not ruled out | Not ruled out |
| 3840×2160 @ 120 Hz needs ≥ 23.89 Gbit/s | FAIL: exceeds | Not ruled out | FAIL: exceeds | FAIL: exceeds | FAIL: exceeds | Not ruled out | Not ruled out |
| 3840×2160 @ 144 Hz needs ≥ 28.67 Gbit/s | FAIL: exceeds | Not ruled out | FAIL: exceeds | FAIL: exceeds | FAIL: exceeds | FAIL: exceeds | Not ruled out |
Same modes at 10-bit (HDR) colour
| Mode | HDMI 2.0 class 18 Gbit/s | HDMI 2.1 FRL 48 Gbit/s | USB-C Alt Mode 2 lanes, DP 1.2 | USB-C Alt Mode 2 lanes, DP 1.4 | DP 1.2 HBR2 (4 lanes) | DP 1.4 HBR3 (4 lanes) | DP 2.x UHBR20 |
|---|---|---|---|---|---|---|---|
| Usable payload, Gbit/s | 14.40 (DERIVED) | 42.67 (DERIVED) | 8.64 | 12.96 | 17.28 | 25.92 | 77.37 |
| 1920×1080 @ 144 Hz needs ≥ 8.96 Gbit/s | Not ruled out | Not ruled out | FAIL: exceeds | Not ruled out | Not ruled out | Not ruled out | Not ruled out |
| 1920×1080 @ 240 Hz needs ≥ 14.93 Gbit/s | UNKNOWN: over DERIVED payload | Not ruled out | FAIL: exceeds | FAIL: exceeds | Not ruled out | Not ruled out | Not ruled out |
| 2560×1440 @ 144 Hz needs ≥ 15.93 Gbit/s | UNKNOWN: over DERIVED payload | Not ruled out | FAIL: exceeds | FAIL: exceeds | Not ruled out | Not ruled out | Not ruled out |
| 2560×1440 @ 165 Hz needs ≥ 18.25 Gbit/s | FAIL: exceeds | Not ruled out | FAIL: exceeds | FAIL: exceeds | FAIL: exceeds | Not ruled out | Not ruled out |
| 2560×1440 @ 240 Hz needs ≥ 26.54 Gbit/s | FAIL: exceeds | Not ruled out | FAIL: exceeds | FAIL: exceeds | FAIL: exceeds | FAIL: exceeds | Not ruled out |
| 3440×1440 @ 100 Hz needs ≥ 14.86 Gbit/s | UNKNOWN: over DERIVED payload | Not ruled out | FAIL: exceeds | FAIL: exceeds | Not ruled out | Not ruled out | Not ruled out |
| 3440×1440 @ 144 Hz needs ≥ 21.40 Gbit/s | FAIL: exceeds | Not ruled out | FAIL: exceeds | FAIL: exceeds | FAIL: exceeds | Not ruled out | Not ruled out |
| 3440×1440 @ 165 Hz needs ≥ 24.52 Gbit/s | FAIL: exceeds | Not ruled out | FAIL: exceeds | FAIL: exceeds | FAIL: exceeds | Not ruled out | Not ruled out |
| 3840×2160 @ 60 Hz needs ≥ 14.93 Gbit/s | UNKNOWN: over DERIVED payload | Not ruled out | FAIL: exceeds | FAIL: exceeds | Not ruled out | Not ruled out | Not ruled out |
| 3840×2160 @ 120 Hz needs ≥ 29.86 Gbit/s | FAIL: exceeds | Not ruled out | FAIL: exceeds | FAIL: exceeds | FAIL: exceeds | FAIL: exceeds | Not ruled out |
| 3840×2160 @ 144 Hz needs ≥ 35.83 Gbit/s | FAIL: exceeds | Not ruled out | FAIL: exceeds | FAIL: exceeds | FAIL: exceeds | FAIL: exceeds | Not ruled out |
Calculated refresh ceilings
The highest refresh rate each link could carry at 8-bit RGB if there were no blanking at all. Treat it as a hard upper bound: if your target is above it, that link cannot do it.
| Resolution | HDMI 2.0 class 18 Gbit/s | HDMI 2.1 FRL 48 Gbit/s | USB-C Alt Mode 2 lanes, DP 1.2 | USB-C Alt Mode 2 lanes, DP 1.4 | DP 1.2 HBR2 (4 lanes) | DP 1.4 HBR3 (4 lanes) | DP 2.x UHBR20 |
|---|---|---|---|---|---|---|---|
| 1920×1080 | 289.3 Hz | 857.3 Hz | 173.6 Hz | 260.4 Hz | 347.2 Hz | 520.8 Hz | 1554.6 Hz |
| 2560×1440 | 162.7 Hz | 482.2 Hz | 97.6 Hz | 146.4 Hz | 195.3 Hz | 292.9 Hz | 874.4 Hz |
| 3440×1440 | 121.1 Hz | 358.8 Hz | 72.6 Hz | 109 Hz | 145.3 Hz | 218 Hz | 650.7 Hz |
| 3840×2160 | 72.3 Hz | 214.3 Hz | 43.4 Hz | 65.1 Hz | 86.8 Hz | 130.2 Hz | 388.6 Hz |
| 5120×1440 | 81.3 Hz | 241.1 Hz | 48.8 Hz | 73.2 Hz | 97.6 Hz | 146.4 Hz | 437.2 Hz |
Step-by-step guides
External monitor not detected or no signal: the fix order, including USB-C “Display connection might be limited”.
Monitor stuck at 60 Hz: find the part that caps your refresh rate.
USB-C dock and adapter display limits: lanes, DisplayLink, Thunderbolt and MST.
Can’t enter BIOS but Windows starts? If there is no picture until Windows loads, switch to the Fast Boot troubleshooter.
Console & handheld display hub: PS5, Xbox, Switch 2 and Steam Deck no-signal and 120 Hz checks.
Sources
Standards bodies (VESA, HDMI Forum, HDMI Licensing Administrator) and vendor support documentation (Microsoft, Plugable). Check times are when ELORUMTECH last read each page. No exact product is rated on this page.
- VESA — Why DisplayPort — VESA, checked 2026-10-17 23:58 CEST
- VESA — early certification program for HBR3 — VESA, checked 2026-10-17 23:58 CEST
- VESA / AMD — Display Summit USA 2016 (DisplayPort link-rate table) — VESA, checked 2026-10-17 23:59 CEST
- VESA — UHBR device certification and DP40/DP80 cables — VESA, checked 2026-10-17 23:58 CEST
- VESA — DisplayPort on the USB Type-C connector (DP Alt Mode) — VESA, checked 2026-10-17 23:58 CEST
- VESA — DisplayPort Alt Mode overview — VESA, checked 2026-10-17 23:58 CEST
- HDMI Forum — HDMI Specification 2.0 release — HDMI Forum, checked 2026-10-17 23:58 CEST
- HDMI Licensing Administrator — HDMI 2.1 — HDMI LA, checked 2026-10-17 23:58 CEST
- Microsoft Support — Troubleshoot external monitor connections in Windows — Microsoft, checked 2026-10-17 23:58 CEST
- Microsoft Support — Fix USB-C problems in Windows — Microsoft, checked 2026-10-17 23:58 CEST
- Microsoft Support — Change the refresh rate on your monitor in Windows — Microsoft, checked 2026-10-17 23:58 CEST
- Microsoft Learn — Windows USB Type-C troubleshooting notifications — Microsoft, checked 2026-10-17 23:58 CEST
- Microsoft Support — Connect Surface to an external display — Microsoft, checked 2026-10-18 00:07 CEST
- Plugable KB — Can I connect my high refresh rate monitor to a Plugable dock? — Plugable, checked 2026-10-17 23:58 CEST (page updated 2026-09-25)
- Plugable KB — How to determine your USB-C port video capabilities — Plugable, checked 2026-10-17 23:58 CEST (page updated 2026-08-20)
- Plugable KB — "Display connection might be limited" with a USB-C dock or adapter — Plugable, checked 2026-10-17 23:58 CEST (page updated 2023-06-06)
- Plugable KB — How to set the display refresh rate in Windows 11 — Plugable, checked 2026-10-17 23:58 CEST (page updated 2026-08-28)
- Plugable KB — Will the UD-MSTH3 support three 4K displays? — Plugable, checked 2026-10-17 23:58 CEST (page updated 2026-08-03)
FAQ
Why does the solver say FAIL for my refresh rate?
FAIL means a documented link or part limit already rules the mode out. Example on this page: 3440×1440 at 165 Hz needs more active-pixel bandwidth than an HDMI 2.0-class 18 Gbit/s link can carry.
What does UNKNOWN mean in the result?
UNKNOWN means nothing on the page rules the mode out, but something required is still missing — often the monitor’s exact timing for that input, or a cable certification.
When can the solver say PASS?
PASS needs the exact monitor model to list your mode for that input, plus documented capability on every part of the chain. A quick check from spec-sheet classes never says PASS.
Why check each part of the cable/dock chain?
The connection is only as good as its weakest part: computer output, anything in between (dock or adapter), the cable, and the monitor input. The solver splits those parts and checks each one.
Where do the bandwidth numbers come from?
The page separates calculated active-pixel bandwidth from full-timing payloads and cites the VESA, HDMI and other sources listed in the Sources section. Where a figure is missing, the result stays UNKNOWN instead of inventing one.