Crash to desktop without error message

Never had such a problem before, but after recently it started to crash to desctop after I loaded in cabin and started to move camera from side to side. I didn’t do anything in this period except updating FBW A320. So, I thought the problem might be in it. I reinstalled and then completely deleted FBW and tried it with default A320. The problem repeated and started appering constantly. I reinstalled MSFS again - nothing helps. The game is now completely unusable. Nvidia drivers are up-to-date. Don’t know how to clear up thisbug from system to reinstall MSFS from ‘clear sheet’…

For me the latest NVIDIA GPU driver causes CTDs. Reverting driver version has solved them all, just some advice :slight_smile:

2 Likes

was just a hint with a little side-note :rofl:

I wrote it also, because it can no recomendation to install such kind of old drivers you linked. There are in meanwhile a lot of security updates and I would only point to the fact, that newer drivers normaly works and only because the latest one makes trouble, the users should not install years old stuff.
Of course, we speak about nvidia and the quality of the drivers becomes worst in last years and if we see the size of the installer we know it is a big mess in meanwhile. Within a different topic there was a discussion about… but users should aware of the security.

I have a new PC, Core I9 12900K, 32 Gb Ram DDR4, RTX3090 and FS2020 (SSD 2to Pcie Gen4) crash to the desktop when I launch à flight (Paris,Bruxelles, New-York) (but not in “small” south europe cities like Lisbon, Biarritz) …

Was on final APPR now into KLGA, CTD - I’m SOOOOOOOO annoyed right now.

:rage: :rage: :rage: :rage: :rage:

If you’re on the new Nvidia driver I believe it causes spikes to your cpu which might or might not object.

If that is consistent, then it has to be a Community mod.

1 Like

HI All,
Not ever having had a CTD in MSFS, it took me by surprise to find that, although loading fine to the point of being inside of the aircraft, it CTDed. As soon as scan left or right, it crashed without an error.
Read lots of post and tried many possible solution without success until I recalled a recent update!!
FOUND the culprit as now it is back to normal. Latest NVidia driver (v497.09 of 1DEC21). I just rolled back to the previous version and presto! (v496.76 of 16NOV21).

2 Likes

it usually happened to me on short final as well.

Same here back to the previous version on Nvidia resolved the sudden CTD issue for me

This game is so sloppy and unorganized that even GPU Driver updating makes CTD’s.
I am thinking to go back to X plane 11 and 12 later.

Maybe a solution: Try to switch off SAM feature (rBAR, resizable bar) in BIOS if you have it turned on.

I did turn off the resizable bar in BIOS couple of days ago and I haven’t seen and CTDs since then.

I will follow the development and report back.

MSFS release 1.21.13.0

system: RYZEN 9 5950X, 128 GB RAM

[Display]
Operating System: Windows 10 Pro, 64-bit
DirectX version: 12.0
GPU processor: NVIDIA GeForce RTX 3090
Driver version: 497.09
Driver Type: DCH
Direct3D feature level: 12_1
CUDA Cores: 10496
Resizable BAR No
Core clock: 1860 MHz
Memory data rate: 19.50 Gbps
Memory interface: 384-bit
Memory bandwidth: 936.10 GB/s
Total available graphics memory: 90065 MB
Dedicated video memory: 24576 MB GDDR6X
System video memory: 0 MB
Shared system memory: 65489 MB
Video BIOS version: 94.02.42.00.A9
IRQ: Not used
Bus: PCI Express x16 Gen4
Device Id: 10DE 2204 87AF1043
Part Number: G132 0010

[Components]

nvui.dll 8.17.14.9709 NVIDIA User Experience Driver Component
nvxdplcy.dll 8.17.14.9709 NVIDIA User Experience Driver Component
nvxdbat.dll 8.17.14.9709 NVIDIA User Experience Driver Component
nvxdapix.dll 8.17.14.9709 NVIDIA User Experience Driver Component
NVCPL.DLL 8.17.14.9709 NVIDIA User Experience Driver Component
nvCplUIR.dll 8.1.940.0 NVIDIA Control Panel
nvCplUI.exe 8.1.940.0 NVIDIA Control Panel
nvWSSR.dll 30.0.14.9709 NVIDIA Workstation Server
nvWSS.dll 30.0.14.9709 NVIDIA Workstation Server
nvViTvSR.dll 30.0.14.9709 NVIDIA Video Server
nvViTvS.dll 30.0.14.9709 NVIDIA Video Server
nvLicensingS.dll 6.14.14.9709 NVIDIA Licensing Server
nvDevToolSR.dll 30.0.14.9709 NVIDIA Licensing Server
nvDevToolS.dll 30.0.14.9709 NVIDIA 3D Settings Server
nvDispSR.dll 30.0.14.9709 NVIDIA Display Server
nvDispS.dll 30.0.14.9709 NVIDIA Display Server
PhysX 09.21.0713 NVIDIA PhysX
NVCUDA64.DLL 30.0.14.9709 NVIDIA CUDA 11.5.121 driver
nvGameSR.dll 30.0.14.9709 NVIDIA 3D Settings Server
nvGameS.dll 30.0.14.9709 NVIDIA 3D Settings Server

Great idea … why not blame Asobo for Nvidia’s bugs indeed :rofl:

1 Like

I donno, the game name is MSFS, so I blame M :joy:
Simple calculation

1 Like

I’m sure Asobo will be relieved :rofl:

Any better idea? :upside_down_face:

:roll_of_toilet_paper:ing back drivers seems to work

No, I had CTSs with previous drivers as well. In fact, after the latest update (1.21.13.0) CTDs started to occur. Before they were quite seldom. I believe Asobo has to take care of CTS sure, but in the meantime, let’s try to make our lives easier.

No such troubles for me but then I can’t see inside everyone’s PC and neither can Asobo. Sure they get crash reports and do what they can their end but it’s no guarantee it will work ours. According to Seb stats show it’s mostly 3rd party mods which Asobo cannot bugfix legally.

I have CTD during “ready to fly” with this last update 7 …