Edit: not the case after reinstalling all content manager content, issue has returned
I had all the same issues stated here, with empty community folder. Didn’t matter which aircraft/airport either. Load times were > 30 mins. After a full reinstall of the sim I’m up and running in the beta without issue, and load times returned to normal - obviously that’s not a fix, or feasible for a lot of people, but worth noting
Exactly the same symptoms here. Community folder empty. Slightly diff fault bucket ID:
Fault bucket 2203677845575967040, type 4
My tip is for the SIM settings. If you have an arrow on ULTRA, change it to the previous level, that is, to HIGH. I have noticed that at some point MSFS is not handling the ULTRA setting well. Could you test? Here I have almost no problem with CTD, but I reduced some parameters and the fluidity and use of the hardware got better.
I think it’s worth the test. 
I’m really lost on my attempts to figure out what add-ons are the cause of the CTDs here.
I’ve got two PC – a desktop and a laptop.
With all my Marketplace Content (empty Community folder) both of these machines will CTD with a high percentage when clicking Ready to Fly.
On my desktop, I removed all Marketplace content except airports and scenery and the system will continue to see the CTDs. If I remove the airports and scenery and put in all my other content – airplanes, ORBX meshes, Seafront Simulations shipping, liveries, regional airport vehicles, etc. the system is stable.
I removed all the airports and have been slowly adding them back in and testing each time looking for when the CTDs resume. I’m still in the middle of this process.
I also am working on the laptop, I figured I see the same behavior. I removed all Marketplace content except airports and scenery and the system does NOT CTD.
How am I supposed to figure out what this even is? If there is an airport/scenery on my desktop that is causing the CTDs, how can it be they aren’t causing the CTDs on my laptop?
This feels like a near impossible to diagnose issue.
The most aggravating thing is, this didn’t exist until this beta. Yes, I could bail on the beta and fall back to the retail release, but unless this gets identified and sorted it’s going to be in SU13’s final release.
I hear you, but is this what we are here for? We try but we also pay. Isn’t this for Asobo to take care of?
Well, if Asobo points the finger here at add-ons (I’m not saying they will, but I’m not saying they won’t), then we need to identify the add-on(s) responsible.
It is in this that I am failing here.
It feels random.
Furthermore, with these horrific load times, I spent nearly all day working on this and I’m exhausted and I’m not flying the sim and I’m not doing what I bought into this ecosystem to do — fly.
It’s a total conundrum.
Did you update the dlss dll’s after you updated the sim? They insist on reinstalling very old versions that pretty much guarantee crashes for me.
Also are you using Filters/Reshade? If so turn them off and test.
Are you using RivaTuner? If so uninstall and test. Turning off isn’t enough, you must uninstall. I had to go into safe mode to do that.
Just a few things for you to try.
I have never done anything with .dlls. Give me a primer. Previous betas haven’t given me this sort of issue.
I have no filters, and no Riva.
These computers have nothing on them but the sim and associated sim support software.
I don’t use them for anything else.
Download the latest DLSS .dll from here and replace the version installed in the sim.
If you have a 40 series card and use FrameGen then download the FrameGen .dll from here and replace the one installed in the sim
I don’t have an nVidia GPU on my desktop.
I have an RX 7900 XTX.
My laptop is a 1060 Max Q, so it might be applicable.
Ah right, this will be no use then. Is it the 0xC0000005 error you are getting?
I get no error. It CTDs w/o any unexpectedly quit dialog box.
I see these in Event Viewer:
and:
Could be wrong but really don’t think this is a driver issue. The CTD happens too late — well after the cockpit has rendered. Also, would not explain the extra time it takes for everything to load.
And, in my case, I am using DX11 without any DLSS/frame generation and still have the problem.
Spent some time today and was reliably able to use FS with Fenix, FBW, and PMDG and my airports enabled.
Tomorrow will try to add back some of the utilities like VGDS, Flo, GSX, etc.
Argh!!
Your airports work?? Mine crash my desktop, but not my laptop.
This is really difficult. I would have sworn what was crashing my desktop would be identical on my laptop. However, that is not the case.
There has to be something else at play here.
No need
KLAX
A310
B787-10
B738
All good
Gaming rig:
Oh the .dll’s won’t have any effect on the loading times. That seems to be dependent on how many addons you have via the Store. I was referring to the CTD’s.
My loading times haven’t changed much either but then I have only bought 3 or 4 things from the store
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes, also a VERY long game AND flight loading time, at least 1,5 to 2 times as long as SU12.
Provide extra information to complete the original description of the issue:
I am running the RealSimGear device interface, XPForce for MSFS, and TrackIR. Will disable these to see if this is the culprit.
EDIT: disabeled all the above, by copying and deleting EXE.XML, as well as exiting FSFlyingSchool, Rex Accu Weather, Riva, and Afterburner. At this time no CTD.
EDIT 2: re-enabeled TrackIR, still no CTD.
EDIT 3: After a flight from EHLE to EHAL, I went back to the main menu to plan the reverse trip. After loading that flight MSFS hung for 20 secs after clicking FLY and showing the plane on Parking 1, and then CTD.
Naam van toepassing met fout: FlightSimulator.exe, versie: 1.34.10.0, tijdstempel: 0x00000000
Naam van module met fout: ntdll.dll, versie: 10.0.22621.2134, tijdstempel: 0xeee69ec7
Uitzonderingscode: 0xc0000374
Foutmarge: 0x000000000010c239
Id van proces met fout: 0x0x5B4C
Starttijd van toepassing met fout: 0x0x1D9CDE92C648F1E
Pad naar toepassing met fout: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.10.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pad naar module met fout: C:\Windows\SYSTEM32\ntdll.dll
Rapport-id: 763fa89a-8670-41a3-8233-c24c21876fd7
Volledige pakketnaam met fout: Microsoft.FlightSimulator_1.34.10.0_x64__8wekyb3d8bbwe
Relatieve toepassings-id van pakket met fout: App
EDIT 4: After restarting MSFS, and loading in a flight from EHLE to EHLE (circuits) and clicking FLY, immediately CTD.
EDIT 5: Re-disabeled TrackIR and restarted MSFS. After loading a flight from EHLE with the DA20 on RWY23, immediately CTD again.
I´m out of this beta, for the very first time since launch… This build can not be released in my opinion.
EDIT 6: Reinstalled SU12. Much faster loading and no CTD after spawning.
If relevant, provide additional screenshots/video:
After about 12 hours of troubleshooting/testing, I believe I have solved my CTDs by removing the following addons:
GSX Pro
FlyTampa Las Vegas/City Bundle
FS Dreamteam Chicago O’Hare airport
These all have in common modifying the airport environment. So, for those still having CTDs I would recommend removing all third party addon airports and GSX Pro and then see if this fixes the problem. You can then start adding airports back in, one by one, to determine which are really the problem - this is a time consuming task.
I’m approaching your 12 hour mark, for sure.
I, unfortunately, haven’t figured out which airports/sceneries are causing my CTDs and I don’t have any of those three add-ons.
I’ve said this a few times now, but there is more to this than meets the eye. I don’t think it’s as simple as it’s X, Y, and/or Z add-on (and im not saying you are!). There is some underlying change that is affecting a number of different add-ons in varying combinations.
The fact that I’m now seeing my two different PCs with identical add-ons installed CTD on one PC and not the other is testament to this. I’d like to understand how the sim loads add-ons and in what order. I’m trying to understand if my experimenting on each PC hasn’t been in precisely the same steps and I’m shifting how the sim is loading the same add-ons in different orders on each PC, which is causing the two PCs to behave differently.
I suspect that there are more than just the three addons I listed causing problems. The time consuming part is each individual determining which are causing problems for them. This process could probably be done much faster by connecting a debugger to the sim to determine what exactly is happening. Hopefully, Asobo can do this.