The fastest way to fix stuttering, low FPS, and crashes in new PC games is to separate the problem first: cap your frame rate for smoother frametimes, use DLSS or FSR instead of blindly dropping every setting, rebuild shader caches after driver changes, and then test CPU, GPU, RAM, temperatures, and overlays one at a time. For demanding releases such as Monster Hunter Wilds, STALKER 2: Heart of Chornobyl, and Kingdom Come: Deliverance II, the best result usually comes from a balanced 60 FPS profile rather than an unstable attempt at maximum settings.
These fixes apply to the best new PC games whether you bought them through Steam, Epic Games Store, or another launcher. Before changing anything, record your resolution, average FPS, 1% lows, GPU utilization, CPU utilization, VRAM use, and the exact moment the game fails. A crash in the menu points to a different cause than a hitch whenever you enter a new village.
Start With a Clean Performance Baseline
Run the same two-minute route every time. In Monster Hunter Wilds, that might mean leaving the Windward Plains camp, riding across a weather event, and entering a busy hunt. In Kingdom Come: Deliverance II, walk through a crowded section of Kuttenberg. In STALKER 2, use a settlement-to-wilderness route where traversal streams new assets. These scenes reveal CPU and shader problems that a quiet menu will hide.
Read the numbers instead of guessing
Use MSI Afterburner with RivaTuner Statistics Server, AMD Adrenalin metrics, NVIDIA FrameView, or the Xbox Game Bar performance panel. Average FPS tells only half the story. A game locked to 60 FPS should deliver a frame roughly every 16.7 milliseconds. If the counter says 70 FPS but frametimes spike to 80 or 120 milliseconds, the game will feel worse than a steady 45 or 60 FPS.
GPU usage near 95–99% means the graphics card is the current ceiling. GPU usage falling to 60–80% while one or two CPU threads are maxed suggests a CPU bottleneck, simulation load, asset streaming, or shader compilation. VRAM sitting at the limit can cause texture pop-in and sudden hitching, while system RAM under 16GB can force Windows to page assets to disk. Close browsers, RGB utilities, hardware monitors you don't need, and recording software before testing.
| Symptom | Likely Cause | First Test | Best Immediate Fix |
|---|---|---|---|
| GPU at 98–100%, stable frametime | GPU-limited resolution or effects | Lower render scale by 10% | Enable DLSS or FSR Quality |
| Low GPU use with CPU spikes | CPU limit, crowds, simulation | Lower crowd and foliage settings | Cap FPS below the CPU ceiling |
| Hitching during new areas | Shaders or asset streaming | Repeat the same route twice | Let shaders finish and install on SSD |
| Black screen or desktop crash | Driver, overlay, unstable overclock | Disable overlays and reset clocks | Clean-install the GPU driver |
| Textures disappear or pop in | VRAM or streaming pressure | Check VRAM meter | Reduce textures and install on NVMe SSD |
Also verify the game's files through its launcher, update Windows, and install the current Microsoft Visual C++ Redistributables. Those steps won't magically add 30 FPS, but a missing or corrupted executable component can explain a crash that follows no obvious pattern. For older engine-specific problems, Steamoz's ELEX crash and FPS fixes show the same diagnostic approach.
Use These Graphics Profiles Before Chasing Ultra
Ultra settings are often designed to make screenshots look expensive, not to provide the best play experience. Start at your monitor's native resolution, choose a sensible upscaler, and cap the frame rate to a number your system can actually hold in the busiest scene. A locked 60 FPS is a far better target than 90 FPS in an empty field followed by 38 FPS in a settlement.
The balanced 60 FPS profile
For an RTX 3060, RTX 4060, RX 6700 XT, or similar card, use 1080p, DLSS or FSR Quality, medium-to-high textures, medium shadows, medium volumetrics, and a 60 FPS cap. Keep textures high if your GPU has 8GB or more VRAM, but drop them to medium if the game's VRAM meter turns red. Textures usually affect VRAM more than raw frame rate; shadows, volumetric fog, reflections, foliage, and crowds are the bigger performance levers.
In Monster Hunter Wilds, begin with Frame Generation off while diagnosing. Set Texture Quality to High only when VRAM allows it, reduce Volumetric Fog and Environment Detail, and use DLSS Quality at 1080p or 1440p. Frame Generation can make camera movement appear smoother, but it does not repair a 35 FPS base render rate or CPU hitching. First make the underlying frame delivery stable.
In STALKER 2, start at 1080p or 1440p with DLSS Quality, then lower hair, foliage, shadow, and global illumination quality before sacrificing textures. Its dense lighting and open-world streaming can punish both GPU and CPU. In Kingdom Come: Deliverance II, view distance, vegetation, crowd density, and shader quality matter more in towns than a small reduction in texture quality. Test Kuttenberg, not a quiet forest.
| Setting | Recommended Starting Value | Typical FPS Impact | Visual Trade-Off |
|---|---|---|---|
| Upscaling | DLSS/FSR Quality | High positive | Slightly softer image, major performance gain |
| Frame Generation | Off until base FPS is stable | High positive latency aside | Can create artifacts and does not fix CPU limits |
| Textures | High below VRAM limit | Low to medium | Lower detail and more visible pop-in |
| Shadows | Medium | Medium to high | Less contact shadow definition |
| Volumetric Fog | Medium or Low | High in foggy scenes | Less dramatic light shafts and atmosphere |
| Reflections | Medium | Medium to high | Less accurate water and shiny-surface detail |
| Foliage and Crowds | Medium | High on CPU-limited systems | Fewer objects and NPCs at distance |
| Motion Blur | Off | Small | Sharper camera movement and cleaner testing |
Ray tracing deserves special caution. Reflections and global illumination can consume a huge portion of the GPU budget for a visual improvement you may barely notice during combat. Leave RT off until your conventional profile holds its target. If you own an NVIDIA RTX 40 or 50-series card, test DLSS Super Resolution and Frame Generation separately; combining multiple changes makes it impossible to identify the real fix. Steamoz's Far Cry 6 performance settings guide uses the same setting-by-setting method.
Stop Stutter From Shaders, Streaming, and CPU Spikes
Not every hitch means your GPU is too weak. Shader compilation happens when the game prepares effects for your specific driver and hardware. The first trip through a storm, a new weapon effect, or a new settlement can therefore stutter even when your average FPS looks healthy. Do not repeatedly force-close a game while it is compiling; you can turn a temporary first-run hitch into a damaged cache.
Rebuild caches correctly
Update the game and graphics driver, launch the title, and wait at the main menu if it displays a shader-preparation step. Play a repeatable route for several minutes, quit normally, and launch it again. If stutter began immediately after a driver update, rebuild the cache rather than stacking old data on new driver files. NVIDIA's shader cache can be managed through the NVIDIA App or Control Panel; AMD users can use Adrenalin's Reset Shader Cache option.
Install the game on an SSD, preferably an NVMe drive with at least 15 percent free space. A nearly full SATA SSD can still work, but open-world titles stream thousands of small assets and are less forgiving of slow storage. Keep the Windows page file system-managed on an SSD. Disabling it is a bad “optimization” that can turn a memory spike into a crash.
For CPU spikes, lower crowds, simulation distance, foliage density, and view distance before lowering resolution. Resolution changes help a GPU bottleneck; they do almost nothing when the processor is calculating NPC routines and world streaming. Cap FPS with the in-game limiter or RTSS. If your machine fluctuates between 72 and 110 FPS but drops to 48 in towns, a 60 FPS cap can eliminate the constant CPU race and produce much smoother controls.
Use V-Sync according to your display. With G-Sync or FreeSync, enable the monitor's adaptive-sync feature, cap a few frames below refresh rate—58 FPS for a 60Hz display or 141 FPS for 144Hz—and avoid running both multiple external limiters at once. Uneven frame pacing often feels like stutter even when the frame rate counter looks impressive.
Fix Crashes Without Randomly Deleting Files
Crashes need a controlled checklist. Start by removing GPU and CPU overclocks, undervolts, XMP or EXPO memory profiles, and third-party injectors for one test session. A game can be the first application to expose unstable RAM even when stress tests appear fine. If the crash disappears at stock settings, tune again gradually instead of blaming the game outright.
Follow this order
- Verify files. Use Steam's Installed Files menu or the equivalent launcher repair option. This replaces missing packages without touching saves.
- Disable overlays. Turn off Steam Overlay, Discord Overlay, NVIDIA ShadowPlay, AMD recording, MSI Afterburner OSD, ReShade, and motherboard utilities temporarily. Re-enable them one by one after stability returns.
- Clean-install the driver. Use Display Driver Uninstaller in Windows Safe Mode if a normal installation does not help, then install the latest stable WHQL driver. Choose the minimal driver components.
- Check temperatures. Sustained GPU temperatures around 80–85°C or CPU temperatures near the thermal limit can trigger clocks, errors, and sudden exits. Clean dust, improve airflow, and watch hotspot temperature rather than only the average core temperature.
- Check Windows logs. Reliability Monitor can show whether the failing module is the game executable, a driver DLL, or hardware-related. Repeated Kernel-Power events after a hard reboot point toward power, thermals, or system stability—not a missing texture.
For Unreal Engine games, a crash mentioning DXGI_ERROR_DEVICE_REMOVED or a hung device often responds to stock GPU clocks, a clean driver, lower VRAM pressure, and disabling ray tracing. Do not immediately add random launch commands copied from a forum. Test one launch option at a time and remove it if it changes nothing.
| Crash Pattern | Most Probable Area | Action | What Not to Do |
|---|---|---|---|
| Crash during shader compilation | Driver or corrupted cache | Clean driver and reset shader cache | Disable the page file |
| Crash entering a new area | VRAM, RAM, streaming | Lower textures, close apps, use SSD | Delete save files first |
| Crash after 20–40 minutes | Heat or unstable overclock | Return CPU/GPU/RAM to stock | Increase voltage blindly |
| Crash only with overlays | Injector conflict | Disable overlays and injectors | Run several monitoring tools together |
| Crash on launch | Files, runtime, permissions | Verify files and install runtimes | Download unofficial DLL files |
Keep saves safe before deeper troubleshooting. Cloud synchronization can preserve progress, but manually copy local saves too. Never download a replacement DLL from an unknown site. If the title has a known issue, check its official patch notes and support channel, such as the official STALKER 2 support site or the Monster Hunter Wilds official site. Steamoz also has a focused crashing and low-FPS troubleshooting guide for another demanding PC release.
Build a Stable Profile for Your Hardware
Once the game stops crashing, tune for consistency. A practical target is 60 FPS at 1080p for mainstream hardware, 60–90 FPS at 1440p for a modern upper-midrange GPU, and 90 FPS or higher only when the CPU and display can sustain it. Competitive shooters benefit from lower latency, but cinematic open-world games usually feel better with stable frametimes and clean image quality.
| Hardware Class | Resolution | Upscaler | Preset Direction | Frame Cap |
|---|---|---|---|---|
| GTX 1660 Super / RX 5600 XT, 16GB RAM | 1080p | FSR Balanced or Quality | Medium; RT off | 45–60 FPS |
| RTX 3060 / RX 6700 XT, 16GB RAM | 1080p–1440p | DLSS/FSR Quality | Medium-high; RT off | 60 FPS |
| RTX 4070 / RX 7800 XT, 32GB RAM | 1440p | DLSS/FSR Quality | High; selective RT | 60–100 FPS |
| RTX 4080 Super / RX 7900 XTX | 1440p–4K | Quality upscaling | High-ultra; test RT carefully | 60–144 FPS |
Sixteen gigabytes of RAM remains workable, but 32GB is the safer recommendation for new open-world games while Discord, a browser, and launchers are running. Match two memory modules when possible, update your motherboard BIOS if it improves memory compatibility, and test EXPO or XMP rather than assuming the advertised profile is automatically stable. Keep at least 8GB of free SSD space beyond the game's installation so shader and temporary files have room to breathe.
Patch notes matter more than old benchmark videos. Developers can change traversal stutter, CPU threading, shader preparation, and VRAM behavior in a single update. Check the Monster Hunter Wilds Steam page, the STALKER 2 Steam page, and official patch notes before copying someone else's configuration.
Finally, change one setting at a time and replay the same route. If lowering volumetric fog fixes a GPU-bound dip, keep textures high. If reducing crowds fixes a town slowdown, restore your resolution. The winning configuration isn't the one with the most sliders on Ultra; it's the one that keeps frame delivery predictable, controls responsive, and your save file intact. For more game-specific testing, see Steamoz's FPS-first crash fix for Everspace 2 and its higher-FPS settings guide.