Thanks Scarlett, now do one for OOM messages, and how to try and resolve them Great guide, well done.

I have matches with the Terrain DLL and it's respective code, I've tried turning down sliders and it didn't work, clearly there is a scenery issue, what can I do about that? I have no payware addon sceneries, do I just reinstall [FSX] ?

Hi Jeremy,

 

Now we are in another thread posting about your crashes? If lowering your sliders does not work, then your computer is not capable of running fsx and will need to be repaired. There is no magic bullet to most of these types of crashes. Wish there were and we could provide a popup solution as soon as you mention the error. Reinstalling FSX is a possibility since lowering your settings did not work. If that does not fix your problem(s) (you have many), then you're going to have to buy a better computer. Look in the FSX hardware forum for suggestions on upgrading your computer.

 

Best regards,

Jim

Thanks, I'll get right on that! I was just surprised that it suddenly stopped after I installed the RAM, but it's just a terrain.dll error so we'll see this.

Thanks Scarlett, now do one for OOM messages, and how to try and resolve them Great guide, well done.

 

OOM messages are not that hard to figure out what is going wrong. You either have your settings set way too high, or your system just can't handle what you are putting it through.

First of all, a happy New Year to all of you. :smile:

 

Lets see if we can unscramble the uiautomationcore.dll stuff a bit. My initiial post regarding Scarlett's description in the guide still stands. In my humble eyes, the meaning of that point is inverted in her guide. It's a problem solver, not something which causes CTDs. Perhaps she can shed some light on this.

 

My impression is that the view is shifted. The OS version of that dll isn't problem. (Old) FSX is. So we are looking for a fix for FSX alone.

 

It seems Microsoft Technet forums have come up with a solution - http://social.techne...b7-f12e759d5e7c as recent as 23 Dec. It involves renaming or deleting the Windows 7 uiautomationcore.dll from the system folders after taking ownership.

Thanks for posting that one, Jim.

 

As explained before, the uiautomationcore.dll in the system's folders is perfectly normal and 'welcome' if you like. Win7 and Win8 install it and there are programs around which rely on it being a proper version. The one from the OS.

 

What happens in the FSX crash case is that FSX picks up that global file and, for reasons unknown, tends to crash on menus or 2D panels after a while. So I would step far far away from recommending to alter files and user rights in the system folders of the OS. Instead, if a user receives the mentioned crashes, it's advised to just drop that Vista uiautomationcore.dll in the FSX folder. FSX only fix.

 

So there's no need to mess up the ownership structure of the OS folders or to delete a file which came with it and may indeed be needed for other programs. If the fix doesn't work, just delete the dll in the FSX folder again. No harm done, no OS globally influenced in any way.

 

 

On a side note. The full quote from bobrbend nearly killed me. ^_^ Yikes!

Cool IP,

 

It lies simply when I stated "Look at your even log". Most uiautomationcore.dll errors that I see come from C/Program FilesX86/Microsoft Games/Flight Simulator X/ Uiautomationcore.dll as the path of the faulty module. Most users I see put that file in their FSX directory as soon as they get their first fatal error. I am on the same page as Jim, only because I simply cannot re-produce the menu crash in Windows 7. Last night, I dropped the file in my FSX folder, and at the end of my flight, my FSX got a crash from uiautomationcore.dll. (Path leading to my FSX folder module).

Adding the CORRECT version of Vista 32 uiautomationcore.dll will IMPROVE the stability of FSX when running under Windows 7 (and windows 8 ?), but it does not 100% fix the issue, and eventually, after a long flight and lots of menus accesses, you will inevitably get a crash due to uiautomationcore.dll

 

The IRONIC thing is, that FSX does not "NEED" uiautomationcore.dll !!

When FSX was first released, and ran on XP, with earlier version of .net, those system did not even have a uiautomationcore.dll.

It was only with later versions of .net that uiautomationcore.dll was installed on those early XP computers, and FSX loaded uiautomationcore.dll as required by .net.

 

If you completely REMOVE uiautomationcore.dll from your computer, FSX will run fine, and not crash with uiautomationcore.dll error.

 

The functions of uiautomationcore.dll are interesting (if not outright SCARY) if you are paranoid about trojans and virii etc

 

While some more recent application make use of uiautomationcore.dll, most don't, and it is highly unlikely that these sort of applications would be needed to run on your PC, at the same time as FSX.

 

So one 'work around' would be to have some utility that "HID" uiautomationcore.dll from FSX. Numerous way that could be done....

 

