Win 7 64 bit + FSX = "Fatal error" & CTD / restart

Anonymous
2010-03-18T16:47:25+00:00

Hello,

I, like a lot of other people,  am getting this error message, and certain Fatal Errors followed by CTD's when in FSX ,to the point that I've almost all but given up on ever playing FSX again.

"this feature requires that {smartassembly} is available on this computer"

I've looked on every forum, including this one, but no constructive info that has helped me so far. I've tried reinstalling windows & FSX 5 times the last couple of days, tried the uiautomationcore.dll fix., shutting down various windows services on boot up, generally following the adivce in the other Win7 + FSX forums here.  Nothing works.

The CTD's occur in flight, but also after a startup at the gates where I leave the aircraft for a couple of hours, I will return to find FSX has restarted itself.

I run FSX on Win 7 64 bit, which, by looking through various forums, is giving people a lot of problems (CTD's) with FSX. It seems that this is a common problem, so I hope you can help fix this. Until then I (and a lot of other people) can't use their FSX

  • addons which we invested a lot of money in.

Please let me know, what further information you need, but pls don't tell me to reinstall Windows & FSX once more. I've done this 5 times over the last couple of days, this is not what is causing FSX to malfuntion.

Thanks in advance.

BR

Robert.

Windows for home | Previous Windows versions | Gaming

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2010-05-11T11:57:00+00:00

I found this information on another forum.

http://social.technet.microsoft.com/Forums/en-US/w7itproappcompat/thread/fb1808ff-92f0-478b-9826-f2ed6fbeae97

IT WORKED FOR ME! I just deleted the uiautomationcore.dll (after backing it up). Problem solved!! It's fantastic! Flew a whole flight from Changi to Frankfurt using the menu's heavily and there were no problems!!

![](http://i3.social.microsoft.com/Image.avatr?size=Small&user=gkair2&id=00000000-0000-0000-0000-000000000000)gkair2

 THE BOTTOM LINE IS THAT THE UIAUTOMATIONCORE.DLL FILE CAUSES OTHER DLL FILES TO MALFUNCTION!

Alright folks, I have the fix---after a whole year of fidgeting and spending $600 on every stinking version of windows out there-XP 32 bit. XP proffessional 64, vista HP32, vista HP 64, Win 7 32 & 64 RC, Win 7 32 enterprise and Win 7 64 bit professional (my primary FSX OS on which I did the succesful fix). As simple as it may sound this works. I tried replacing the Uiautomationcore.dll file and FSX would still crash albeit after a while. And if it wasn't that dll file then it would be some other file like ntdll. So I tried completely deleting the uiautomationcore.dll file from both the syswow64 and system 32 folders. Now I am playing FSX with graphics and traffic settings set to custom and turned all the way up while  I have aircraft, scenery and weather settings turned to ultra high and no crashes for two days!!!! I can click in and out of any menu such as the MAP or virtual flight path or change aircraft mid-flight or change weather mid-flight with no crashing. I have tried every which way to get FSX to crash and I just cannot get it to!

FSX really is awesome when it works.

HERE 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.dll

cacls C:\Windows\System32\uiautomationcore.dll /G username:F

takeown /f C:\Windows\Syswow64\uiautomationcore.dll

cacls C:\Windows\Syswow64\uiautomationcore.dll /G username:F

Now 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.)

If you have Nvidia cards download their latest driver also. Its got a huge performance increase. The only problem I have had by deleting the UIautomationcore.dll file is that if I exit FSX completely while in flight my windows desktop becomes dysfunctional and I have to restart. If I first end the flight and then exit FSX I have no problem. I have four different OS's on seperate partitions on my computer built specifically for FSX. There is no point in playing FSX on any 32 bit version of windows because you will get more out of FS 2004 than FSX on a 32 bit system.

Now, since I have 12 gigs of RAM, dual 9800GT's, intel core i7 920 running at stock (cuz MSI MB's suck for OC), and three 22" monitors-- instead of getting 10 FPS (on my 32 bit windows 7)I get 25 FPS on my 64 bit Windows 7 with two virtual cockpit windows on two monitors and all of my instruments on the 3rd monitor. BTW 6 GB (if you have tri-channel) or 8GB Ram (if you have dual channel) with a 64 bit OS is plenty-I just found my DDR3 RAM for dirt cheap at Microcenter a year ago. 4 GB is not enough as you will get OOM errors with settings even turned up halfway. No need to buy fancy graphics cards either because FSX is CPU intensive and doesn't really do well on the newer graphics cards. The 9800GT's are dirt cheap at like $70. Also definitely upgrade to the core i7.

