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

Question

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.

Answer 1

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!!

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!!!

Answer 2

It's to do with Windows .NET Framework i believe.

Try updating or re-installing the .NET Framework on your computer and see if that fixes the issue.

---

MCP. MCDST. LVL 80

Answer 3

Hi Hordie,

.NET Framework 3.5 with servicepack 1 which is a requirement, comes with Windows 7 64bit. Never the less I tried reinstalling both 3.5 +the servicepack, but Win 7 won't let me. Also checked in the control panel and verified that .NET Framework 3.5.1 is installed.

Answer 4

hmm ,, thats the only thing I could find anywhere on that issue..

i would try sfc /scannow and reinstall the game if you have not done so already.

---

MCP. MCDST. LVL 80

Answer 5

I am having the same issue as Robert, although I am using Windows 7, 32-bit.

From reading a lot about this problem over the past few weeks it seems there are an ENORMOUS number of FSX users who are having the exact same problem. After the game being active for some time, whenever any of the menu's are touched, a fatal error occurs and the program crashes to the desktop.

Robert is correct, it is NOT an FSX installation problem, it is NOT a OS installation problem, and it is NOT an add-on problem. I have tried all the compatability modes as well, as well as all the general advice from forum users. I have tried running the software without being connected to the internet, with all startup programs stopped... the problem remains.

There seems to be no movement from Microsoft on this. This issue is killing FSX.

John