Disclosure: As an Amazon Associate, reviewstook.com earns from qualifying purchases. Links to Amazon on this page are affiliate links; they cost you nothing extra.
You buy a capable graphics card, the frame counter says 90 frames per second, and the game still feels broken. Every few seconds the picture hitches, the mouse feels heavy, or the whole scene seems to skip. That is stutter, and it is one of the most misunderstood problems in PC gaming because the average frame rate can look perfectly healthy while the experience is poor.
This guide explains what stutter actually is, how to tell the different kinds apart, and how to work through the causes in a sensible order so you do not waste a weekend changing settings at random. It is written from general PC hardware knowledge and standard troubleshooting practice rather than from lab testing of specific products, so treat the thresholds as rules of thumb and always confirm model-specific details with the maker.
By the Reviewstook Editorial Team. Last updated: November 1, 2026.
Stutter Is About Frame Time, Not Average FPS
A frame rate counter reports how many frames were drawn in the last second. That is an average, and averages hide spikes. If a game draws 59 frames in 10 milliseconds each and then one frame that takes 400 milliseconds, the counter still reads close to 60, but you clearly feel that one long frame as a freeze.
The number that matters for smoothness is frame time, the time between one frame and the next. At 60 frames per second each frame should take about 16.7 milliseconds. At 144 frames per second it should take about 6.9 milliseconds. Smoothness comes from those intervals being consistent. Stutter is what you see and feel when they are not.
| Target frame rate | Ideal frame time | What a spike feels like |
|---|---|---|
| 60 FPS | about 16.7 ms | A frame at 33 ms is a visible hitch |
| 120 FPS | about 8.3 ms | A frame at 25 ms is noticeable |
| 144 FPS | about 6.9 ms | Even small spikes break fluid motion |
| 240 FPS | about 4.2 ms | Very sensitive to CPU and background load |
Because of this, the first rule of diagnosing stutter is to stop trusting the average. Use a tool that shows a frame time graph. Many graphics driver overlays, game launchers and free monitoring programs can draw one. A smooth game shows a flat line. A stuttering game shows spikes, and the pattern of the spikes tells you a lot about the cause.
The Four Kinds of Stutter
People use the word stutter for several different problems. Separating them early saves a lot of time because each has a different cause.
1. Periodic stutter
The hitch happens at regular intervals, for example every few seconds or every minute. This usually points to something running on a schedule in the background: a sync or backup tool, an overlay polling for updates, a monitoring utility, antivirus scans, or a driver doing periodic work. It can also come from a game with a timed autosave.
2. Random spikes
The hitches arrive with no pattern. Random spikes often come from CPU contention, too little memory, a storage drive that stalls, or a game that streams assets from disk as you move through the world.
3. Hitching when something new appears
The hitch happens when you enter a new area, see a new enemy type, or use a new effect for the first time and then goes away on the second try. That is the signature of shader compilation or asset loading, not of weak hardware in the usual sense.
4. Constant judder
The game never feels smooth, and motion has a stepped look even when the frame rate seems steady. This is usually a frame pacing or display sync problem, such as a frame rate that does not match the monitor’s refresh rate, a variable refresh rate setting that is misconfigured, or a mismatch between the game’s frame cap and the display.
Quick Diagnostic Table
Use this table as a map before changing anything. Find the row that matches your symptom and start with the first likely cause.
| Symptom | Most likely causes | First thing to try |
|---|---|---|
| Hitch every few seconds on a timer | Background app, overlay, scheduled task | Close overlays and monitoring tools, test again |
| Hitch the first time a new area or effect appears | Shader compilation or asset streaming | Let shaders finish compiling, play the same area twice |
| Frame rate drops hard in busy scenes | CPU limit or not enough memory | Watch CPU and memory use while playing |
| Long freezes, then recovers | Storage stall, virtual memory paging, overheating throttle | Check free space, memory use and temperatures |
| Smooth number but stepped motion | Frame pacing or sync mismatch | Check refresh rate, sync mode and frame cap |
| Stutter only in one game | Game or driver issue | Update the game and graphics driver, check the game’s known issues |
| Stutter in every game | System-level cause: heat, memory, storage, power plan | Run through the system checks below |
Step 1: Establish a Baseline
Before you change settings, record what is happening. Pick one game and one repeatable spot, such as a particular route in the game or a built-in benchmark. Open a monitoring overlay that shows frame time, graphics card usage, CPU usage, memory usage and temperatures. Play for five minutes and note when the stutter happens and what the numbers do at that moment.
Three readings give you most of the answer:
- Graphics card usage near 95 to 100 percent during the stutter suggests you are graphics limited. Lower resolution or graphics settings should help.
- Graphics card usage well below that, with one CPU core near the limit suggests a CPU bottleneck. Many games depend heavily on one or two fast threads, so total CPU usage can look low while a single core is saturated.
- Memory usage near the total available, or the page file growing suggests you ran out of RAM and Windows is moving data to disk.
If none of those explains the spikes, look at temperatures and storage next.
Step 2: Rule Out Background Software
Periodic and random stutter often comes from software you forgot was running. The usual suspects are:
- Overlays from game launchers, chat apps, recording tools and hardware utilities.
- Monitoring programs that poll sensors many times per second.
- Cloud sync and backup clients that scan files while you play.
- Browser tabs with video, which can use graphics memory and decode resources.
- RGB and peripheral control software that polls devices.
- Antivirus scans and Windows update tasks running in the background.
The cleanest way to test is a temporary reduction. Close everything you can, start the game, and check whether the pattern changes. If the stutter vanishes, add programs back one at a time until it returns. This feels tedious, but it is the only reliable way to find a periodic offender.
Step 3: Check Memory and the Page File
Modern games can use a lot of memory, and a PC with too little will start moving data to the page file on the drive. That is much slower than RAM and produces long, ugly hitches.
As a rough guide, 16 GB of RAM is a workable minimum for current games, and 32 GB gives comfortable headroom if you also keep a browser, voice chat and streaming software open. Memory also needs to be installed correctly. Two matched sticks in the correct slots run in dual-channel mode, which gives noticeably more memory bandwidth than a single stick. Check your motherboard manual for the recommended slots and see our DDR5 RAM list if you are upgrading.
Also check that memory is running at its rated speed. Many kits run at a slower default until you enable an XMP or EXPO profile in the BIOS. An overly aggressive memory overclock can cause instability that looks like stutter, so if you recently enabled a profile and problems began, test with the profile off.
Step 4: Look at Storage
A game that streams data while you move relies on storage that responds quickly. Hard drives struggle with this, especially in open-world games. If you still run games from a hard drive, moving them to a solid state drive is one of the most effective fixes for hitching during exploration. Our SSD buying guide explains SATA versus NVMe and how much capacity to buy.
Other storage issues to check:
- Free space. An almost full drive slows down because it has little room to manage writes. Keep a healthy margin free.
- Drive health. A failing drive can stall. Check the drive’s health status with the maker’s tool or a reputable utility.
- Thermal throttling. Fast NVMe drives can slow when hot. See whether your drive has a heatsink and whether it sits in a hot spot under the graphics card.
- Shared bandwidth. Copying large files or running a download while playing can compete with the game for the same drive.
Step 5: Temperatures and Throttling
When a processor or graphics card gets too hot, it reduces its speed to protect itself. The result is a frame rate that starts fine and then degrades, or sudden dips during long sessions. Watch temperatures and clock speeds during play. If clocks drop as temperatures climb, you have a cooling problem.
Common causes are dust in filters and heatsinks, poor case airflow, a cooler that is too small, dried thermal paste, or fans set to a quiet curve that never ramps up. Clean filters and fans, make sure intake and exhaust fans move air in a sensible direction, and make sure the cooler is mounted firmly. If you need a bigger cooler, see our AIO liquid cooler list and the power supply list for parts that matter to stability.
A weak or failing power supply can also cause odd behavior under load, including stutter and crashes. If problems appear only when the graphics card is working hard, a power supply with too little headroom is worth considering. Our power supply guide covers sizing.
Step 6: Shader Compilation and First-Time Hitches
Many modern games compile shaders, which are small programs that tell your graphics card how to draw materials and effects. If a game compiles a shader the first time it needs it, you get a hitch exactly when something new appears. Some games compile shaders on first launch or after a driver update, and some do it while you play.
What helps:
- Let the game finish any shader compilation step it offers at launch.
- Play the same area twice. If the second pass is smooth, shader compilation was the cause.
- Avoid clearing the shader cache unless instructed, because you will trigger the hitching again.
- Keep the graphics driver stable. A driver update can invalidate the cache and cause a fresh round of compilation.
This kind of stutter is a game design issue as much as a hardware one, so a faster graphics card does not always remove it.
Step 7: Display and Frame Pacing
If the frame rate looks fine but motion is stepped, the problem is often synchronization between the game and the monitor.
- Check the refresh rate. A high refresh rate monitor often runs at 60 Hz until you change it in the operating system’s display settings. Our refresh rate guide explains how to check it.
- Use variable refresh rate correctly. FreeSync and G-SYNC match the monitor to your frame rate, but they need to be enabled in both the monitor menu and the graphics driver, and the game should run within the monitor’s supported range.
- Cap the frame rate. Capping slightly below the maximum refresh rate often gives steadier frame times than letting the game run uncapped.
- Test vertical sync. Traditional vsync can add input delay but gives stable pacing on fixed refresh monitors. Compare both options.
- Use a good cable. A damaged or unsuitable cable can cause signal dropouts that look like flicker or stutter. Our gaming monitor buying guide lists what to check on ports and cables.
Step 8: Power Plan, Drivers and Windows Settings
System settings can quietly hold your hardware back.
- Power plan. A power saving plan can reduce processor speed. Use a balanced or high performance plan on a desktop, and check that a laptop is plugged in.
- Graphics driver. Use a current driver from the graphics maker. If a problem began after an update, try the previous version. A clean driver installation removes leftover files.
- Chipset and storage drivers. Motherboard makers publish drivers that affect performance and stability. Keep them current.
- Game mode and hardware acceleration. Windows features can help or hurt depending on the system. Test with them on and off.
- Background recording. Always-on recording features use encoder and storage resources. Turn them off to test.
Change one setting at a time and retest, or you will not know which change helped.
Step 9: CPU Bottlenecks and Core Parking
Some games stutter because a single thread cannot keep up. This happens more at high frame rates and in crowded scenes. Signs include one core pinned near 100 percent and a graphics card that is not fully used.
Options are to lower CPU-heavy settings such as crowd density, view distance and physics detail, to cap the frame rate to a level your processor can hold steadily, or to upgrade the processor. Processors with large cache are popular for gaming because many games benefit from fast access to data. Our gaming CPU buying guide and gaming CPU list explain the trade-offs.
On laptops, check that the system is not limiting power to the processor because of battery settings or heat.
Step 10: When the Fault Is the Game
Sometimes the hardware is fine and the game is the problem. Signs are stutter in one title only, reports from other players with similar hardware, and improvement after game patches. In that case:
- Check the developer’s notes and community discussion for known issues.
- Try different graphics API options if the game offers them.
- Verify game files through the launcher.
- Lower the settings that are known to be heavy in that game, such as shadows or ray tracing.
- Wait for a patch rather than replacing hardware.
A Practical Order of Operations
If you want one checklist, work in this order, retesting after each step:
- Record a baseline with a frame time overlay.
- Close background software and overlays.
- Check memory use and that RAM runs in dual channel at its rated speed.
- Check storage space, health and where the game is installed.
- Watch temperatures and clocks for throttling.
- Test shader compilation by replaying the same area.
- Verify refresh rate, sync mode and frame cap.
- Update graphics and chipset drivers, and review the power plan.
- Look for a CPU bottleneck and adjust CPU-heavy settings.
- Check whether the issue is specific to one game.
When an Upgrade Is the Honest Answer
Settings and cleaning fix many problems, but sometimes hardware really is the limit. Use the evidence from your baseline to decide.
| Evidence | Likely upgrade |
|---|---|
| Graphics card at full load, frame time spikes in heavy scenes | Faster graphics card, or lower resolution and settings |
| One CPU core saturated, graphics card underused | Faster processor, possibly with a new motherboard |
| Memory near full, page file in use | More RAM, matched in a dual-channel kit |
| Game on a hard drive, hitches while exploring | Solid state drive |
| Clocks drop as temperatures climb | Better cooling and airflow |
| Crashes or stutter only under heavy load | Check power supply headroom |
Match the upgrade to the evidence. Replacing the graphics card when the real limit is a hard drive will not help.
Frequently Asked Questions
Why does my game stutter even though my FPS is high?
Average frame rate hides frame time spikes. A few very long frames among many short ones still feel like stutter. Use a frame time graph to see the spikes and then look for the cause using the steps above.
Does a higher refresh rate monitor fix stutter?
Not by itself. A higher refresh rate can make frame time variations easier to see, and variable refresh rate can hide small variations, but it cannot fix a stall caused by memory, storage or the processor.
Is stutter caused by the CPU or the GPU?
It can be either. Look at graphics card usage during the stutter. If it is near full, the graphics card is the limit. If it is low and one CPU core is saturated, the processor is the limit. If neither, look at memory, storage and temperatures.
How much RAM do I need to avoid stutter?
16 GB is a workable minimum for many current games, and 32 GB gives more headroom if you multitask. Running in dual-channel mode matters as well as the total amount.
Will an SSD stop my game from stuttering?
It helps if the game streams data from a slow hard drive. It will not fix stutter caused by shader compilation, overheating or a CPU limit.
Should I cap my frame rate?
Often yes. A cap slightly below your monitor’s maximum refresh rate usually produces steadier frame times than running uncapped, and it reduces heat and noise.
Bottom Line
Stutter is a frame time problem, so measure frame time rather than average frame rate. Identify which of the four types you have, use the symptom table to pick a starting point, and work through background software, memory, storage, temperatures, shader compilation, display sync and drivers in that order. Change one thing at a time. If your evidence points to hardware, upgrade the part that your measurements show is the limit, not the one that is easiest to buy.