and the bad boy was in that case also the nvidia driver. I remember a case, where a new nvidia driver version let crash P3D while startup and was’nt able to use P3D at all.
But as the new error message (which mentioned in former posts from som users ) now explicitly repeated : its DX12**(beta)** . So the two choices the users have should be pretty clear : dont use the dx12 beta or dont use the problematic ‘newer’ nvidia drivers. In my opinion are most of these newer nvidia drivers all beta versions and we are the beta testers - most important for nvidia is to blind the users with new features and if games use that beta stuff and it crash, then nvidia made bugfix releases ( how quick, it may depend on how the relation of the game-developer and nvidia is ? ). All the last nvidia drivers are bugfixes for games, no optimizations, nothing new, just fixes..
hey guys, i think i found one of the solutions.
Since November 22, I almost always had this CTD, when I wanted to return to the main menu. I know I have a poor GTX950M, WIN 10, DX11, but everything was fine before November.
I tried everything, revert to an old driver, modify the tdr, reduce the settings, underclock, delete the cache etc. No result.
But today a flash of genius: I completely uninstalled my NVIDIA card and turned off the computer, on restarting the card was automatically reinstalled with the latest driver.79.
So, I installed the 517.48 driver instead, and I just did 3 flights in a row around New Caledonia for 1 hour without CTD. Hope it lasts, fingers crossed. I guess in my case the problem was corrupt files since november from the graphics card installation. I’ll give more news if it does.
So, do you mean you uninstalled the drivers and rebooted, or completely removed the physical card?
Completly uninstall the graphic card and reboot, then uninstall the driver .79 and reinstall the driver 517.48 (as a new install).
Not uninstall physically the card, only uninstall by the files manager
Oh excuse me : by the Window devices manager
532.03 is peachy on my end. Using DX 12 with frame generation nearly fully maxed out.
Today I flew a pretty “demanding” flight. 1:30 hours. No problem what so ever. For like 6 weeks ago the sim kept crashing all over again every 10 minutes, whatever configuration, and even in menus.
Now this runs well… again.
Here is what I did:
Nothing.
I did N-O-T-H-I-N-G!
Driver: 531.41
If it works. Dont touch it!
If it doesnt work. Wait a bit and try again. Something is going on that isn´t informed…serverside as it seems…
Reverted to 517.48 from 532.03 on my Alienware with the RTX 3070 Ti mobile GPU and the error went away fot me-was able to takeoff and land at an airport OK.
Yes I reverted back to 531.21. No problems so far.
Being in this thread since Spetember 2022 I have had some time to collect some information. Here is my conclusions:
- This bug probably have more than one triggers.
- Syncing clouddata to local computer is one probable cause.
- Fiddling around with local settings is just a way to get around the bug while lowering FPS//Quality and stuff…
- Rancid is a very good band.
Cheers!
Hello. I’ve never had this issue until a awhile ago. I’m guessing this has to do with the new update for me at-least. I’m not sure.
It tends to happen in places that do indeed need a lot of VRAM. Such as Orbx’s London. I’m just confused why it’s happening now when I’ve never seen that message before. A restart seems to solve it most of the time.
Same here. But, going back to DX11 until it is sorted out has cured the issue for me.
Same for me, I never had any issues before, MSFS was very stabil until last SIM update and some of my friends have the same issues since the last SIM update. It’s really dissapointing when I read that other user having issues already since September 2022 and it seems that Asobo don’t see the priority to solve it asap. Atm my sim crashes on every second flight, it’s so annoying.
Alas after 3 days of tranquility and several serial flights, I have new CTDs after a quality update of Win10. I’m going to try my procedure again tomorrow to see
I think the frustrating thing is how random this glitch is. Yesterday, I was able to complete two flights. Today, I’ve tried twice to fly. The first time the glitch happened was when I was on the flight planning page. The second time was when trying to load into the flight.
Edit: The third attempt resulted in 16 minutes of flight before the glitch occurred. I’m done for the day lol.
Happened to me too. Flying from EWR to SEA. Got the error over North Dakota. I’m going to try again on Sunday with DX 11 instead of DX 12 and I’m going to save the game as soon as I reach the border of ND.
What’s even weirder is that I got a message that my bandwidth is too low and they were going to put me offline. Until the crash, though, I didn’t lose ATC at all.
Hmm, fingers crossed, is the same msfs issue they are referring to…
GeForce GRD 535.98 Feedback Thread ( | NVIDIA GeForce Forums
Fixed Gaming Bugs:
- [Microsoft Flight Simulator] Game may randomly crash when playing in DX12 mode after updating to driver 531.41 [4051526]
I’ll be the guinea pig and try it out :).
I used the Display Driver Uninstaller (DDU) again for Nvidia and AMD, reinstalled latest AMD driver and was able to fly 6 or 7 flights.
Maybe there has still been some parts of the old Nvidia driver causing the problem…
(Using 6900XT now / 1070 before)
