Emulators crashing on Steam Deck
Set a lower DRAM cap when emulators crash on Steam Deck. Update the GPU driver, lower the memory limit, then rerun the game.
Crashes on the Deck come in three shapes
| What happens | Usual cause |
|---|---|
| Dies a few minutes in, after a loading screen | Out of memory — DRAM cap too high for the title |
| Dies immediately on boot | Driver or backend mismatch |
| Dies in one specific scene or menu | Title-specific bug, not your setup |
The first is the one you can fix from settings. The third you cannot — it needs a newer build.
Lower the memory ceiling first
Switch emulators reserve a fixed block of emulated DRAM and allocate it up front. On a desktop that is harmless. On a Deck sharing 16 GB with SteamOS, the compositor, and the game’s own shader cache, a high cap pushes the title into an allocation failure that surfaces as a crash rather than a warning.
Ryubing’s tracker has the exact case: Pokémon Legends: Z-A hitting an out-of-memory crash above a 4 GiB DRAM setting. Set it to 4 GiB, which is the compatibility default, and retest before changing anything else.
Update the driver through SteamOS
The Deck’s GPU driver only arrives via system updates. If an emulator started crashing after a SteamOS update that did not finish, the compositor and the emulator can end up on different driver paths. Complete the update, reboot, and retest before reinstalling anything.
Free memory around the emulator
Close the browser and any game still running in the background — the Deck suspends rather than closes, so a “closed” game can hold several gigabytes. Turn off the Steam overlay recording features too; they cost VRAM that the emulator expects to use.
When it is one title only
A crash in a single scene, menu, or character editor is a title bug, and the tracker reflects that — a Mii editor crash in Miitopia and a Vulkan feature error on a specific macOS driver are both recorded as title-level faults. Those two are logged on other systems, not on the Deck; the point is that the fault follows the game, not the hardware. Check the emulator’s issue list for that game, and if nothing matches, downgrade or upgrade the build rather than adjusting settings at random.