BTW I have actually "REMOVED" uiautomationcore.dll from my W7 FSX server, and FSX runs fine, and never crashed with a uiautomationcore.dll error ... and so far, I have yet to find any application that I would run with FSX, that has suffered from not finding uiautomationcore.dll.

 

Food for thought !

Using the default Win7 uiautomationcore.dll file absolutely WILL cause a crash - you can test it yourself. Load FSX without it and just bring up the right click menu a bunch of times while sitting on the runway in the sim. After 25-30 clicks you should get the grayed out screen and the sim crashes. Put the Vista version back in and this doesn't happen (or if it does it's a heck of a lot more clicks to do it). I consider this an essential thing for FSX under Win7 and highly disagree with the OPs assessment of it - I fix customer crash issues with it every single day.

Tabs,

 

The menu crashes you speak of are not every system. They are system specific. With my setup, and Jim's setup, I have tested and right clicked, accessed the menu over 40 times, without any crashes. Because it's system specific, when users are having uiautomationcore.dll crashes, I have to rule on the fact based on their even log that the uiautomationcore.dll is causing the problem. More pre-cautionary, most of the time they experience no menu crashes when I tell them to remove it.

I concur with Ryan's statement and my guess would be that a lot of devs may report the same as he does. Imagine their view on the user systems with getting plenty of emails or tickets a day. That Vista file helps the Win7 and, now, Win8 folks with FSX. However, Geoff may have a point when it comes to the pure FSX operation and the missing 'need' for that file in general.

 

I recall others, using more programs on their rigs, and e.g. stating that some office or media editing soft requires a proper version though. The one from Win7 and Win8. So to hide that file from FSX is ok, to delete is.. up to the user. Can be risky. FSX only and one may indeed be fine. Nice input.

 

Scarlett, just because we all differ on the statement and status of that part from your guide, perhaps it's helpful to somehow mark it as disputed. Sorry, didn't find another word for it.

 

My first and often only recommendation when someone really gets menu crashes or ones on 2D panels is to try the Vista file. And, so far, it always fixed the problem. If one would accidentally pick the wrong one, this may cause trouble though. Geoff points that out.

 

Maybe we can even link to the correct file for Win7 x64 users in this thread.

 

UIAUTOMATIONCORE.DLL-Most commonly paired with Exception Code 0x0000005

 

Take a look at your error log. Does the log point the DLL location to your main FSX folder? Most commonly yes, this means you have installed and dropped the vista version of "Uitautomationcore" in your main FSX folder. This is causing FSX to crash.

 

This is 100% false.

As Ryan said, the vista version will fix the ctd while the win 7 version is the problem.

I have verified this many times on my own system. An added step for myself was having to register the vista version through a command prompt.

Haven't had a crash from menu related operations since.

 

 

Sent from my iPhone...typing errors imminent

I am going to leave this dispute with this statement.

 

My best judgement would be that the uiautomationcore.dll vista version does very well fix menu crashes for users who are suffering from these crashes. It may indeed provide a very helpful solution for customers, and can be a great tool. But I will also guess that this vista DLL also causes crashes. Most likely very helpful for users on one end, but can crash on occasion. Just like a drug with side affects. I really have no other advice to give a user when they experience a uiautomationcore.dll crash, and the event log points it to the DLL in their FSX folder than to remove the dll that caused the crash. Again, these 'menu crashes' are system specific, so it's likely this user won't need this DLL in the FSX folder in the first place.

If you set your FSX.exe compatibility level to VISTA SP2 the UIAutomation.dll will go away if you are running WIN 7-8. I can prove this by removing the compatibility level which causes the error to resurface. Not sure why people are still fighting this one. Cheers jja

 

PS if you run the WIN 7-8 compatibility troubleshooter on FSX.exe it will set the VISTA SP2 for you.

Good statement, Scarlett. Well, lets hope that most users start with a clean FSX, so there's no uiautomationcore.dll in the FSX folder. If they get menu crashes, they should try the Vista file fix. If they still get crashes, something else may be broken (too).

 

They should also mind the correct version of the file and shouldn't download 'just another' dll. By the way, downloading dlls from unknown sources may cause other risks to develop. ^_^

 

Oh, jj brought up another point. I ran FSX a long time with some compatibility mode and it later caused some trouble with my Feelthere addons. Then I ran it normal, as Win7 decides (no extra mode), and didn't receive a downside but all addons worked.

 

I guess this compatibility setting indeed is another open point.