I have the crashes again :(  So I downloaded the "uiautomationcore.dll" again, and hope for the best.  Will let you know the results.

I just wonder what add on might have installed another version of "uiautomationcore.dll" over the fixed one I had installed ages ago?!?

Actually, the only thing I added recently was "SteveFX - DX10 Scenery Fixer" and now use the DX10 preview mode.  Maybe it had something to do with it

 

Update:

Nope, crashed again.  So it was not related to the "uiautomationcore.dll" this time.  I clicking on a panel to make it big, and it locked it up.  Must be with the aircraft I guess :(  Guess I need to head on over to their support site.

 

Update:

BTW, my banner shows PMDG, but it was NOT their product, just so you know

 

Bruce

I just wonder what add on might have installed another version of "uiautomationcore.dll" over the fixed one I had installed ages ago?!?

I split your post from the old one you posted to. As reported several times here on AVSIM, FSDT installed another version of uiautomationcore.dll over any you had installed ages ago. I discovered this as I do not believe in the uiautomationcore "fix" but constantly found the uiautomationcore.dll module in my main FSX folder. I did not put it there and FSX does not install it there so it had to be another software program. FSDT stated they inadvertently installed the uiautomationcore.dll whenever the Addon Manager or one of their products was installed. They had put it there to test it to see if it fixed any problems and forgot to remove it from the installation package. It has now been removed so, if you install the latest Addon Manager and the product packages (for instance, the KORD Airport installation program). So, if you downloaded KORD (for instance) and couple of years ago and you want to reinstall it, then you should download the one on their website instead of using the old package.

 

I don't see where you have ever reported a crash before. If you are having crashes, you should look at the AVSIM CTD Guide, located to the right of this forum under Hot Spots, for solutions. An AppCrashReport might be helpful. System specs in your profile would be great too.

 

It is extremely doubtful that DX10 Preview caused any of your problems.

 

Hope this helps,

 

Best regards,

 

You stated you clicked on a panel to make it big and FSX locked up. Was this panel on a second monitor? If so that will not work in full screen mode but in Windowed Mode it may work. I can replicate that crash on my second monitor 100% of the time.

Sorry Jim, I should have been more clear.  I was clicking on one of the VC clickspots to enlarge one of the instrument windows and that is where it locked up and restarted FSX.

I did update the Addon Manager for GSX, but it was the newest one from their site, so obviously, that wasn't it.

I never have reported crashes before because I either figure it out, or have accepted that sometimes FS crashes.  I know, I should be more dligent, but this time I am definately at a loss.

I seems like I have sooo much installed in FSX and just get tired of it working flawlessly for a long time, and then it suddenly doesn't :(

Anyways, I will take a more thorough look through the CTD forum again and see what I can find out and maybe start to post some of my crash specifics and system specs.

Thank for getting back to me promptly

 

Bruce

Make sure you have the Microsoft.net program used by the developer for the aircraft you are having issues with. Microsoft.net is not completely backward compatible so, if the developer installed Microsoft.net 2.0, the program needs to see Microsoft.net 2.0. Some of the developers, like Orbx, are upgrading their programs to be compatible with the latest versions of Microsoft.net. This is why the AVSIM CTD Guide tells you to make sure you have Versions 1.1 thru the latest installed and has tools for you to check this. It is important too that you download and run AppCrashView and see what the faulting module, if any, is displayed that might have caused your crash. The Windows Event Viewer provides details too but they are limited. The AppCrashView interprets the Microsoft error reports that are generated whenever you have a crash.

 

Whenever you have problems with graphics, like enlarging a Window, suspect your video card installation.

 

Best regards,

The fault seems to come down to the "QWBAE146.GAU" file.  I can only think of reinstalling the BAe.  I will go to the QW support and see what I can find out.  Unless you think I should post a new CTD report?!  Will that give any more news than what I have already decifered from it?

 

Bruce

Well, scratch that :(  FSX locked up again.  I will post a CTD report.