No.  Post #4 provided a solution.  I do not know anything about your computer.  Perhaps that fix relates somehow.  You can look at it and say, "oh yeah!  The parking brake switch!"

 

Sorry you were confused by the link.

 

Perhaps someone else can help if this does not provide a solution.

Hi Jim Thanks alot again, I had hoped the AppCrash View utility would have highlighted a consistent problem, I don't think post 4 really addresses my problem with my PMDG & FSX my problem always occurs when I try to make changes using my menu bar anyhow Jim many thanks for all the kind inputs and time you've devoted to my concerns, guess i'll have to live with this one.

 

Thank You very much

      Richard

I would submit a ticket to PMDG Support.  They have a FAQ section too that provides solutions to common questions.

 

Best regards,

Thanks Jim

thankfully with your help i've sorted the AREA 123 error message and got all my sceneries into the Sceneryconfig Editor, also sent a ticket to PMDG for some advice.

Looking at previous posts I see that most have had more success running the UIAutomation.dll 6.0  6001. 18000 Ihave the other vista 32 version so i'll pop that in my FSX folder and see what happens.

 

Thanks Jim so glad there's an expert on these things on here, to provide excellent support

Many Thanks again

Richard

 

 

I see that most have had more success running the UIAutomation.dll 6.0 6001. 18000

 

Hi Richard,

 

Glad to hear you got the Scenery.cfg fixed.  An annoying message for sure!  The consensus seems to be divided regarding the proper version of the uiautomationcore.dll.  I don't use it but did try both versions and thought I was getting better fps with the older version but think that was another placebo.  I no longer have the dll in my main fsx folder.  It is part of the Microsoft.net framework so that's why I try to make sure everyone has all the dotnet versions installed that are related to FSX. 

 

I slightly modified your topic subject as it was in all caps and, in the computer world, that's called shouting and people get all upset seeing it.  It also cleans up the forum a little...  B)

 

Thanks for your kind comments!  Truly appreciated.

 

Best regards,

Hi Jim

I tried the older version of the UIAutomationcore.dll tonight and it made no difference sadly, and still after a few hits on the menu bar my scenery crashed, PMDG support advised making any menu changes to leave the full windowed mode, but no change there either.

and sadly my white rectangeles of missing ground scenery have returned, so i think i'll dispense with the UIAutomationcore.dll and see what happens.

Jim do you think if i bought a new FSX with Accelerator it might flush alot of these problems away if it builds new files?

Anyway Jim thanks for your excellent support !!

 

Richard

 

 

Jim do you think if i bought a new FSX with Accelerator it might flush alot of these problems away if it builds new files?

 

No.  But completely uninstalling FSX and reinstalling FSX/Acceleration will probably fix the problem.  I use the following guide to uninstalling/reinstalling FSX except that I suggest running a freeware registry cleaner after uninstalling FSX http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx.  It is important that everything is uninstalled before trying to reinstall.  Just install FSX, run it at least once, then install Acceleration.  That's it.  No SP's or anything.  Make sure you right click the installation programs and select Run as Administrator.

 

Are you still getting the PMDG_737NGX.DLL 1.0.0.0 faulting module error?  If so, it really does sound like your installation has been corrupted. 

 

Best regards,

Hi Jim

back a while we discussed the automationcore dll. i gathered your not too enthused with that and to date  though its stopped my freezes i still get crashes if i attempt anything flamboyant like changing the weather using the menu bar, Jim is there another solution eliminating the use of the autommationcore.dll

 

many thanks

Richard

You made the following statement on January 29th:

 

 

 

tried the older version of the UIAutomationcore.dll tonight and it made no difference sadly, and still after a few hits on the menu bar my scenery crashed, PMDG support advised making any menu changes to leave the full windowed mode, but no change there either.
and sadly my white rectangeles of missing ground scenery have returned, so i think i'll dispense with the UIAutomationcore.dll and see what happens.

 

Now you state:

 

 

 

back a while we discussed the automationcore dll. i gathered your not too enthused with that and to date though its stopped my freezes i still get crashes if i attempt anything flamboyant like changing the weather using the menu bar

 

This is very confusing to me.  First it does not work, then it works but only partially.  I am not excited about the so-called uiautomationcore.dll "fix".  I really think it is a placebo.  I have never had the need to use it.  If I get a freeze, I track down the freeze and fix it and it's not the uiautomationcore.dll that fixed it.

 

If you deleted your Fsx.cfg and let fsx rebuild it and you still have crashes/freezes, that tells me that there is nothing wrong with your configuration of fsx.  There are no tweaks that are causing fsx to crash.  Tweaks cause many crashes.  Tweaks are not good.

 

I still have not seen an actual crash report using AppCrashView (as requested in Post#8 above).  The AppCrashView gives me more information about your installation of FSX.  For instance, you need to have Microsoft Visuals C++ 2005 w/SP1 through 2010 installed (PMDG uses the 2010 version).  None are backward compatible.  Microsoft Visuals are used by the developers to make sure you product is installed properly.  I also need to know if you have all of the required Microsoft.net (dotnet) applications.  For FSX you need versions 2.0 through the latest 4.5.  The AVSIM CTD Guide provides a link and provides information on how to make sure you have all of the required dotnet's installed.  These are used by the developers, in conjunction with Microsoft Visuals, to make sure your application runs properly as intended by the developer, including memory management.  Dotnet's, for the most part, are not backward compatible.  Microsoft still provides guidance for you to install all previous versions.  They are usually updated by Windows Update. 

 

I apologize for not going into more detail.  The AVSIM CTD Guide (which I wrote for AVSIM) provides all the details and procedures for troubleshooting and finding the solution to your problems.  The AppCrashView will normally show the faulting module and that gives you a clue as to what is causing your crash(es).  The AVSIM CTD Guide has some fixes for some faulting module crashes.  The guide also tells you to delete your Scenery and Facilities indexes as that has fixed many crashes.  I have been where you have been where I was not too familiar with computers and fsx so I know where you are coming from.  It would be nice if I could be sitting in front of your computer and looking for the problems but I cannot.  The next best thing is the AVSIM CTD Guide (a direct link to it is under Hot Spots on the right side of this forum).

 

Best regards,

Hi Jim

thanks again, i placed an AppCrash report on page 13 previously but i can do another if required.

Sorry if i was a little vague, I placed the 32 bit autommationcore.dll into my fsx folder, what I mean't was that although it prevented my FS freezes, my toolbar crashes continued when i try to change weather or gates etc.

Since a reinstall FSX and placing the highmemfix=1 into the graphics section of my FSX Config I haven't noticed so many missing scenery areas before i'd get a lot of white tiles of missing scenery enroute, now if i don't use the toolbar I can have a normal flight with no crashes, though I still find when i land at certain airports, on arrival many terminal buildings are absent.

anyway Jim thanks again for your patience and i'll heed your advice again and see if I can erradicate these problems

 

Many thanks

Richard