Hi !
I have a systematic CTD when taking off from LFMN and flying to LFMD. The CTD occurs close to LFMD. This began after the SU5 update.
I’m using the default TBM, there’s nothing in the community folder.
This doesn’t seem to happen at other airports I have tried.
- Take off from LFMN 22L or 22R,
- Climb to 1700ft,
- Fly approximately southwest straight to the Iles de Lerins (islands south of Cannes),
- Then turn north to the LUXUS waypoint (which is just east of LFMD)
I CTD just before or after this waypoint while flying north (yellow circle).
I used to have a payware LFMD mod, but have removed everything, refreshed content.xml.
Maybe someone can try this, it’s a few minutes of flight only ?
I’m probably the only person in the world with the problem, but who knows…
Thanks in advance !
Can report no problems with me. Flew around for a bit before landing too, seems ok.
I found the majority of my CTDs were caused by FBW A320… My sim was fine once I removed it. Although they seem to have it sorted now with the development version. Have it installed again and don’t have any CTDs… Touch wood 
Thanks for trying, Tim !
As I said I have no mod at all at this time, unless there’s some trace of that LFMD scenery remaining somewhere.
Hope someone else can try also…
Hello @CalitFIPST
Can currently not try myself,
but maybe it is worth searching in the msfs folder for the mod? Some mods also put files into LocalState/packages, but that should not apply to airports as far as I am aware.
Did you check for updates in the in-game content manager and did you try to delete and re-enable your rolling cache?
Isn’t LFMD a Deluxe or Premium Deluxe Airport? If so you could try deleting it through content manager then reinstall it again? Funny thing, I too had a CTD with the TBM last night, it actually gave me a BSOD. I was flying in an area I had just flown with another aircraft but I was also using the TBM mod with the Working Title G1000NXi and am attributing it to one of the two or both. BTW, if you have that installed through content manager it will not be in your community folder! It will be in your Official OneStore folder. You don’t have that installed do you, the G1000NXi?
1 Like
Just to add.
I would recommend not manually deleting from the OneStore folder and use the in-game content manager instead.
2 Likes
@CalitFIPST Are you flying the waypoints using AP? If so, can you at some point when you can maybe trying flying the same route backwards and see what happens? Or are you hand flying it?
No, hand flying, just using that waypoint as a rough reference.
1 Like
That’s good to know, alrighty. Later I will give this a shot and see if I crash 
I tried the pattern ( flew around )… no issue so far.
I remember old issues with the marketplace addon LFMD. But, you deinstalled it… hmmm…
A few things to try.
Spawn at LFMD instead of flying to it.
Delete, then re-create the scenery cache.
I had the issue others had when the Nordics update came out, where the landing challenge crashed the sim. I crashed when trying it, or trying to fly there from the East. I was able to fly in from the West though, and land there. After that I could fly the landing challenge. I assumed it was a scenery caching issue.
2 Likes
Yeah, good suggestion indeed, @CalitFIPST didn’t mention if he/she deleted rolling cache and rebuild or not. Didn’t have an issue here either so perhaps it may be the rolling cache!
1 Like
I actually had already deleted & recreated the rolling cache.
I have now disabled it completely, but the CTD still occurs. I’m really stumped…
to be sure… can you also post the message from windows event viewer ? May be we can see something interessting.
1 Like
Sure.
From several tests today, the same, systematic CTD happened when flying north, just east of the airport :
The faulting module logged most often is clr.dll (= .Net), sometimes ntdll.dll or FlightSimulator.exe itself, just some examples :
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: clr.dll, version: 4.8.4400.0, time stamp: 0x60b90751
Exception code: 0xc0000005
Fault offset: 0x00000000001bb377
Faulting process id: 0x1d50
Faulting application start time: 0x01d792c25487466b
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 7070d578-527c-4b7b-9c5f-db6f9ee0cd6b
Faulting package full name: Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.19041.1110, time stamp: 0xe7a22463
Exception code: 0xc0000005
Fault offset: 0x000000000005124e
Faulting process id: 0x23e4
Faulting application start time: 0x01d79272249d496d
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report Id: 5595a19d-ee11-4350-a033-0cc820c08ed2
Faulting package full name: Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000182e913
Faulting process id: 0x5a60
Faulting application start time: 0x01d7926dd60b54fc
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 00520f45-023f-479f-8f58-9afada415d19
Faulting package full name: Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Have you by chance ran Windows Update recently? Have you had any updates for .Net through Windows Updates?
Yes, I keep the PC up-to-date.
.NET was was upgraded to the latest versions on Aug 13 (2021-KB5004331 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10). But the problem was there before already.
Hey guys, I really appreciate you thinking with me. Will continue tomorrow !
1 Like
Every crash I have ever had in this game has shown errors that are .Net related… VC80 and the ntdll. Side by Side errors come up as well. The errors have increased for me upon installing a .Net preview update, specifically KB5004331. I mentioned it in the following post. It was a ‘preview’ at the time it auto installed and I always stay away from preview updates. I also get the Disk # 7 or 8 has been surprised removed when these crashes occur. Mind you, I only have 6 drives in my PC, 4 Solid State Drives and two Hard Drives. This one occurs with other games as well that you get specifically through windows store app. Apparently there are many virtual disks being created when the game is running. I found this out on a forum post about Forza and then another poster showed he was crashing in MSFS with this Disk Surprised Removed being listed in event viewer. He had screenshots of like 10 or more virtual disks active with the game process by clicking to show hidden drives.
When I first installed this game I did it with a fresh OS install and only the latest versions of .Net and specifically avoided installing some other games because they install older .Net version assemblies that are know to cause side by side errors that result in crashing other apps and games. So, as time has gone on it appears to me the crashing with these .Net errors has increased at every .Net update. One of these .Net updates was seemingly mandatory for the sim to even launch, not sure which it was exactly but it was before KB5004331 and when I searched for updates as a post here on the forums suggested to, there was a few updates for .Net that once they were installed the game launched again.
Anyways, sorry for the long post. I just felt as if it was relevant to mention.
Cheers!
hmmmm… I have same version for clr.dll 4.8.4400.0.
May be you can check registry:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
=> key Version : ( in my case 4.8.04084 )
But I’am not sure about a .net issue… the ntdll.dll sounds a bit more “un-nice”.
There is seemingly not a single ‘cause’ for that… I have lot’s of different reports in mind and solutions like corrupt UserCfg , windows check (sfc /scannow , dism) , sound drivers (e.g. nahimic) , gpu issues , installed mod , conflicting tools (e.g. also backup tools ) , etc…
But of course , if you get these only at these airport, and after SU5… hmmm… who knows
