[NOT SOLVED] EXCEPTION_ACCESS_VIOLATION (0xC0000005)

[Nastycyber]

Update 2.
The problem keeps coming back whatever I do.

I think the game is trying to access the CPU memory.
Different CPU has different memory protection.
Especially the newest CPU will have a higher security setting.
I’m starting to think that it’s just another optimization issue.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Update.

The error occurred again after I played around 3 hours.
It's a huge improvement tho.
This time I looked into the event viewer and the error code is

Faulting application name: REDlauncher.exe, version: 2.15.1.46, time stamp: 0x6516c634
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x4530
Faulting application start time: 0x01d9f50e295c8661
Faulting application path: C:\Users\User\AppData\Local\Programs\CD Projekt Red\REDlauncher\REDlauncher.exe
Faulting module path: unknown
Report Id: 239881d7-626b-4ad5-9cc4-0d41b18b690b
Faulting package full name:
Faulting package-relative application ID:


I'm gonna use command to skip the launcher and continue to test the game.


-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I think I found the cause of this error.

I am using PRO Z790-A WIFI as MB and i found that the CPU OC is activated by default.

And as you know Cyberpunk is extremely vulnerable to OC.

At first, I though it was the XMP(Memory OC) since the error code is related to inaccessible memory. Of course XMP was one of the reason, but after I turn off the CPU OC, the game runs without crashing for an hour, which makes my theory quite solid beacuse before I turn it off, the game will crash within 5 minutes.

Also, DEP is off in the current state and I will try to turn it on again to see if it's really the CPU OC messing with the game.

