Cyberpunk 2077 PC Crash Issues

[SpacedDuck]

I have 8 sticks of the same ram across 2 PC's all other sticks do not cause the crash, (tested one at a time in the same machine) there is something dodgy about the one stick. This game has highlighted the pre existing issue. Should have been more clear. I have been having crashes for months intermittently in similarly demanding titles. But watch dogs legion and other titles currently installed are not crashing with the stick in question.
All it takes is for a single file you need to be sent to one bad sector and it screws up the whole system. I'm sure other games possibly handle these instances by retrying on another sector but it doesn't change the fact the ram is bad.

Oh okay that makes more sense and yes leaving out crashes for months is a big omission haha.

 

[br_gauron]

Hey.

I’ve try to run on Win7. I hit \Cyberpunk 2077\bin\x64\Cyberpunk2077.exe> (there is window to allow open Cyberpunk2077.exe to run as administrator) and after few second process Cyberpunk2077.exe just disappeared from Task Manager. With no info, no “Cyberpunk 2077 has flatlined”, no crash report. Nothing
Anybody know where is any crash file? I can’t find any of this. Maybe there will be some info what’s wrong.

I’ve installed new graphics driver, restart Windows, try every hint from offcial support page. Still the same.

I got: Intel i7-6700HQ 2,6 GHz
16 GB RAM
NVIDIA GeForce GTX 970M

