Constant CTD due to access violation error (0xc0000005). I Have tried EVERYTHING.

[madridge]

After more than 100 hours of playing, all of a sudden I started getting persistent access error violations, even on fresh installs of the game with no mods. The date this started occurring was October 18th, which is the same day driver update released for my CPU. I tried uninstalling that driver then rolling back to the previous driver, but that didn't solve it. I have tried several benchmarking and stress testing tools to see if this issue occurs again due to faulty hardware, but it only happens for cyberpunk. This error also seems to have started happening the moment that the Phantom Liberty area / quest was unlocked for me. However, this error still occurs if I load a save before I unlocked it. This is so insanely depressing, I've been trying for nearly a week to fix this issue but NOTHING is working. I have noticed recently that sometimes when I restart my PC, after the initial shut down, my screen will remain black, and the DRAM led status indicator on my motherboard will be lit. I usually have to turn off my PC via the power button on my case and turn it back on to get it running. But why would my RAM be perfectly fine running very stressful benchmarking applications and not cyberpunk? Note that with a fresh install and zero mods and after validating the files, it takes about an hour to experience the crash. With the mods I was playing with for my 100+ hour save, it crashes very quickly, within a couple minutes. Below, I will include everything that I have tried to fix this issue, system specs, and the contents of the analyzed Crash DMP file. I am running the latest Steam version of the game.

Things I have tried, with no success:
- Updated Windows 11, made sure all drivers are up to date
- Uninstalled the game, then did a clean install with no mods
- Verified integrity of game files
- Checked for malware
- Clean boot
- Run Cyberpunk 2077.exe as administrator
- Reseatted RAM
- Ran DDU to uninstall GPU drivers then installed the latest NVIDIA GPU Drivers
- Uninstalled CPU driver, rolled back to previous driver
- Rolled back to previous Chipset driver
- Uninstalled and reinstalled Microsoft C++ Redistributables
- Disabling all CPU / RAM overclocking settings in BIOS (i only used AMD EXPO/XMP profile before and it ran perfectly before this error started occurring)
- Updated my BIOS
- Ran MemTest86 overnight --> zero errors found
- Windows memory test --> zero errors found
- Ran Prime95 for two hours --> zero errors found
- Ran Heaven benchmark for 1.5 hrs, OCCT for 1 hr, FurMark for 1 hr --> no errors
- sfc /scannow --> no corrupt system files found
- Turned off cross-platform saves
- Reset keybinds to default
- Checked Windows Event Viewer --> sometimes it gives me something to check, sometimes it doesn't. it always gives me the same access violation error, but doesnt list a faulty module.
- Cleared CMOS

System Specs:
GPU: NVIDIA GeForce RTX 4080 SUPER
CPU: AMD Ryzen 7 7800x3d
Motherboard: B650 AORUS ELITE AX ICE
RAM: GSKILL TRIDENT Z5 NEO RGB DDR5
Storage: Samsung SSD 990 PRO 2TB

Crash DMP File Contents (Note that Exception Paramter1 is always the same):
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 0

Key : Analysis.Elapsed.mSec
Value: 495

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 0

Key : Analysis.Init.Elapsed.mSec
Value: 2373

Key : Analysis.Memory.CommitPeak.Mb
Value: 168

Key : Analysis.Version.DbgEng
Value: 10.0.27704.1001

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Failure.Bucket
Value: INVALID_POINTER_READ_c0000005_Cyberpunk2077.exe!Unknown

Key : Failure.Hash
Value: {88f97a57-4e57-16de-3c3e-c05d5e0510bf}

Key : Timeline.OS.Boot.DeltaSec
Value: 11947

Key : Timeline.Process.Start.DeltaSec
Value: 803

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Version
Value: 10.0.22621.1


FILE_IN_CAB: Cyberpunk2077.dmp

NTGLOBALFLAG: 0

