You're not alone — Cyberpunk 2077 crashing after patch 2.1 has been a common complaint since the update dropped. Let's get you back into Night City without the frustration.
The Quick Fix (Works for 80% of People)
If you have any mods installed (even one), the most likely culprit is a mod conflict. Patch 2.1 changed core game files, and many mods from 2.0 or earlier simply break the game now. Here's how to fix it:
- Move all your mods out of the game folder. Go to
Steam\steamapps\common\Cyberpunk 2077\archive\pc\modand move everything in that folder to your Desktop. Don't delete them yet — just move them. - Also move REDmod files. If you use REDmod, go to
Cyberpunk 2077\modsand move those out too. - Launch the game through Steam (or GOG). Click "Play" and wait. You should see the CD Projekt RED logo and then the main menu.
If the game starts fine with mods removed, then you found the problem. Now you need to figure out which mod was causing it. I'd start with any mod that touches core gameplay systems — like cyberware overhauls or vehicle handling mods. Those are the usual suspects after a big patch.
If Mods Aren't The Issue: Clear the Cache
People skip this because it sounds too simple, but a corrupted cache causes all kinds of weird crashes. Here's how to clear it properly:
- Go to
%LOCALAPPDATA%\CD Projekt Red\Cyberpunk 2077. You can copy that path into the Windows Run box (Win+R) and press Enter. - Delete the
cachefolder inside. - Also go to
%APPDATA%\GOG.comand delete theGalaxy\storage\games\cyberpunk 2077folder if you have GOG. For Steam, it's%PROGRAMFILES(x86)%\Steam\userdata\<your_steam_id>\1091500\remote— just delete the contents. - Restart your PC, not just the game.
After that, the game should rebuild those files fresh. You'll see a slightly longer load time on first launch — that's normal.
Why This Works
Patch 2.1 introduced a new level of dynamic UI and revised police behavior. That touched a lot of scripts. Old mods were built for the 2.0 script structure, so they either crash at load or cause random crashes during gameplay. The cache, on the other hand, holds precompiled shaders and script data. After a patch, that cache can be stale and the game tries to read outdated entries — that's a recipe for a crash to desktop.
I've seen this exact issue on Windows 10 and 11, both on Steam and GOG versions. The fix is identical either way.
Less Common Variations
Crash Only When Driving
If the game only crashes when you're driving fast through the city, that's usually a texture streaming issue. Lower the "Texture Quality" to Medium in the settings. Yes, it's a workaround, but it's been stable for a lot of players since 2.1.
Crash After an Hour of Play
This smells like a memory leak. Check if you have page file disabled — some players turn it off for performance, but Cyberpunk needs it. Go to System Properties > Advanced > Performance > Settings > Advanced > Virtual Memory, and set it to "System managed size". Then reboot and try again.
Crash on Saving
Rare, but it happens. The game writes save files to %USERPROFILE%\Saved Games\CD Projekt Red\Cyberpunk 2077. If that path is on OneDrive, it can cause sync conflicts and crashes. Right-click the folder, go to Properties > Location, and move it to a local folder like C:\Saves\Cyberpunk.
Prevention for Future Patches
The real fix is to be disciplined with mods. Before any major update, disable all mods and run the game once without them. That way, you know the base game is solid. Then add mods back slowly — a few at a time — and test for an hour before adding more.
Also, make a backup of your save folder before each patch. It's a 2-minute step that saves you hours of grief if something goes sideways.
And if you're on a mod manager like Vortex, don't rely on it to update mods automatically after a patch. Mod authors need time to fix compatibility, so check the mod page for a "supports 2.1" note before enabling it.
One more thing — if you're using FSR or DLSS, try turning it off first. Some players report crashing with certain driver versions. The game runs fine without it, so it's worth a test.
Start with the mod removal and cache clear. That combination fixes the majority of crashes. If you're still stuck after that, let me know what exactly happens — does it crash on launch, in the menu, or mid-game? That detail narrows things down fast.