2.0 Crashing Fixes and Solutions

[Goodgoodie]

If anyone else has experienced crashing and found a solution please let me know. My specs are RTX4090 I-9 13900K 32Gb DDR5 on 2Tb NVME.2 and my game crashing every few minutes. I've already tried to verify game files,update drivers/windows, and changed settings, disabled Hyper-Threading, and even undervolted my CPU values from 55-58 to 54 for my performances cores and that didn't fix it either. PLEASE SHARE your experiences and fixes.

[Lost]

Turn off HDD mode and turn off cross platform saves in the game settings that's what worked for me and also if you're running a melee build don't use the airstrike melee mod on your katana because the game will crash when you're going for a melee animation.

[Teal Master]

Subscribing.

[Sparhawk122]

Originally posted by Lost:

Turn off HDD mode and turn off cross platform saves in the game settings that's what worked for me and also if you're running a melee build don't use the airstrike melee mod on your katana because the game will crash when you're going for a melee animation.

I have those two settings disabled. Still getting the crashing.

RTX 4090, i9 13900k, 64GB DDR5 Ram @6400Mhz CL32, 4TB NVMe M.2 SSD and Windows 11.

[Peter_Frank]

Run memtest86

[Grandmother CFO]

I'm on amd 6800xt and I use older drivers, try going back in the drivers, and locking the fps :)

[Sparhawk122]

Originally posted by Peter_Frank:

Run memtest86

No memory issues found. I've also checked all temps which are very good. My hotspot on the GPU for example hovers between 64 and 68. Actually core GPU temp usually in the 50s. Also very good. CPU on idle 30 degrees celcius and ingame 50s.

FPS locked at 85 FPS for 3440x1440p resolution. Framerate is very stable.

No errors in event viewer for any of my hardware.

Only error level notification is the system viewing RedLauncher as a faulty module.

My PC is also brand new so no dust build up. PSU is a MSI MEG 1300W platinum rated PSU.

Have ran SFC /SCANNOW and found no issues with my operating system. Latest bios and drivers.

Game plays smooth for a few hours. Then NPC and object textures start phasing in and out. Next minute game locks up and CTDs. From experience this is indicative of a VRAM or system ram capacity issue. But I have 24GB VRAM and 64GB system ram. And Memtest86 found no issues.

My VRAM temps are also really good.

This rig has been tested thoroughly in benchmarks and passed them all with no instability issues.

[Peter_Frank]

Originally posted by Sparhawk122:

Originally posted by Peter_Frank:

Run memtest86

No memory issues found. I've also checked all temps which are very good. My hotspot on the GPU for example hovers between 64 and 68. Actually core GPU temp usually in the 50s. Also very good.

Then I would check stacktrace.txt. It's in AppData/Local/REDEngine/ReportQueue/Cyberpunk(*latest*). The dump file is there also

[Sparhawk122]

Originally posted by Peter_Frank:

Originally posted by Sparhawk122:

No memory issues found. I've also checked all temps which are very good. My hotspot on the GPU for example hovers between 64 and 68. Actually core GPU temp usually in the 50s. Also very good.

Then I would check stacktrace.txt. It's in AppData/Local/REDEngine/ReportQueue/Cyberpunk(*latest*). The dump file is there also

more specific instructions to find that?

My file pathways seems different to the above. I am playing on Steam.

[startower]

for me it was autosave. the game tries to write a new file way to often and fails to sync to the cloud, worse, i usually disabled autosave with a user.ini file but this does not work anymore, if autosave is manually disabled in v2.0 the game either do not allow you to progress missions or even crashes.

[808GTI]

I can confirm that what fixed the immediate crash for me was Discord.

1. Disabling the Discord Overlay, Settings > Activity Settings > Game Overlay > Enable In-Game Overlay.
2. I also tried running the Studio version of the latest Nvidia drivers with no GeForce Experience, this alone did not fix it, I may have discord closed off when I was testing and had the assumption that it initially worked. But then I opened discord, alt+tabbed, immediately crashed. So I can't confirm if Nvidia Overlay will have any negative effects, I don't want to reinstall the drivers again for the 4th time.
3. Riva-Tuner Overlay is fine.

