🖥Monitor stuck at 60 Hz

By the Devicedial test desk

Has anything actually asked for 144 Hz yet?

This is the first check because it is the most common answer. Plugging in a high-refresh monitor does not switch it to its highest mode: the display advertises what it can do, and the operating system picks a mode, which is very often the safe one. On Windows the setting lives in Settings → System → Display → Advanced display, on macOS under Displays. Set it explicitly, then re-run the refresh rate test to confirm the change reached the screen.

Two traps hide here. The setting is per display, so a second monitor can still be at 60 Hz while the first is at 144. And a fresh graphics driver, a new cable or a docking station can reset the mode without telling you — which is why a monitor that ran at 144 Hz last month can be at 60 today with nothing obviously changed.

Is it the cable or the port?

Frequently, and the monitor’s manual answers it faster than any forum. Many 144 Hz displays offer their full rate only over DisplayPort while capping their HDMI input at 60 Hz, so the same monitor behaves differently depending on which socket the cable is in. Where both are available, DisplayPort is the one to try first.

The reason is bandwidth, and the arithmetic is unforgiving: at the same resolution, 144 Hz carries 2.4 times as many pixels per second as 60 Hz. A link that cannot carry the higher mode does not show an error — it negotiates down to something that fits, which looks exactly like a driver problem. Suspect the cable in particular when the higher rate is offered in the settings list but produces a black screen or reverts after a few seconds.

Why does this page report a different number than Windows?

Because a browser cannot see the panel. What a web page can do is time the gaps between successive animation frame callbacks, which measures the rate at which frames were actually delivered to that tab. The control panel reports the mode the display is set to. Those are different quantities and they disagree for reasons that are all real:

• the tab was in the background, where browsers throttle animation deliberately;
• hardware acceleration is off, so compositing runs on the CPU and cannot keep up;
• the browser window is on a second, slower display;
• the machine is in a power-saving mode, or the system is applying a variable refresh rate;
• something else on the machine is holding the GPU busy.

In every one of those cases the panel setting is untouched and the delivered rate is genuinely lower — so the browser’s number is the one describing what you are looking at. Keep the tab in the foreground and the window on the monitor you are testing, and the two numbers usually converge.

Why does my laptop behave differently on battery?

Because a high-refresh panel is expensive to run. Laptops commonly drop to 60 Hz when unplugged, either through a battery-saving option in the operating system, through the graphics vendor’s control panel, or through the dynamic refresh rate feature that raises the rate for scrolling and gaming and lowers it for static content.

The test for this is thirty seconds long: run the refresh rate test on battery, plug the charger in, run it again. If the number moves, the answer is power management and nothing is broken.

What does the extra refresh rate actually buy?

Two separate things, and it is worth knowing which one you care about.

Smoothness is the frame time: 16.7 ms at 60 Hz, 6.9 ms at 144 Hz. Latency is the waiting — a finished frame can sit for a whole frame period before it is shown, so at the same 1000 Hz polling rate the worst-case press-to-pixel delay falls from 17.7 ms to 7.9 ms. That 9.7 ms is more than any mouse can save you, which is the argument for fixing the display before buying peripherals. The input lag chart works out both columns for nine refresh rates, and the polling rate test measures the other half of the pair on your own mouse.

If the screen is misbehaving in a way that is not about timing — a fixed dot that never changes colour — that is a panel defect rather than a mode problem, and the dead pixel test with the guide to dead versus stuck pixels is the right place to start instead.