hey everyone 

 

getting random CTD in the menus, pretty much done all the recomended fixes 

trying to capture one with app crash 

 

however they don't show up ????

 

any ideas 

thanks 

JHo

 

 

Do you have the Vista version of the uiautomationcore.dll in your main FSX folder?  This is considered a fix by many for the menu ctd's; however, I think you are close to running out of memory when you are trying to access the menus.  The uiautomationcore.dll is part of the Microsoft.net framework packages and fsx needs version 1.1 thru 4.5.  Dotnet makes the applications run in the way the developer programmed it and that includes management of memory for the app/addon.

 

Best regards,

Jim

Hey jim 

 

Thanks for the reply 

 

i do have the vista version of the uia 

its placed in the main folder with the fsx exe

i've even tried removing all of them and running it ( i put them back ofcourse )

i've tried everything i can think of 

 

and now when it does it ( very random ) 

it does not show any events listed in my app crash viewer 

 

anything else i can try 

i'm about ready to throw in the towel haha 

 

JHo

ok i did some digging in the event viewer 

seeing as how nothing shows up in the App crash 

 

only thing i could find were these two messages 

 

first one: event id 9013

The Desktop Window Manager was unable to start because composition was disabled by a running application

 

second one: event id 9010

A request to disable the Desktop Window Manager was made by process (Couatl Scripting Engine for FSX)

 

 

these have to have something to do with the CTD seeing as how they happened around when i was flying 

and there are several of them matching up to when it crashed 

 

any ideas 

Thanks guys 

JHo

FSX shuts down Desktop Windows Manager as fsx is not compatible with Windows Aero.  The 9013 event will appear every time you start FSX.  I get it too.

 

The 9010 is normal too except it should have indicated FSX instead.  The Couatl Scripting Engine is a security thing for DreamTeam and I think BluePrint products.  Maybe a product is not properly installed??  When you start up FSX, click on the menu and then click on Add-ons then Couatl powered products and then click on Restart Couatl. 

 

I doubt either event is connected with your FSX crash.  I suspect FSX is freezing up and then shows an error message that FSX has stopped responding.  This could be caused by a multitude of things.  High fsx settings is one.  A bad tweak is another.  Have you tried renaming your fsx.cfg to fsx.orig and then restarting fsx and letting the config rebuild.  This fixes a lot of things, especially a bad tweak or high settings.

 

I would also take a look at your system hardware drivers.  I use a freeware program called Driver Scanner.  It scans my computer for out-of-date drivers and then indicates what items are out-of-date.  You can have the program fix the problem automatically but it will require you purchase the program or you can take a look at the out-of-date driver and usually go to the website that has the updated driver and install it yourself.  In any case it will give you an indication as to whether you have out-of-date drivers or not.

 

If none of these suggestions work, then I would completely uninstall and reinstall FSX and make sure fsx is completely wiped out before reinstalling.  When FSX Deluxe is installed, make sure you run it at least one time so the FSX.cfg can be properly configured.  Then, if you have Acceleration, install that program and run it before installing any addons.

 

Best regards,

Jim