Hello friends! http://www.smileys.ws/sm/action/00000065.gifMy FS9 has been stable as a rock all these months - until I decided to hop in the MelJet 777 http://www.nextgenerationrecords.co.uk/boa...es/icon_eek.gifFS9 began to CTD with a "ntdll.dll" error. These CTDs occur at any of the following when:1. FS9 is at the splash screen2. I select a 777 and hit the "Fly now" button3. I change the type of plane Im in to a 777 (eg:from iFDG A320 to MelJet 777)But (and its a wierd "but"!) all of the above only occur when the Meljet 777 is loaded with the 777 panelThats right...while trouble-shooting I found that if I aliased the 777 to any other random panel the plane loaded up perfectly with no more CTDs.Its almost like FS9 has decided that the 777 panel will cause a CTD with the ntdll.dll error.I found a workaround:I load the 777 aliased to an MD80 panel. Once the plane has loaded I then jump back into the panel folder and alias the Meljet back to its regular 777 panel. I then reload the flight. The 777 then loads normally with its regular panel. Its irritating...but it works and at least now I can fly the 777 with a proper panel and w/o CTDs.________________________Have any of you had this problem and if so how did you solve it? I found out that ntdll.dll is a Windows module that contains NT system functions. Why it would *only* cause a problem when the 777 panel is initially loaded in FS9 has me bouncing off the walls http://www.nextgenerationrecords.co.uk/boa...es/icon_eek.gifWould greatly appreciate some insight from you all...thanks lots! :)

Nevin,I'm having the same problem down to the Meljet 777.However I don't get any indication what is causing it to CTD. It asks me if I want to send the error report to microsoft...blah blah blah.I did notice when the fall season came around, the CTD happened.I switched it back to Summer season and the CTD stopped.I have megascenery NY installed but it only shows up in Winter or Summer. Fall and Spring reverts to the default FS9 scenery.Another thing is that when in the fall season, I take a 737 out, the CTD doesn't occur, but it occurs with the Metljet 777's. I wonder why?

Midnight LS1 - I fixed it! I deleted the fs9.cfg and let it build a new one. All the CTDs and errors went away!Give it a try, you dont have to delete the old .cfg either...just rename it :)

I did that before while troubleshooting and it didn't help either.

Oh no :(I wonder why your FS9 is being stubborn....does my workaround work for you (what I first posted in this thread)?Its a bit of a pig but at least you can fly your plane...unless of course you find a better faster way.Hope you find a fix soon!!

Hi,I had the same CTD with my own panel.Some "debugging" showed up a gauge with used the Transparancy=.. Tag.In the panel is another gauge with uses the same Tag.It seemed the simulator didn't liked to have two transparancy's projected over each other.After removing the Tag in one gauge, the CTD's were history.So may be something in the 777 panel in combo with the Mel?Start outcommenting {Windows} in the panel,cfg and when no CTD anymore then gauges until you find the offending one.If you use the default 777 that means just one gauge!Jan"Beatus Ille Procul Negotiis"

Thats interesting Jan, thanks for the reply :) But the strangeness of it is: For months & months I was flying the 777 without problems. Then one day....**SPLAT** these problems started. I swear Windows, FS9 & PCs have a low-level of AI.....and that now and then they conspire to have a bit of a laugh at our expense.http://www-psych.stanford.edu/~stork/haleye.gifIm afraid I cannot let you fly today Dave