Menu
What's new
By:
Filters
the Sim Settlements forums!

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Found my CTD issue, I hope...Nvidia Drivers

Thasic

Thasic

Member
Messages
35
I have been having issues with CTDs when entering Concord since I started a new play through, several months ago. At first I thought it was related to my load order with SS2. I tried altering my LO, trimming my LO down to almost nothing and finally removed SS2 and switched to SS1, to no avail. Finally, I seem to have found my problem and I thought I would share my findings in case anyone else is having similar issues. I use a Nvidia Video card, specifically, a GeForce GTX 1660 card. Nvidia has upload several drivers in 2020 and I usually download new drivers pretty quickly. Well... It seems the newest drivers are having some issues with the main FO4 program. I rolled back to the newest 2019 drivers and have had no issues in 30 hours of play. I haven't tried this solution with SS2 or SS1 yet but I am going to load up a game and see what happens. I hope my many weeks of frustration will help someone else.
 
I've found the same thing, actually. No idea why that'd cause those exact issues, but it seems to have worked. (shoutout to @msalaba who was the one who suggested that as a potential fix to me)
 
Thasic said:
I have been having issues with CTDs when entering Concord since I started a new play through, several months ago. At first I thought it was related to my load order with SS2. I tried altering my LO, trimming my LO down to almost nothing and finally removed SS2 and switched to SS1, to no avail. Finally, I seem to have found my problem and I thought I would share my findings in case anyone else is having similar issues. I use a Nvidia Video card, specifically, a GeForce GTX 1660 card. Nvidia has upload several drivers in 2020 and I usually download new drivers pretty quickly. Well... It seems the newest drivers are having some issues with the main FO4 program. I rolled back to the newest 2019 drivers and have had no issues in 30 hours of play. I haven't tried this solution with SS2 or SS1 yet but I am going to load up a game and see what happens. I hope my many weeks of frustration will help someone else.
Click to expand...
During the process of installing Buffout 4, I thoroughly read through the Nexus posts. There was mention that nVidia drivers newer than v442.92 do not play nice with the FO4 engine. There is information on this at the bottom of this page:

Buffout 4 FAQs

wiki.fireundubh.com wiki.fireundubh.com
It is also worth noting that W10 automatically updated my nVidia drivers last patch Tuesday. I had quite a few WTF moments when I couldn't play more that 5 min before a CTD. There wasn't even any nVidia related entries in the Buffout 4 crash log. Just 19 entries of Fallout 4.exe and one ntdll.dll. After rolling back to v442.92, I have not crashed since.
 
Perhaps some one should inform Nvidia they may sort it out with a compatible patch. Hopefully
 
BinaryMisfit said:
They have known for some time. It needs to be fixed by Bethesda which is highly unlikely.
Click to expand...
I take it that means whatever nVidia changed that broke FO4, fixed a bunch of other games? Translation = nVidia will not be reverting whatever they changed.
 
More to the point, as far as Nvidia is concerned (and Bethesda too for that matter), this is a very old game and not worth taking a lot of effort to correct, especially if it causes other issues with newer and hotter titles. Since I am a BIG Fallout and Skyrim fan, I just won't update my drivers for the foreseeable future.
 
Thasic said:
More to the point, as far as Nvidia is concerned (and Bethesda too for that matter), this is a very old game and not worth taking a lot of effort to correct, especially if it causes other issues with newer and hotter titles. Since I am a BIG Fallout and Skyrim fan, I just won't update my drivers for the foreseeable future.
Click to expand...

AKA, Bethesda wants you to stop enjoying the game you love and go buy 76.
 
I don't think there are any nefarious motives, it`s just Bethesda isn't making any money on FO4 any more and the company has moved on.
 
Rayhne said:
How do you roll back drivers? Just in case.
Click to expand...
Download the older driver. During installing of the old driver tick the clean install box and it will remove the existing driver before installing the one you want. There is a link to a page for the old drivers on the Buffout 4 FAQ page.
 
