Elden Ring Nightreign Stuttering Fix (PC): Stop Freezes and Hitches

To fix Elden Ring Nightreign stuttering and freezing, force V-Sync on in your GPU control panel (the game has no in-game V-Sync), lock the frame rate to 60 FPS externally, and update or clean-install your GPU driver — the RTX 50-series freezes trace to a driver-plus-engine mismatch. Nightreign runs on the same aging engine as the original Elden Ring, so most stutter fixes carry over, with a few spinoff-specific issues to clear first. This guide works through each in order of impact.

What actually causes Elden Ring Nightreign stutter

Nightreign stutter falls into four buckets, and the fix depends on which one you have:

Symptom	Most likely cause	Primary fix
Multi-second freezes on RTX 50 GPUs	Driver + old engine mismatch	Update/clean-install driver; force V-Sync; cap 60
Tearing + frame-time stutter	No in-game V-Sync	Force V-Sync in NVIDIA Control Panel / Adrenalin
Occasional hiccups everywhere	60 FPS cap + uncapped frame pacing	Lock to a steady 60 FPS externally
Hitches in the first session	Shader compilation	Play on; clear shader cache if it persists

Diagnose before you change settings: watch your frame time with the RivaTuner Statistics Server overlay. A single huge spike that freezes the screen for seconds is the RTX 50 driver bug; small repeated spikes are frame-pacing without V-Sync.

Fix 1: Force V-Sync — the game has none

Nightreign ships without an in-game V-Sync option, which causes tearing and frame-time stutter. Force it on externally:

• NVIDIA: open the NVIDIA Control Panel → Manage 3D Settings → Program Settings, add the Nightreign executable, and set Vertical Sync to On.
• AMD: in AMD Adrenalin, add the game and enable Wait for Vertical Refresh.

Many players report that forcing V-Sync here — combined with the 60 FPS cap below — removes most of the freezing and hitching on its own.

Fix 2: Clear the RTX 50-series freeze

Owners of RTX 50-series cards (5060, 5070 Ti and similar) reported freezes lasting several seconds, traced to a mix of the launch-era NVIDIA drivers and Nightreign’s old engine. To clear it:

1. Update to the latest NVIDIA driver. If you are on the launch-window driver, this alone often fixes it.
2. If freezes persist, clean-install the driver with DDU to remove a corrupt or partial install.
3. Force V-Sync (Fix 1) and cap to 60 FPS (Fix 3) — the freezes are worst when frames run unrestricted.

Fix 3: Lock to a steady 60 FPS

Nightreign keeps the 60 FPS cap from the original Elden Ring (cutscenes run at 30). The engine handles a steady, externally-locked 60 far better than an uncapped rate. Cap it with the NVIDIA app, AMD Adrenalin, or RivaTuner Statistics Server to a flat 60 so frame times stay even. Our FPS cap guide and best FPS cap for low latency walk through the mechanics.

Fix 4: Shader compilation and storage

• Let shaders compile. Some early hitching is one-time shader compilation as you encounter new areas and effects — see our shader compilation stutter explainer. If it persists after the first session or you changed drivers, clear the shader cache.
• Install on an SSD. Nightreign’s fast, condensed runs load new areas constantly; an SSD removes streaming pop-in and micro-stutter (see NVMe vs SATA for gaming).

Fix 5: Windows and system housekeeping

• Disable VBS for a free CPU-bound FPS gain, and set a high-performance power plan.
• If some titles stutter with hyper-threading/SMT, and only if other fixes fail, test the game with it disabled — this has helped a subset of Nightreign players.
• For periodic system-wide hitches unrelated to the game, check for high DPC latency.

The base-game fixes still apply

Because Nightreign runs on the same engine as the original game, the shared engine-level tweaks carry over. If you still see hitching after the steps above, work through our original Elden Ring stuttering fix for the deeper engine and Windows tweaks.

Still dropping frames?

Once the game is smooth, the remaining wins are in input responsiveness. Lower system-level input lag with the timer resolution guide and our input delay guide.