Crimson Desert crashing on PC? Fixes players confirmed

The problem: the game crashes straight to the desktop, often with no error message. For many players it started after the Enhanced update or after a newer NVIDIA driver, even if they’d played for 50 to 150 hours without a crash before. Lowering settings, turning off DLSS or FSR, verifying files and clean reinstalls usually don’t help.

There isn’t one fix for everyone. These are the changes players in several Steam threads said actually stopped their crashes. Try the quick ones first.

What worked, and for whom

• Hardware-Accelerated GPU Scheduling. One player with almost 500 hours said they only ever crashed when this was off, and the crashes stopped when they turned it back on. Two more players confirmed it fixed theirs. One of them found their controller stopped working afterwards, so keep that in mind.
• Steam background game recording. The player who started the “[FIXED]” thread had already tried the driver rollback, lower settings, no upscaling, GPU scheduling and two reinstalls. Turning off Steam’s background recording was what finally worked, with no crashes over several long sessions on Ultra with DLSS on and the latest drivers.
• NVIDIA driver 610.88. An RTX 5080 owner traced their crashes to drivers 616.56 and 616.64. Windows logged them as LiveKernelEvent 141 with nvlddmkm errors, and rolling back to 610.88 made the game stable again at max settings. Others in that thread, including an RTX 4060 owner, said they had the same crash. In another thread the rollback was marked as the answer.
• Frame Generation off. This fixed menu crashes for one player. It also let another player open the menu again, though opening the map still crashed their game.
• Crashes when you open or flick through menus. This is the most common pattern in newer threads: the game dies when you switch inventory tabs quickly, go from the map to the journal, or open the “Other” or “Skills” tabs. Rolling back the NVIDIA driver was again the fix most people reported in these threads, which also include crashes on loading a save or fast travelling. One player with menu crashes said rolling back to 610.88 fixed it completely. Another rolled back to the older 595.75 they’d used before and played over an hour without a crash. In the same thread, a third player went back from 616 to a 610 driver and hasn’t crashed since. A different player fixed it by turning off Ray Tracing and Reflex instead.

Mixed results

• The driver rollback isn’t universal. One player said 610.88 alone didn’t stop their crashes and the game only settled after a PC restart. Others play on newer drivers, including 616.92 and 616.56 on an RTX 5090, with no crashes at all. If you’re not on NVIDIA or the crash started some other way, try the other fixes first.
• NVIDIA 621.01 (October 21, 2026): mostly crash reports so far. One player who had stayed on 610.88 to avoid crashes updated to 621.01 and said the crashes were gone. Since then, most reports have gone the other way. In three threads from October 21 and 22, players said the game crashed at the splash screen, wouldn’t start, or crashed after a few minutes on the new driver. Rolling back fixed it for the player who started the “New Drivers crash game” thread, and for an RTX 5070 owner who went back to the early-October driver they’d used before. Another player, on the latest NVIDIA driver, found the game only stopped crashing with DLSS, Frame Generation and related features off, and it still crashed on Cinematic settings. Windows logged their crashes as LiveKernelEvent 141 and nvlddmkm errors. After going back to 610.88 with NVIDIA’s normal installer, without DDU and keeping their settings, they play on Cinematic with DLSS on and no crashes. In the same thread, one player was still crashing after 7 to 27 minutes after rolling back, so it isn’t a fix for everyone. If 621.01 makes things worse, go back to the driver you were on before.
• Thinking of updating your driver? Several players are holding off for now. One suggested making a Windows restore point before you update, so you can go back easily if the game starts crashing. A laptop RTX 4050 owner said a recent update gave them heavy stuttering until they rolled it back.
• 616.64 is hit and miss. One player said going back to 616.64 fixed their crashes. Two others, including the player who started that thread, were still crashing on it, and one of them only became stable on a 610 driver.
• Some players haven’t found a fix yet. In threads from October 19 to 22, several players said the game had started crashing after a few minutes of play, some of them right after coming back from a break. Verifying the game files and reinstalling graphics drivers didn’t help them. Neither did turning off Frame Generation and Ray Tracing, lowering settings or clearing the DirectX shader cache. It isn’t only NVIDIA, either: on October 22 an AMD RX 7900 XTX owner said the game had been crashing after a few minutes for two nights, and an RTX 4080 Super owner said it crashed 10 seconds after loading even though they hadn’t updated their driver.
• Freezes, then crashes, after short sessions. The player who started the “Sudden freezes and crashes?” thread tried a driver rollback first, and it didn’t help. What stopped it was switching the upscaler from AMD FSR to NVIDIA DLSS: they then played for many hours without a single freeze. Another player in that thread said turning on VSync fixed the same problem for them.
• The -dx11 launch option. One player said adding it to Steam’s launch options fixed most of their crashes. Another said it made no difference for them.