By Walter Jobs, Technology writer and editor · Published 9 October 2026
Short answer: the requirements almost certainly described 1080p and you are not playing at 1080p. That single mismatch explains more of these cases than everything else combined, because moving to 1440p roughly doubles the work and moving to 4K roughly quadruples it, while the published table said nothing about which resolution it meant.
Here are eight reasons in the order they are worth checking, with what each one looks like so you can tell them apart.
1. You are playing above the resolution the spec assumed
Recommended specs conventionally describe 1080p at high settings and roughly 60 frames per second. Nothing says so on the page.
| You play at | Work relative to 1080p | Expect from a recommended card |
|---|---|---|
| 1080p | Baseline | Roughly what was promised |
| 1440p | About 1.8 times | Noticeably short, around 35 to 45 fps |
| 4K | About 4 times | Not close. Around 20 to 30 fps |
Test: set the game to 1080p for a minute. If performance transforms, you have found it, and the fix is a settings decision rather than a hardware one.
2. You are at Ultra and the spec meant High
The step from High to Ultra frequently costs a quarter of your frame rate for changes most people cannot identify in motion: shadow resolution, distant detail, and reflection quality in scenes you are running past.
Test: drop to High. If you gain twenty percent and cannot see what changed, that is your answer, and which graphics settings to use goes through which ones are worth keeping.
3. The recommendation quietly assumed upscaling
An increasing number of recommended specs are written with DLSS or FSR switched on, without saying so. If the publisher assumed Quality mode and you are rendering at native resolution, you are doing roughly twice the pixel work their figure described.
Test: turn on the game’s upscaling at Quality. A large jump suggests the table assumed it all along.
4. One memory stick instead of two
Requirements state a capacity and never mention channels. A single 16 GB stick satisfies a 16 GB requirement on paper while feeding the processor through half the available width, and the loss is real and continuous in anything processor heavy.
Test: Task Manager, Performance, Memory, read the Slots used line. “1 of 2” means you are running single channel and a second matching stick is the cheapest fix available.
5. The game is still compiling shaders
Severe stutter during your first hour in a new area, improving as you spend time there and never returning. This is not a hardware shortfall, it is work the game does once.
Test: does it get better the second time you walk the same route? Then it was compilation, and nothing needs buying.
6. You are short of video memory rather than card speed
A card with the right name and less memory than the requirement asked for fails differently from a slow card. The average frame rate can look acceptable while the experience is ruined by spikes, because textures are being shuttled across the bus mid frame.
Test: drop texture quality one step and leave everything else alone. If the stutter disappears while the average barely moves, memory was the constraint.
7. The machine is throttling
Fine for the first ten minutes, then settling lower and staying there. Requirements assume hardware running at its rated clocks, and a dusty cooler, an aged thermal interface or a restricted case means yours is not.
Test: log temperature and clock speed for fifteen minutes. Falling clocks against rising temperature is the signature, and this one is the only cause on the list that arrives on a delay.
8. Something else is taking the processor
A launcher updating in the background, a cloud sync, a scheduled scan or a browser doing something expensive. Requirements describe a game running alone, and yours is not.
Test: sort Task Manager by processor usage while the game runs windowed and look at what sits above it.
Narrowing it down quickly
| What you notice | Start at |
|---|---|
| Consistently low, from the first second | Reasons 1, 2, 3 and 4 |
| Fine, then worse after ten minutes | Reason 7 |
| Average is fine but it hitches | Reasons 5 and 6 |
| Unpredictable, comes and goes | Reason 8 |
| Only in this one game | Reasons 1, 2 and 3 |
If none of them fit and your card is simply sitting idle, the limit is upstream of the game and low GPU usage while gaming works through the nine causes of that.
Check what you should actually be getting
Before chasing any of this, it is worth knowing what your parts ought to produce in that specific game at your specific resolution. Our Can I Run It checker gives an estimate for your pair at the resolution you choose, next to the requirements the publisher published. If your real frame rate is close to the estimate, the machine is behaving and your expectations came from a table that never mentioned resolution. If it is far below, something on this page is costing you the difference.
Frequently asked questions
Why does my game run badly when my specs are above recommended?
Usually resolution. Recommended specs conventionally describe 1080p, and if you are at 1440p you are asking for roughly 1.8 times the graphics work with no extra allowance made for it. Set the game to 1080p briefly and see whether the problem disappears.
Can a game run badly because of my monitor?
Your monitor sets the resolution your card must fill, which is a large part of the workload, so in that sense yes. It cannot otherwise slow the machine down. What it can do is hide a problem or create a false one through a refresh rate left at 60 Hz on a panel capable of more.
Is it the game’s fault or mine?
Sometimes genuinely the game’s. A release with widely reported performance problems is not something your settings will fix, and patches often do. Before concluding that, rule out resolution, single channel memory and shader compilation, since those three account for most cases that get blamed on the developer.
Will reinstalling the game help?
Rarely, with one exception: it clears the shader cache, which means the game recompiles and you get the first hour of stutter all over again. That makes reinstalling counterproductive for the most common stutter cause rather than a fix for it.
Do background launchers really cost that much performance?
A launcher sitting idle costs almost nothing. One downloading an update, verifying files or running an overlay costs real processor time, and it does so unpredictably, which is why this cause gets described as the game randomly stuttering.
The resolution multipliers above are the scaling our own model applies and are approximate; real games vary with how much of their work is pixel bound. The method is on how we calculate this.