Cyberpunk 2077 PC Crash Issues

+
New update 1.12 still game crash on launching the game from launcher. Hangs at CD Project Red then just crashes

Well I'm pleased to say I've hopefully sorted the crashing on launch issue I was having, after checking all of the usual suggestions it was the switching off 'Discord Overlay' that has allowed me to resume playing the game
I don't have that turned on even :-S. Or if i quit discord, still doesn't work
 
Alright so just after this last update, my game keeps flatlining on boot up. Nooooooooooooooooooooooooooo! *dies* Whyyyyyyyy? I hope I get to play today. :p
Post automatically merged:

NVM. I just updated a few things and all is once again well within my gaming Chi bubble. :giggle:
 
Last edited:
Alright so just after this last update, my game keeps flatlining on boot up. Nooooooooooooooooooooooooooo! *dies* Whyyyyyyyy? I hope I get to play today. :p
Post automatically merged:

NVM. I just updated a few things and all is once again well within my gaming Chi bubble. :giggle:
What "things" ?
 
I've updated everything I can think of along with a fresh install since it kept crashing this morning, and now that it's almost 2pm, it's still crashing on launch. This is *still* ridiculous.
 
Re-installed Windows 10 again to test if something else might be the crash reasons. So, re-installed CP2077 again (on fresh win installation), pure vanilla state. No mods and craps. Only things that residents at my pc atm to test CP2077: Windows 10/Steam/Audio/GPU drivers/Cyberpunk 2077. Not any kind of overlays (Steam/AfterBurner/GeForce/Discord), and game KEEP CRASHING. Tried on 2nd pc, crashing again. Every single time, be it after 5 or 10 or 20 mins. Can't play it over 20 mins.

Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0x2ADE9400A88.
File: <Unknown>(0)

&

Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0x0.

File: <Unknown>(0)

Game is just broken, beyond any imagination. I want my money back. Thank you.
 
any one know how to fix this
View attachment 11073101
Hello,

I get this Error as well. I get it when I start the game now. I verified files first then tried full uninstall to reinstall. GPU Drivers are up to date.

1612921384172.png
 
So started as Nomad - when you enter Night City and there is a bunch of cutscenes - when it goes to load it looks like I am in a car and the game crashes every single time. Tried lowering gfx settings but didnt make a difference. I'm not using the GOG launcher (but disabled overlay as some suggested). Disabled steam overlay too.

Tried a new game as corpo - as i enter the office and hit "sit down" it also crashes. Not tried street kid yet but assuming there will be a point of crash there too.

Any suggestions?

EDIT to update system specs:
OS: Windows 10 10.0.19041 Build 19041
CPU: Intel i7 960 @ 3.2Ghz
Memory: 16GB
GPU: AMD Radeon R9 390
Running on HDD (SSD out of space)

I know it is an old system.. but so far I've never had an issue playing anything. Seems a tonne of people have the exact same issue I have - crashing at the "exact" same spot (Sitting down in corpo start, or entry to city in nomad and getting a "glimps" of sitting in a car I think).

Appreciate anything to get this working - not a complain post but "can you help me" post :) I know it has tonnes of bugs and I need an upgrade :)

EDIT again: AVX fix exe worked for me and am now sitting in the car :) So yeah they just need to release an official fix..

I've had similar, but not exactly the same. Ranging from unplayable due to weird graphics effects that look like V is permanently under brain attack from Johhny (even before you get the chip) , the game just plain not loading after a restart from a save file (automatic or manual), to weird graphical bugs like NPC's starting to float, NPC gangs becoming invulnerable, weapon stats staying on screen until you restart, character clipping through previously solid walls/floors. Missions being impossible to complete as dooers wouldn't open (game didn't even recognise it was a door) objects and key enemies not appearing at crucial moments so they couldn't be scanned or interacted with..... There seems to be more of these issues when playing as a "Corpo" V, but no proof

The most common being the "Shift", "CTRL", "C" and "F" failing to work until restart.

