Or, we could stop blindly firing into the darkness by doing some simple deductive diagnosis.
Orbiter's log files will tell you exactly what you're missing, at least 99% of the time. If Orbiter CTDs, the reason is written into the Orbiter.log file, as is every other piece of useful debug data, which is why it's always the first place to look if there's a problem with Orbiter.
So, for the hundredth time this week, please wander into your Orbiter folder, open the file called "Orbiter.log" in a text editor (Notepad works fine). Select all (CTRL + A), copy (CTRL+C), move to the window with this thread in it, and click in the Quick Reply box below. Paste (CTRL+V). Now, select what you just pasted into the box (highlight it with the mouse, or, with the focus on the input box, CTRL+A), and press the "Code" button on the little toolbar for the editor.
Then post the result.