Game crashing - I have everything new.

[Argo7000]

Hi. My game crashes all the time. No mods.

I have new Windows 11, Intel Core i5-12400F, GeForce RTX 3060, 32GB RAM.

Attechments - report from the performance test.

GPT says that:

Key Information
ErrorReason: Unhandled exception
Exception: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: Attempting to read inaccessible memory address 0x8000070

This is the same error type (0xC0000005) that we saw in Windows minidumps (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED). In short: the program (in this case: Cyberpunk) attempted to read from a corrupted or non-existent memory location.

What can be seen in the loaded modules?
The game was simultaneously using:
DLSS (nvngx_dlss.dll, nvngx_dlssg.dll, nvldumdx.dll)
FSR3 (ffx_fsr3_x64.dll, ffx_fsr3upscaler_x64.dll, ffx_frameinterpolation_x64.dll)
Intel XeSS (libxess.dll, libxess_fg.dll)

So you have three different upscaling systems and the Steam overlay running in memory simultaneously. This puts a heavy load on the GPU driver and rendering libraries.

The error occurred during a benchmark (performance test) – meaning at maximum GPU/VRAM load.

Possible causes:
GPU drivers (NVIDIA)
nvldumdx.dll, nvwgf2umx.dll, and nvapi64.dll were active.
Cyberpunk is one of the most demanding titles for DLSS/FSR/XeSS → if the driver is bugged, it ends with 0xC0000005.

I have newest drivers. Playing without upscaling also also causes crashes. What is going on?

 

[SigilFey]

Microsoft Visual C++ Redistributable All-in-One.

I'd start there. Be sure to install the x86 version followed by the x64 version. Both should be installed side by side.

There are not three different supersampling systems running at the same time -- games simply need to account for all three so that the correct data can be loaded when the player selects one in the options. Only one will every be loaded into RAM at a time.

Steam Overlay can very easily be disabled through Steam. CDPR doesn't control that; it's a Steam feature. Normally, it's just a TSR, so its footprint is actually quite small on any system that has 8-16 GB of RAM available.

The error code means that a software program made a call that the hardware could not read. That's all. It's a general error. That's exactly what things like APIs are for -- they allow the OS to interpret calls in a language they can process. Not uncommon for MS Redists to get jumbled over time, which is why they're often included in installation packages. Running them fixes any data that needs adjusting and ensures that older files are overwritten by the correct/needed versions.

 

[Argo7000]

Still crashes despite installing both versions. But it works randomly. Yesterday I played for 1.5 hours and then the game froze. Today it froze after 20 minutes, and you never know when it will happen.

Post automatically merged: Sep 4, 2025

And there is also a bug connected with sound.
Suddenly, some random music starts playing even when the volume in the music and radio settings is set to zero. I have to save the game, exit to the menu, load the save, and then the music disappears.

Farlight84 has a similar problem, where the game freezes due to the audio driver. I have to change the audio output to a different one. It's just ridiculous.

 

[Rollo]

The EXCEPTION_ACCESS_VIOLATION (0xC0000005) error is often caused by a UEFI configuration for a preset XMP overclock. Not all RAM can handle this. I had this in another case, and the system was also new.

It's best to disable XMP in the UEFI. If you don't know how, use a search engine or write down your motherboard manufacturer.

Good luck!

 

[Argo7000]

I have XMPI, XMPII and auto and it was set to auto all the time.

Post automatically merged: Sep 5, 2025

The EXCEPTION_ACCESS_VIOLATION (0xC0000005) error is often caused by a UEFI configuration for a preset XMP overclock. Not all RAM can handle this. I had this in another case, and the system was also new.

It's best to disable XMP in the UEFI. If you don't know how, use a search engine or write down your motherboard manufacturer.

Good luck!

I have XMPI, XMPII and auto and it was set to auto all the time.

Post automatically merged: Sep 5, 2025