I still got a lot to trouble shoot and UAT to perform but I wish everyone who encountered this problem would check their CPU OC setting and perform UAT as to share your result in here.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to write to an inaccessible address at 0x18.
File: <Unknown>(0)

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.4902785 P4CL: 6408866 Stream: //R6.Root/R6.Release
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.19045.2.0.0.256.1
LoadedModule[0]=Cyberpunk2077.exe
LoadedModule[1]=ntdll.dll
LoadedModule[2]=KERNEL32.DLL
LoadedModule[3]=KERNELBASE.dll
LoadedModule[4]=USER32.dll
LoadedModule[5]=win32u.dll
LoadedModule[6]=GDI32.dll
LoadedModule[7]=gdi32full.dll
LoadedModule[8]=msvcp_win.dll
LoadedModule[9]=ucrtbase.dll
LoadedModule[10]=ADVAPI32.dll
LoadedModule[11]=msvcrt.dll
LoadedModule[12]=sechost.dll
LoadedModule[13]=RPCRT4.dll
LoadedModule[14]=SHELL32.dll
LoadedModule[15]=ole32.dll
LoadedModule[16]=combase.dll
LoadedModule[17]=sl.interposer.dll
LoadedModule[18]=SETUPAPI.dll
LoadedModule[19]=cfgmgr32.dll
LoadedModule[20]=bcrypt.dll
LoadedModule[21]=dbghelp.dll
LoadedModule[22]=WS2_32.dll
LoadedModule[23]=OLEAUT32.dll
LoadedModule[24]=PhysX3CharacterKinematic_x64.dll
LoadedModule[25]=libxess.dll
LoadedModule[26]=PhysX3Common_x64.dll
LoadedModule[27]=PhysX3Cooking_x64.dll
LoadedModule[28]=PhysX3_x64.dll
LoadedModule[29]=SHLWAPI.dll
LoadedModule[30]=icuin.dll
LoadedModule[31]=PxFoundation_x64.dll
LoadedModule[32]=bink2w64.dll
LoadedModule[33]=icuuc.dll
LoadedModule[34]=WINMM.dll
LoadedModule[35]=HID.DLL
LoadedModule[36]=redlexer_native.dll
LoadedModule[37]=REDGalaxy64.dll
LoadedModule[38]=libcurl.dll
LoadedModule[39]=CRYPT32.dll
LoadedModule[40]=WLDAP32.dll
LoadedModule[41]=XINPUT9_1_0.dll
LoadedModule[42]=Normaliz.dll
LoadedModule[43]=VERSION.dll
LoadedModule[44]=amd_ags_x64.dll
LoadedModule[45]=POWRPROF.dll
LoadedModule[46]=oo2ext_7_win64.dll
LoadedModule[47]=VCRUNTIME140.dll
LoadedModule[48]=dxgi.dll
LoadedModule[49]=MSVCP140.dll
LoadedModule[50]=d3d12.dll
LoadedModule[51]=XeFX.dll
LoadedModule[52]=XeFX_Loader.dll
LoadedModule[53]=VCRUNTIME140_1.dll
LoadedModule[54]=WININET.dll
LoadedModule[55]=IPHLPAPI.DLL
LoadedModule[56]=MSWSOCK.dll
LoadedModule[57]=kernel.appcore.dll
LoadedModule[58]=dbgcore.DLL
LoadedModule[59]=icudt.dll
LoadedModule[60]=IMM32.DLL
LoadedModule[61]=UMPDC.dll
LoadedModule[62]=gameoverlayrenderer64.dll
LoadedModule[63]=PSAPI.DLL
LoadedModule[64]=CRYPTBASE.DLL
LoadedModule[65]=bcryptPrimitives.dll
LoadedModule[66]=windows.storage.dll
LoadedModule[67]=Wldp.dll
LoadedModule[68]=SHCORE.dll
LoadedModule[69]=napinsp.dll
LoadedModule[70]=pnrpnsp.dll
LoadedModule[71]=wshbth.dll
LoadedModule[72]=NLAapi.dll
LoadedModule[73]=DNSAPI.dll
LoadedModule[74]=NSI.dll
LoadedModule[75]=winrnr.dll
LoadedModule[76]=fwpuclnt.dll
LoadedModule[77]=rasadhlp.dll
LoadedModule[78]=secur32.dll
LoadedModule[79]=SSPICLI.DLL
LoadedModule[80]=clbcatq.dll
LoadedModule[81]=wbemprox.dll
LoadedModule[82]=wbemcomn.dll
LoadedModule[83]=wbemsvc.dll
LoadedModule[84]=fastprox.dll
LoadedModule[85]=amsi.dll
LoadedModule[86]=USERENV.dll
LoadedModule[87]=profapi.dll
LoadedModule[88]=MpOav.dll
LoadedModule[89]=GameServicesSteam.dll
LoadedModule[90]=steam_api64.dll
LoadedModule[91]=steamclient64.dll
LoadedModule[92]=imagehlp.dll
LoadedModule[93]=vstdlib_s64.dll
LoadedModule[94]=tier0_s64.dll
LoadedModule[95]=uxtheme.dll
LoadedModule[96]=CChromaEditorLibrary64.dll
LoadedModule[97]=WINTRUST.dll
LoadedModule[98]=mfc140u.dll
LoadedModule[99]=Comctl32.dll
LoadedModule[100]=MSASN1.dll
LoadedModule[101]=CRYPTSP.dll
LoadedModule[102]=rsaenh.dll
LoadedModule[103]=gpapi.dll
LoadedModule[104]=cryptnet.dll
LoadedModule[105]=WINNSI.DLL
LoadedModule[106]=sl.common.dll
LoadedModule[107]=drvstore.dll
LoadedModule[108]=devobj.dll
LoadedModule[109]=nvapi64.dll
LoadedModule[110]=sl.dlss.dll
LoadedModule[111]=_nvngx.dll
LoadedModule[112]=DEVRTL.dll
LoadedModule[113]=SPINF.dll
LoadedModule[114]=ntmarta.dll
LoadedModule[115]=nvngx_dlss.dll
LoadedModule[116]=nvngx_dlssg.dll
LoadedModule[117]=vulkan-1.dll
LoadedModule[118]=nvcuda.dll
LoadedModule[119]=nvngx_dlssd.dll
LoadedModule[120]=sl.dlss_d.dll
LoadedModule[121]=sl.reflex.dll
LoadedModule[122]=GFSDK_Aftermath_Lib.x64.dll
LoadedModule[123]=nvwgf2umx.dll
LoadedModule[124]=D3D12Core.dll
LoadedModule[125]=dxcore.dll
LoadedModule[126]=nvspcap64.dll
LoadedModule[127]=DINPUT8.dll
LoadedModule[128]=inputhost.dll
LoadedModule[129]=CoreUIComponents.dll
LoadedModule[130]=CoreMessaging.dll
LoadedModule[131]=wintypes.dll
LoadedModule[132]=PROPSYS.dll
LoadedModule[133]=dhcpcsvc.DLL
LoadedModule[134]=nvldumdx.dll
LoadedModule[135]=NvCamera64.dll
LoadedModule[136]=d3d11.dll
LoadedModule[137]=WindowsCodecs.dll
LoadedModule[138]=MessageBus.dll
LoadedModule[139]=d3dcompiler_47_64.dll
LoadedModule[140]=D3DSCache.dll
LoadedModule[141]=twinapi.appcore.dll
LoadedModule[142]=nvcuda64.dll
LoadedModule[143]=nvrtum64.dll
LoadedModule[144]=NvTelemetryAPI64.dll
LoadedModule[145]=NvTelemetryBridge64.dll
LoadedModule[146]=MMDevApi.dll
LoadedModule[147]=AUDIOSES.DLL
LoadedModule[148]=Windows.UI.dll
LoadedModule[149]=TextInputFramework.dll
LoadedModule[150]=WindowManagementAPI.dll
LoadedModule[151]=resourcepolicyclient.dll
LoadedModule[152]=Wtsapi32.dll
LoadedModule[153]=XInput1_4.dll
LoadedModule[154]=MSCTF.dll
LoadedModule[155]=dcomp.dll
LoadedModule[156]=dwmapi.dll
LoadedModule[157]=WINSTA.dll
LoadedModule[158]=MessageBus.dll
LoadedModule[159]=d3d11on12.dll
LoadedModule[160]=dxilconv.dll
LoadedModule[161]=schannel.DLL
LoadedModule[162]=mskeyprotect.dll
LoadedModule[163]=NTASN1.dll
LoadedModule[164]=ncrypt.dll
LoadedModule[165]=ncryptsslp.dll
AppName=Cyberpunk2077.exe

