Question Crashing in Cyberpunk 2077 ?

Geoff Leven

Distinguished
Jun 2, 2013
122
4
18,595
Hello all,

For the longest time I have had random crashing in Cyberpunk. The severity of the crashes are quite varied, ranging from a simple crash to the desktop with no error from the game nor nothing reported in Windows event viewer (WEV) to - a very nasty crash to desktop, with screen flickering, errors reported in WEV and having to reinstall video drivers because they had become corrupted and no game at all on my system would launch anymore.

All evidence points to the nVidia drivers or my video card as I get the following errors reported in WEV sometimes when the game does crash:

Error (A)
The description for Event ID 0 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\000000f0
Error occurred on GPUID: 100
The message resource is present but the message was not found in the message table

Error (B)
Faulting application name: Cyberpunk2077.exe, version: 3.0.76.55031, time stamp: 0x65d7ab23
Faulting module name: Cyberpunk2077.exe, version: 3.0.76.55031, time stamp: 0x65d7ab23
Exception code: 0xc0000005
Fault offset: 0x0000000000131acd
Faulting process id: 0x0x590
Faulting application start time: 0x0x1DA6B80DE2A5D53
Faulting application path: H:\Steam\steamapps\common\Cyberpunk 2077\bin\x64\Cyberpunk2077.exe
Faulting module path: H:\Steam\steamapps\common\Cyberpunk 2077\bin\x64\Cyberpunk2077.exe
Report Id: b0ee5f5e-2987-4824-9303-85f75cb0ad17
Faulting package full name:
Faulting package-relative application ID:

Erorr (C)
Display driver nvlddmkm stopped responding and has successfully recovered

Error (D)
Application Cyberpunk2077. has been blocked from accessing Graphics hardware.

Before we get carried away and say the video card is faulty I believe it is not, because every other game I am playing and have played never crashes like this. I recently played through the entirety of Alan Wake 2 without a single crash. and Other games I have tested also have never crashed like this.

I have an open support ticket currently with CDProjectRed, and their advice has been helpful but a solution still not found. They have however recently brought to my attention an interesting bug report from RADGameTools, specifically one of their software's used in Cyberpunk called Oodle (LINK at the bottom). Basically it is saying mainboard manufacturers are using overly optimistic BIOS settings which in turn can cause errors in Oodle's data compression.

My mainboard specifically is a Gigabyte Z790 Gaming AX. In the bug report from Oodle, they mention some settings specific to my mainboard and CPU combo. So far, I have tried solution A from the report, and thought I had possibly finally found the solution. However, after several days of playing Cyberpunk without crashes at all then today outta the blue it crashes again.

Solution A specifies the following :

In BIOS, select "ADVANCED MODE", in the Tweaker tab, locate the CPU Vcore and select "Normal" option, select "Dynamic Vcore(DVID)" option, change it from "Auto" to "+0.005V" Increase the DVID by +0.005 and reboot OS, until the game crash disappears and the system is running stable. I had applied this solution and the DVID set to +0.015. First tried +0.005 but the system was not stable.

My question is: What do I need to be wary of / consider when changing this value? What's the most I could possibly apply to the DVID? With the crashes in Cyberpunk in mind, is more or less voltage applied to the DVID better?

Solution B I have not tried yet. I hope someone here can enlighten me a little more on the subject.

My entire specs:
OS: Windows 11 Pro
MAINBOARD: Gigabyte Z790 Gaming X AX
CPU: i9 13900KF
CPU Cooler: Corsair H100i
RAM: 32GB Corsair Dominator Platinum 7200mhz
VIDEO CARD: Gigabyte Gaming 24gb OC RTX 4090
MOUSE: Logitech Gaming 300s
KB: Corsair K70 MK.2
Xbox Elite2 Gaming Controller
MONITOR: AW3423DW, 27GL850
HDD: Kingston KC3000 2TB
HDD: Samsung NVMe M.2 Evo Plus 970 1TB
Power: Silverstone ST1200w Platinum

Oodle bug report:
https://www.radgametools.com/oodleintel.htm
 
Last edited:
If it's just Cyber then whatever isn't agreeing with it is going to be tough to isolate, hopefully they patch the game to be more stable on newer hardware. How long have you had this issue? Only on this system? Im not sure about dvid part, someone else can chime in with that. No game should require adjusting anything in bios except maybe rebar. But then again there was that thing about Destiny 2 and Ryzen, but think that was a once off and that required a bios update to fix.

Try
10% minimum processor state in Windows.

Rebar/resizable bar disabled in bios, if it's enabled. Geforce drivers as they are released may introduce or fix bugs. Best way to make sure a successful driver install is do the clean install option so shaders are removed and created again next time you run a game.

Update motherboard chipset drivers if available.
 
Last edited:
Sound like the specific in game Graphic settings used result in the GPU not getting the proper required power.

Seems your PSU ought to be capable, rated 100A on the 12v rail, I'd return that GPU If I was you!

Pay that kind of money and struggle along with such issues, not everybody's game.
 
Sound like the specific in game Graphic settings used result in the GPU not getting the proper required power.

Seems your PSU ought to be capable, rated 100A on the 12v rail, I'd return that GPU If I was you!

Pay that kind of money and struggle along with such issues, not everybody's game.

I've have to prove the power supply is faulty somehow, I wouldn't know where/how to start? And to even test if this was the issue its not like I have another 1200w power supply just sitting around.