I have also suffered from the problem of random CDTs. I did not know that the cause was the Nvidia driver. But in my case, it was resolved in another way, I use the version translated into Spanish, if I generate SS2.esm with XTranslator, these CDTs disappear. Why? I have no idea.
 
msalaba said:
During the process of installing Buffout 4, I thoroughly read through the Nexus posts. There was mention that nVidia drivers newer than v442.92 do not play nice with the FO4 engine. There is information on this at the bottom of this page:

Buffout 4 FAQs

wiki.fireundubh.com wiki.fireundubh.com
It is also worth noting that W10 automatically updated my nVidia drivers last patch Tuesday. I had quite a few WTF moments when I couldn't play more that 5 min before a CTD. There wasn't even any nVidia related entries in the Buffout 4 crash log. Just 19 entries of Fallout 4.exe and one ntdll.dll. After rolling back to v442.92, I have not crashed since.
Click to expand...
I found the same thing. For me it was calling on nvwgf2umx.dll which is a nVidia .dll that was updated a while ago and no longer provides the information Buffout 4 looks for. Uninstalling Buffout 4 and running Baka ScrapHeap fixed the issue for me. Unfortunately Baka doesn't have some of the nice patches and stuff Buffout does but I ran 12 hours straight without a crash instead for 10-15 minutes.
 
NikitaDarkstar said:
I found the same thing. For me it was calling on nvwgf2umx.dll which is a nVidia .dll that was updated a while ago and no longer provides the information Buffout 4 looks for. Uninstalling Buffout 4 and running Baka ScrapHeap fixed the issue for me. Unfortunately Baka doesn't have some of the nice patches and stuff Buffout does but I ran 12 hours straight without a crash instead for 10-15 minutes.
Click to expand...
Actually that's a false statement.

Buffout 4 is not coded against any DLL and 100% correct in it's analysis. It retrieves information from the OS. It sound more like you had Buffout 4 installed wrong. I can confirm with or without Buffout that the NVidia drivers crash certain cards.
 
BinaryMisfit said:
Actually that's a false statement.

Buffout 4 is not coded against any DLL and 100% correct in it's analysis. It retrieves information from the OS. It sound more like you had Buffout 4 installed wrong. I can confirm with or without Buffout that the NVidia drivers crash certain cards.
Click to expand...
Huh. I'm pretty much repeating what I read on Buffout 4's FAQ entry about that specific .dll. Granted my grasp on coding is limited at best so it's entierly possible I either didn't grasp the info, or failed to communicate my understanding of it. Either way the solution was to remove Buffout as their suggested solution is to roll back drivers which just isn't an option for me.
 
NikitaDarkstar said:
Huh. I'm pretty much repeating what I read on Buffout 4's FAQ entry about that specific .dll. Granted my grasp on coding is limited at best so it's entierly possible I either didn't grasp the info, or failed to communicate my understanding of it. Either way the solution was to remove Buffout as their suggested solution is to roll back drivers which just isn't an option for me.
Click to expand...
Any particular reason rolling back drivers isn't an option?
 
NikitaDarkstar said:
Yhea it reintroduces some really annoying flickering to some of my other games, and downgrading and upgrading drivers when I jump between games on a daily basis is not worth the hassle.
Click to expand...
Interesting. Most games should work fine with any version of the driver. Your flickering might be setup related. I rolled back on my 2080 and run a lot of the newer games without any issues with G-Sync.
 
read this, and this explains why I was getting way more stutters with driver 460.79, however I don't experience CTD that much with 460 series. just more stutters when loading new cells. I went back to pre 445 series as buffout 4 mentions, and yeah it's better, but unfortunately if I play more recent games like Cyberpunk 2077, I'll get weird graphical artifacts in game, which doesn't happen with 460 series (for obvious reasons).

My question is, so they said anything after 445 series is no no, but how about 460 series, a little weird to see that anything after 445 is a no no. There must be one driver after 445 series that works good.
 
Well I've just played 4 hours in both far harbor and commonwealth with out any CTD's, I wonder if it has anything to do with Nexus as its having problems over the new mod for Fallout 3, could it be Nexus causing the CTD's?
 
You must log in or register to reply here.
Top