i have just installed this game on steam. i am having trouble with the ripperdoc mission. everytime it varies...i can get into a car, and then drive to the ripperdoc, but before i even turn to go down the alley way it CTD. idk what to do.....its upsetting. just moved my cyberpunk game to my C harddrive...and still crashes.
Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to write to an inaccessible address at 0x23851334BA8.
File: <Unknown>(0)
this is what i am getting....it crashed this last time when i tried to get into V's car with Jackie...soooo. idk what to do.
I've been getting both these write access
and read access violations for a while now. Moving your install location is unfortunately not going to do anything to curb this issue. These types of crashes are almost always caused by a program referring to a memory address they have no access to. What this is means is that the game is allocated by Windows areas in memory it can use to do what it needs to do to run, but it goes into protected areas anyway. Currently I'm not sure if it is either GPU or System memory it's trying to access because I don't have any developer tools that will let me dive more into this game's engine than at a relatively surface level but I'm currently quite positive this is the underlying issue for many CTD's during active gameplay based on the rudimentary testing I've done so far.
These crashes tend to happen during gameplay in very graphically dense areas of Night City, as you mention in your post I too was getting them heavily in Watson. Especially when driving fast and then having to quickly adjust my camera or taking a corner hard. It appears doing so causes the game to need more access to memory threads than it already does and when it goes to grab them, Windows catches it and then terminates the process, which in turn notifies CDPR's crash reporter and so on and so forth. This function overall is the result of an internal service in Windows called "data execution prevention", which specifically looks for this sort of issue and CTDs programs it's happening under the auspices its malicious code running at a rather deep level of your system and memory.
Initially, I wanted to just add Cyberpunk2077.exe to its exception list, only to find out through much trial and error Microsoft apparently disabled any and abilities to add 64bit executable programs to this list. No workaround actually does anything, however all 32bit programs play ball with it just fine. Thus, it would appear turning this service off entirely would've remedied it, despite being a bit risky since this service does actually help malicious code from utterly screwing your system to death. Oddly enough, disabling this system wide to test if it would change anything or even be just a temporary hotfix did nothing after a while. There is still some underlying service that is catching the Cyberpunk runtime accessing somewhere in memory it shouldn't and then force shutting it down.
Clean reinstall of windows, the game, and all mods uninstalled changed nothing, these errors were still happening at a consistent rate in the same areas. I changed graphics settings to regular settings and then both to extreme high and low settings to see if it was hardware overload leading to the game and system running inconsistent from one another, which can happen. Wasn't the issue. Shutting off DEP entirely (which I really don't recommend you do, I only did this for the purposes of testing) didn't change anything. This is appears to an internal issue with the game and its memory and graphics handling. The only way to fix this, from what I can tell with my sadly limited resources and testing would be a rewrite of these systems, and that could take some time.
