I also make sure to keep a backup of the right version of UIAutomationCore.dll (6.0.5840.16386) in a safe place, so that I can easily replace it if it gets overwritten. 

 

I apologize if in trying to help, it was perceived that I was sharing "bad information".  Sometimes, someone's "bad information" is someone else's "solution".  In my case, the information regarding UIAutomationCore.dll has kept my flying "crash free" since I installed it in 2010.

Jim,

 

Are you saying it is OK for us to delete the UIAutomationCore.dll in the main FSX folder?  I'm TOTALLY fine with that if deleting it won't break something else.

Thanks, B247NG!

I've been using the "right version" 6.0.5840.16386 with no problems for several years!

If you are not getting any menu crashes, I would at least move it to a temporary folder.  In Windows 8 the Uiautomationcore.dll in the main fsx folder is not compatible so it must be removed. 

 

A lot of people don't get crashes but it's not because of the Uiautomationcore.dll in their main fsx folder.  Personally I think it's a memory related issue as the Uiautomationcore.dll is used by fsx to manage memory for the applications.  It should do you no harm to keep it in your folder but I can assure you that it does not fix anything but menu crashes (and I question that!).  Tonight I just had another ntdll.dll crash and, when I looked at my crash report, there was the Uiautomationcore.dll in my main fsx folder.  I don't know which developer is throwing this useless dll into my main fsx folder but I do suspect PMDG.  I have deleted it.  I will now try to run the flight again and see if the ntdll.dll crash returns.

 

Best regards,

Jim

It seems to me that AS2012 goes through a boot up process every time you start it, which includes validating your copy and connecting to the weather servers. You know more than me, but I don't see how it can possibly do this if it's not running. Also, the reason I always enter a flight plan in AS2012, is to get the winds at each waypoint, which I enter into the PMDG FMC prior to each flight. Additionally, I always print the AS2012 flight log so I can keep track of the ATA and fuel remaining at each fix, as is done in the real world. This maybe overkill, but old habits are hard to break. Thanks!

Pete, I evidently was wrong about AS2012 settings being used even if you run the default weather program.  Tonight I tried a flight using AS2012 and there was nasty weather.  I got a crash.  So restarted and just used the default weather program.  This time no crash but the weather was sunny and partly cloudy.  I started up AS2012 while the sim was running and suddenly there was rain and nasty weather.  So, unfortunately you do have to run AS2012 every time you start up FSX if you want real weather.  Apologize for the confusion but I can swear in the last version of AS2012, they had a statement on the front page of AS2012 (the startup window) that stated the default weather also used AS2012. 

 

Best regards,

Jim

