Hey Guys ! So i switched to DX12 and it did not crash! (Thats one fix)
The better fix would be to roll back your NVIDIA drivers and switch back to DX11! That worked for me too..
1 Like
Maybe if Asobo would implement detailed crash logs and debug dumps for issues like this instead of relying on Windows Events, it would be easier to track downâŠ
1 Like
Since there is no permanent fix for this problem right now I found a way that I can run the sim crash-free, usually for several hours, so I thought I would share it here in the hopes that it works for some others looking for some kind of workaround.
All I do is reinstall the NVidia driver before running MSFS.
I have the driver install file on my desktop, I turn on my PC and run the driver install, then start MSFS, and it works every time, usually for several hours without a crash - usually.
Some caveats:
-
I just do the express install, and install the driver ONLY! Do not reinstall GeForce Experience or it wonât work. Itâs ok if GeForce Experience is already installed, just donât install it again. For some reason that causes it to continue crashing. You do NOT have to uninstall first! The reinstall will take care of that.
-
I like to have the ATC popup window on another monitor. That will cause crashes while approaching the airport, so you must not pop out the window.
-
If you open anything else (browser, msi Afterburner, etc) it will probably cause a crash.
-
If the sim crashes or you shut it down and restart it, you must reinstall the driver again. It DEFINITELY will crash just as before. The sim seems to change something in the driver each time it runs.
-
Settings donât seem to have much of an effect as far as preventing crashes. This is the only thing that works consistently for me, and I have tried everything in this thread. My settings are below, in case it does make a difference.
-
I have a pretty beefy machine, and hardware probably plays some part in success or failure. This PC is only a few weeks old with only a few games installed. All fresh installs, no addons, no overclocking, everything up to date.
-
I will still get occasional crashes, but if this works for you as it does me, they will be much more rare.
-
I have the standard version of MSFS and only fly the C-152 (I wish I had known that it does not include the steam gauge C-172, or I would have paid for the deluxe version and Iâm not paying the rediculous upgrade price for a single plane, but thatâs for another time). I have no idea if that makes a difference or not. Airports donât seem to make any difference.
Some of my sim settings are as follows:
Display: Full screen, 1920x1080
Anti-aliasing: TAA. This setting seems to work for me on either TAA or DLSS
DirectX: DX11. DX12 also seems to work fine
Terrain level of detail: 330
Depth of Field, Motion Blur, Lens Correction and Lens Flare all off
Worker Density 60
Everything else is set at Max or Ultra
Windows settings as follows. These donât seem to have any effect on crashes, but I have to experiment more to be sure:
HAGS off
Game Mode on
System Hardware:
Corsair RMX Series 1000 Watt power supply
ASUS TUF Gaming Z690-Plus WiFi D4
64 GB Corsair Vengeance LPX DDR4 3600 RAM
EVGA GeForce RTX 3080 ti FTW3 Ultra Gaming Video Card
Intel Core i9-12900KF Processor
Samsung 980 PRO 2TB SSD
Windows 10 Pro version 10.0.19044 Build 10944
I hope this helps some people to be able to do some flying until a real fix comes along. I know how painful withdrawal can be.
1 Like
I can pretty much guarantee that a âproperâ fix will include a reduction in gpu performance so maybe not trying to squeeze every last fps out of it is the answer. Increasing LOD and traffic may actually help.
That can be true if the error was due to a lack in hardware capabilities, which is not true in this situation.
& technically, this would not be considered a way to fixing things, because this means the sim has to be limited instead of being leveling up.
1 Like
Why not? because thatâs exactly the way that sandboxed games work, they establish their limits and then apply them across the board.
agree. but not when you are talking about MS product, not an indie software or limited developing one.
this sim cant be compared to another.
Itâs a continuously moving target and until Microsoft say âfinishedâ will always be so. There will be ups and downs, there always is.
1 Like
there will be never a finishing line in tech. LOL
1 Like
100% true.
Do you have the same issue if you follow the OPâs steps to reproduce it?
Yes, I have been getting this same error after flying in MSFS for a while after the last sim update. I never had CTD problems with the program and I never received this error before the last sim update.
Provide extra information to complete the original description of the issue:
This error has been occurring regularly since the last sim update. Windows Event Viewer has errors for âCloud Files Diagnostic Event Listenerâ failed to start with the following error: 0xC0000022", âThe description for Event ID 0 from source nvlddmkm cannot be foundâ and âDisplay driver nvlddmkm stopped responding and has successfully recoveredâ. I have an NVIDIA GEFORCE 1650 video card on an I-7 system with 32 GB of RAM.
Are you using DX12?
NO
Are you using DLSS?
NO
If relevant, provide additional screenshots/video:
Ok, the main reason for me to post this observation is that Nvidia had a post in their releasenotes for their previous driver. The issue was that the system reported wrong values according to temperature. I figured that the WDDM could be a part of thatâŠ
Given the fact that this problem is completely âmutedâ by Asobo anc MS I figured it could be a OS-problem that MS didnt want to shout out loudâŠ
Well, I flew another flight (DTW to LGA) and it works fine for me when using DX12.
Iâll have to try DX11 again to see if it crashes once again, but DX12 appears to be stable for me (for now).
Quite possibly. Most corporations try to avoid making erronious statements about another companyâs products and if they do say anything you can bet itâs only with approval of their law department.
Win 11 Official release indeed has problems like memory leaking, 22H2 has additional errors over 21H2, related to remote control management, storage speeds, and other problems, and all were confirmed by Microsoft.
but this is far from our issue, because the sim worked fine to all simmers, just SU10 hold an issue. so definitely it is not an OS issue.
Not to mention that different simmers are using different operating systems.
Tbh 22H2 and the latest NV driver work perfectly for me so I guess Iâm just lucky.
Actually no ⊠the taskbar has stopped hiding itself under some situations and I must then toggle the windows key to close it 
1 Like
They released some patches and the process is still going.
1 Like
Hello
Since today I have this crash with the same error message.
I never had CTD problems with the program and I never received this error before the last update of Nvidia drivers version 522.25 (12 oct 2022) and the update of W11 KB5018427 11 oct 2022.
My graphic card : RTX 2080 Super
proc i9-9900K
This is the error detail, itâs well related to nvidia drivers (nvlddmkm) :
Nom du journal :System
Source : nvlddmkm
Date : 15/10/2022 21:48:34
ID de lâĂ©vĂ©nement :0
Catégorie de la tùche :Aucun
Niveau : Erreur
Mots clés : Classique
Utilisateur : N/A
Ordinateur :
Description :
La description de lâID dâĂ©vĂ©nement 0 dans la source nvlddmkm est introuvable. Le composant qui a dĂ©clenchĂ© cet Ă©vĂ©nement nâest pas installĂ© sur lâordinateur local ou lâinstallation est endommagĂ©e. Vous pouvez installer ou rĂ©parer le composant sur lâordinateur local.
Si lâĂ©vĂ©nement provient dâun autre ordinateur, les informations dâaffichage doivent ĂȘtre enregistrĂ©es avec lâĂ©vĂ©nement.
Les informations suivantes Ă©taient incluses avec lâĂ©vĂ©nement :
\Device\Video3
Error occurred on GPUID: 100
La ressource de message est présente, mais le message est introuvable dans la table des messages
XML de lâĂ©vĂ©nement :
0
0
2
0
0
0x80000000000000
3737
System
\Device\Video3
Error occurred on GPUID: 100
00000000020030000000000000000000000000000000000000000000000000000000000000000000
Do you have the same issue if you follow the OPâs steps to reproduce it?
yes
Provide extra information to complete the original description of the issue:
Also RTX 2080 Super
Are you using DX12?
no
Are you using DLSS?
yes
If relevant, provide additional screenshots/video: