Cyberpunk 2077 has flatlined ctd

[CHEEZY]

I've been scratching my head and ripping my hair out for the past week trying to diagnose this. My game has been crashing a lot as of late, one second it's running fine and then suddenly a half a second freeze and then immediate crash to desktop with the "Cyberpunk has flatlined!" error message.

I did play with a modded setup and knew that came with risks to stability, and it would only happen ever so often. But it got to the point where it seemed it was happening more and more frequently, then during one session it crashed while I was driving. I booted up the game again and decided to just deal with it, but then it crashed just a few minutes later while sneaking around the interior of a gig, then again, and again with only 10-15 minutes max of playtime between each one. I realized I have to get to the bottom of this its becoming unplayable.

Luckily I could recreate the crash very consistently. I loaded the save where I was driving from heywood to the watson megabuilding. I took the same route everytime and it would always without fail crash in an underpass close to the afterlife bar. I bisected, disabled mods, updated drivers, messed around with windows performance settings, turned off raytracing and DLSS, all to see if it would fix the crash. No luck.
Finally said screw it, even after disabling all my mods right down to a vanilla state, following this whole guide on bisecting your mod installation to try and find the culprit: https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/user-guide-troubleshooting#finding-the-broken-mod-bisecting

I completely wiped my game, deleted all mods and even my vortex staging folder to guarantee a completely clean installation. Reinstalled the game, loaded my save, did the drive, crashed in the same spot. Started a new game figuring my save was borked, crashed in the nomad opening when Jackie is driving into the checkpoint.

Im at a loss. Sorry for the long winded expo just wanted to give context because im at my wits end. Wondering if anyone else is experiencing these types of crashes despite the game running perfectly fine in between.

Edit: 2.11 came out and the game still crashes in the same damn spot. Extremely puzzling. Crash wasnt present in 2.0 or previous versions aside from launch.

System;
i7-10700k
32GB DDR4
RTX 4080
4tb SSD

[Silverbane7]

did you try using a cleaner?

https://www.nexusmods.com/cyberpunk2077/mods/8595
Cyberclean

a lot of players found that even with their mods removed, and vortex uninstalled, there were still fragments left behind (yes, even after a 'clean install' of removing files/redownloading just the game) they were still crashing.
I'd try the 'cybernuke' version.
it's quick and easy. stick the 'cybernuke' batch file into the cyberpunk 2077 folder, run it by double clicking it and let it clear anything left behind.

if the game is still crashing after that, even with a new save, then something else may be going on.

[Tokenn]

I had a problem with my game crashing all the time at a specific spot...turned out there was a mod remnant causing it. There's a Mod Remover utility on Nexus you might want to try running. I hope it helps...sounds like you've tried a lot, and I don't know what else to suggest.

https://www.nexusmods.com/cyberpunk2077/mods/8597

[PanPan]

Everybody has some random crash (when overload usually).
Happened to me 2 or 3 times in 50h.
No mods, clean windows install
Also happen on console...

I even got Forza crashing because of Twitch running in background.
Some stuffs just happen.

[rabitsrule]

could try deleting your prefetch files and resetting the shaders on your GPU and try installing your GPU drivers again using DDu to clean any left over driver files that are old

[CHEEZY]

Originally posted by Silverbane7:

did you try using a cleaner?

https://www.nexusmods.com/cyberpunk2077/mods/8595
Cyberclean

a lot of players found that even with their mods removed, and vortex uninstalled, there were still fragments left behind (yes, even after a 'clean install' of removing files/redownloading just the game) they were still crashing.
I'd try the 'cybernuke' version.
it's quick and easy. stick the 'cybernuke' batch file into the cyberpunk 2077 folder, run it by double clicking it and let it clear anything left behind.

if the game is still crashing after that, even with a new save, then something else may be going on.

Appreciate the suggestion, I just tried both the normal version and the cybernuke version and both came up with messages saying it couldn't find any specified folders and that I had a vanilla installation.

[CHEEZY]

Originally posted by Tokenn:

I had a problem with my game crashing all the time at a specific spot...turned out there was a mod remnant causing it. There's a Mod Remover utility on Nexus you might want to try running. I hope it helps...sounds like you've tried a lot, and I don't know what else to suggest.

https://www.nexusmods.com/cyberpunk2077/mods/8597

I have used this mod remover before and I just tried it again even with a vanilla game, no luck. Ran the bat file, verified the game files, booted it up, did the drive, crashed in the same spot.
Still appreciate the help nonetheless.

[CHEEZY]

Originally posted by rabitsrule:

could try deleting your prefetch files and resetting the shaders on your GPU and try installing your GPU drivers again using DDu to clean any left over driver files that are old

Honestly hadn't thought of that but sounds a little complex and a tad risky, most if not all my other games function just fine so I'm not sure I want to risk doing something im that unfamiliar with.
Still thank you for the suggestion.

[CSOCSO]

my game flatlines as soon as I click on Play. game doesnt even start. verified file integrity. I have zero mods. Clean gpu driver installed.

[Silverbane7]

Originally posted by CSOCSO:

my game flatlines as soon as I click on Play. game doesnt even start. verified file integrity. I have zero mods. Clean gpu driver installed.

Ok, just try one thing first then.
Go into the games folder, find 'cyberpunk 2077.exe' double click it, see if it starts for you that way.
Also, try right clicking and select 'run as Administrator' in case it thinks you don't have the rights.

(I had a clean, full install on un modded 1.63 legacy that did the same. Wouldn't start via steam, but run fine from the .exe shortcut.)

[AIX]

The game is CTD'ing after an update, right after the loading screen

"An error occurred while initializing ray tracing in Cyberpunk 2077. the game will be closed. Since the cause may be outdated or damaged video card drivers, you need to perform a clean installation of the drivers before launching the game again" is the Google translation of what it says, has anyone encountered something similar, if yes have you found sollution ?

My specs are
RTX3060 12 gb
12th Gen Intel(R) Core(TM) i3-12100 3.30 GHz
24gb RAM
and the game is installed on HDD, plus I have mods : Cyber tweak engine and Third person mod

For those who understand russian in original error it says : при инициализации трассировки лучей в Cyberpunk 2077 произошла ошибка. игра будет закрыта. Поскольку причиной могут стать устаревшие или повреждённые драйверы видеокарты, требуется выполнить чистую установку драйверов перед следующим запуском игры.

P.S. I have updated video card driver which is 551.23

Thanks a bunch

[Bowlhittz]

N mods installed or anything just crashes as soon as I hit space bar to play the game won’t let me refund either POS game studio

[orcaa]

bunch of these threads....look in technical section for suggestions.

[Cowboy]

Hello, guys! I didn't play much prior to patch 2.11. Anyway, I started my new play through (no mods - never used them), and at the beginning of the game, when V first visits Vikktor with Jackie, the game CTD when I exit Misty's and get a call from Regina. I reloaded the game and it crashed at the same spot. I managed to get past that point, but it's strange - and disappointing.

Edit: For those experiencing crashes when trying to load a save: reset keybindings to default, making sure that when you customise them you DO NOT have any actions bound to the side buttons on your mouse. This a know bug with the recent patch (2.11).