I found the only solution that worked for me was to delete every saved game on the PC, then restart with a complete fresh "V"...
Tedious, I was already fed up with the interminable "dialogues" after the first run.

I think it's a memory issue, memory is being used somewhere and not released again.

Since then I ran task manager on a second screen, and watched the memory stats, A pretty crude tool, but might give an idea. I found that memory on the game itself was growing and not "refreshing" at all, I have 32 gig, and this wasn't even close to getting full (CCP2077 was claiming around 18 gig and growing) but weirdly other apps not related, like the "Steam client webhelper" spawned multiple times, each consuming >500 meg and growing, killing these processes didn't help. Naturally they restarted, but with only around 30 meg each, and grew quickly. I think once the issue starts, the only fix is to restart afresh.

If you have a browser running in the back ground, that may exhibit the same "feature", spawning multiple child processes that all grow alarmingly. I had firefox accidentally on during one session, the thing started chewing through 500+ meg while "idle" and kept growing, plus spawned 3 more "child" processes that started eating ram.

I think a few would have browsers running in the back ground, for guides, to help working out missions/bugs etc.

I checked out other titles, and saw a similar situation, but none had these secondary apps spawning so many child processes or growing to anywhere near the same size. The only one that came close was Gaijin's "Warthunder" which may account for the myriad of issues that publication has.

So why does only this game seem to have this "feature" on my PC? Maybe it's just an evolution thing, TBH I tend to wait a year or so before buying any title, but I admit I got sucked into this one. (never again)

Sorry for the long reply, hope it might help
 
Last edited:
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0x0.
File: <Unknown>(0)

Message: Gpu Crash for unknown reasons! Callstack here is probably irrelevant.
File: e:\r6.patch0hotfix2\dev\src\common\gpuapi\src\dx12\gpuapidx12error.cpp

I want to share my solution to the above crashes with you guys:

The solution I found out was that my RAM was causing the problems. This was overclocked from 3200Mhz to 3400Mhz (Prime95 / Furmark stable). Without this overclocking, I never had a single Cyberpunk2077 crash!

I hope I can help some of you with this. Also recommend a stability test of your RAM with MemTest.
As is known, CP77 could be sensitive to OC.


System:
5800X (75% TDP limit) at X570
32Gb RAM @3200Mhz CL14
RTX3080 (Undervolted)
 
Last edited:
I just bought the Game, after installation ,the Game crashed every single time 10 seconds after hitting the Play button in GOG. I searched for a solution, learned that i need to disable GOG overlay.. (WTF?!) First 3 times, still instant crash, the 4th Time Game started.
So i try to begin my game, click on new game, select difficulity, and on the Lifepath selection the Game crashes after i click on something. ... Nice. After this, i had another 5 hopeless tries to start the Game, it started on the 6th try. Guess what it crashed again at Lifepath.

WHat the Hell??? Seriously, Guys?? I Paid 55 euros for this??! I knew and heard that there are some bugs around, but i never assumed that the game is literally unplayable, beacuse of this.
Post automatically merged:

I just bought the Game, after installation ,the Game crashed every single time 10 seconds after hitting the Play button in GOG. I searched for a solution, learned that i need to disable GOG overlay.. (WTF?!) First 3 times, still instant crash, the 4th Time Game started.
So i try to begin my game, click on new game, select difficulity, and on the Lifepath selection the Game crashes after i click on something. ... Nice. After this, i had another 5 hopeless tries to start the Game, it started on the 6th try. Guess what it crashed again at Lifepath.

WHat the Hell??? Seriously, Guys?? I Paid 55 euros for this??! I knew and heard that there are some bugs around, but i never assumed that the game is literally unplayable, beacuse of this.
UPDATE: I updated my NVidia drivers to the latest version, it helped nothing. Another Thing i tried, was to set back the Game to a Previus version, it did not help either. But at least i get to the Main Menu every time, but never get past Character editing. Lame. (My pc specs are good enough, if someone is asking)
 

Attachments

  • vybercrash.jpg
    vybercrash.jpg
    933.1 KB · Views: 223
Last edited:
I just discovered that NVidia are to blame for my crashing every few minutes.

