Crash nvlddmkm error in event viewer

[Norcus]

Game crashes constantly and the event viewer returns the same error every time:

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\000000c5
Error occurred on GPUID: 800

The message resource is present but the message was not found in the message table

[Norcus]

Also I use a RTX 3080 with latest driver. I use "optimized" settings from Gforce Experience.

[thunda]

Your GPU is crashing. Some RTX 3080 models (like mine) come from the factory with a factory OC that is unstable. You might need to lower your clocks. Use Afterburner and set your Core Clock 20 MHz lower. You wont lose even 0.1 fps, but could fix your crashing. If it doesnt work, keep dropping it in 20 MHz increments until crashing stops.

My 3080 is now undervolted to .850v with 1815 MHz clocks with +500 on mem clocks, but thats another story. Lose about 3-4% performance, and 70-80 Watts less power usage.

[Norcus]

I did a complete uninstall with DDU (guru3d.com) and a clean install of downloaded drivers (remember to download installers and disconnect internet while doing this).

No crashes after that.

[ArtSkunk]

Originally posted by Norcus:

I did a complete uninstall with DDU (guru3d.com) and a clean install of downloaded drivers (remember to download installers and disconnect internet while doing this).

No crashes after that.

Gonna try this for mine, fingers crossed! I have a 2080 Ti and I'm getting the same errors along with a warning event: "Display driver nvlddmkm stopped responding and has successfully recovered."

[Neuralsplyce]

Using DDU to do a completely uninstall the driver helped some. What I found to significantly reduce the Crash To Desktop (CTD) issue was manually deleting the shader cache files. This is based on comments I've seen elsewhere about this being a recurring issue with Nvidia cards going back years. It also make sense to me because I have both Steam and PC Game Pass versions of Starfield installed. Both worked fine for days but today, both started experiencing CTDs. That indicates the issue isn't (entirely) with the game and is a result of an accumulation of issues inside the cache.

Here's what I did:

1. Exit the game and Steam.
2. Open Nvidia Control Panel
3. Select Manage 3D Settings.
4. Scroll down to Shader Cache Settings and change to 'Disabled'
5. Click on Apply and wait for the changes to take effect (the window flickers a bit)
6. Reboot the PC
7. After the reboot, open CMD or File Explore and go to C:\AppData\Users\<user name>\Local\Nvidia.
8. Go into the DXCache and GXCache folders and delete everything.
9. Go back into Nvidia Control Panel and change Shader Cache Size to 'Driver Default'
10. Reboot the PC.

I still have the occasional CTD when using menus or viewing the galaxy map, but far less frequently. My hope is that by going to another solar system the game will clean up any residual issues tied to the system the CTDs started in. So many PC issues seemed to appear at random and disappear just as suddenly (almost like the PC has bad days too).

[supermag]

recently had the same issue as op has, tried the shader cache trick...didn't work here, gpu drivers up to date, went into game settings and disabled upscaling, (the other two settings in this setting are for amd cards), no ctd so far...

[Antagonist1]

This is hardware issue, took me one year to fix. First check if increasing RAM mhz worsens the problem, if black screen reset bios until you have access again, alternatively check if lowering mhz alleviates the problem somewhat. This dosent necessarily mean RAM issue but we are getting closer. Now if you have a PCIe extendor cable for you graphics card please remove it and fit graphics card directly into mobo PCIe slot without extendor cable, if you don't have extendor cable, try different PCIe slot. Most likely your issue will be solved, reinstall driver properly everytime you experiment this and if the mobo don't recognise the card give it a couple chances as this only worked for 2nd time I tried, of course after everything else failing. 2nd option is your ram is busted and you need new ram. If problem never gets solved, I would start by buying new RAM, if that dosent fix it, I would buy new mobo, if that dosent fix it, new graphics card, and this is as much experience I have gotten from fighting this 1 year and fixing it. My issue was cheap, the PCIe extendor cable had to go or be switched with a new one.
Another guy fixed it by switching PSU cables, hardware issue for sure.

[Ǥɾᴧᴤʆᴧᵯᴧ]

It can't hurt to check the mainboard description to see which PCIe lanes are shared. Usually, one port is used exclusively for the graphics card, i.e. it does not serve a second PCI device.
It can also help if you pull out your cards and push them back in to 'clean' the contacts. This also applies to the RAM, even if the bars are light and tend not to move. The mainboard always vibrates because of the ventilation.
Also check the power supply voltages while you are playing. There are tools for this... AIDA64, for example, and so much more....

Yes, you rarely think about cables, they never actually break and yet they do :)
If nothing helps, there's probably something in there that wants to say goodbye.
Good Luck!

[HNXRogue]

Had the same issue with latest nvidia driver + (outdated) dlls mod from nexus, reason beeing mod didn't get updated to new driver. Downgrading driver removed the issue.

[Volk]

Nothing worked for me after hours upon hours of looking, applying fixes, and retrying, but I eventually found out that I had an event trigger in widows event logs "Display driver nvlddmkm stopped responding and has successfully recovered," and located a registry entry fix detailed HERE: https://gameplay.tips/guides/starfield-crash-fix-for-display-driver-nvlddmkm-stopped-responding-and-has-successfully-recovered.html
So far no crashes after I applied the registry fix. I wanted to share this in common posts so people can find it easier.

[ZDuB]

i use to get this same crash error until i found this fix :

1. Goto registry editor (start -> run -> regedit)
2. Navigate yourself to HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/GraphicsDrivers (make sure GraphicsDrivers is highlighted).
3. Right click -> New -> DWORD (32-bit) value -> Name it: TdrDelay -> double click it -> Set it to A (hexadecimal) or 10 (decimal).

[[NoPants] Nahrix]

I rolled back to some drivers in August, and haven't had any issue since.