ryujinx keeps crashing mid game
Update to a current build and watch your GPU driver. Mid-game crashes usually trace to a Vulkan device loss or a memory ceiling, not the save.
The game runs for a while, then Ryujinx dies — sometimes with a “VulkanException: ErrorDeviceLost”, sometimes with no message at all. This is different from a startup crash: the emulator got through boot and into rendering, then something in the GPU or memory path gave out.
What’s actually happening
Two failure modes cover most mid-game crashes.
| Symptom | Likely cause | First move |
|---|---|---|
Crash with ErrorDeviceLost | GPU driver reset / unstable overclock | Update or roll back GPU driver |
| Crash after a specific action (drawing, saving) | Emulator bug in a build | Update to a current build |
| Crash after long play or heavy scenes | Memory ceiling hit | Raise DRAM limit, close background apps |
| Random crash, no pattern | Corrupted shader cache | Clear shader + PPTC cache |
Fix the GPU path first
-
Update your GPU driverAn
ErrorDeviceLostis the GPU telling the driver it reset. Stale or buggy drivers are the usual trigger, especially after a Windows update that shipped a generic driver over your real one.The crash stops recurring at the same scene. -
Revert any GPU overclock or undervoltEmulation pushes the GPU harder than most games. An overclock that's stable in benchmarks can throw device-lost errors under sustained emulation load.Crashes that only happened after 10–20 minutes of play disappear.
-
Lower graphics settings as a testDrop resolution scale and disable any custom GPU accuracy settings temporarily. If the crash moves later or vanishes, you've found a load threshold.The game survives a session it previously couldn't.
Fix the memory path
-
Raise the DRAM limit if you're near the topSome titles need more than the default memory ceiling, and they crash mid-load or mid-game when they hit it. A crash tied to a specific large scene is the tell.The crash tied to a heavy scene stops.
-
Close everything elseEmulation is memory-bandwidth hungry. A browser with dozens of tabs competes for the same bandwidth and can tip a borderline session into a crash.Memory pressure in Task Manager drops before you launch.
Build-specific and per-game crashes
A few crashes are outright emulator bugs, not your setup — a Tomodachi Life mid-session crash with a DescriptorSetUpdater error is one. For those, the fix is a newer build, and the game-specific case is covered on the Tomodachi Life crashing page. Out-of-memory crashes on specific new titles are covered separately too.