Cyberpunk 2077 Flatlined

"Cyberpunk 2077 has flatlined" means the game crashed hard enough that RED Engine couldn't recover. The fastest fix path: remove all mods, verify game files, update your GPU driver (DDU clean install), and increase virtual memory to 20GB. If the crash always happens in the same spot, try loading an earlier save. Mods cause the majority of flatlines — if you're running Cyber Engine Tweaks, redscript, or any .archive mods, start there.

What's actually happening

The "flatlined" dialog is CD Projekt Red's custom crash handler for Cyberpunk
2077. When the RED Engine hits an unrecoverable error — null pointer dereference, stack overflow, out-of-memory, GPU device loss, or a script exception that propagates too far — it catches the exception, generates a crash dump, and shows the flatlined popup. The game's process is already dead at this point; the dialog is just telling you what happened.

The dialog sometimes includes a crash ID and a brief description, but most of the time it's unhelpfully generic. The actual crash details are logged to %LOCALAPPDATA%\CD Projekt Red\Cyberpunk 2077\CrashDumps\. Each crash produces a .dmp file and sometimes a .log with a stack trace. If you're trying to diagnose a persistent crash, that .log file is gold — it tells you exactly which function or script failed.

Cyberpunk 2077 has been through massive evolution since launch. Patches 1.x through 2.x rewrote large portions of the engine, and the Phantom Liberty expansion added new systems. Each major update shifted the stability landscape: what crashed in 1.6 is stable in 2.x, but new issues emerged. Mod compatibility is the biggest casualty — mods built for one version frequently cause flatlines on the next.

The most common causes (in order of likelihood)

Mod conflicts. This is cause #1 by a wide margin. The Cyberpunk modding ecosystem is massive: Cyber Engine Tweaks (CET), redscript, RED4ext, ArchiveXL, TweakXL, and hundreds of individual mods that modify everything from combat to NPC appearances. After any game update, there's a window where many mods are broken and cause flatlines because they reference functions or data structures that have changed. Even between updates, conflicting mods that modify the same game systems (two mods that both change vehicle handling, for example) will crash. CET itself can cause flatlines if its version doesn't match the game version.

Corrupted save file. Cyberpunk saves can grow large — 10-20MB is common with many hours played — and they can corrupt, especially if the game crashed during an autosave. A corrupted save causes flatlines at specific locations (usually wherever the corrupt data references) or immediately on load. The save corruption is often subtle: the game loads fine, plays for 10 seconds to 5 minutes, then flatlines when it tries to load the corrupted chunk.

GPU driver crash (DXGI device loss). Cyberpunk hammers GPUs harder than almost any other game, especially with ray tracing and path tracing enabled. If your GPU driver times out (TDR), the engine catches it as a flatline. This is more common on 8GB VRAM cards running RT settings, or on any card with an unstable overclock. The path tracing mode in particular pushes VRAM usage to extremes — 10-14GB on Ultra settings at 1440p.

Insufficient virtual memory. Cyberpunk can use 14-18GB of system RAM on its own, plus it relies heavily on the Windows pagefile for memory-mapped assets. If your pagefile is set too small (or managed automatically on a nearly full drive), the engine runs out of virtual address space and flatlines. This manifests as random crashes that happen more frequently the longer you play.

Corrupted shader cache. The game compiles shaders for your specific GPU on first launch and caches them. If this cache gets corrupted (interrupted compilation, disk error, game update that invalidates the cache), you get flatlines during gameplay whenever the engine tries to load a broken cached shader. The crash typically happens during transitions — fast traveling, entering buildings, or driving through dense areas.

Game file corruption. Straightforward: if a game file was damaged during download, update, or by a disk error, the engine crashes when it tries to load that asset. This causes consistent crashes in specific locations or when specific assets are loaded (a particular weapon, vehicle, or NPC model).

How to fix it

