Elden Ring PC Stuttering: Fixes for Each Known Cause
Elden Ring stutters in two distinct ways — a brief freeze the first time you meet a new enemy or spell, and general low frame pacing — and the two have different fixes. Match your symptom to the cause first, then apply only the fix that fits, from shader caches to VRAM budgets.
Elden Ring runs well on modest hardware once it is configured correctly, but it stutters in a very recognizable way, and the internet is full of fixes that solve the other kind of stutter. The game actually has two separate problems that players lump together: a one-frame-freeze hitch tied to shader compilation, and general poor frame pacing or low FPS. Applying the right fix to the wrong symptom is why so many "this fixed it for me" threads do nothing for anyone else. Diagnose first, then fix.
Menus may shift with patches. FromSoftware has adjusted graphics options across updates, and launcher layouts change too. The paths below were stable for years, but if an option has moved, the name to look for has not.
Step 1: Identify which stutter you have
Play for ten minutes and watch when the hitch happens:
- The game freezes for a fraction of a second the first time a new enemy type, spell, or visual effect appears on screen — then never stutters on that enemy again. This is shader compilation stutter. Your hardware is fine; this is a known behavior of the engine. Steps 2 and 3 reduce it.
- Frame rate is generally low or uneven everywhere, or drops in specific areas (dense forests, caves with many light sources, boss arenas with effects). This is a performance problem. Steps 4 to 6 address it.
This distinction matters because shader-compilation hitches cannot be fixed by lowering settings — you can drop the resolution to the floor and the first encounter with a new enemy still hitches. Conversely, a VRAM shortage will not care how clean your shader cache is.
Step 2: Reset the shader caches once
The game compiles DirectX shaders on the fly and stores them in GPU-driver caches on disk. When a cache is corrupted — after a driver update, an interrupted session, or a crash — the same enemy hitches every time instead of just the first. The fix is a one-time rebuild:
- Close the game completely.
- Delete the contents of %LOCALAPPDATA%\NVIDIA\DXCache (NVIDIA GPUs) or %LOCALAPPDATA%\AMD\DxCache and %LOCALAPPDATA%\AMD\LnDCache (AMD GPUs). Paste the path into the File Explorer address bar.
- Also check the game's own folder structure under %LOCALAPPDATA% for a shader cache subfolder if one exists.
- Launch the game and expect the first hour to be slightly more hitchy than usual while caches rebuild — this is normal and settles on its own.
Clearing caches is a reset, not an optimization. Do it when the same enemy stutters repeatedly. After that, leave the caches alone — deleting them regularly just guarantees a hitchy first hour every time.
Step 3: Set expectations about first-encounter hitches
Steam's shader pre-caching feature has limited effect on this engine's DirectX 12 pipeline, so some first-encounter hitches will remain no matter what you do — community testing has repeated this finding since launch. The pragmatic plays are: spend your first minutes in a starting area deliberately agitating the common enemy types (soldiers, dogs, birds) so the game compiles those shaders somewhere harmless, and simply know that a single hitch on a brand-new enemy type is the engine, not your PC.
Step 4: Respect the VRAM budget
The single biggest performance lever is texture quality versus video memory. The High texture setting pushes a VRAM footprint that comfortably exceeds 6 GB at 1080p–1440p once drivers, Windows, and a browser tab or two are counted. When VRAM overflows, textures spill to system RAM over the PCIe bus, and the result is exactly the uneven, rhythmic stutter players describe as "the game stutters no matter what."
- GPUs with 6 GB VRAM or less: set Textures to Medium. The visual difference in motion is small; the frame-time consistency gain is large.
- 8 GB: Medium to High depending on resolution; 4K wants the full 8 GB.
- Verify with Task Manager → Performance → GPU (the "Dedicated GPU memory" line) while playing for a few minutes. If it sits at or near 100 percent of your card's capacity, lower one tier.
Step 5: Frame rate cap — and why the game has no built-in one
Elden Ring's PC options menu does not include a frame limiter. If you want a cap — and capping is genuinely useful here, both for frame pacing and because uncapped frame rates in FromSoftware engines have historically produced odd animation and physics edge cases — you set it outside the game:
- NVIDIA: NVIDIA App or Control Panel → Manage 3D Settings → Program Settings → ELDEN RING → Max Frame Rate.
- AMD: Adrenalin → Gaming → ELDEN RING → Frame rate target control.
- Any GPU: RivaTuner Statistics Server (RTSS), which ships with MSI Afterburner, cap set to 60 or a value matched to your display.
Cap choices that behave well in practice: 60 for maximum consistency (and to sidestep every framerate-related edge case), or a value just under your monitor's refresh — for example 141 on a 144 Hz panel — paired with V-Sync off and, if your card supports it, G-Sync/FreeSync enabled.
Step 6: The generic layer that still matters
On top of the Elden Ring-specific causes, the usual suspects apply — our general Windows 11 stutter guide covers them in depth. The short version for this game:
- Set Screen Mode to Fullscreen in the game's display options, not borderless windowed — the exclusive path has measurably steadier frame pacing here.
- Disable overlays (Steam, Discord, GeForce/AMD) for a test session. Overlay hooks are a recurring frame-time tax.
- Run Settings → System → Display → Graphics and confirm the game is assigned to your high-performance GPU on laptops with hybrid graphics.
- Verify game files through your launcher after any crash — corrupted chunks produce stutter that cache clearing will never fix.
One deliberate omission: no "performance boost" packs or FPS-unlock mods. The game runs online with anti-cheat protection, and any tool that modifies game files puts your online save at risk of a restriction — the legitimate gains above already cover what those packs claim.
A fast order of operations
- Classify the stutter: first-encounter hitch (steps 2–3) or general (steps 4–6).
- One-time shader cache clear if the same enemy hitches repeatedly.
- Textures to match your VRAM; confirm with Task Manager.
- Caps via driver panel or RTSS, not the in-game menu.
- Fullscreen mode, overlays off, files verified.
Treat the first-encounter hitch as engine behavior, budget your VRAM honestly, and Elden Ring's frame pacing becomes boring in the best way. The same VRAM-first thinking transfers directly to other big open-world releases — and if you want the underlying reasoning about which settings actually cost frames, the Minecraft performance guide breaks down that decision process in detail, while the performance guides index collects the rest of the walkthroughs by symptom.
