To fix stuttering, low FPS, and crashing in PC games, start with a clean GPU-driver installation, verify the game files, cap FPS below your monitor's refresh rate, reduce CPU-heavy settings, and check temperatures and background software. Don't throw every graphics option to Low at once: frame-time spikes, shader compilation, VRAM overflow, and CPU bottlenecks each need a different fix.
This guide targets Windows PC games broadly, including Steam, Epic Games Store, Xbox app, and standalone launches. The exact menu names vary by game, but the diagnostic method is consistent. If you want a quick hardware reference first, our PC requirements breakdown explains why minimum specifications rarely equal a smooth experience.
Find the real cause before changing settings
First, separate low average FPS from bad frame pacing. An FPS counter can report 90 frames per second while the game still feels awful if individual frames arrive at 8ms, 10ms, then 70ms intervals. That 70ms spike is the hitch your eyes notice. Enable a frame-time graph in MSI Afterburner with RivaTuner Statistics Server, CapFrameX, or the overlay built into your GPU software.
Play the same 60-second route three times: a busy city street, a combat encounter, or a save area that reliably causes trouble. Watch CPU usage, GPU usage, VRAM, RAM, temperatures, and clocks. A GPU sitting at 97–99% usage with stable clocks points to a graphics limit. GPU usage falling to 60–80% while one CPU thread is maxed suggests a processor or game-engine bottleneck. VRAM sitting at its limit often causes texture pop-in and sudden hitching rather than merely lower average FPS.
| Symptom | Likely Cause | First Test | Best Initial Fix |
|---|---|---|---|
| Low FPS everywhere | GPU or CPU below the game's target | Check GPU usage and clock speed | Use a balanced preset and lower resolution or CPU-heavy options |
| Brief hitches while entering areas | Shader compilation, asset streaming, or slow storage | Repeat the route after restarting | Allow shaders to finish and move the game to an SSD |
| FPS is high but motion feels uneven | Unstable frame times or uncapped rendering | View a frame-time graph | Cap FPS and configure V-Sync or VRR correctly |
| Crash after 10–30 minutes | Heat, memory instability, driver conflict, or leak | Log temperatures and RAM usage | Remove overclocks and test a clean driver install |
Also test with overlays disabled. Steam, Discord, Xbox Game Bar, GeForce Experience, Radeon Software, OBS, Overwolf, and RGB utilities can hook into the same rendering path. Disable one group at a time rather than changing ten variables and losing track of the result.
Repair drivers, files, and Windows dependencies
Driver problems are especially likely after a major game update, a Windows feature update, or a GPU upgrade. Download the current driver directly from the NVIDIA driver page or AMD support page. During installation, select the clean-install option when available. If the issue began immediately after updating, test the previous stable driver instead; newer isn't automatically better for every release.
For stubborn corruption, use Display Driver Uninstaller in Windows Safe Mode, disconnect the internet temporarily so Windows Update doesn't inject a generic driver, then install the downloaded package. This is worth doing when crashes mention nvlddmkm, amdkmdag, DXGI_ERROR_DEVICE_REMOVED, or a driver timeout. Don't use registry cleaners or random driver-updater utilities. They add risk without fixing the usual cause.
Next, verify the installation through the launcher. In Steam, open Properties, Installed Files, then Verify integrity of game files. Epic Games Launcher offers Manage and Verify. The Xbox app uses the game's Advanced options, where Repair and Reset may appear. Verification replaces missing executables and damaged archives, but it won't fix a broken configuration file or an incompatible mod.
Install or repair the Microsoft Visual C++ 2015–2022 Redistributables in both x64 and x86 versions, update DirectX through Microsoft's official installer when an older title requests it, and run Windows Update. You can also consult Microsoft's app repair guidance. If a game only crashes with mods, restore the vanilla install before blaming the engine.
For older titles, compatibility settings can help, but use them carefully. Disable fullscreen optimizations only when borderless or exclusive fullscreen behaves incorrectly. Avoid forcing Windows 7 compatibility mode on a modern game; it can break anti-cheat, HDR, or controller support.
Use a graphics profile that protects frame time
Start from the game's High preset, then adjust the settings that actually control performance. Resolution scaling is the largest GPU lever, while shadows, volumetric effects, reflections, and view distance can create expensive spikes. Texture quality mainly consumes VRAM: lowering it won't rescue a CPU-limited system, but it can stop streaming stalls on a card with 6GB or less.
| Setting | Recommended Value | Typical FPS Impact | Visual Trade-Off |
|---|---|---|---|
| Resolution scale | 90–100%; DLSS or FSR Quality if available | Very high | Slight softness at lower scale, strong performance gain |
| Ray tracing | Off or Low | High | Less accurate reflections, shadows, and global lighting |
| Shadows | Medium | Medium to high | Shorter shadow distance and softer detail |
| Volumetric fog and clouds | Medium or Low | Medium | Less dense atmosphere in foggy scenes |
| Reflections | Medium; disable hardware RT first | Medium | Lower reflection accuracy and update quality |
| View distance and object detail | High on strong CPUs, Medium on older CPUs | Medium | More pop-in and fewer distant objects |
| Textures | High only if VRAM remains under the limit | Low average, high hitch risk when overloaded | Lower surface detail and asset clarity |
Use upscaling intelligently. DLSS Quality at 1440p renders internally below native resolution and reconstructs the image; FSR 2 or FSR 3 can do a similar job on broader hardware. Avoid Ultra Performance except on a struggling laptop, where the shimmering and blur are usually worse than a lower native resolution. Frame generation can raise the displayed FPS, but it does not remove input latency or fix a poor base rate. Treat 60 real FPS plus frame generation very differently from 30 real FPS plus frame generation.
Set a cap that your system can hold in the hardest scene: 58 FPS for a 60Hz display, 117 for 120Hz, or 141 for 144Hz. A stable cap often feels smoother than an unlocked 75–110 FPS range. With G-SYNC or FreeSync, keep VRR enabled and cap a few frames below refresh. If you don't have VRR, test V-Sync on and off; tearing is annoying, but poorly implemented V-Sync can add latency.
Stop shader and asset-streaming stutter
Modern games increasingly compile shaders during the first launch or while you explore. That can cause short hitches when a new material, effect, or lighting combination appears. Let the game's shader-preparation screen finish completely, even if it takes several minutes. After a driver change, the shader cache may be rebuilt, so the first run can be worse than later sessions.
Don't repeatedly delete the shader cache as a general fix. Clearing it can help after corrupted driver data, but it guarantees another compilation cycle. NVIDIA's shader cache and AMD's reset option are useful troubleshooting tools, not performance buttons. If every play session stutters in the same places, keep the cache, update the game, and check whether the developer has acknowledged a shader issue.
Storage matters too. Install demanding open-world games on an SSD with at least 15–20% free capacity. A nearly full SATA SSD can struggle with temporary files, while an HDD may produce traversal stutter as the game streams textures and geometry. Pause downloads, cloud-sync jobs, and antivirus scans during testing. Windows Security exclusions should be used cautiously and only for a trusted game folder.
RAM pressure can look like a GPU problem. Close browsers with dozens of tabs, launchers, and editing software. If total system memory reaches the physical limit, Windows starts paging to disk and frame times can explode. The page file should normally remain system-managed; disabling it is a common bad tweak that turns recoverable memory pressure into crashes.
For more examples of game-specific performance work, compare our ELEX crash and FPS fixes and EscapeVR troubleshooting guide. The recurring lesson is simple: streaming-heavy games need stable storage, shader caches, and enough free memory.
Diagnose crashes, overheating, and unstable hardware
Crashes with no error message deserve a hardware check. Log CPU and GPU temperatures with HWiNFO or Afterburner while reproducing the failure. A GPU running near its thermal limit may reduce clocks first, then crash when voltage or memory becomes unstable. A CPU that reaches its thermal ceiling can also produce clock drops that feel like stutter before the application closes.
| Test | What It Reveals | Safe Action | Warning Sign |
|---|---|---|---|
| Remove GPU overclock | Whether core or memory tuning is unstable | Return core, memory, and voltage to default | Crashes disappear at stock settings |
| Run Windows Memory Diagnostic or MemTest86 | RAM errors and unstable EXPO/XMP | Test with EXPO/XMP disabled | Any reported memory error |
| Watch temperatures and clocks | Thermal throttling or cooling failure | Clean dust and check fan curves | Clock speed collapses under load |
| Check Event Viewer | Application, driver, or hardware timeout clues | Match the timestamp to the crash | Repeated display-driver or WHEA errors |
Temporarily disable XMP or AMD EXPO if games crash under load. Memory profiles are overclocks, even when the motherboard advertises them as a one-click feature. If stability returns at JEDEC defaults, update the BIOS, test a slightly lower memory speed, or adjust the kit according to the motherboard manufacturer's guidance. Never increase voltage blindly.
Check Event Viewer under Windows Logs and Application for the crash timestamp. A faulting module pointing to the game executable may still be caused by a driver or mod, while repeated WHEA-Logger events suggest hardware or firmware instability. If only one title fails, verify files and remove overlays first. If five unrelated games fail, investigate RAM, GPU stability, power delivery, and temperatures before reinstalling Windows.
Finally, use the official Steam Support troubleshooting tools when the launcher itself is involved. Keep a short record of every change and test the same repeatable scene after each one. That discipline beats downloading another magic optimizer: stable drivers, sensible caps, completed shader caches, and stock hardware settings solve far more PC game stutter and crashing than aggressive tweaks ever will.