CONTEXT: (.ecxr)
rax=00000000ffffffff rbx=0000000136b60be8 rcx=000000afffffff50
rdx=000001c292630000 rsi=000001c292630000 rdi=0000000136b60f40
rip=00007ff77c0b40a6 rsp=0000000136b60b50 rbp=0000000136b60ca0
r8=0000000000000002 r9=0000000136b60f5c r10=0000000000000001
r11=0000000136b60c10 r12=000001aeae2c73e0 r13=000001ae887b9730
r14=0000000136b60f40 r15=000001ae887b9738
iopl=0 nv up ei ng nz ac po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010296
Cyberpunk2077+0x29840a6:
00007ff7`7c0b40a6 488b8411000b5c00 mov rax,qword ptr [rcx+rdx+5C0B00h] ds:00000272`92bf0a50=????????????????
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff77c0b40a6 (Cyberpunk2077+0x00000000029840a6)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000027292bf0a50
Attempt to read from address 0000027292bf0a50

PROCESS_NAME: Cyberpunk2077.exe

READ_ADDRESS: 0000027292bf0a50

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000027292bf0a50

IP_ON_HEAP: 0000000600000003
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.

FRAME_ONE_INVALID: 1

STACK_TEXT:
00000001`36b60b50 00000006`00000003 : 000001c2`92bf0ae0 000001ae`740602f8 00000000`00000160 000001ae`74060cf0 : Cyberpunk2077+0x29840a6
00000001`36b60b58 000001c2`92bf0ae0 : 000001ae`740602f8 00000000`00000160 000001ae`74060cf0 00000000`00000000 : 0x00000006`00000003
00000001`36b60b60 000001ae`740602f8 : 00000000`00000160 000001ae`74060cf0 00000000`00000000 00000000`00000000 : 0x000001c2`92bf0ae0
00000001`36b60b68 00000000`00000160 : 000001ae`74060cf0 00000000`00000000 00000000`00000000 00000001`36b60f40 : 0x000001ae`740602f8
00000001`36b60b70 000001ae`74060cf0 : 00000000`00000000 00000000`00000000 00000001`36b60f40 00000000`003c50a0 : 0x160
00000001`36b60b78 00000000`00000000 : 00000000`00000000 00000001`36b60f40 00000000`003c50a0 00007ff7`7c0b3e2e : 0x000001ae`74060cf0


STACK_COMMAND: ~6s; .ecxr ; kb

SYMBOL_NAME: Cyberpunk2077+29840a6

MODULE_NAME: Cyberpunk2077

IMAGE_NAME: Cyberpunk2077.exe

FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_Cyberpunk2077.exe!Unknown

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 3.0.77.64623

FAILURE_ID_HASH: {88f97a57-4e57-16de-3c3e-c05d5e0510bf}

Followup: MachineOwner

 

[LeKill3rFou]

Just to be sure, when you say "clean install with no mod" it's this :

How do I perform a clean install of the game? — Cyberpunk 2077 | Technical Support — CD PROJEKT RED

Welcome to CD PROJEKT RED Technical Support! Here you will find help regarding our games and services, as well as answers to frequently asked questions.

support.cdprojektred.com

Also, did you try on a brand new playthrough?
Because loading a modded save on an unmodded game could cause even more issues.

 

[SigilFey]

It's possible that there's still corruption in the installation. It's looking for something in memory that it either can't load, or it isn't able to read it when it's loaded.

- Uninstalled the game, then did a clean install with no mods

