Good question, I received my new machine yesterday with zero items in community folder and I get a loss of FPS after an hour of play and random CTDs but I had live weather and traffic so going to try without those this evening.
EIDW orybx mod causes CTDs for me aswell.
You can make this even heavier.
When utilizing for example the directx API, and you have fed it with 100% valid data, the data is out of your hands. it has been given to an API with fully valid method parameters. If whenever, for whatever reason, there is a data fault occuring because of (stated above). You will still possibly be getting CTD’s.
flightsim method → directx handover → directx internal methods (VRAM copy, for example) → high capacitor discharge → bit fault → CTD.
So as stated by @CodeLoran69, the flight sim is not exclusive. Even though we are speculating, and trying to draw conclusions, the stack traces tell the truth.
Hence in my app, plugins can cause severe crashes, because it’s almost impossible to catch all kind of external factor errors (like mods). The question is, are the traces we see proper enough to be able to say so.
So the debate stays, it can be the sim, a mod, or the hardware. But only come to some near conclusion if a stack trace can be dissected enough to come to that conclusion.
Edit: This post was meant as generic, not as a direct reply. PEBKAC situation here.
Thanks, makes sense. I think the procedure is described here:
It requires editing the registry, so I first need to take a brave pill 
Not sure why crash reporting is not an integral part of the sim, you would think they would need all the crash reports they can get …
Why write your own if it’s handled by the system it runs on. It’s like re-inventing the wheel. these traces for developers more then often have enough info.
Some subsystems do not allow these exceptions to go up the stack back to the source. For example the windows graphics pipeline timing watchdog shuts down the app and writes it’s own trace.
Possibly ending up into two traces, one by the subsystem and one by the app. Combining them as a developer shows cause.
Clean install, have helped me several times.
Just because a package comes from the Marketplace does not mean it’s not an addon, and therefore means your install is not equivalent to “zero items in community”. If you purchase a package from the Marketplace, it’s the same thing as having a mod in community. Orbx packages have been causing CTD’s from the day they released their first package for MSFS.
I’m not making any statement here or trynig to say you shouldn’t purchase from Orbx, only trying to help people realize there are other mods than those in Community, which are just as susceptible to being poorly written and/or cause issues/need updating after updates.
No I fully understand but I had everything removed.
I was referring to my old system with EIDW installed.
Out of Interest, anyone here have experience of software development, where they have written code, that had CTDs, and have then gone in, analyzed the cause, and fixed it ??
I get the impression, a few ???
Yep, especially in multithreaded environments and in hybrid solutions (multiple platforms (win/nix/android/ios) with different API’s for identical tasks).
yes, you were Obvious !!! 
Have you looked at any of your MSFS CTD CrashDumps, and formed any conclusions from them ?
( I see a long reply in the making and being edited !! )
I watched two, and they both looked to be my fault, my app crashed one time together with the sim (that was obvious) and one with the sim crashing quickly after starting my app. This moment i was not sure, but the cause appeared to be the same. So other crashes i didn’t care when running my app.
Others i have not watched, but if, they have been from other users, lot of them involved illegal access (directx), and one was from an nvidia dll (don’t remember of that was also an illegal access or not). Stopping whatever “optimization app” that was running solved it, although the user still blamed mfs though.
But the reasons when it crashed for me was when not doing something else (self identified as) obvious reasons. USB detach (I’m an AMD user, guess what i did 
), loading assets while zooming in, etc.. I also didn’t care USB attach/detaches when i do some prototyping after fixing the original USB issue.
So, in my case. it was 9 out of 10 my own fault.
I sometimes talk too much, illogical or running for being typo master. But now i’m done i think.
Talking about USB .
I 100% every time, get a CTD when I plug in a certain Thrustmaster Joystick. ( So do every other Thrustmaster “Top Gun” FF Joystick owners.)
Seems to crash at or about the time it would be creating the Configuration file.
Without a symbol table, or the Source, I am having difficulty determining exactly what is going wrong, and no way is Asobo going to pursue this one, even if it is
(1) A Thrustmaster Joystick ( Thrustmaster is a Dev Partner)
(2) Its the “TOP GUN” model – and MSFS is about to bring out a TOP GUN addition.
You up to to taking a look, to see if you can figure out what is going wrong if I get the Crash Dump file to you ?
The only time I get CTD’s when when my 3080 is overclocked, even mildly when 100% stable in any other game. So from my experience MSFS seems to be very sensitive to GPU OC’s.
I don’t remember to have to change anything in registry to generate dump file when CTD. I use this old tool I found in a random forum, probably not the best one, but do the job: BlueScreenView.exe
Web site: Blue screen of death (STOP error) information in dump files.
I thought you had to have a minimum amount of Virtual memory on the Boot drive to be able to capture a CoreDump, and then you need to set up here you want the dump saved etc etc. and what type of CoreDump you want ( I use “Complete Memory dump”)
I also have about 32G of page Page File, and have it FIXED in size, not managed by system, and changing size.
I also have the registry set to clear it on shutdown (or is it startup) ?
Nice to start with a clear 32G contiguous space.
Maybe these are just old habits from the days of Mechanical Hard Drives, but these setting seem to still serve me well.
Probably the same reason I see commercial software regularly packaged as version 1.0.0.0, even thought the installer is version 9.3 or whatever.
Well, if i need to identify cashgrab, lazyness, or quality? That would be one of the criteria. Especially for this, i would buy a bin, print out any contents and burn it with a cursed voodoo doll (no, not for real).
@N6722C Could take a look, i doubt if it would be useful. It’s the Afterburner FF?
Yes, AFTERBURNER ..
Assuming its some file creation issue,
First I’ll try making a Profile along the lines of the ones already in the SIM, for the specifically supported Joysticks, with the correct info for the Afterburner.
See if it pick up on that .. otherwise, the “Afterburner” is heading to Ebay .
Maybe not so afterburning fast. It would be sad if it was only because of some weird character in the peripheral name. Like having "-double quotes (Really? Yes, really, seen enough of that kind of stupidities).
Had only my 2nd CTD last night.
First was last year, making a flight plan on the world map. Last night i was doing about 500mph in the F-22 over LA & i looked to my right. That big performance drop with the scenery culling is a serious problem at higher speeds.