^{Thanks, Jim.  Since I'm in Win 7 (and plan on staying there a while), I hopefully will not have to deal with this soon!}

After all is said and done, this is one of those things that some us just may have to deal with for now, I guess.

I just did a flight that was over 6 hours, and all went well. I was online most of the time and had Vattastic running and AS2012 in the tray. I also had "What Is Hang" going just in case I got a freeze, so maybe it would tell me what the problem was. From what I've read, physical RAM may not be the problem. If you're using complex planes like PMDG products, you need a 64 bit OS, which allows you more Virtual Address Space (VAS).   All I can say is that VATSIM and freezes don't mix. Let's hope for Flight Simulator XI.

 

 

have you checked if that was the right version of Uiautomationcore.dll? The right version is 6.0.5840.16386(higher version would probably be fine, but earlier not).

 

Hi Zeljko,

 

The version that was in there was 6.0.6001.18000 dated 1/20/2008.  In any case, I ran the exact same setup without the Uiautomationcore.dll in the fsx folder and was able to complete my flight to Chicago.  I decided this morning to put the Uiautomationcore.dll back into my FSX folder to see if I could replicate another ntdll.dll crash.  No joy.  I was able to make a successful flight from Washington to Chicago.  So, not sure why I got the ntdll.dll module crash and it went away when I removed the Uiautomationcore.dll but removing it has successfully fixed two CTD's.  Although I did not get a ctd with the Uiautomationcore.dll in the fsx folder I'm still removing it to a temporary location.  Thanks for your help.

 

Best regards,

Jim

Hi Zeljko,

 

The version that was in there was 6.0.6001.18000 dated 1/20/2008.  In any case, I ran the exact same setup without the Uiautomationcore.dll in the fsx folder and was able to complete my flight to Chicago.  I decided this morning to put the Uiautomationcore.dll back into my FSX folder to see if I could replicate another ntdll.dll crash.  No joy.  I was able to make a successful flight from Washington to Chicago.  So, not sure why I got the ntdll.dll module crash and it went away when I removed the Uiautomationcore.dll but removing it has successfully fixed two CTD's.  Although I did not get a ctd with the Uiautomationcore.dll in the fsx folder I'm still removing it to a temporary location.  Thanks for your help.

 

Best regards,

Jim

 

It seems that only 6.0.5840.16386 is the right version. I have checked, and i had 6.0.6001.18000 when Freezing, hanging, stutters and CTD happened to me. I thought i put that version by mistake, but if you are right and 777 installer puts that  version in FSX, it could be a reason for that problem 777 users have - freezing mid flight. 

 

With 6.0.5840.16386 FSX menu seems to be much responsive, and that feels in flight too - better smoothness. To see any effects, PC restart is required after puting or replacing Uiautomationcore.dll in FSX main folder(at least on my PC). 

 

I think this should be tested. 

 

I don't want to reinstall 777 just to test if installer puts Uiautomationcore.dll in FSX, can somebody else with 777 check Uiautomationcore.dll version too? Or better, can we have a confirmation by PMDG?

 

I have now the right version, and FSX is smooth again.

 

Thanks Jim. 

It seems that only 6.0.5840.16386 is the right version. I have checked, and i had 6.0.6001.18000 when Freezing, hanging, stutters and CTD happened to me. I thought i put that version by mistake, but if you are right and 777 installer puts that  version in FSX, it could be a reason for that problem 777 users have - freezing mid flight. 

 

With 6.0.5840.16386 FSX menu seems to be much responsive, and that feels in flight too - better smoothness. To see any effects, PC restart is required after puting or replacing Uiautomationcore.dll in FSX main folder(at least on my PC). 

 

I think this should be tested. 

 

I don't want to reinstall 777 just to test if installer puts Uiautomationcore.dll in FSX, can somebody else with 777 check Uiautomationcore.dll version too? Or better, can we have a confirmation by PMDG?

 

I have now the right version, and FSX is smooth again.

 

Thanks Jim. 

You are exactly correct Zeljko!  I have never placed the Uiautomationcore.dll into my main fsx folder so some software is doing it.  A month or two ago I found it in my main fsx folder and removed it immediately (and it fixed my BEX/StackHash crashes).  When I got the ntdll.dll crash yesterday I looked in my main FSX folder and saw it there again!  I know it was not installed with FSX/Acceleration so I have narrowed it down to the PMDG installer.  That was the most recent program installed for FSX and I know the dll was not in there earlier.  In their Introduction Manual, Page 15 they recommend a replacement for the Uiautomationcore.dll and have a link to download it.  I just downloaded it and it is the version you and I had in our main FSX folders - 6.0.6001.18000.  Perhaps they decided to install it with their installer as many PMDG users to not read the manual.  In any case, I'm removing my copy of the Uiautomationcore.dll unless I get a crash or freeze.  If I have a freeze or ctd, I'll install the version you are using and see it that fixes the problem.

 

I just want to make sure everyone realizes that the Uiautomationcore.dll in the main fsx folder is only for those who are running Windows 7, 64 bit.  It is not compatible with Windows 8 or the 32 bit version of Windows 7 and that will create crashes too.

 

Best regards,

Jim

I did the same thing after i wrotte previous post, downloaded version from introduction manual and it was 6.0.6001.18000  :lol: 

 

Paul just confirmed freezing, hanging, CTD's with 6.0.6001.18000 http://forum.avsim.net/topic/421372-nvidia-32723-drivers/page-3

 

So, that must be explanation. Now i understand why you insist with removing Uiautomationcore.dll. You probably have a bad experience with wrong version. If you ever have time, just try the right one, it may improve FSX responsivity and smnootness as well, without side effects.

 

I'll try to run installer later and see what happens. 

 

 

You probably have a bad experience with wrong version.

 

No, it only fixes repeated hits with the fsx menu.  I think Word Not Allowed said it had to be at least 20 hits.  I did not have the Uiautomationcore.dll in my main fsx folder and tried to replicate the menu crash but no joy.  If you look in this CTD forum you will see in the crash reports that individuals had the Uiautomationcore.dll in their main fsx folder but still got a CTD and many were long before the PMDG737 and 777.  But it is still possible the people did not have the right version in their fsx folder.  I know some replaced the system Uiautomationcore.dll but that is correctable with the sfc \scannow program.  When individuals get crashes and the recommendation is to place the certain version of the Uiautomationcore.dll in the main fsx folder and the individual does and the individual reports back he has no more crashes (breathing), I think it is a placebo as anytime you shutdown FSX and/or your computer system and restart, that alone will fix a lot of issues, especially with memory.

 

I wish there was a magic bullet like the Uiautomationcore.dll but don't think we'll ever find one for fsx.

 

Thanks for your help Zeljko!

 

Best regards,

Jim

Jim, don't worry, i'm trying to stay objective. I didn't say that Uiautomationcore.dll fixes everything. Just that I'm pretty sure i had some stuttering with wrong version, but now everything is realy smooth. This makes sense, becouse with wrong version we get hanging and freezing, so probably this can cause some stuttering too.

 

I can replicate menu crash without Uiautomationcore.dll every time. If i remove Uiautomationcore.dll, load the flight and start to play with menu, FSX will freeze every time. I don't know how many hits i need, but more then 10 for sure.

 

Thank you Jim, you have probably discovered reason for 777 freezing, hanging and CTD's! 

 

 

Thank you Jim, you have probably discovered reason for 777 freezing, hanging and CTD's!

 

I hope it fixes many of the issues here. 

 

That's amazing you were able to replicate the menu crashes.  Now I will get a freeze or maybe even a crash if I Alt-Tab or go to the Task Manager for something and then try to get back into FSX.  But hitting a blank spot on the screen and then the menu several times gives me no joy.  But I am starting to appreciate the need for the dll in the main fsx folder.

 

Best regards,

Jim

I can confirm that more recent versions like 6.0.6001.XXXXX are a major headache.  Version 6.0.5840.16386 of the UIAutomationCore.dll appears to be the "sweet spot" if it is needed.  I can also confirm that FSX (on my system) appears to run fine without the UIAutomationCore.dll.

 

So the options seem to be: avoid it if you can, but if you can't, use only 6.0.5840.16386.

 

Best,

Carlyle

I have just checked PMDG and simforums has both wrong 6.0.6001.18000 version, Word Not Allowed has the right version. That can be a explanation why so much people has problem with Uiautomationcore.dll. I hope they(PMDG and simforums) will change this. 

 

Carlyle, i think Uiautomationcore.dll is actually needed in Windows 7, but right version. You can avoid it, if you don't use FSX menu to often. But no side effects from right version, i can see some improvements in overall fsx responsiveness BTW

In the AVSIM Software and Hardware Guide, PaulJ is recommending the correct version.  Looks like a lot of people are putting the wrong version in the main FSX directory. 

 

Best regards,

Jim

I just want to make it clear here that the PMDG installers does not install any versions of the Uiautomationcore.dll.  PMDG is definitely not responsible for installing any version of the Uiautomationcore.dll.  Some other addon developer is installing it though.

 

Best regards,

Jim