------------------
System Information
------------------
Time of this report: 9/30/2023, 14:35:56
Machine name: DESKTOP-RMQOQ45
Machine Id: {85A35412-5960-4582-8E76-127FEB374BAB}
Operating System: Windows 10 Pro 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406)
Language: English (Regional Setting: English)
System Manufacturer: Micro-Star International Co., Ltd.
System Model: MS-7E07
BIOS: A.30 (type: UEFI)
Processor: 13th Gen Intel(R) Core(TM) i9-13900KF (32 CPUs), ~3.0GHz
Memory: 32768MB RAM
Available OS Memory: 32610MB RAM
Page File: 10148MB used, 118460MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 144 DPI (150 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, no HDCP
Microsoft Graphics Hybrid: Not Supported
DirectX Database Version: 1.0.8
DxDiag Version: 10.00.19041.2075 64bit Unicode

HELP

 

[MartineDee]

It looks memory-related. A few shots in the dark...

If you have 16 GB of memory and no pagefile, try also having 16 GB of pagefile.

Second one...
If your DRAM is overclocked, as in on an XMP profile, try to dial it down to the stock values, or find someone who knows-how to do it for you... And is also able to restore its present setting once you've tried that.

It's just my hunch that the DRAM might not be stable enough for the demands of the game and that shows.

The real cause could be something completely different. Or the memory itself could be broken.

 

[toddtheo]

I am having a similar issue, or the same: exception errors.

Constant Crashing on Steam v2.0 Windows 11 | Forums - CD PROJEKT RED

I have done everything that can be done to run this game correctly, if you want to read my long and arduous process. My event managers always say the issue is with RedLauncher so I am going to try just launching cyberpunk from the bin folder as administrator and killing red launcher to see if that makes a difference.

 

[SigilFey]

Try manually reinstalling the Microsoft Redistributables that come with the game.

If that doesn't work, install the All-in-One Visual Studio pack that you can find here.

 

[toddtheo]

Hello, I have been having exception errors nonstop and I found something that worked for me, which no one has listed in any subreddit or forum that I have seen.

What I did was go to

Go to advance power settings. I set my CPU to 99% min and 99% max, I also put my graphics card (PICe) settings to performance settings, and ram as well to performance.

Also, I did not use the Redlauncher, Redlauncher is what is crashing my game according to Windows EventManager. Go to your bin folder and start the game as administrator. I haven't had a crash yet and also my other games that started crashing after I installed phantom liberty have started working correctly again. Hope this helps.

 

[SigilFey]

Hello, I have been having exception errors nonstop and I found something that worked for me, which no one has listed in any subreddit or forum that I have seen.

What I did was go to

Go to advance power settings. I set my CPU to 99% min and 99% max, I also put my graphics card (PICe) settings to performance settings, and ram as well to performance.

Also, I did not use the Redlauncher, Redlauncher is what is crashing my game according to Windows EventManager. Go to your bin folder and start the game as administrator. I haven't had a crash yet and also my other games that started crashing after I installed phantom liberty have started working correctly again. Hope this helps.

While this might be a valid workaround, overclocking or underclocking your PC in order to achieve stability is never a solution to the problem. If doing so works, it's indicative of a more significant error somewhere at the hardware or OS level. It usually won't be harmful to limit the voltage or clock speeds, but I wouldn't simply leave it unaddressed.

The very first step in troubleshooting any issue is to return all hardware to default clock and voltage speeds.

 

[Nastycyber]

It looks memory-related. A few shots in the dark...

If you have 16 GB of memory and no pagefile, try also having 16 GB of pagefile.

Second one...
If your DRAM is overclocked, as in on an XMP profile, try to dial it down to the stock values, or find someone who knows-how to do it for you... And is also able to restore its present setting once you've tried that.

It's just my hunch that the DRAM might not be stable enough for the demands of the game and that shows.

The real cause could be something completely different. Or the memory itself could be broken.

Yeah I've tried disabling XMP profile and OC function. I've tried to set the page file to "Disable" and "64000"(Cause i have 32GB RAM).

I am something of a technical support (Help Desk) myself and I've tried all options to trouble shoot this problem.

I fresh installed OS(Windows 10 Pro), ran everything in Administrator profile, updated all software including windows, NVidia driver, Steam,Cyberpunk 2077, Java, Microsoft Visual C++ etc..

Making exception in firewall and DEP for Cyberpunk2077.exe and REDLauncher. Disabled Windows Performance mode.

Runing repairing command like sfc \scannow, EVEN after I reinstalled the OS.
Of course I've also tried verifying game files, clean install the game (deleting all related folders in %AppData%), setting --launcher skip command in Steam launch option, disabling Cross platform save function in-game.

I have no problem playing other games like Baldur's gate 3, Starfields, Armored Core VI, Hogwarts legacy, Resident Evil Re 4 etc..
Only this game.

 

[DC9V]

• Please double check if you made an exception in DEP also for public networks.
• When your PC is shut down, turn off your PSU and unplug the power cable. Then turn on the PSU and press the power button on your PC case. The power LED should light up for a split second. Any capacitors that could potentially store currupted data are now discharged. Turn off the PSU, plug-in the power cable, and turn it on again.

 

[Nastycyber]

I am having a similar issue, or the same: exception errors.

Constant Crashing on Steam v2.0 Windows 11 | Forums - CD PROJEKT RED

I have done everything that can be done to run this game correctly, if you want to read my long and arduous process. My event managers always say the issue is with RedLauncher so I am going to try just launching cyberpunk from the bin folder as administrator and killing red launcher to see if that makes a difference.

I've tried that too. No luck.

Post automatically merged: Oct 1, 2023

• Please double check if you made an exception in DEP also for public networks.
• When your PC is shut down, turn off your PSU and unplug the power cable. Then turn on the PSU and press the power button on your PC case. The power LED should light up for a split second. Any capacitors that could potentially store currupted data are now discharged. Turn off the PSU, plug-in the power cable, and turn it on again.

1. I've completely disabled the DEP function with command "bcdedit.exe /set {current} nx AlwaysOff" but I'm still getting the same error.
2. Layer 1 trouble shooting won't help at this point anymore. I appreciate your suggestion tho.

 

[Azulath]

I am also experiencing EXCEPTION_ACCESS_VIOLATION (0xC0000005) crashes since 2.1 (*). For me, it is very unpredictable and sometimes it does not crash for 2h (not playing much longer) while other times it crashes after 30min. While this might be hardware related I am really wondering if this might be a bug introduced by 2.x and/or Windows/GPU updates.

*) I did not continue playing with 2.0 PL and just tested it for a while with the PT update. So, if I had played it more, it might have crashed as well.

 