1. Remove all mods and test vanilla. This is the most important diagnostic step. Delete or move everything from the following folders: Cyberpunk 2077\bin\x64\plugins\ (CET, RED4ext), Cyberpunk 2077\r6\scripts\ (redscript mods), Cyberpunk 2077\archive\pc\mod\ (.archive mods), and Cyberpunk 2077\mods\ (if using Vortex or mod manager). Also remove CET itself: delete the bin\x64\plugins\cyber_engine_tweaks folder. Launch the game vanilla. If it doesn't flatline, your mods are the problem. Add them back in small batches (3-5 at a time) and test until you find the culprit. Check each mod's Nexus Mods page for compatibility notes with your game version.
2. Verify game files. On Steam: right-click Cyberpunk 2077 > Properties > Installed Files > Verify Integrity. On GOG Galaxy: click the game > Manage Installation > Verify / Repair. On Epic: three dots > Manage > Verify. This replaces corrupted files but will NOT remove mods from the mod folder — you still need to do that manually.
3. Delete the shader cache. Navigate to %LOCALAPPDATA%\CD Projekt Red\Cyberpunk 2077\. Delete the folders named "shader_cache" and "shader_cache_dx12" (or any cache-related folders you see). The game rebuilds these on next launch. The first launch after clearing the cache will have stuttering for a few minutes as shaders recompile — that's normal.
4. Update your GPU driver with a DDU clean install. Download DDU from guru3d.com. Boot into Safe Mode. Run DDU, clean and restart. Install the latest driver from nvidia.com or amd.com. NVIDIA's Game Ready drivers usually include Cyberpunk-specific optimizations — check the release notes for mention of Cyberpunk
5. For AMD, the Adrenalin drivers with RDNA3 optimizations are particularly important for performance and stability.
6. Increase virtual memory. Right-click This PC > Properties > Advanced System Settings > Performance > Settings > Advanced > Virtual Memory > Change. Uncheck "Automatically manage." Select your SSD, click Custom Size, set Initial to 20480 and Maximum to 32768 (20-32GB). Click Set, OK, and restart. This is especially critical if you have 16GB of system RAM — Cyberpunk needs the headroom.
7. Try loading an earlier save. If the flatline happens at a specific location or during a specific quest, load a save from before you entered that area. Sometimes save corruption is localized to recent autosaves. If the earlier save works, play forward past the problem area and avoid the trigger. Check the Cyberpunk subreddit (r/cyberpunkgame) with the quest name — if it's a known bug, there's usually a workaround.
8. Lower GPU-intensive settings. In Graphics settings: turn off Path Tracing if enabled (switch to regular Ray Tracing or Rasterization). Set Crowd Density to Medium or Low. Disable DLSS Frame Generation if enabled (it has known stability issues on some driver versions). Set Screen Space Reflections Quality to Low. Lower Volumetric Fog Resolution. These changes reduce GPU load and VRAM pressure, which directly reduces flatline frequency.
9. Close background applications. Chrome with hardware acceleration eats VRAM. Discord with hardware acceleration adds GPU overhead. Wallpaper engines, OBS, streaming software — all compete for GPU resources. Close everything you can before launching Cyberpunk.

Is this a hardware or software problem?

Flatlines are almost always software. Mods, corrupted saves, and driver issues cover 90%+ of cases. If the flatline only happens in Cyberpunk and no other games crash, it's a Cyberpunk-specific software issue.

Hardware suspicion is warranted if: other demanding games also crash with GPU errors (possible VRAM failure — run OCCT VRAM test), your system randomly reboots during Cyberpunk (possible PSU wattage issue — Cyberpunk with RT can pull 400W+ total system draw), or Windows Memory Diagnostic or memtest86 shows RAM errors.

If you're not sure, Crashless can check your drivers, temps, VRAM, and 400+ known patterns automatically — just use the chat above.

Games commonly affected

This is a Cyberpunk 2077-specific error. No other game shows the "flatlined" dialog. However, if your flatlines are caused by GPU driver issues (DXGI device loss), you'll likely also experience crashes in other demanding titles like Hogwarts Legacy, Alan Wake 2, and Star Wars Jedi: Survivor.

Frequently asked questions

Q: The game was working fine and now it flatlines constantly after an update. What happened?
A: Game updates break mods. This is the #1 cause of post-update flatlines. Remove all mods, update CET and RED4ext to their latest versions (they need to match the game version), then reinstall mods one at a time. Check each mod's Nexus page for update compatibility.

Q: I'm not using any mods and it still flatlines. Now what?
A: Delete the shader cache, verify game files, and increase your virtual memory. If flatlines persist, do a DDU clean GPU driver install. If it still crashes, check the crash dump logs in %LOCALAPPDATA%\CD Projekt Red\Cyberpunk 2077\CrashDumps\ — the .log file's stack trace can point to the specific system that's failing.

Q: Does Path Tracing cause more flatlines than regular Ray Tracing?
A: Yes. Path Tracing (Overdrive Mode) is dramatically more demanding than standard RT. It uses more VRAM, more GPU compute, and pushes the driver harder. If you're flatline-prone, switch to regular Ray Tracing or full rasterization and see if stability improves. Path Tracing on an 8GB card at 1440p is asking for trouble.