If you were using mods in the past, it may be necessary to load the same mod library as before, ensuring that all mods are up to date and working with the present version of the game (or whatever version you're using). That's definitely something that could mean a needed file is missing from RAM when the game goes to load the save file.

 

[madridge]

Just to be sure, when you say "clean install with no mod" it's this :

How do I perform a clean install of the game? — Cyberpunk 2077 | Technical Support — CD PROJEKT RED

Welcome to CD PROJEKT RED Technical Support! Here you will find help regarding our games and services, as well as answers to frequently asked questions.

support.cdprojektred.com

Also, did you try on a brand new playthrough?
Because loading a modded save on an unmodded game could cause even more issues.

Yup. Just tried that again, and got a crash after starting a new game. I played for approximately 14 minutes before the crash occurred. It's the exact same crash too, with the Exception_Parameter1 being the same. I started a new game with the option of skipping to Phantom Liberty just fyi.

Post automatically merged: Oct 25, 2024

It's possible that there's still corruption in the installation. It's looking for something in memory that it either can't load, or it isn't able to read it when it's loaded.

If you were using mods in the past, it may be necessary to load the same mod library as before, ensuring that all mods are up to date and working with the present version of the game (or whatever version you're using). That's definitely something that could mean a needed file is missing from RAM when the game goes to load the save file.

I tried that multiple times. I even redownloaded every mod i had and installed them on a fresh new installation of the game, and the error still occurred. I installed one mod at a time, and tested to see if it's an issue with any one particular mod, but I get the same crash regardless. Even if there's no mods, and even if there's only one mod.

 

[LeKill3rFou]

Yup. Just tried that again, and got a crash after starting a new game. I played for approximately 14 minutes before the crash occurred. It's the exact same crash too, with the Exception_Parameter1 being the same. I started a new game with the option of skipping to Phantom Liberty just fyi.

Ok
If you didn't, you should really contact the support (provide a DxDiag and the link of this thread).

My game crashes — Cyberpunk 2077 | Technical Support — CD PROJEKT RED

Welcome to CD PROJEKT RED Technical Support! Here you will find help regarding our games and services, as well as answers to frequently asked questions.

support.cdprojektred.com

 

[SigilFey]

^ That.

Whatever is happening, there's a problem with your system caching or reading the RAM.

 

[madridge]

^ That.

Whatever is happening, there's a problem with your system caching or reading the RAM.

That's what I'm thinking too, I'm not sure why I wouldn't get crashes when running very stressful benchmarking applications though. I sent a support ticket.

 

[DonnerTech]

That's what I'm thinking too, I'm not sure why I wouldn't get crashes when running very stressful benchmarking applications though. I sent a support ticket.

Hey, did support answer you?

 

[Abrams]

This error was really annoying to me, I got random (every few minutes) crashes to desktop with

access violation error (0xc0000005)​

It seem that it happen more often when I travel in game, when game is loading new content...
I have tried bios settings, default key bindings, paging file ... all these "solutions" found on internet without success.

I am also using a lot of mods which I did not wanted to give up on.
My game is modified manually - i downloaded all the mods from the Nexus Mods and unzipped in the game folder.
I am also using the GOG version (not Steam).

For me the solution was to "disable" the mods in the GOG. ​

Just before you click "Play", click the gear icon and DESELECT "enable mods", this DOES NOT DISABLE your manually installed mods, I still have the CET console, mod settings in game, etc. all the mods are working as before, this option only disables the REDmod, NOT the manually installed mods !!
And for me this was the solution, i did not have a single crash to desktop since. Tested for hours-long sessions already

My game version is 2.31a.

 

[slockey]

Game was working basically perfectly before latest patch.

Now I just get this.

Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread caused a user-mode data execution prevention (DEP) violation at 0x7FFE5734B2D9.

I tried a clean install of the game.... exact same thing.
I even did a clean install of windows and redownloaded the game fresh... exact same thing.
Tried starting the game from the windows game bar.... got a bit further into the intro sequence than before then crashed the entire computer.....
Page fault in nonpaged area....

I've got a 4090 so am well beyond minimum specs for this game. Was happily playing with ray-tracing enabled at a solid 60fps before....

What went wrong????

 

[slockey]

I get the exact same thing trying to run the game with zero mods. Fresh install of windows and game.

 

[LeKill3rFou]

Tried starting the game from the windows game bar.... got a bit further into the intro sequence than before then crashed the entire computer.....

You mean that Windows crashes no just the game?
If yes, it's a bit worrying
So first, look at the suggestions by the support in case of crashes and be sure you check everything. If nothing works and if it's not already done, send a ticket to the support for help ("contact us" button).

My game crashes — Cyberpunk 2077 | Technical Support — CD PROJEKT RED

Welcome to CD PROJEKT RED Technical Support! Here you will find help regarding our games and services, as well as answers to frequently asked questions.

support.cdprojektred.com

 

[SigilFey]

Threads merged.

For me the solution was to "disable" the mods in the GOG. ​

I get the exact same thing trying to run the game with zero mods. Fresh install of windows and game.

Disabling mods is not always enough. Often, removing mods can cause issues, as the reference data created by mods will remain in the save state of the game. A clean installation, followed by beginning a brand new game in an unused save slot is the only way to ensure that the game is running in 100% vanilla mode.

Older save game files may not work properly unless all mods that were ever used are installed using versions updated specifically for the present version of the game. (This is not guaranteed to happen -- it all depends on the mods used, possibly synergy issues between different mods when used with a specific game version.)

If beginning a new game in a new save slot following the clean installation still results in an error, do send that into Support. That would be an issue with the game itself.

 

[Bartinga2077]

Game was working basically perfectly before latest patch.

Now I just get this.

Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread caused a user-mode data execution prevention (DEP) violation at 0x7FFE5734B2D9.

Why don't you simply rollback the game? CDPR was so kind to offer rollback on Steam too. Just right-click the game, select Properties, Betas, Beta Participation.

Only issue is that a save of the new version doesn't work on the old, last I checked.

 

[SigilFey]

Why don't you simply rollback the game? CDPR was so kind to offer rollback on Steam too. Just right-click the game, select Properties, Betas, Beta Participation.

Only issue is that a save of the new version doesn't work on the old, last I checked.

Most likely, any saved game made on a later version will experience some sort of issue if used in a roll-back installation. Especially if mods were also used. It will probably clear up any issues that mods may have introduced, but at the same time introduce new issues with vanilla data.

 

[Bartinga2077]

Most likely, any saved game made on a later version will experience some sort of issue if used in a roll-back installation. Especially if mods were also used.

Learned that the hard way. Luckily made a backup so avoided that drama.

 

[SigilFey]

Learned that the hard way. Luckily made a backup so avoided that drama.

Game version/modding drama:

 

[Bartinga2077]

Game version/modding drama:

Especially if you have a thousand of 'em.

 

[Abrams]

Disabling mods is not always enough. Often, removing mods can cause issues, as the reference data created by mods will remain in the save state of the game. A clean installation, followed by beginning a brand new game in an unused save slot is the only way to ensure that the game is running in 100% vanilla mode.

Older save game files may not work properly unless all mods that were ever used are installed using versions updated specifically for the present version of the game. (This is not guaranteed to happen -- it all depends on the mods used, possibly synergy issues between different mods when used with a specific game version.)

If beginning a new game in a new save slot following the clean installation still results in an error, do send that into Support. That would be an issue with the game itself.

It's all true, it may happen... but in my case I did not have to do all of this, and I am not interested in running 100% vanilla mode.
I think it's worth trying "unchecking" one box before clean installation of the game and replaying the game from the beginning without mods.

- I still use the current installation
- all mods are still working
- I still use the current progress (save game)
- only thing that changed for me is that I don't have "EXCEPTION_ACCESS_VIOLATION (0xC0000005)" error anymore, no more crashes to desktop

There may be multiple solution for this problem, depending on multiple variables.
In my case all "solutions" found on internet were not resolving the issue, the only thing that worked for me was unchecking this one box. Didn't have a single crash since.

 

[SigilFey]

It's all true, it may happen... but in my case I did not have to do all of this, and I am not interested in running 100% vanilla mode.
I think it's worth trying "unchecking" one box before clean installation of the game and replaying the game from the beginning without mods.

- I still use the current installation
- all mods are still working
- I still use the current progress (save game)
- only thing that changed for me is that I don't have "EXCEPTION_ACCESS_VIOLATION (0xC0000005)" error anymore, no more crashes to desktop

There may be multiple solution for this problem, depending on multiple variables.
In my case all "solutions" found on internet were not resolving the issue, the only thing that worked for me was unchecking this one box. Didn't have a single crash since.

There certainly will be multiple solutions for different users. If using mods, individual troubleshooting will invariably be part of the process.

The important thing to keep in mind, however, is that CDPR Support cannot offer any help with a modded playthrough. In order to submit a report ticket, the issue needs to be confirmed as happening in 100% vanilla -- meaning a brand new playthrough that has never been modded at any point.

By all means, keep the mods and fiddle away -- as long as it continues working in the end, that's a win! But if sending a Support ticket in, it will have to be a vanilla issue.