[Beamer_Boy99]

I fixed the problem by loading an old save from 1 hour before the first crash and for now the game doesn't crash again. So i think the reason these errors kept happening is because something is wrong with starting or finishing a side quest or side mission but i am not sure which one it was.

 

[Azulath]

I am also experiencing EXCEPTION_ACCESS_VIOLATION (0xC0000005) crashes since 2.1 (*). For me, it is very unpredictable and sometimes it does not crash for 2h (not playing much longer) while other times it crashes after 30min. While this might be hardware related I am really wondering if this might be a bug introduced by 2.x and/or Windows/GPU updates.

*) I did not continue playing with 2.0 PL and just tested it for a while with the PT update. So, if I had played it more, it might have crashed as well.

For me, it seems like a mod is actually causing the issue. Don't know which one. (I have not reported the issue before since I did not test my game w/o mods of course.)

 

[IllusionaryInno]

I've been having constant issues with this error the last few days.
I've done so much, verified, reverified, cleared caches.
Reinstalled GPU drivers, ran DDU then reinstalled GPU drivers.
Turned off my XMP.

The annoying thing is after I get this error, I crash when loading saves.
I have to fully shutdown my computer, let it sit for a few seconds then try booting it up before I regain the ability to load my save.
Worse, it is a coin flip (heavily weighted towards this happening) that loading a save mid-game will trigger a crash with this exact same error.
I'm running a GTX 4070 with 32GB of RAM, and my Cyberpunk install is on an m.2 SSD, with a i5 12600k as my CPU.