Please get the word out to all of our fsx friends!!!

Was this answer helpful?

8 people found this answer helpful.
0 comments No comments

83 additional answers

Sort by: Newest
  1. Anonymous
    2014-05-30T19:16:51+00:00

    Difficult to tell for now, but could you first:

    • open the Windows event viewer (located in the Administration Tools)
    • in the event summary view in the center, open the Error tree,
    • search if there are events for Experience GeForce

    If you find events for Experience GeForce, double click them to open the details tab and see what it says there.

    Maybe another test to perform, place back the UIautomationcore.dll files in C:\Windows\System32 and C:\Windows\Syswow64 if you previously deleted them - But be carfull, there is one for 32 bits and another one for 64 bits, although they have the same name - , and retry to run Experience GeForce.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-05-30T17:35:17+00:00

    It is possible that by doing this Step takeown /f C:\Windows\System32\uiautomationcore.dll

    cacls C:\Windows\System32\uiautomationcore.dll /G username:F

    takeown /f C:\Windows\Syswow64\uiautomationcore.dll

    cacls C:\Windows\Syswow64\uiautomationcore.dll /G username:F

     I do NOT longer updates the video card driver? This is the message Experience GeForce encountered an error and must close 

    OS Windows 7 64 BT

    Graphic Card Nvidia 660 GTX 2 gb

    I5 3,5 ghz

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-05-28T17:31:52+00:00

    I just take some time to write this memo, because I read dangerous things here.

    Frankly speaking, you should not delete any UIautomationcore.dll file in Windows system directories (C:\Windows\System32\uiautomationcore.dll and C:\Windows\Syswow64\uiautomationcore.dll), these files are necessary for the system to work, on Win 8, you are going to hang the metro interface and probably break other applications on your PC :(

    But you need to have a correct version of uiautomationcore.dll in your FSX root directory.

    See instead this thread, on how to get a "working with FSX version" of uiautomationcore.dll:

    http://answers.microsoft.com/en-us/windows/forum/windows8_1-gaming/fsx-with-acceleration-pack-crashes-with-windows-81/05b9632a-6c75-4b5d-abad-e0384209a0e4

    Remember that FSX is a 32 bits application, it will use only a 32 bits version of uiautomationcore.dll, so don't mess up any 64 bits version of this file, even on a 64 bits system.

    When you add the DLL to your FSX root directory, better reboot your PC to be sure to clean up the Windows DLL cache. DLL are cached in Windows, this is why an application loads faster the second time you run it.

    But in the present case, FSX might still load the c:\windows\system32 version of the file, instead of the one you just copied into FSX root directory!

    Remember that you can check the reason of an app crash, by opening the event viewer (in Windows administrative Tools) there is an error tree where you should see an FSX crash line, if you experience a crash. And then, see in the details tab, the reason of the crash.

    Another reminder, on how a Windows application loads its DLLs files, from MSDN article:

    http://msdn.microsoft.com/en-us/library/windows/desktop/ms682586(v=vs.85).aspx

    and an extract of this, explaining the DLL search order for a desktop app:

    "

    1. The directory from which the application loaded.
    2. The system directory. Use the  **GetSystemDirectory** function to get the path of this directory.
    3. The 16-bit system directory. There is no function that obtains the path of this directory, but it is searched.
    4. The Windows directory. Use the  **GetWindowsDirectory** function to get the path of this directory.
    5. The current directory.
    6. The directories that are listed in the PATH environment variable. Note that this does not include the per-application path specified by the App Paths registry key. The App Paths key is not used when computing the DLL search path.

    "

    So putting the right UIautomationcore.dll in FSX root directory will make it loaded instead of the system one. This is a Windows mechanism.

    This stays an advice of course, but for FSX to work, I greatly advise not delete any Windows system DLLs, especially 64 bits ones.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-05-27T16:43:42+00:00

    I found this information on another forum.

    http://social.technet.microsoft.com/Forums/en-US/w7itproappcompat/thread/fb1808ff-92f0-478b-9826-f2ed6fbeae97

    IT WORKED FOR ME! I just deleted the uiautomationcore.dll (after backing it up). Problem solved!! It's fantastic! Flew a whole flight from Changi to Frankfurt using the menu's heavily and there were no problems!!

    ![](http://i3.social.microsoft.com/Image.avatr?size=Small&user=gkair2&id=00000000-0000-0000-0000-000000000000)gkair2

     THE BOTTOM LINE IS THAT THE UIAUTOMATIONCORE.DLL FILE CAUSES OTHER DLL FILES TO MALFUNCTION!

    Alright folks, I have the fix---after a whole year of fidgeting and spending $600 on every stinking version of windows out there-XP 32 bit. XP proffessional 64, vista HP32, vista HP 64, Win 7 32 & 64 RC, Win 7 32 enterprise and Win 7 64 bit professional (my primary FSX OS on which I did the succesful fix). As simple as it may sound this works. I tried replacing the Uiautomationcore.dll file and FSX would still crash albeit after a while. And if it wasn't that dll file then it would be some other file like ntdll. So I tried completely deleting the uiautomationcore.dll file from both the syswow64 and system 32 folders. Now I am playing FSX with graphics and traffic settings set to custom and turned all the way up while  I have aircraft, scenery and weather settings turned to ultra high and no crashes for two days!!!! I can click in and out of any menu such as the MAP or virtual flight path or change aircraft mid-flight or change weather mid-flight with no crashing. I have tried every which way to get FSX to crash and I just cannot get it to!

    FSX really is awesome when it works.

    HERE 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.dll

    cacls C:\Windows\System32\uiautomationcore.dll /G username:F

    takeown /f C:\Windows\Syswow64\uiautomationcore.dll

    cacls C:\Windows\Syswow64\uiautomationcore.dll /G username:F

    Now 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.)

    If you have Nvidia cards download their latest driver also. Its got a huge performance increase. The only problem I have had by deleting the UIautomationcore.dll file is that if I exit FSX completely while in flight my windows desktop becomes dysfunctional and I have to restart. If I first end the flight and then exit FSX I have no problem. I have four different OS's on seperate partitions on my computer built specifically for FSX. There is no point in playing FSX on any 32 bit version of windows because you will get more out of FS 2004 than FSX on a 32 bit system.

    Now, since I have 12 gigs of RAM, dual 9800GT's, intel core i7 920 running at stock (cuz MSI MB's suck for OC), and three 22" monitors-- instead of getting 10 FPS (on my 32 bit windows 7)I get 25 FPS on my 64 bit Windows 7 with two virtual cockpit windows on two monitors and all of my instruments on the 3rd monitor. BTW 6 GB (if you have tri-channel) or 8GB Ram (if you have dual channel) with a 64 bit OS is plenty-I just found my DDR3 RAM for dirt cheap at Microcenter a year ago. 4 GB is not enough as you will get OOM errors with settings even turned up halfway. No need to buy fancy graphics cards either because FSX is CPU intensive and doesn't really do well on the newer graphics cards. The 9800GT's are dirt cheap at like $70. Also definitely upgrade to the core i7.

    Please get the word out to all of our fsx friends!!!

    Hi gkair2 I think you may be my salvation. Let's see if I understand:

    1.  I open the FSX folder and delete a file UIautomationcore.dll (right mouse button and delete)
    2. Going into folders name syswow64 and system32 and delete UIautomationcore.dll
    3. 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.dll

    cacls C:\Windows\System32\uiautomationcore.dll /G username:F

    takeown /f C:\Windows\Syswow64\uiautomationcore.dll

    cacls C:\Windows\Syswow64\uiautomationcore.dll /G username:F

    Question: Also restart the PC???? 

    and the question most important:

    The uiautomationcore.dll file must not be present in any folder on your PC in the future?

    Thanks at all

    Was this answer helpful?

    0 comments No comments