Search results

ok so update on my side is that it worked and still works. 5 hours of undisturbed gameplay. I can launch it close it launch it again etc and had no issues aside from two tiny graphic glithes that are pretty much not even worth mentioning. I have no idea why somthing so insignificant fixed it for...

Damn that's a shame :/ but maybe it will help at least someone. I had the EXCEPTION_ACCESS_VIOLATION (0xC0000005) , so i guess that's a different error resulting in a crash in the same spot.

POTENTIAL BREAKTHROUGH FOR NOT STARTING ISSUE So I saw the post by AXILEXY but it didn't work. HOWEVER i fiddled a bit with screen refresh settings and noticed mine was set for 59 and not 60. well i decided to check what would happen if i set it to 60 BOOM the game launched. I'm gonna check how...

Well to be fair, the messege on the support page still says that they are looking into crashes and as you all probably noticed this hotfix didn't do much in regards to major issues and mostly fixed some quest related stuff. I would assume that this patch was made by a dev team that was divided...

I didn't even get that far lol the game literally doesn't even start for me. no splash logo, no nothing. ehh and here i was excited for finally getting to play. more waiting i guess

Just so everyone knows -The issue with the game not starting at all still persists for me and other people on this forum.

Issue with crashing right on pressing play in launcher still not fixed. Exact same error as before.

same here, but i've heard it's some kind of GOG related file, so that's apparently unrelated

Interesting. The plot thickens lol. I will tell you though that I also have checked every possible thing just as you did. Waiting it is then i guess.

i have the exact same error code. let me guess. you probably can't even start the game like me

It doesn't matter whose got merged with which. They merged us and we can do nothing about it.

Yes. But our threads got merged, so don't say "this thread is A or B" since that is no longer the case. And the thing i quoted is a overall available thing here https://support.cdprojektred.com/en/cyberpunk/pc/sp-technical/issue/1829/game-crashes-on-launch-error-cyberpunk-2077-has-flatlined and...

That is all because this is multiple threads merged together that these issues get mixed up, but i still believe they might be somewhat related. There are people like me who can't launch the game at all and have the AVX support, and people who crash in specific locations whose CPU do not support...

It seems to be related to how the game tries to handle the commands that it sends to our CPUs rather then just an issue of strictly lack of supporting the AVX

A lot of us are in the same boat. No solution so far. We will probably just have to wait until they roll out a patch. or someone gets a miracle breakthrough lol

I am aware of that. the thing is that bottom line everyone gets a variation of this Error reason: Unhandled exception Expression: EXCEPTION_ILLEGAL_INSTRUCTION (0xC000001D) Message: The thread tried to execute an invalid instruction. it may be different file code, but the error structure is...

that might be the issue for some, but still it can not be the general source since a lot of people get crashed with AVX. I myself run a i7 4790, which may not be especially powerful but it still above even recommended specs, and yet i can't even start the game.

I can't launch and I'm on windows 10 20H2, so I'm afraid this is not the issue either

this thread is a merged one of multiple ones, so it's a bit of a mess now

Well my CPU does support AVX and I can't even get past the play button on gog since I immidiately get the flatout error. So no, It can not be universally due to AVX.