Okey,
– I’ve try every hint from this article: “Nothing happens after double-click” (https://support.gog.com/hc/en-us/articles/212454069?product=gog)
– change regedit: “Windows 7 - Games not launching / Rundll32 related issues” (https://support.gog.com/hc/en-us/articles/360025926714?product=gog)
– even replace Cyberpunk2077.exe: “Cyberpunk 2077 - Crashes because my CPU doesn't support the AVX instruction set” (https://support.gog.com/hc/en-us/articles/360016365457-Cyberpunk-2077-Crashes-because-my-CPU-doesn-t-support-the-AVX-instruction-set?product=gog).

Still the same problem. Nothing happens. Process Cyberpunk2077.exe riches about 2GB RAM and disappeared from Task Manager. No error, no “Cyberpunk 2077 has flatlined”. Even no god-dam*ed crash report. Folder in c:\Users\[user_name]\AppData\Local\REDEngine\ReportQueue\ is empty!

I give up…

or does anybody have some new idea?

 

[earthdrowned]

All these crashes and bugs just seem to bottle down to a few different errors.

• DX12 Error - There is thousands of apperant fixes but its hit or miss which one will work
• AVX Error - There is a community fix for this on nexus works 80% of the time.
• Watchdog timeout errors - No known fix for these and I'm stuck in this pool so testing fixes best I can.

This launch hasn't been the best for them this is my first cdpr game and to be fair atleast they aplogised about it but still not an excuse for what has been released.

And you are right about this. There's multiple errors for each of these problems and none of them have a complete fix. Some of these errors in this thread are also not completely disclosed. :/

 

[ThePict]

[...]

There is one fix that will definitely work though and only if you bought through Steam!

Request a refund (you should have no problem considering the state of the game known all around the net) from Steam. Then wait till you hear that it is fixed by the developer and not us trying all sort of quick fixes that don't work. Then repurchase.

[SOLVED}

[Edited -- SigilFey]

 

[abyssalsmoke]

I'm happy this worked for you and I know you're just trying to help, but it's absolutely insane that this is something anyone should have to do to get a brand new game to run. Not blaming you at all; this rant is not directed at you!! This is just way outside reasonable troubleshooting.

Someone said it before - my PC is normally very stable, good hardware, minimum to no problems. Things like driver updates, a reboot, verifying - these are normal things.

Wiping Windows, pulling hardware, hex editing the exe - that's ridiculous. This is worse than Fallout 76 or PUBG. I'm not going to sit here and risk the integrity of my PC for this game.

I've wasted days now sitting here trying to get this game to run with literally zero progress, and it seems like getting it to launch is just the tip of the iceberg. What do I have to look forward to? 27fps? Crappy police AI? In-game crashing? Bugs and glitches everywhere I look?

If there's no sign of this game being stable in the next week or two then I'm refunding and waiting for them to get it together. It's disappointing that this is acceptable in gaming these days, but it's way less stressful that way.

Totally agree, should not have had to waste 3 days of my life to find this issue. When 99% of other games seem fine. But with that being said that's how much I just wanted to experience the game so it was worth it for me. Mileage may vary.
Also my ram is within warranty so has been replaced free of charge given there is actually something wrong with it.

 

[ThePict]

Refund submitted

 

[abyssalsmoke]

Oh okay that makes more sense and yes leaving out crashes for months is a big omission haha.

Sorry iv reposted this everywhere to try and help people so must have missed that out here.
Suspiciously notoriously unstable games like battlefield etc had this issue caused by the ram but 99% of the games I play seem fine / handle the issue with the ram much better / never crash at all.

 

[Avierr]

Tried all the fixes for the Dx12 error on reddit and on these forums.

I got a bit further on the prologue but the game reliably crashes after 30-60mins now. The nVidia drivers made it so OBS didn't work anymore, and the control panel wouldn't work either so I had to roll back the drivers.

I had enough and submitted for refund.

CDPR has lost their reputation and I'm not sorry to say that they should be absolutely ashamed of this release. Especially with how they not only lied to console players, but also to PC players and didn't even bother to mention that in their recent tweet.

It's clear you mentioned consoles because Microsoft/Sony kicked you in the balls for lying and making them look bad, but PC players don't really have a big company that will do that for them so it's easy to completely ignore.

Enjoy lying in the bed you made.

 

[SwissArmyKnife]

Just want to reiterate in the hopes devs see this and it gets addressed at some point. Using mirrors are causing hard video driver crashes, to the point the monitor loses signal from the GPU until the monitor is rebooted. Game runs fine otherwise but as soon as a mirror gets involved RIP to your GPU. Seems to happen with lots of specs, Win7 to Win10 included. Don't know why it's only effecting some of us.

Here's my specs:
Win 7 64bit
GTX 1080 (MSI Brand, tried with Afterburner on and off. Also tried underclocking the card)
Intel i7-4790k
16gb RAM
Installed on a Samsung SSD

Here's a few threads of people with the same issues.
https://forums.cdprojektred.com/index.php?threads/game-consistently-crashes-in-scenes-on-a-mirror.11043323/
https://reddit.com/r/cyberpunkgame/comments/kbbzjc
https://steamcommunity.com/app/1091500/discussions/7/2988665684340499377/
https://steamcommunity.com/app/1091500/discussions/7/2988665684326866412/?ctp=2

Here's a thread of someone reporting permanent issues after these nuclear grade driver crashes.
https://reddit.com/r/cyberpunkgame/comments/kbe12p

Only consistent fix seems to be to hamstring your settings as much as possible so that when Cyberpunk attempts to render V's character model in a reflection it doesn't set your rig on fire. Please sort this shit out.

 

[Beatupmech]

CDPR has lost their reputation and I'm not sorry to say that they should be absolutely ashamed of this release. Especially with how they not only lied to console players, but also to PC players and didn't even bother to mention that in their recent tweet.

It's clear you mentioned consoles because Microsoft/Sony kicked you in the balls for lying and making them look bad, but PC players don't really have a big company that will do that for them so it's easy to completely ignore.

Enjoy lying in the bed you made.

The infuriating part, at least for me, is that we endured all those delays just to experience this. The last delay was ostensibly to "fix" console versions but we ended up with neither the PC not console being stable. They could just as well have released it back in nov and it would still be the same but at least they would have had more time to go through all the reports and work on a proper fix. Now it looks like we won't be seeing another patch till after new year 2021 because of the holidays. I don't begrudge them their rest but knowingly releasing in this state and in dec when most(including their own staff) would be taking off just leaves a bad taste.

 

[Sayan_Mayt]

or does anybody have some new idea?

so there a few
one guy changed his display port cabble to hdm cable and helped
also one guychecked his moonitor refresh rate and was set to 59 he change it to 60 Hz and it helped
did u tryed this one ?
also did u deinstaled the display drivers ussing ddu metod in safe mode and then reinstaled it ?? or reinstalin the directX ?
also some guy done a bios update that aperently helped him to
so u can try more or give up and wait for another patch

 

[drona.667]

All this crashing problems ... I myself get crash every 2-3 hours or so. After patch 1.04, the game runs way better than ever but the crashes are somehow more frequent. While loving the game, it does bummed me a lot.

FOR REAL though, this game should have been released on PC ONLY THIS YEAR as in CDPR really focuses on PC perfromances & polishing the game to boot, like destroying the bugs, optimization, etc. Meanwhile the console versions can be focus upon next year. I am 100% sure the hype will keep going if PC versions run butter smooth & almost no bugs, even with the inevitable console players complains of waiting the game next year.

There is no denying 2020's CV19 pandemics clearly hammered devs works probably losing more than half the capacity & effectiveness. I am pretty sure ever since the first delay, CDPR probably are in constant stress to port the game on consoles, especially the base consoles version, so their actual polishing works even more reduced to the point simply not enough.

The CDPR execs should have taken great measures & risks to go temporarily PC exclusive, trying to "divide & conquer" the whole situation, instead of taking everything & we got this kind of situation. THIS WILL BE A VERY HARD LESSON to them.

 

[fridgeband]

I can't believe this is happening

 

[wuping]

Been getting the same Gpu crash for unknown reason.. unfortunately it's been happening literally everywhere. First happened when I arrived on my bike at the alley where Viktor the Ripperdoc is located, crashed there 3 times after reloading right as I arrived. After that I was able to continue playing for a bit, then crashes began to occur every 10 mins, then 5 mins then sometimes it wouldn't even get past the loading screen. Tried updating windows, verifying integrity of game cache, reinstalling drivers, only having CP2077 open (closing chrome, obs etc)



this is running a RTX3080 & Ryzen 9 3900x

I had the same problem, when I disabled RTX and DLSS the crashes stopped. I'm running a RTX 3080 & 3950X

 

[Slayhem90]

Crash,Crash,Crash ( Hotfix 1.04 )

Registered crash info file...
InternalVersion: 3.0.3217599 P4CL: 4158334 Stream: //R6.Root/R6.Patch0Hotfix2
!!!CRASHED!!!
Error Reason: Unhandled exception
Expression: EXCEPTION_ILLEGAL_INSTRUCTION (0xC000001D)
Message: The thread tried to execute an invalid instruction.
File: <Unknown>
Line 0

Any Solution ?

Ryzen 5800x
Rtx 3070

Windows is updated
GPU Driver is Updated

 

[Sam_Iverson]

I want to try a solution to one of the crashes at certain points in the story for example the Evelyn braindance, im stuck at that in a constant crash loop. Can some kind soul who can play through that quest PLEASE, once finished the quest, RIGHT AFTER IT, please make a manual save and go to the saves in (user here)/Saved Games/CD Projekt Red/Cyberpunk 2077, and please share the save file!!!! I want to try to manually skip the quest and see if it works If that happens, ill provide help to fix other crashes at certain points too!
(i noticed in the metadata that quests have names, if you can technically change that metadata name to the next quest, i wonder if it would work)

Use the AVX fix mod on Nexusmod and it will stop crashing

 

[TheSaneWonko]

I think the thing that finally did it was flashing my BIOS and updating it to the latest one. This is for: https://www.msi.com/Motherboard/MEG-X570-ACE

No crashes at all for hours now... and I was crashing every 5-10 minutes before then.
No other game or application had any issues with the old BIOS, but 0 for whatever reason - this one seemed to.
So maybe try updating your bios by looking at the respective motherboard vendor's website.

Tried that also as last resort. And was disappointed back then, as it didn't help... I'm getting really sick of that. I wonder if that offer for consoles with the refund is also accepted for PCs, when you by no means can play longer than a couple of minutes.

 

[Gruntwill]

I had the same problem, when I disabled RTX and DLSS the crashes stopped. I'm running a RTX 3080 & 3950X

Just a heads up, for me it stopped crashing when I underclocked my card by 100mhz
weird huh

 

[whitewolf_sp]

My game crashes in random places all the time , sometimes playing for 2 minutes, sometimes i can play a hour, but i never exit this game normal , always crash, i cant imagine what console players are feeling right now, if they extend the refund option for PC i will do it in a blink .....

 

[GhostxXxx]

So far my game crashed only 2 times, and thats how i fixed them.

Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0xFFFFFFFFFFFFFFFF. <-----(it was crashing before hiting main menu) lauching game from the folder fixed it i could play, in next session i was able to enter into game from steam without any problems.

Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0x18. <-------(game crashed as soon i loaded in into the world) i needed to load in from older save i was lucky older save was 10 sek older.

Hope it will help someone.