Ironically, this started happening immediately after adding the Object Flow 2 for ORBX products for P3DV4 airports. They stated I should ask FSDT.
Which is funny, since from your report, which I trust, it should have been obvious the problem was related to installing the new Orbx .DLL, which has just been released. Our has been there since the day P3D was released, and always worked ever since...
Reason being is after I get that SODE error and the SIM crashes to desktop, when I run FSDT LIVE UPDATE, it appears to fix the issue temporarily but it then starts again when starting the sim at a later time.
I can easily tell you why you might THINK this has "something" to do with FSDT, because it's sees to be fixed by the Live Update.
What's really happening is that, since the sim crashed (likely because of the new OrbX module you installed), Windows itself tried to "fix" the crash automatically, and set a compatibility registry key for Prepar3d.exe which in fact would make the problem worse, and prevent the sim from starting.
So, as a safety measure, we clear this registry key with the FSDT Live Update, so you see the sim is starting again, but that's not because we "fixed" or "updated" our software, but JUST because we cleared that dangerous registry key which prevent to start the sim, even when the cause of the crash didn't had anything to do with us.
SODE has the same option to clear this key, just is not automatic, and it's the "Fix 3rd party software Error" option in the Platform Manager menu. It does exactly the same thing as our Live Update: just clear the registry.
One final thing I did notice was this only happens when I go to a FSDT airport. So when launcing the sim it crashes to desktop. When I run FSDT Live Update the sim starts. If I restart the sim at a non FSDT airport after the repair I can then start the sim over and over without it crashing to desktop.
The first thing to try, would be trying to disable the OrbX module, and see if there's any difference.
