The LC-41 crew tower had textures by accident allocated. I played around with some standard textures for concrete etc., but their path ended up pointing to the CST-100 folder instead of the standard texture folder. Will correct this.
On the CTD's at startup: I am glad you also experience them sometimes! Nobody was complaining up to now, so I thought maybe my Orbiter setup was damaged.
My experience is a sudden death at the end of the loading screen. No suspicious entries in the Orbiter.log. Statistically it happens more often after resuming the current scenario.
Interestingly, after crashing a scenario in D3D9 client, the same scenario still starts in Orbiter's default graphics client. And the funny thing is, sometimes later the very same scenario might as well resume in the D3D9 client.
Currently I am looking in the code as well if the are corrupted meshes. Will also clean out missing textures, but they normally do not crash the program.
Main suspects are memory leaks or wrong memory allocation.
Maybe somebody has an idea how to populate the ~Destructor() so it really gets rid of anything in the memory?