DISM and SFC have done nothing. Whatever the game is doing, it's doing something in memory that can't be cleared without a clean reboot to purge whatever crashes me when I try to load a save on a boot session after the error.
Often the most I can get is maybe two-three hours if I'm lucky before the game crashes.

Exact same error always.
Exception_Access_Violation.
The thread attempted to read inaccessible data.

 

[BocaSpanky]

Boys i really think thats a Windows Problem.
I cant remember i have crashes on Release 2020. That was the Time of Windows 10.

Here my Specs:
Intel 13900k
Nvidia 4080 Super
64GB DDR5 RAM
2000GB Sasmung SSD 990PRO
Samsung 49 Inch Odyssey
Asus z790 Prime a Wifi Mainboard

- RAM on 4000Mhz
- nothing is OC
- newest Nvidia Driver
- fresh Installed Windows 11 and up do date.
- newest Bios Version
- newest Monitor Driver
- Cyberpunk2077.exe / Compatibility to Windows 8 ON / Fullscreen Opti. OFF / start as Admin ON
- exception in Firewall
- exception in Windows Virus Defender

I can play now for 20 Minutes. Then i open a Door and the Game crashes.

That is so f... anoying

 

[cmarland00]

Here having the same issue, specs are:
AMD Ryzen 7 5700G with Radeon Graphics 4.40 GHz
64.0 GB (63.8 GB usable) Corsair DDR4 3200
RTX 3070
This issue did not seem to occur until last couple of months, I cannot finish the DLC due to the constant crashing D:
Even launching the game outside of the launcher as admin right from within the folder does not seem to resolve the issue, as checking the dump file on crash shows the same 0xc0000005 exception code being the cause of the crash.
Really would love a fix for this :C

 

