Well a few weeks back, there had been a thread going on here about people having lock ups and CTD's with FSX on giving a message that a fatal error had occured. I could not find the old thread, so I apologize if I'm making a new one when I'm just blind to the old one. Now last I saw of the topic, there were no real solutions, but a few suggestions had been given. Since then I have tried re-installing, avoiding additional addons such as other payware aircraft and FSCrew2. For a while it seemed to have made the difference, but low and behold after about 5 successful flights in, I get the error. Now the real frustrating part has been that FSX never provides any kind of error report, or anything that was even pointing me towards what was causing the problem. I've been able to get over that hill by using the event viewer in Windows. Here is the report as follows. Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3Faulting module name: uiautomationcore.dll, version: 7.0.0.0, time stamp: 0x4a5bdb1dException code: 0xc0000005Fault offset: 0x0000e52aFaulting process id: 0x41cFaulting application start time: 0x01ca8a58eddd9e1bFaulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exeFaulting module path: C:\Windows\system32\uiautomationcore.dllReport Id: 58764d98-f658-11de-bd64-001a4d574b64Looking through the event viewer, 99% of the other application error logs were this same error, and all to do with FSX.The uiautomationcore.dll is what is causing the issue. There were a few other help topics I found through Google about the same error. But no real fixes, other than using a different OS. The easiest way to produce the crash is to use an outside view of the aircraft, and then try to use the alt-menu while the sim is running. After about 20 clicks on the menu, the next click seems to cause the crash. The whole thing makes it very hard for checking the map, the weather, increasing or decreasing the sim rate, etc. What I am curious to know, is that if any of the developers here, or other members, have experienced this problem, or might have any insight / ideas on what to do about it. Changing my operating system is not a viable solution, nor should it have to be. I have already tried re-installing FSX, my aircraft, and addons, as well as deleting the fsx.cfg file and letting FSX rebuild it. I will continue to look around and see what other information I can find. Any help or info would be greatly appreciated.

Hi Jordan, One thing that may help, is I always make a note to do a fresh install of the latest .Net framework and the C++ redistrib after all of my FS+Addons. Some addons I have use much older versions and even though I don't think windows allows them to overwrite newer files do it anyway,,, just in case. This has helped many clear up similar event log errors.Also, just out of curiosity, how much ram do you have? And which version of windows? I am guessing Vista 64?

Hi Jordan, One thing that may help, is I always make a note to do a fresh install of the latest .Net framework and the C++ redistrib after all of my FS+Addons. Some addons I have use much older versions and even though I don't think windows allows them to overwrite newer files do it anyway,,, just in case. This has helped many clear up similar event log errors.Also, just out of curiosity, how much ram do you have? And which version of windows? I am guessing Vista 64?

Sorry I should have listed. I'm running Windows 7 Ultimate x64 with 4GB of DDR2 RAM.

Sorry I should have listed. I'm running Windows 7 Ultimate x64 with 4GB of DDR2 RAM.

No prob, vista and win 7 use the same kernel so the errors look alike in the logs. Try the above .net and C++ and see if that helps at all. After you've installed the latest of each (C++2005, C++ 2008, & .net) reboot after each). Also after, check your windows updates to see if it adds any. This was the case with me, after I did the above on Vista64 I had an update for .net available.

Is it necessary to have both the 2005 and 2008 versions? I'm not really sure what they even do, just know that some programs need them to run.

Is it necessary to have both the 2005 and 2008 versions? I'm not really sure what they even do, just know that some programs need them to run.

