2.0 Crashing Fixes and Solutions

[Goodgoodie]

If anyone else has experienced crashing and found a solution please let me know. My specs are RTX4090 I-9 13900K 32Gb DDR5 on 2Tb NVME.2 and my game crashing every few minutes. I've already tried to verify game files,update drivers/windows, and changed settings, disabled Hyper-Threading, and even undervolted my CPU values from 55-58 to 54 for my performances cores and that didn't fix it either. PLEASE SHARE your experiences and fixes.

[SuckaFish: hydration complete]

Escrito originalmente por Zer0:

Escrito originalmente por SuckaFish: REHYDRATED:

at least you can play the game, I've tried all day to troubleshoot without even the ability to see anything in-game other than the character creator.

Crash on startup I'd use DDU. Seems driver related. Also make sure Windows is updated.

I haven't used DDU yet but I've done quite literally everything to get this thing running, my windows and my drivers are all up to date though so I don't think it's that. (however I fail to see what uninstalling my drivers will even do, I can get into and launch the game just fine and I don't even crash or freeze I just am looking at the loading bar at 30 percent for over 20 minutes, probably longer if i let it keep going without me using task manager to close the bastard.)

[Dyna]

Escrito originalmente por SuckaFish: REHYDRATED:

Escrito originalmente por Dyna:

Anyone tested 2077 in administrator mode?

I have been "playing" in administrator mode with both the Redlauncher and Cyberpunk exe and not launching in administrator means the game won't even open in just goes into a black screen and closes, not even a crash report. SO i do believe running in administrator alleviates some issues.

'
Interesting.

Maybe worth a shot with the Access Violation bug. I am going to bed now though so i hope a few people might test it and report back.

[SuckaFish: hydration complete]

Escrito originalmente por Dyna:

Escrito originalmente por SuckaFish: REHYDRATED:

I have been "playing" in administrator mode with both the Redlauncher and Cyberpunk exe and not launching in administrator means the game won't even open in just goes into a black screen and closes, not even a crash report. SO i do believe running in administrator alleviates some issues.

'
Interesting.

Maybe worth a shot with the Access Violation bug. I am going to bed now though so i hope a few people might test it and report back.

The access violation bug was my exact issue prior to not having launched the exes in admin mode, now I'm lucky enough to see the character creator and the menus :D. But now I can't get in-game no matter what I do. When not doing it this way though I would either get and access violation error or as previously mentioned just a force close without any flatline report.

[Zer0]

Escrito originalmente por SuckaFish: REHYDRATED:

I haven't used DDU

Well I can't make you try my suggestions. Can't help then though.

The startup screens are when shaders are being prepared. If you want to try something before DDU, presuming you're willing to, I'd clear the shader cache. You can do this with both NVIDIA and AMD drivers directly. You'll know this worked if game startup is noticeably slower.

I'd also, since it's very easy, clear both your settings and saved file directories. Warning that deleting these folders will wipe your saves and settings. If you want to keep your saves I'd just move them elsewhere as a troubleshooting step.

After doing some, or preferably all, of the above I'd launch the game outside Steam so that there's no cloud sync.

Settings:

%LOCALAPPDATA%\CD Projekt Red\Cyberpunk 2077

Saves:

%USERPROFILE%\Saved Games\CD Projekt Red\Cyberpunk 2077

Game executable:

<install dir>\bin\x64

[Holliday]

I have done everything, deleted and verified every file I've been told to, reinstalled the game 6 times, clean installed, removed the launcher, launched from the .exe, and had to restart my PC about 20 times. This game will simply NOT WORK. If I'm lucky I'll finish character creation just for the loading screen to freeze. Most of the time I can't even get past the developer splash screen without it crashing. Someone PLEASE help because this is getting to the point where I may just try to refund the game since I simply DOES NOT WORK.

[SuckaFish: hydration complete]

Escrito originalmente por Zer0:

Escrito originalmente por SuckaFish: REHYDRATED:

I haven't used DDU

Well I can't make you try my suggestions. Can't help then though.

The startup screens are when shaders are being prepared. If you want to try something before DDU, presuming you're willing to, I'd clear the shader cache. You can do this with both NVIDIA and AMD drivers directly. You'll know this worked if game startup is noticeably slower.

I'd also, since it's very easy, clear both your settings and saved file directories. Warning that deleting these folders will wipe your saves and settings. If you want to keep your saves I'd just move them elsewhere as a troubleshooting step.

After doing some, or preferably all, of the above I'd launch the game outside Steam so that there's no cloud sync.

Settings:

%LOCALAPPDATA%\CD Projekt Red\Cyberpunk 2077

Saves:

%USERPROFILE%\Saved Games\CD Projekt Red\Cyberpunk 2077

Game executable:

<install dir>\bin\x64

Thank you, I will try both of these things shortly I'm just floored that I'm having such trouble playing this game since I have the specs for it and upgraded my computer to play the DLC and new update. I've just been squeamish doing things like deleting my shader cache and drivers just for a shot at playing this game.

[Zer0]

Escrito originalmente por SuckaFish: REHYDRATED:

Thank you, I will try both of these things shortly I'm just floored that I'm having such trouble playing this game since I have the specs for it and upgraded my computer to play the DLC and new update. I've just been squeamish doing things like deleting my shader cache and drivers just for a shot at playing this game.

Understood, it can be a bit daunting doing this but these are all standard troubleshooting steps. DDU is so well known for that reason. You'll be fine.

If someone tells you to up the voltage on your CPU then you should run screaming.

[SuckaFish: hydration complete]

Escrito originalmente por Zer0:

Escrito originalmente por SuckaFish: REHYDRATED:

Thank you, I will try both of these things shortly I'm just floored that I'm having such trouble playing this game since I have the specs for it and upgraded my computer to play the DLC and new update. I've just been squeamish doing things like deleting my shader cache and drivers just for a shot at playing this game.

Understood, it can be a bit daunting doing this but these are all standard troubleshooting steps. DDU is so well known for that reason. You'll be fine.

If someone tells you to up the voltage on your CPU then you should run screaming.

Used DDU program on my nvidea card, and to my surprise the loading bar actually made it half way before crashing :D

[Za'Muro]

deleting the stuff inside dxcache folder for nvidia fixes it but u have to delete it on every start or it will crash again

[SuckaFish: hydration complete]

Escrito originalmente por Za'Muro:

deleting the stuff inside dxcache folder for nvidia fixes it but u have to delete it on every start or it will crash again

Already did this, as well as literally everything everyone else suggested. Now I get clr errors instead of the game being stuck at a loading screen even though I've reanstalled net framework as well as the latest Visual V++ redists. There is no other course of action for me to take other than to refund or wait until CDPR fixes their poorly made game.

[o-o]

hey, so just read this thread and im trying stuff, but my errors are different. my main redengine reports are reading the generic and oh-so unhelpful for searching online

"Error reason: Assert
Expression: <Unknown>
Message: Gpu Crash for unknown reasons! Callstack here is probably irrelevant. Check if Breadcrumbs or Aftermath logged anything useful.
File: E:\R6.Release\dev\src\common\gpuApi\src\dx12\gpuApiDX12Error.cpp(42)",

while checking temp files gives me an error that i used to see in apex and apex alone:

"Device Removed Reason: 0x887a0006 : The GPU will not respond to more commands, most likely because of an invalid command passed by the calling application."

this isnt the only error code i get, but it is usually the 0x887a0006 error, ive also gotten the same (at least at first glance, not sure if it was the exact same) errors with a 5 or 7 ending. figured it was something with drivers, but any attempts at a clean driver install or studio drivers hasnt fully fixed anything. Now, while generally searching an error code will either be entirely off the face of the earth and unhelpful, or super common knowledge with a good fix, mine is currently neither. This error code is only ever coming up for apex legends fixes (which do not work in cyberpunk, for various reasons). So far, turning HDD mode to "auto" with the nvidia studio drivers at full default settings (with the game at medium graphically, no motion blur or anything though) has given me the most stability, but nothing has fully stopped crashes happening. I even went ahead and upgraded to windows 11, but that didnt fix it either. I'm running no overclocks, ive reset my bios to default settings, ive tried weird fixes like installing mods to make my graphics worse to use the GPU less, I even went and reseated my graphics card and the power cables to see if maybe it was just a bad connection. No dice for anything. If anyone has any (and i mean any) possible fixes for these errors, please reply with it. thanks. (P.S. sorry for the wall of text this message has, wanted to include as much possibly helpful info as i could).

[o-o]

Also, similar to another person in here, my redlauncher also pops up in my error log whenever it autocloses for launching cyberpunk.

[Zer0]

Escrito originalmente por Docn1ght:

Message: Gpu Crash.

That's what's happening. Your GPU driver is actually crashing. If you're not sure you'll see that Windows notes the crash in event logs. There's a myriad of reasons this happens, but none of them particularly good. This ranges from a bad driver, to bad thermals, all the way to a bad actual card.

You should list your GPU first off. Next I'd watch thermals while you play. Typically I don't see this error from heat but it's possible. You mentioned reseating it and re-attaching power cables. Make sure all power cables have their own rail (you don't use more than one plug per cable that goes to PSU). Usually bad power cables result in a hard shutdown due to transient spikes.

When you see "device removed" for a GPU, basically Windows just can't communicate with your card anymore. So it will disappear from the system briefly. Most commonly this is just a driver crash. Windows will automatically restart the driver. But, it is entirely possible the card is bad.

[o-o]

alright guys, well so far in several hours of gameplay, ive not crashed once. the magical, fix it all solution? turned off the nvidia overlay. i suspect that the overlay was interfering with the game, some way or another.

[Zer0]

Escrito originalmente por Docn1ght:

alright guys, well so far in several hours of gameplay, ive not crashed once. the magical, fix it all solution? turned off the nvidia overlay. i suspect that the overlay was interfering with the game, some way or another.

Ah good to hear. Means the driver was just crashing.