[Zer0]

Originally posted by Sparhawk122:

more specific instructions to find that?

%LOCALAPPDATA%\REDEngine\ReportQueue

Looks like the data sent by the crash reporter. The stack trace isn't actually a stack trace (likely due to no PDBs) but does at least include the exception type and line number. Also a memory dump, some metadata, your sav, etc...

More than enough to fix all bugs in like 3 seconds presuming they hired devs above the junior level. I'm available for the next week and a half, but pretty sure they can't afford me.

[Sparhawk122]

Originally posted by Zer0:

Originally posted by Sparhawk122:

more specific instructions to find that?

%LOCALAPPDATA%\REDEngine\ReportQueue

Looks like the data sent by the crash reporter. The stack trace isn't actually a stack trace (likely due to no PDBs) but does at least include the exception type and line number. Also a memory dump, some metadata, your sav, etc...

More than enough to fix all bugs in like 3 seconds presuming they hired devs above the junior level. I'm available for the next week and a half, but pretty sure they can't afford me.

This is what the top crash report says:

Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0x2B82A3E0000.
File: <Unknown>(0)

[Viper]

Have you ever installed a mod for the game. Make sure to completely uninstall them. Which includes deleting some directories. Don't remember off hand which but its has been posted several times.

[Zer0]

Originally posted by Sparhawk122:

This is what the top crash report says:

Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0x2B82A3E0000.
File: <Unknown>(0)

I don't see any exceptions on my end, but I'm AMD. Are you running the launcher? I wasn't aware there even was one until recently since GOG oddly enough does not use a launcher at all.

If yes, disable the launcher with "--launcher-skip -skipStartScreen" in Steam.

If no, my next steps would be to check Windows event logs. Event Viewer -> Windows Logs.

These are more of a pain to get through, but you want to filter for only errors. Ideally look for either the application itself or a device failure (GPU).

If you can reliably reproduce the game crashing you should be able to time box your log search and make it easy.

That said, if you want the specifics, your "stack trace" says Cyberpunk 2077 tried to access protected memory in Windows. The kernel, in response, goes "um.... no". Pretty common, but this is why the crash is happening.

This error commonly happens with driver failures. Another thing you should try is clearing the shader cache. No idea how to do this on NVIDIA, but it should be there somewhere. If the driver itself crashed the error is always recorded in Windows event logs.

Unfortunately it's also common in pointer math (the engine is C++). That's where code points to a safe place in memory, then they do some math to point to somewhere else in memory that's now protected by Windows. I'm aware the launcher has memory leaks so that's why I mentioned that first.

[Sparhawk122]

Originally posted by Zer0:

Originally posted by Sparhawk122:

This is what the top crash report says:

Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0x2B82A3E0000.
File: <Unknown>(0)

I don't see any exceptions on my end, but I'm AMD. Are you running the launcher? I wasn't aware there even was one until recently since GOG oddly enough does not use a launcher at all.

If yes, disable the launcher with "--launcher-skip -skipStartScreen" in Steam.

If no, my next steps would be to check Windows event logs. Event Viewer -> Windows Logs.

These are more of a pain to get through, but you want to filter for only errors. Ideally look for either the application itself or a device failure (GPU).

If you can reliably reproduce the game crashing you should be able to time box your log search and make it easy.

That said, if you want the specifics, your "stack trace" says Cyberpunk 2077 tried to access protected memory in Windows. The kernel, in response, goes "um.... no". Pretty common, but this is why the crash is happening.

This error commonly happens with driver failures. Another thing you should try is clearing the shader cache. No idea how to do this on NVIDIA, but it should be there somewhere.

Event viewer error is RedLauncher faulty.

No GPU or other hardware errors. Device manager shows everything is updated. No OS issues either since SFC scannow could not find anything. I also ran a check disk on my SSD. No issues there and in storage disks says it is "healthy". Memtest86 passed my RAM.

Some kind of software issue. Like trying to find a needle in a haystack.

I am using DDU uninstaller now. To fully uninstall my GPU driver and will reinstall. DDU should get rid of the shader cache for me too? Unless you are referring to the shader cache I saw in the Cyberpunk 2077 game files.