The uiautomationcore.dll does not link to those runtimes. So, this shouldn't be the problem in this case. But... there are bugs in the 2005 runtime that seem to crash sometimes when using FSX. You can download a patch for this. It's described in the KB article 961894 at the Microsoft website.So, as far as I know, you only need the 2005 runtime for FSX... but, maybe I'm wrong. To explain what it is: That's the common part that every application, that has been created with Visual Studio 2005 oder 2008 needs to run... (if it's not statically linked)... so, there are a lot of applications that need this package.About the other problem (the crash because of the uiautomationcore.dll) ... I heart, that it could probably be solved by copying the uiautomationcore.dll from Vista into the FSX folder so that this old version will be used... I don't know if it works, but I'm trying this now...Rudolf

The uiautomationcore.dll does not link to those runtimes. So, this shouldn't be the problem in this case. But... there are bugs in the 2005 runtime that seem to crash sometimes when using FSX. You can download a patch for this. It's described in the KB article 961894 at the Microsoft website.So, as far as I know, you only need the 2005 runtime for FSX... but, maybe I'm wrong. To explain what it is: That's the common part that every application, that has been created with Visual Studio 2005 oder 2008 needs to run... (if it's not statically linked)... so, there are a lot of applications that need this package.About the other problem (the crash because of the uiautomationcore.dll) ... I heart, that it could probably be solved by copying the uiautomationcore.dll from Vista into the FSX folder so that this old version will be used... I don't know if it works, but I'm trying this now...Rudolf

Well ok... it seems that it works... the PC simulated a whole flight from LSGG to KLAS now withtout crash (that wasn't possible before)... my only problem this time was, that I wasn't able to disable the auto-thrust after landing and so I wasn't able to stop the plane... but that has nothing to do with the FSX problems :-) ...Rudolf

Well ok... it seems that it works... the PC simulated a whole flight from LSGG to KLAS now withtout crash (that wasn't possible before)... my only problem this time was, that I wasn't able to disable the auto-thrust after landing and so I wasn't able to stop the plane... but that has nothing to do with the FSX problems :-) ...Rudolf

yeah, that fixes the menu crash bug. I posted instructions here:http://www.simforums.com/forums/forum_post...D=189242#189242

I was having CTDs with UIAutomationCore.dll in win7 64 after clicking on menus a lot. My solution which seems to have fixed the problem is as follows: 1. Get a copy of UIAutomationCore.dll from a 32 bit Vista install (in c:\windows\system32 somewhere) and copy it to your FSX directory 2. Open an Administrator command prompt 3. cd to your FSX install 4. run "regsvr32 UIAutomationCore.dll" (without the quotes) You should see a dialog pop up saying that it was successfully registered.5. FSX will now use the DLL in its home directory rather than a 64 bit version which seems to cause issues. Hopefully your CTDs will go away. More info here, although there is an extra step mentioned (the takecontrol thing) which is not necessary http://forums1.avsim.net/index.php?showtop...49211&st=25 Hope this helps, -stefan

-stefan

yeah, that fixes the menu crash bug. I posted instructions here:http://www.simforums.com/forums/forum_post...D=189242#189242-stefan

Hey thanks a lot guys, that helps a ton.

Yes, right, but... alltough the dll contains COM-components, it is NOT necessary to register it to make the FSX using it. FSX does load the dll from it's directory, even when you don't call regsvr32 ! ... that's what I wanted to say :-)

Yes, right, but... alltough the dll contains COM-components, it is NOT necessary to register it to make the FSX using it. FSX does load the dll from it's directory, even when you don't call regsvr32 ! ... that's what I wanted to say :-)

While testing the fix, I initially didn't register it, and as a result, it didn't get used. Your mileage may vary.-stefan

Does it have to be a 32 bit version of Vista? I only have access to a 64 bit version at the moment. Or what about a 32 bit version of Windows 7?

While testing the fix, I initially didn't register it, and as a result, it didn't get used. Your mileage may vary.-stefan

Use the Process Explorer to see which one it loads. (And, of course you have to use the 32 bit version of the dll...) ... oh and by the way... I'm using the FSX with acceleration pack... maybe this makes a difference too?

Does it have to be a 32 bit version of Vista? I only have access to a 64 bit version at the moment. Or what about a 32 bit version of Windows 7?

You have to use the 32 bit version of the dll. On a 64 bit system you can find it in the C:\Windows\SysWOW64 folder ... it does not make a difference what type of system you use to run FSX.

Use the Process Explorer to see which one it loads. (And, of course you have to use the 32 bit version of the dll...) ... oh and by the way... I'm using the FSX with acceleration pack... maybe this makes a difference too?You have to use the 32 bit version of the dll. On a 64 bit system you can find it in the C:\Windows\SysWOW64 folder ... it does not make a difference what type of system you use to run FSX.

Right, but can it be a 32 bit version from Windows 7? The system I am running FSX on is Windows 7 Ultimate x64. But I have access to other computers in the house that I could obtain another .dll from. So What I'm asking is, could I take the .dll from another machine I have running Windows 7 x32? or does it have to come from Vista? And do you mean that I can find the 32 bit version of the .dll on a x64 system in the SysWOW64 folder? or am I misunderstanding?

Right, but can it be a 32 bit version from Windows 7? The system I am running FSX on is Windows 7 Ultimate x64. But I have access to other computers in the house that I could obtain another .dll from. So What I'm asking is, could I take the .dll from another machine I have running Windows 7 x32? or does it have to come from Vista? And do you mean that I can find the 32 bit version of the .dll on a x64 system in the SysWOW64 folder? or am I misunderstanding?

Ah, sorry... no, it can't be a Windows 7 x86, since the dll on both systems (x86 and x64) are the same. It is only, that the 32 bit dll on the x64 system is in the syswow64 instead of system32 folder... on Vista it's the same. The whole 32bit stuff on a x64 bit system is in the syswow64 folder. So, the "real" system32 folder on a x64 system is the syswow64 folder... but, because of the redirection system of windows, every 32 bit process accessing the system32 folder on a 64 bit system is automatically redirected... :-) ... a bit complicated, I know... but that's how it works...OT: I never understood, why they didn't rename the system32 into system64 on 64 bit systems... but, that's Microsoft... that's politics, not informatics...