Fallout 4 Crashing after some minutes nvlddmkm error

[NoVa.exe]

wSo i bought and Played the Game back in 2015 at release and it worked just fine.

Now i actually got the Fallout fever and reinstalled the game.

Thing is, it doesn't work. i keep getting out of house, Running up the Hill to the Vault and usually it crashes somewhere around the Bridge in sanctuary hills.

i made it to the vault elevator once, then it crashed again while standing on the vault door. but usually i can only make it to the bridge.


since then i tried tons of stuff to fix it, and i probably tried any additional voodoo-advice i could google, but to no avail.
Game is used completely Vanilla, no mods installed.

Any Other Game (CS:GO, New Vegas, Cyberpunk, etc.)Tested works great without any issues.

Done by now:

Uninstalled and Reinstalled Graphics Driver
Uninstalled and Reinstalled Fallout 4 on C:/ Drive
Tried all possible gfx settings (Fullscreen, Windowed, VSYNC On/Off, Whatever)
Re-Seated GPU
Did some Registry-Changes according to a Forum-Topic i found.
Disabled Steam Overlay and NVidia Overlay
AV can't be the Problem, don't have one.



My System:

Win 10 Professional
i7 7700k
RTX2070Super
32GB DDR4 RAM
Steam and Game both running from the Same SanDisk SSD.


All Drivers up to date including MoBo.

[Death Approaches]

nvlddmkm is usually overheating, that's when the card disconnects from the driver on it's own... did you flash your own firmware, or change the base/turbo/memory clocks and re-flash the card? are you using coolbits or OC or UV? "Super" usually implies a factory overclock already.

I'd, just to be safe, resinstall a new nvidia driver, either up or downgrade, doesn't matter, just something that refreshes the whole install, and reinstall the directx redistributable.

And it's probably not it, but pay attention to temps. Try a lower res lower detail startup, obviously a 2070 should run ultra everything at 20% utilization or whatever, but just give it a shot if the other stuff doesn't help. (the reason I want to try lower stuff is, what if there's a bad bit in VRAM? lower utilization might not hit that region, and you'll play fine.)

edit: you said you played before, could you make sure you're not using old configs? either rename or whack the .ini files in My Games\Fallout 4 and let the launcher create new ones.

[Chaosium]

Provided you disabled weapon debris, having drivers up to date is actually an issue

Long story short, Nvidia drivers past version 442.92 have something that the game doesn't like for some reason and cause random crashes, rolling back to this one removed the vast majority of the random crashes (for me and others at least)

[DANEDANGER]

Found an older post about the same issue, seem to be related to your gpu - https://steamcommunity.com/app/377160/discussions/0/412446890561905593/

People seem to have had a fix in the post, maybe it works for you too.

[NoVa.exe]

Well it has actually been the combination of my RTX Card and Weapon Debris enabled. Disabling Weapon Debris or alternatively Install the Weapon Debris Crash Fix Mod fixed it for me.

[wtiger27]

Messaggio originale di Chaosium:

Provided you disabled weapon debris, having drivers up to date is actually an issue

Long story short, Nvidia drivers past version 442.92 have something that the game doesn't like for some reason and cause random crashes, rolling back to this one removed the vast majority of the random crashes (for me and others at least)

Yeah, I think that was certainly true at one time. But this new computer I got this last Feb, with NVIDIA drivers dated back in Dec. of 2021, on a RTX 3060ti, plays the game just fine. Weapon debris is turned off of course.

[Zekiran]

lol this is probably the one time I'd say 'wait for iron to come by to tell you to mess with bios' but they're currently still banned i think... >_>

[Nerdmigo]

Hello, this issue still occured for me and yes: deactivating weapon debris completey solves the issue! What does weapon debris actually do? Never fully got that...

[DarkMan]

If your crash generated a Display Warning event in Windows Event Viewer/Windows Logs/System with "Display driver nvlddmkm stopped responding and has successfully recovered.", adding the registry key below will fix the issue.
nVidia, Microsoft and other technical forums suggested that changing TdrDelay will eliminate premature display adapter reset events (cause of crash).

Change steps:

regedit

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers]

New QWORD(64bit)

Name: TdrDelay

Value: 10

Reboot
-------------------------
Also found a good step by step ...

What is this error? ("Display driver nvlddmkm stopped responding and has successfully recovered.") This error occurs when your computer thinks that your graphics card has stopped responding, mainly due to a low frame rate. The program that controls this is called "Timeout detection and recovery." The error is very vague, and doesn't correlate to one problem. Getting this error is like your computer saying "something went wrong with your graphics card, and we're not sure what." It could be you're power supply, ram, temperature, or just the card in general. It happens on all types of cards, and even built in ones, with your motherboard. You will know you have it if your monitor goes black for a few seconds, and comes back, with the popup from the intro picture. If you have only gotten it one time, just ignore it, but if you get it again, you should try the solutions.

https://www.instructables.com/How-to-Fix-the-Nvlddmkm-Error/

[Nerdmigo]

After looking through microsoft forums aswell that error could also be from a piece of OLDER SOFTWARE thats not correctly using some elemets of newer drivers. So my guess that this is actualyl Fallout 4s fault by doing something wrong with the Weapon Debris system. Also ALL othe rgames run FINE. For me at least.