Hello everyone.
I’ve been battling for 2 weeks with the infamous subject dll problem.
I had never experienced this problem before the graphics card switch about 2 weeks ago.
Since then it has been impossible to carry out any flight, repeating CTD.
I thought of a buggy scenario, I thought about the drivers and changed them all, I removed all the OC profiles from CPU, RAM, removed g-sync, put it back, then removed the GPU BAR… endless drama.
I even thought about reinstalling the game.
Then one day I just used (again DDU) but this time using it with a windows restart in SAFE MODE.
After cleaning the drivers Windows restarted and automatically installed the Nvidia drivers of this version:
531.79
I started MSFS and a pop-up warned of possible driver incompatibility issues. I continued and scheduled a flight.
No CTDs.
Then a second.
Then a third.
For now I’m at 4 without crashing.
Thanks for the info. I’ve been having crashes in the same module, and others related to NVidia for about the last two weeks as well. I always strip the bloat out of the drivers when I download them, so I’m going to test 536.67 as is. If that doesn’t work then I’ll start backward a bit and may end up where you are. I’ve been reading that others here have had more CTDs lately, so something is going on.
It might have to do with how the driver interacts with external screens, at least in my case. I tested a bit and tried the latest driver as I noted above and still had the problem. I noticed that it occured just after I had clicked on an ATC or VFR map window, which I tend to move to a second monitor. It never did it immediately, but after, I’d guess, about twenty interactions.
I moved the ATC window to my main screen and used LNM instead of the VFR map, and I’ve had five flights with no CTDs. So at least it’s working… for now.
BTW I did IT support way back in the day when 20 mb hard drives were more than you would ever need in a PC. I still love tearing apart IT problems - just not in MSFS… I just wanna fly!
I kept on getting an Nvidia DLL error message after getting a CTD a couple of years ago and taking out my graphics card and disconnecting the cables then putting it back in solved the problem. Whether it was the same DLL error as yours I cannot remember.
I’ve started with nvwgf2umx.dll crash recently and don’t use reshade. I have found that having reBar enabled with the frame generation mod active brings it on quite quickly say within 10 mins of starting a flight, but it still happens occasionally without this set in NVidia Inspector also. Anybody have any other clues to what might be triggering it?
Thanks for the suggestion but from what I gathered, this is an NVidia issue, so I’ve cleared the driver with DDU and re-installed it, I’m now going to test whether it has any effect at all. If that fails then yes I suppose the next logical step would be removing add-ons.
Edit: Test one of a 50minute flight around the Philippines after DDU and re-install and NO CRASH, I even gained 10fps, so something must have gone wonky on my end with the installed driver (546.33) while I was testing different graphics settings the other day. So far so good.
Edit 2: the second test was a bust, I’m still getting crashes, totally at random with the same faulting module.
Actually i’m running 546.33 Nvidia Driver and crash occured with various different MSFS settings (both TLAA or DLSS, both frame gen or frame gen off)…
So please …do you remember which MSFS settings you was running before rolling back to default Windows Nvidia driver ??
And actually, after rolling back to oldest driver, are you running the same MSFS settings you use when you had the crashes ??
I still love tearing apart IT problems - just not in MSFS… I just wanna fly!
