Frame rate, stutter and graphics problems

Short answer

Work out the pattern before changing settings. A frame rate that is low and steady everywhere points at the graphics settings or the hardware. A frame rate that collapses only when a lot is happening points at the processor or at effects settings. Brief freezes on an otherwise smooth game point at storage, shader compilation or a background process. A gradual slide during long sessions on a laptop points at heat. Change one variable at a time, and measure with frame time rather than an average.

What is actually setting the limit

Every frame passes through several stages. The processor works out what exists in the scene and issues drawing instructions; the graphics processor turns those instructions into pixels; the result is handed to the display, which shows it at a fixed refresh rate. Whichever stage takes longest sets your frame rate, and everything else waits.

This matters because the usual advice — turn the settings down — only helps when the graphics processor is the slowest stage. If the processor is the limit, dropping texture quality changes almost nothing, and the setting to look for is the one that reduces how much the game has to keep track of: draw distance, shadow detail, crowd or effect density.

Average frame rate hides the problem

An average of sixty frames per second can describe a smooth game or an unpleasant one. Frame time — how long each individual frame took — shows the difference immediately: a steady line feels smooth, and occasional spikes feel like stutter even when the average looks healthy. Most graphics control panels and several free monitoring tools display frame time, and it is the number to watch while testing a change.

Steadily low, everywhere in the game

Symptom

The frame rate is roughly the same whether the screen is busy or empty, and it is below what you expected from the hardware.

Check first: Resolution and the scaling setting. Rendering above the display's native resolution, or leaving a resolution scale above one hundred per cent, is the most expensive single choice available and is easy to set by accident.
Then: Whether the game is using the right graphics hardware. A laptop with both integrated and discrete graphics can run a game on the integrated one, which produces exactly this pattern. Both Windows graphics settings and the manufacturer's control panel let you assign a specific application.
Then: Driver version. A current driver from the hardware manufacturer, downloaded from that manufacturer, is worth the few minutes it takes. On macOS the equivalent is applying the pending system update.
Then: Power settings. A machine in a battery-saving or balanced profile will deliberately hold clocks down. On a laptop, plug it in and set the profile to favour performance before drawing conclusions.

Fine until the screen gets busy

A frame rate that sits comfortably high in quiet moments and falls sharply when many objects, effects or players appear is the classic sign that the processor, not the graphics card, is the bottleneck. The settings that help are the ones that reduce work rather than visual polish.

Which settings tend to cost the most, and which stage they load
Setting	Loads mainly	Typical cost	Visual loss when reduced
Resolution and resolution scale	Graphics processor	Very high	Noticeable — reduce last, and prefer the display's native resolution
Shadow quality and distance	Both	High	Moderate; often the best single saving
Effects and particle density	Both	High during heavy action	Low outside busy moments
Draw distance / detail distance	Processor	High in open scenes	Distant objects appear later
Anti-aliasing	Graphics processor	Moderate	Edges look harder
Texture quality	Graphics memory	Low until memory runs out, then severe	Surfaces look softer
Post-processing (bloom, motion blur)	Graphics processor	Low to moderate	Mostly stylistic

The practical method is to set everything to a low preset, confirm that the game then runs well, and raise settings one at a time in the order above. It takes ten minutes and produces a configuration you understand, rather than one you copied from a video made for different hardware.

Smooth, then a freeze for a moment

Short, repeated hitches are a separate fault from a low frame rate, and turning settings down usually does not touch them.

Shader compilation. Modern games build shaders the first time an effect appears, which causes hitching early in a session or after a patch. It normally settles once the cache is built; deleting the shader cache resets that process and it starts again.
Storage. A game streaming assets from a slow or nearly full drive stutters while it waits. Leave free space on the drive holding the game, and avoid running it from an external drive over a slow connection.
Background processes. Cloud sync, antivirus scheduled scans, browser tabs playing video and launcher updates all take time in bursts. Check what is scheduled rather than guessing.
Overlays and capture. Recording or streaming software adds a cost that appears as periodic spikes. Test one session with all of it closed.
Memory pressure. When system or graphics memory runs short, the machine starts moving data in and out, and the result is stutter rather than a lower average. Closing other applications is a genuine fix here.

It starts well and gets worse over an hour

Performance that declines as a session goes on, usually alongside louder fans, is thermal. Processors and graphics chips reduce their own clock speed to stay within a temperature limit, which is protective behaviour rather than a fault.

Give the machine air. Laptops on a bed, a couch or a thick rug block their intakes. A hard flat surface is worth more than any software setting.
Clear the dust. Vents and fans collect it, and the effect is gradual enough that people attribute the slowdown to the game.
Check the ambient temperature. Through an Australian summer, a room at thirty-five degrees leaves a laptop very little headroom; the same machine behaves differently in the evening.
Cap the frame rate. Limiting frames to the display's refresh rate reduces heat and power draw considerably with no visible loss, because frames above the refresh rate are never shown.

Tearing, input lag and the display itself

Some complaints described as performance problems are display configuration. A picture torn across the middle during fast movement is the frame rate and the refresh rate being out of step, which vertical synchronisation or a variable refresh rate feature resolves. Sluggish response with a high frame rate is often a display running at a lower refresh rate than it supports — worth checking in the operating system's display settings, because a monitor capable of a high refresh rate does not always default to it.

Full screen, borderless window and window modes also behave differently. Borderless is convenient for switching applications, but on some systems it adds a frame of latency compared with exclusive full screen. If responsiveness matters more than switching, try exclusive full screen and compare.

What not to spend time or money on

Optimiser utilities, registry cleaners, memory boosters and paid driver updaters are a persistent category of software that promises frame rate and delivers, at best, nothing. The genuine improvements are free: the manufacturer's own driver, adequate free disk space, fewer background processes, a clean air path and settings chosen deliberately. Treat any tool that reports urgent problems on your computer and then asks for payment as the pattern Scamwatch describes, and close it.

Measuring a change properly

Pick one repeatable scene — the same map, the same opening minute, the same view — so that two measurements can be compared at all.
Record the frame time graph, not just an average, for a minute of ordinary play.
Change exactly one setting, then repeat the same scene.
Keep a short note of what you changed. After a dozen changes, nobody remembers the original configuration, and restoring defaults undoes the useful changes along with the useless ones.

Low frame rates, stutter and graphics faults