Errors from the event manager according to the GPT:

WHEA-Logger (EventID 17)
This is more serious.
WHEA = Windows Hardware Error Architecture – the system logs hardware errors.
ErrorSource = 4 → PCI Express Error.
VendorID = 0x8086 → is Intel (chipset).
DeviceID = 460D → is Intel Root Port / PCIe controller (part of the CPU or chipset).
CorrectableErrorStatus = 0x1 → this was a "correctable" error (meaning the system resolved it), but it shouldn't have occurred at all.

Everything in my PC is new, but the problems are old. Maybe it's the panel in the PC case? The case is old, and maybe the cables are not up to par, causing a micro-voltage surge? I bought an external power switch with audio and USB, and this weekend I'll disconnect the panel in the case and replace it with this switch.

Post automatically merged: Sep 5, 2025

Ok I think I know what is the problem. I changed in BIOS Tweaker to 2666 MHz and removed GSkill 16GB RAM. GSkill is a trash. I have GOODRAM 16 GB and the game works well. In my previous computer I had also GSkill Ram stick but 2x8GB and I had at least one BSOD a day...

 

[SigilFey]

Ok I think I know what is the problem. I changed in BIOS Tweaker to 2666 MHz and removed GSkill 16GB RAM. GSkill is a trash. I have GOODRAM 16 GB and the game works well. In my previous computer I had also GSkill Ram stick but 2x8GB and I had at least one BSOD a day...

G.Skill is actually fantastic RAM! But there can be manufacturer defects in even the best of the best stuff.

If the game is working correctly now, no worries. For the future (just in case the system is not done acting up, yet

When dealing with any sort of crashing, hanging, or error codes, something appearing in the Event Viewer / System Logs relating to hardware isn't necessarily serious.

1.) If it's just a random, one-off thing, I wouldn't worry at all. Programs can get flustered with unique situations, conflict with other programs, Windows can do something at an inopportune moment, etc. (There are also neutrinos in the universe, and all it takes is one smacking into one electron in your RAM or processors to create a full on system crash. Totally nothing to worry about.)

2.) If it's consistently happening with only a single program, still nothing to worry about. I'd focus on updates, drivers, APIs, etc.

3.) If it's consistently happening across multiple programs, now it's worth recording the errors and figuring out whether it's hardware or software.

4.) If you get the same BSoD more than once, it's definitely time to start paying attention to both software and hardware. But it will likely be a problem with a very easy and direct fix.

5.) If you get the same BSoD AND the system shutting itself off -- you definitely have a hardware issue. This is the situation where real concern is warranted. This is likely a more serious problem, and the fix may be either easy or complicated and more expensive.

6.) If you get multiple different BSoDs, possibly with the system powering itself down as well...this is the scary place. This is the dark place. Sometimes, it's as simple as a dying PSU or SSD, but it could be much worse. At that point, it's time to start seriously pricing out a replacement system.


_______________


The main gist, though, is that Windows logging hardware events is not, in and of itself, a cause for alarm. The errors you identified were all PCIe / GPU related. And yet you seemed to have cleared it up by changing the system RAM. Possibly, nothing directly related to the GPU or the PCIe slot on the motherboad at all. The problem may have simply been manifesting there, according to Windows.

Out of curiosity, what GPU do you have? Why are the events concerning "Intel chipset"? Do you have one of the Intel ARC cards?

 

[Neuronin]

(There are also neutrinos in the universe, and all it takes is one smacking into one electron in your RAM or processors to create a full on system crash. Totally nothing to worry about.)

I can't believe CDPR haven't accounted for this vulnerability already. Bug report incoming.

 

[SigilFey]

I can't believe CDPR haven't accounted for this vulnerability already. Bug report incoming.

Heheheheh...!

I think that will make a frame-able ticket. "Dear CDPR: It is inexcusable that you did not account for interstellar radiation when designing your engine for Cyberpunk 2077..."