I'm in the same boat, the game was running perfect until patch 1.05 and now my computer crashes. I'm going to revert to patch 1.04 and see if that helps. Tried all the obvious solutions to no avail.
Welcome aboard... stating the obvious perhaps, but backup your saves first... they won't be backwards compatible with 1.04 from what I understand.
update : just sent a report to cdpr and they said that i have to update my MOTHERBOARD AND SOUND BOARD doing that right now to se if its going to work if it works i will do another update
Post automatically merged:
did that twice already
Post automatically merged:
Update : same sh#t after updating everithin guys relly be playn with us they f#ck up tell us to update everithing this hot fix 1.05 [more like hot sh#t 1.05] its making me mad as hell ngl
Last edited:
Dude, @motorbit is giving outstanding advice, so I suggest you spend some time trying to understand it. Ask questions. It's OK if you've never stress tested a PC before using tools like Prime95. A lot of people spend time in these forums for one sole reason -- to help others enjoy the game.
You, on the other hand, are misplacing your frustration at a forum member that is going above and beyond to try to help you restore stability.
None of us wrote the game, were involved in its testing, etc. so check the hostility at the door please.
Now, I will echo what @motorbit has been saying..... you are experiencing something that we see time after time in the PC gaming community. You have a system that has seemingly been stable, and now it is unstable with "just this game".
To your credit, you did a good troubleshooting step by removing RAM. But the results don't support what you think it means -- that it is the game. Instead, the results indicate that your RAM is either faulty, mismatched, or configured wrong, and/or overclocked.
Hence when you remove 2 of the 4memory modules, the problem goes away.
What that means, is your system was never fully stable running high compute workloads -- you just never happened upon a workload that makes that instability come to the surface.
Now, it could be bad memory, or memory that is not quite compatible... it could even be that your CPU memory controller is bad, or your power supply isn't quite up to the job. There are quite a few possibilities.
But the right way to proceed is to stop blaming the game, and turn your attention to truly stress testing your system and wringing out whatever is causing memory to not work. You may not even have to replace any parts., or you might.
But I would be willing to bet a 6 pack that the problem can be duplicated using prime 95.
Sorry to get on you a little, but I think it was necessary. You will have a lot of people trying to help you, but not if you continue to snap at their hands as they try.
Coincidentally enough, EVGA just happened to have newer BIOS for both my mobo (x299 FTW-K) and sound card (NU Audio)... so I updated both. Exact same issue persists. Not sure how previous poster got a response from CDPR, but the fact that they are telling people it's their hardware, and to start messing with BIOS n shiznit, after the game had been running flawlessly (in the case of posters in this thread) up to 1.05, and other games work flawlessly, and nothing on these systems indicate any hardware issues... now all of a sudden it's a hardware/bios issue (and not the game which is riddled with major issues)... does not invoke confidence in the devs abilities to address these issues... possibly they're just trying to get people to upgrade this and that to rule out hardware issues... but clearly they are not paying attention to the reports which clearly indicate this issue (among others) are the game, not the user, not the users hardware... I am beginning to loose what little faith I had. It's a fantastic game, and the engine is beautiful, so they have devs who know what they're doing, but clearly there is some disconnect with their QA / Test engineers.
For those posting here starting to get frustrated with each other blaming the game or the user or the hardware ya'll are equally "hostile" from different perspectives... not helping. Still, I'd bet 2 stick of RAM this is not a hardware issue.
For those posting here starting to get frustrated with each other blaming the game or the user or the hardware ya'll are equally "hostile" from different perspectives... not helping. Still, I'd bet 2 stick of RAM this is not a hardware issue.
im relly sorry for taking your time but can you help me? my issue is before hotfix 1.05 the game was perfect not a single crash, after it i cant play for more then 10 min without a crash and the crash dont even comes with a report the role system crashs blue screen [sorry for the bad english im verry frustreted] and games on pc its a kinda new thing with me but wathever you tell me to do i will try[ if i dindt have already ]
Post automatically merged:
i reported to then on the crash report an they sent me an email like 30 min after asking me to update my motherboard driver [ my motherboard asus 390z m prime ] and the sound drive i updated the hole thing and it dindt change nothing at all stil cant play more then 5 min
Last edited:
to my experience its seldom defective hardware, but missconfiguration or outdated firmware. still problems with the system though.
in any case. you do not seem to look for useful answers but answers you like. as you pointed out, you percive anything else as hostility. i am wasting my time here.
I'm playing the ps4 pro, not having issues for the most part. Bar some few minors drops but ive gotten hard stuck at the mission where you jump onto the float, after takemuras text line [wait] then says stay safe. If i reply that to him the game immediately goes into loading and hard crashes.
Anyone else having this issue? Would maybe loading a previous save file fix this or should i wait for patches?
Anyone else having this issue? Would maybe loading a previous save file fix this or should i wait for patches?
really? because I've tried every suggestion in this thread and many others... short of taking the game apart with a hex editor or my system apart with a hex wrench. The system of which I speak is but a few months old and is (was) top of the line everything. It's also water cooled, so forgive me if I'm reluctant to start breaking it down and start swapping out parts until someone (from CDPR who is intimate with the games tech) tells me they've determined it's hardware/driver related... not just throwing out random things to try and crossing fingers.
When the game is working flawlessly until the 1.05 patch, then all of a sudden it doesn't work at all, my first suspect is obviously the patch. Nothing else in my system changed during that hour window... no hardware, no drivers, no software, nada... just the patch. So, while it's certainly possible some remote section of memory went bad or some random Windows update glitched something the game chokes on... it's still the game choking, not my hardware. I happen to also be a game developer and am well aware of the complexities and intricacies of PC hardware, but if multiple reports suggested that their issues arose simultaneously with a new patch, I'd start looking at why the patch might be broken on certain systems instead of telling people to start messing with their BIOS in hopes that might magically make the patch start working again.
If it is indeed the patch that borked the game for so many... wouldn't you rather they figure out why and fix it? Instead of having thousands of people messing with low level stuff on their machines that might actually exacerbate the problem and make it harder to reproduce or track down?
"Hostile" was your words, not mine.
unrelated to this thread. 1.06 just went life
so you might want to try that.
Post automatically merged:
look. divination is not my strong suit. i can give you some tips. of course they are not guaranteed to work because i cant tell for sure whats wrong with *your* system.
what i can tell you is that if your system shuts down or freezes, its not the game. but as a developer you should know that, though i would bet you are also a rocket surgeon.
i also dont tell you to take your system appart or bother to check your bios settings. in fact, im quite totally done with telling you anything. after all... its not me having these issues
Last edited:
Maybe I missed something here... my crashes aren't BSODs/system crashes, they are game flatlines/CTDs... I assumed that's what everyone in this thread was talking about "Game crashes after 1.05". If it were BSODs, then yeah, time to start messing with hardware, but the CTDs are undoubtedly game/1.05 specific.unrelated to this thread. 1.06 just went life
so you might want to try that.
Post automatically merged:
look. divination is not my strong suit. i can give you some tips. of course they are not guaranteed to work because i cant tell for sure whats wrong with *your* system.
what i can tell you is that if your system shuts down or freezes, its not the game. but as a developer you should know that, though i would bet you are also a rocket surgeon.
i also dont tell you to take your system appart or bother to check your bios settings. in fact, im quite totally done with telling you anything. after all... its not me having these issues
Glad you're not having these issues... it's a great game and it sucks to not be able to play it over the holidays when I actually have time to. Also glad you're willing/able to help out here regardless... but getting defensive over what I'd consider a friendly debate over the nature of the beast here... well, your prerogative I suppose.
I did install the 1.06 patch, and the issue persists unfortunately.... which makes sense because the patch addresses save file corruption, not CTDs. Sooo we wait...
well. if its "just" ctd, yes. its at least possible that its the games fault.
however. the game does run rock stable for the vast majority of users many of whom use very simmilar hardware to yours.
i would argue IF the game was indeed to be blamed here, it would affect everybody.
in any case, the game does write a crashlog when ctd happen. any luck analyzing them?
Without debug info, or even aftermath hooks for that matter, the crashlog is somewhat useless, but it's identical to other logs I've seen posted for this issue:
Version=1
EventType=REDEngineErrorReport
EventTime=0
ReportIdentifier=ffffffff-ffffffff-00000001-00000000
Sig[0].Name=StackHash
Sig[0].Value=0x0000000000000000
Sig[1].Name=ErrorReason
Sig[1].Value=Unhandled exception
Sig[2].Name=InternalVersion
Sig[2].Value=3.0.3235023 P4CL: 4177747 Stream: //R6.Root/R6.Patch0Hotfix2
...wouldn't necessarily affect everyone... could be anything else in common only with these users (besides the patch); Something corrupted in the cache, something in inventory that disappeared, some game setting or graphics setting... we won't know until someone (probably with debug access) tracks it down.
yeah, or another app running haywire. as said. could be the game in your case. im still sceptical. guess you can ask teksupport, but they will be *really* buissy.
found this: https://www.gog.com/forum/cyberpunk_2077/game_crash/post29
found this: https://www.gog.com/forum/cyberpunk_2077/game_crash/post29
I've sent several reports to CDPR both via the crash reporter and support email... haven't heard a peep from them yet. The link has some helpful info for sure, and seems encouraging since it does seem to fix the issue for those on older versions of Windows (<=1607)... but I've been on the latest version of Windows 10 Pro (20H2 build 19042.685) since August(?). I also checked my VC++ redist packages which are also all >= required versions (probably because I use Visual Studio daily)... so close, but no cigar in my case :/