I kept crashing no matter which driver I rolled forwards or backwards to.

All of the fixes and suggestions made no difference.



Eventually I gave up and decided to go back to the Witcher. On loading, I got the prompt that I could take screenshots with Nvidia Ansel. I saw a nice backdrop and hit the hotkeys and Ansel brings up an overlay. I mess around, then think... hey, this is an overlay. Cyberpunk doesn’t play nice with overlays. I went looking, because overlays were one of the things I’d checked. I run through GoG, so I made sure no GoG overlays were active, but as it turns out, NVidia removed the ability to access Ansel. They took it out of Add/Remove programs (I guess people were uninstalling it and they weren’t happy). There is no way to turn the Ansel overlay off (that I could find) other than downloading a third party program some people have made to access the NVidia settings.

I downloaded it, ran it, found the Ansel setting and turned it off.

Loaded Cyberpunk and got to play for a few hours with ZERO crashes. My previous best was somewhere closer to 5 minutes.

Fuck NVidia.

If you have an NVidia card and you’ve tried everything else, then killing Ansel (hiding in the background) might be the answer for you.

I thought I’d turned off all overlays, but NVidia hide theirs.
 
Hi all.

I had the same problem. My game crashed even before it launched with Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005).

So I reverted to v1.06 (53GB download) and all is working as before (for now at least).
Hope this helps someone.
 
@SigilFey

After spending hell load of time on my issue ... i finally got it.

I received BSOD ... and later in logs found that system was not able to write memory dump.

NVME temp sensor failed - and was not reporting correctly that it was simply overheating - NVME replaced - problem solved.
The worst thing about this is .. no stress test soft revealed this issue - i think i was lucky to finally get this BSOD.
 
Was that a Ryzen 5600x, by any chance? I know another person that just had some serious heat issues with them.
 
The game crashes every 1h or so for not apparent reason. Every overlay or other program closed, antivirus disable.
flatline.png
 
After 100+ hours started crashing with these errors:

Code:
Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0x140ED74B2.
File: <Unknown>(0)

Code:
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.patch0hotfix2\dev\src\common\gpuapi\src\dx12\gpuapidx12error.cpp(40)

GPU is GeForce RTX 2080 S

Crashing resolved by:
  • Uninstalling latest Nvidia driver with DDU and installing GeForce driver version 446.16

  • Underclocking VRAM -502 mHz using MSI Afterburner
 
The DPC WATCHDOG Violation blue screen is very dreaded error and to fix the errot Microsoft community suggested to replace the iastor.sys driver with the storahci.sys driver will fix DPC Watchdog Violation error.

So, follow the steps to do so:
  • Right-click the Start > choose Device Manager.
  • Then expand the IDE ATA/ATAPI controllers.
  • Now choose the controller with SATA AHCI in its name (Standard SATA AHCI Controller).
  • Well to verify you’ve selected the right controller > right-click the controller > choose Properties > click the Driver tab, > Driver Details. And check that iastor.sys is a listed driver > click OK.
  • Next from the Driver tab > choose Update Driver.
  • Then choose Browse my computer for driver software.
  • And select Let me pick from a list of device drivers on my computer > choose Standard SATA AHCI Controller.
  • Click Next > Close > restart the PC.
Source: https://answers.microsoft.com/en-us/windows/forum/all/suddenly-employee monitoring-getting-bsod-with-dpc-watchdog-violation/d295c21a-a59a-4271-b0d9-e8cdd2eddd56

is it possible that it helped once, then after a long time the error appeared again and now it does not help?
 
Tweaks like this can and very often will be borked by the next (and all subsequent) Windows updates. .SYS files are core Windows OS files, and updates will normally either delete or replace such files with "unmodified" ones. In other cases, the way the new version of the OS works, it will no longer be able to recognize the changes introduced by such tweaks, and will therefore ignore them. (As in, the new version of the OS does not always read and process the older version of .SYS file that was replaced, so it will simply default to the .SYS file it wants, or will cause a new issue.)
 
Top Bottom