[devivre]

It might be best to send a ticket to cdpr support so they can investigate. The error code alone doesn’t necessarily mean that the cause is exactly the same for everyone, so it’s always good to have more information.

Support can be reached here:
https://support.cdprojektred.com/en/cyberpunk/pc/sp-technical/issue/1700/my-game-crashes-7 (please check out the support article first, and if that doesn’t help, send a ticket to support by clicking on Contact Us)

 

[cmarland00]

It might be best to send a ticket to cdpr support so they can investigate. The error code alone doesn’t necessarily mean that the cause is exactly the same for everyone, so it’s always good to have more information.

Support can be reached here:
https://support.cdprojektred.com/en/cyberpunk/pc/sp-technical/issue/1700/my-game-crashes-7 (please check out the support article first, and if that doesn’t help, send a ticket to support by clicking on Contact Us)

I really hope someone can resolve these issues yet, I tried endless things, reinstall OS, editing memory pagefile, windows memory diagnostic and memtest86 dont seem to be having any issues, my card is factory OC though. It just is so strange to have a game that ran fine for so long all the sudden start to crash almost every hour reliably... hoping for the best!!

 

[silentecho00]

It appears that this issue is quite the bug. I didn't start having the issue until after the 2.13 patch. Here's the interesting bit: I think I have it narrowed down to where in the game the error starts to generate. I have two playthroughs (since 2.13) that both crash after Act 1. All during Act 1, nothing happens, crash wise. Runs normally, saves normally, loads save files without issue. However, both of the recent game files will not load after you make the first save in either the Interlude, or Act 2. The first of the two recent files I played through the Interlude (not thinking this would happen) just to clear it before saving after V is brought back to their place by Misty, and they are awakened to Johnny batting them around before taking the pills to shut him up. Saved right after that, and quit until the next day. Tried to load the file, crashed every time I tried. Tried going back to previous saves, and it still wouldn't load a file; as even the previous saves run the Act 2 load screen (the NPC in the junkyard watching TV). Did all the recommended fixes (clean load, disable mods, change OC settings on the MB, run from bin/x64, etc.) and still wouldn't work.

So, I tried starting a new game file, thinking that might do the trick. Played through Act 1 again, and everything was fine. Until I got to the Interlude. Testing my theory that it had to be something with the crossover to the Interlude/Act 2, I saved the game right at the start of the Interlude (when Johnny is walking down the hallway toward the stage, right before he talks to the groupie), and logged out of the game. Went to load the file back up, crashed.

There is something weird going on with clearing Act 1, and going on in the game after the Relic brings V back. If anyone that has had this problem can comment where you were in the game when the crashing started happening (Act 1 consistently, or Interlude/Act 2, or later), I would enjoy the data to see if my hunch is correct, and every time there is a patch it breaks something in the game files at the crossover point between the end of Act 1, and moving forward with the game. Sent a crash report ticket already so I can get dev help with this too. But, I am still curious if there is a real common denominator to the crashes based on where in the game a player is when they start happening.

