hi guys, i was flying my PMDG 747 to cape town, and so i decided to speed up time, and when i thought it was time to bring it back to normal speed, i accidently clicked slowest, then it had a fatal error. as everyone who flies long haul flights, you can understand how upset i was by putting 7 hours of flying time down the drain. this also happens to me when i click the drop down menu by clicking the right mouse button, and also happens to me when i go online and whoevers hosting has an add-on a/c, its also happens when i try to playback fsrecorder with add-on a/c. any help??cheersP.S im running win7(64bit)

Tried rebuilding your fsx.cfg file yet?

Hi,Not sure if your using any FSX Tweaks, if so that may be your problem. I've since removed all system tweaks except Highmemfix and bufferpools and I've run four 8+ hour flights (real time) with no CTD, freezes and/or fatal errors.I would delete your fsx.cfg file and let fsx rebuild it, run FSX and see if you get the fatal error again. If the error is gone, your probably in the same boat I was in, too many tweaks that FSX just didn't like.

hi guys, i was flying my PMDG 747 to cape town, and so i decided to speed up time, and when i thought it was time to bring it back to normal speed, i accidently clicked slowest, then it had a fatal error. as everyone who flies long haul flights, you can understand how upset i was by putting 7 hours of flying time down the drain. this also happens to me when i click the drop down menu by clicking the right mouse button, and also happens to me when i go online and whoevers hosting has an add-on a/c, its also happens when i try to playback fsrecorder with add-on a/c. any help??cheersP.S im running win7(64bit)

hi .i think u shd scroll these forums or google "uiautomationcore.dll" , i had similar issue , downloaded vista uiautomationcore.dll to my fsx directory (not default directory) and no more fatal errors on clicking fsx menu .assuming u have a quad core processor>>set affinitymask=12 in jobscheduler if your running fsx sp1else if u have sp2 or acceleration no need for affinity mask add usepools=0 and highmemfix=1 to your fsx config

hi .i think u shd scroll these forums or google "uiautomationcore.dll" , i had similar issue , downloaded vista uiautomationcore.dll to my fsx directory (not default directory) and no more fatal errors on clicking fsx menu .assuming u have a quad core processor>>set affinitymask=12 in jobscheduler if your running fsx sp1else if u have sp2 or acceleration no need for affinity mask add usepools=0 and highmemfix=1 to your fsx config

Does this fix a bluescreen or ctd?jja

yes this fixes fsx freezes when clicking menu and ctd's it works for me ....but cant assure until you try.....might depend on diff OS/Hardware .Try your Luck !!

yes this fixes fsx freezes when clicking menu and ctd's it works for me ....but cant assure until you try.....might depend on diff OS/Hardware .Try your Luck !!

This also worked for me about 2 years ago and still no problems with ctd,fatal errors or freezes...lou

This also worked for me about 2 years ago and still no problems with ctd,fatal errors or freezes...lou

I have Vista 64 on my laptop and am trying that version of the uiautomationcore.dll.So far so good!jja

so do i just put it in my FSX folder?

Hi,Not sure if your using any FSX Tweaks, if so that may be your problem. I've since removed all system tweaks except Highmemfix and bufferpools and I've run four 8+ hour flights (real time) with no CTD, freezes and/or fatal errors.I would delete your fsx.cfg file and let fsx rebuild it, run FSX and see if you get the fatal error again. If the error is gone, your probably in the same boat I was in, too many tweaks that FSX just didn't like.

this has happened ever since i got it, and i dont use any tweaks

put it in your fsx folder .....chk and run flightsim ....should work and if it doesnt try thisHERE IS THE FIX: You may have to take ownership of the files if windows stops you from deleting the file. Open CMD prompt and right click to run as administrator and then type in exactly as below substituting your windows login username where it says username:takeown /f C:\Windows\System32\uiautomationcore.dllcacls C:\Windows\System32\uiautomationcore.dll /G username:Ftakeown /f C:\Windows\Syswow64\uiautomationcore.dllcacls C:\Windows\Syswow64\uiautomationcore.dll /G username:FNow you can just navigate to your syswow64 and system32 folders in windows explorer and after backing up the UIautomationcore.dll files just delete them from your computer. (Remember to delete the Uiatomationcore.dll file in ure FSX folder also if you installed it as the fix in other posts.)posted by gkair2 on microsoft technet

Yes, you would put the replacement uiautomationcore.dll in the main FSX folder.I can confirm that rebuilding my FSX.cfg and adding the AffinityMask tweak has cured years' worth of fatal errors for me. I get the occasional error but it's hardware-related and not sim-related.As for UsePools=0 and HIGHMEMFIX=1, I found that UsePools=0 gives me more pausing and very frequent "blurries." I have heard very good things about HIGHMEMFIX=1 and will give it a try.Good Luck!

will it sound strange if i say (unless im not looking in the right folder) that i in fact dont have a uiautomationcore.dll file in my FSX main folder?

Hi,There is a much easier way to take ownership and delete these files.============================================Right Mouse Click on the file and select propertiesGo to securitySelect your group or user namePress editSelect your group or user nameNow give yourself full controlPress apply and OK============================================Side effects-------------------There is only one reported side effect with this solution:"If you exit FSX completely while in flight your windows desktop may become dysfunctional and you will have to restart your computer. If you first end your flight and then exit FSX you should have no problem." I have not seen this problem, but don't be surprised if it happens to you.Personally I do not like deleting Windows System files, In this case I would just rename them with a bak extension.Link to UIAutomationCore.dll: http://www.mediafire.com/?mik2mlqdz1wNOTE: You will not have this UIAutomationCore.dll file in your FSX directory unless you put it there, so don't worry if you do not see it.

put it in your fsx folder .....chk and run flightsim ....should work and if it doesnt try thisHERE IS THE FIX: You may have to take ownership of the files if windows stops you from deleting the file. Open CMD prompt and right click to run as administrator and then type in exactly as below substituting your windows login username where it says username:takeown /f C:\Windows\System32\uiautomationcore.dllcacls C:\Windows\System32\uiautomationcore.dll /G username:Ftakeown /f C:\Windows\Syswow64\uiautomationcore.dllcacls C:\Windows\Syswow64\uiautomationcore.dll /G username:FNow you can just navigate to your syswow64 and system32 folders in windows explorer and after backing up the UIautomationcore.dll files just delete them from your computer. (Remember to delete the Uiatomationcore.dll file in ure FSX folder also if you installed it as the fix in other posts.)posted by gkair2 on microsoft technet

will it sound strange if i say (unless im not looking in the right folder) that i in fact dont have a uiautomationcore.dll file in my FSX main folder?

I didn't have one either. It's ok if it's a new file. Just make sure that you are placing the new version into the correct folder. As long as it's in there, the problem will be easier to solve, that is, if putting it in there doesn't already remedy it.