TL;DR - Noticed a weird pattern in that the game crashes I see with this error code start happening after you complete Act 1. Would love to see if anyone can confirm the hunch by commenting where they were in game play (Act 1, Interlude/Act 2, or later) to see if it is something that is broken on the load screen for Act 2 that is causing the problem, or not.

Cheers

 

[LeKill3rFou]

It appears that this issue is quite the bug. I didn't start having the issue until after the 2.13 patch. Here's the interesting bit: I think I have it narrowed down to where in the game the error starts to generate. I have two playthroughs (since 2.13) that both crash after Act 1. All during Act 1, nothing happens, crash wise. Runs normally, saves normally, loads save files without issue. However, both of the recent game files will not load after you make the first save in either the Interlude, or Act 2. The first of the two recent files I played through the Interlude (not thinking this would happen) just to clear it before saving after V is brought back to their place by Misty, and they are awakened to Johnny batting them around before taking the pills to shut him up. Saved right after that, and quit until the next day. Tried to load the file, crashed every time I tried. Tried going back to previous saves, and it still wouldn't load a file; as even the previous saves run the Act 2 load screen (the NPC in the junkyard watching TV). Did all the recommended fixes (clean load, disable mods, change OC settings on the MB, run from bin/x64, etc.) and still wouldn't work.

So, I tried starting a new game file, thinking that might do the trick. Played through Act 1 again, and everything was fine. Until I got to the Interlude. Testing my theory that it had to be something with the crossover to the Interlude/Act 2, I saved the game right at the start of the Interlude (when Johnny is walking down the hallway toward the stage, right before he talks to the groupie), and logged out of the game. Went to load the file back up, crashed.

There is something weird going on with clearing Act 1, and going on in the game after the Relic brings V back. If anyone that has had this problem can comment where you were in the game when the crashing started happening (Act 1 consistently, or Interlude/Act 2, or later), I would enjoy the data to see if my hunch is correct, and every time there is a patch it breaks something in the game files at the crossover point between the end of Act 1, and moving forward with the game. Sent a crash report ticket already so I can get dev help with this too. But, I am still curious if there is a real common denominator to the crashes based on where in the game a player is when they start happening.

TL;DR - Noticed a weird pattern in that the game crashes I see with this error code start happening after you complete Act 1. Would love to see if anyone can confirm the hunch by commenting where they were in game play (Act 1, Interlude/Act 2, or later) to see if it is something that is broken on the load screen for Act 2 that is causing the problem, or not.

Cheers

Did you try to perform a clean install like explained in the link below and start a new game without any mod?
Because if you didn't, there are good chances that mod data remain in the game files (even if you disable/uninstall all mods) and so, could cause the crashes you experience.
It's just to be sure, because if it's somehow tied to mod, it's quite useless to send crash reports, support won't be able to do anything, nor providing help.

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

Edit : I saw your post on another thread, so a mod which worked perfectly fine in a previous version of the game, could now cause issue in 2.13, so you can't say it's no due to mods... unless you perform a clean install like in the like above and start a brand new playthrough without any mod.

 

[silentecho00]

Did you try to perform a clean install like explained in the link below and start a new game without any mod?
Because if you didn't, there are good chances that mod data remain in the game files (even if you disable/uninstall all mods) and so, could cause the crashes you experience.
It's just to be sure, because if it's somehow tied to mod, it's quite useless to send crash reports, support won't be able to do anything, nor providing help.

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

Edit : I saw your post on another thread, so a mod which worked perfectly fine in a previous version of the game, could now cause issue in 2.13, so you can't say it's no due to mods... unless you perform a clean install like in the like above and start a brand new playthrough without any mod.

I did that. And it still had the issue. Something about going from Act 1 to the Interlude is mot working correctly. Or, hasn't for me, I should say.