Hey all...I cant really enjoy FSX since I suffer from CTDs. They always appear (sometimes after 5, sometimes after 10 minutes of trying to reproduce or around 60 minutes of flying) when using the menu ingame. I got a 100% reproduce-rate when rightclicking ingame and selecting all the elements, pressing alt, selecting the elements there, clicking on one of them and repeat that until it crashes.It happens with addons or with an absolute-fresh-install, no sp, with sp2, with acc. exp pack...I dont think that this is related to any fsx mods so.My current system:Board: Asus M5A99X EvoCPU: AMD Phenom 2 X6 6x,3.2GHZRAM: G.Skill DIMM 8 GB DDR3-1333 KitGraphic: ATI HD4870OS: Win7 x64 with automatic updatesFirst of all: I updated my PC a few months ago, had a AMD X2 2x2,7ghz CPU and 4GB of RAM with a different Mainboard (can find that out if it matters) and Win7 x32, and I dont remember experiencing those CTDs. After updating the PC I began to play FSX again a few weeks ago and suffer from those CTDs since then. Most of the time it says the failing module is uiautomationcore.dll. I found a lot entrys about uiautomationcore.dll and Win 7 x64, all reported that the solution should be to use a vista uiautomationcore.dll and place it in the FSX directory. Sadly it doesnt change anything, it still crashes with this module (although the module version number has the one from vista). I tried with simple inserting it in the directory, registering the dll and even deleting all the uiautomationcore.dll from Win7 in sys32 and the other folder.When I delete all the uiautomationcore.dll from my PC it still crashes, the failing module is simply "unknown" afterwards. I tried reinstalling FSX (with deleting everything related to FSX on my PC), even changing the RAM Mode from ungaged to gaged because I read it somewhere here in the forum. Since I have no ideas anymore (and cant find any tips on the internet anymore) I will install Win Vista x32 tomorrow, just for FSX to try if it changes anything.I appreciate any help and really hope someone has a clue what I could do, because even if the second OS trick worked I wouldnt like switching the OS ever when I want to use FSX. I read some posts about changing RAM/CPU settings, maybe I should work there? Could it be wrong RAM timings for example? I have really no explanation anymore...If there is any information missing please feel free to ask!Thanks in Advance, Bloody

Edited February 29, 201214 yr by Bloody

See here.Cheers,- jahman.

Hey,followed every single step in this thread, even the different .dlls. Sadly I'm still able to reproduce this problem, so it didnt help....Any other ideas?

Alright, I installed Win Vista x32 as a second OS today and couldnt reproduce the CTD anymore. This makes me really believe that it is no hardwareissue, more a 64-Bit problem. Since it only happens when using the menus the symptoms have a 100% match to the uiautomationcore.dll problem.Sadly all the fixes on the internet aint working here. Does anyone have another idea? Having it working under Vista is great, but its still not comfortable to switch the OS if I just want to fly a little.

When I delete all the uiautomationcore.dll from my PC it still crashes, the failing module is simply "unknown" afterwards.

The uiautomationcore.dll is part of Microsoft.net and automatically installed with the Windows 7 platform. It's a system module and must NOT be deleted. Download and reinstall dotnet, then run Microsoft update to make sure it is up-to-date. For earlier OS's, like Vista, you need to download and install the latest version of dotnet. There's another program used by Microsoft and addon developers to install and run Microsoft programs - Microsoft Visuals C++ Redistributables. You should have all the MSV's installed from 2005 to 2010 (look in your Add/Remove Programs). They are usually installed when FSX/Acceleration or an addon is installed but something may have prevented it. When installing FSX or any FSX addon, you should make sure UAC is disabled and any anti-virus program. MSV's are constantly updated by Microsoft and even 2005's and 2008's are updated too. They are not backward compatible so you need them all as FSX is an old program.As I was writing the above, I noted you installed Vista 32 bit and you no longer have the CTD's so you think it's a 64 bit problem. Most of us here have the 64 bit version installed on our systems as it is better with memory management (for one thing). With the 32 bit version you have to install the /3GB switch for Vista so FSX can 'see' and 'use' more memory. I think the fact you installed your 32 bit OS on another partition and then reinstalled FSX on that partition fixed your CTD's (if that's what you did). I agree, you could be having problems with RAM settings in the bios too as you related in the OP. You might want to open the bios and make sure you have set the settings manually and they are not set to 'auto'. There are some MB's that have a hard time managing memory set at 'auto'. Make sure the frequency is set at 1333 and your timings and voltages are set in accordance with what the program CPU-Z states should be the settings. If you have the XMP option in your bios, I would use the XMP-1600 settings in the timing tables shown in the CPU-Z program. Good luck!Best regards,JimI might add that you can further research your problem by doing a Google/Bing search for 'menu crashes fsx'. This is a common problem throughout the flight sim community.Best regards,Jim

Hey firehawk, thanks for that detailed reply!I do understand that uiautomationcore.dll is not meant to be deleted, but I wanted to try it anyways, just for testing purposes.

With the 32 bit version you have to install the /3GB switch for Vista so FSX can 'see' and 'use' more memory.

DO I have to do that? The screen that activates on every vista boot tells me already that I have 8GB of RAM. Is it still needed? I used a version of vista where SP2 was already included. Probably is it installed already?

I think the fact you installed your 32 bit OS on another partition and then reinstalled FSX on that partition fixed your CTD's (if that's what you did).

So you think the reason it works now is because I installed FSX on another partition and nothing else? I didnt explicitly try that, but it doesnt sound...reasonable to me. What do you recommend on getting it working on Win7? Format C and reinstall FSX on another partition? Wouldnt like that solution, but in case it works I would prefer it than switching the OS all the time.

I agree, you could be having problems with RAM settings in the bios too as you related in the OP. You might want to open the bios and make sure you have set the settings manually and they are not set to 'auto'. There are some MB's that have a hard time managing memory set at 'auto'. Make sure the frequency is set at 1333 and your timings and voltages are set in accordance with what the program CPU-Z states should be the settings. If you have the XMP option in your bios, I would use the XMP-1600 settings in the timing tables shown in the CPU-Z program. Good luck!

I will have another look at this soon. The XMP-1600 Settings are a little different to my current settings, I will change them.

I might add that you can further research your problem by doing a Google/Bing search for 'menu crashes fsx'. This is a common problem throughout the flight sim community.

Most of the posts there refer to uiautomationcore, but I will have another look there.Again thanks for your reply, in case you got anymore hints please feel free to share them with me. :)

I installed Win Vista x32 as a second OS today and couldnt reproduce the CTD anymore.

1. Copy the UIAutomationCore.dll from your <Vista 32>Windows/System32 folder
2. Paste it in your FSX folder
3. Try FSX again!

Cheers,- jahman.

Jahman: Did that alot of times :/ANYWAY:Seems I got my solution! I found this post again after I tried it with 3 different vista uiautomationcore.dll files. Because I got nothing to lose I deleted all the files again on my PC and - I am NOT able to reproduce my problem within 20 minutes of just rightclicking on the screen and highlighting menu-entrys. I even tried to add the uiautomationcore.dll to the FSX directory and it didnt take me 2 minutes to get a CDS again. So I think dotnet has to live without this file from now on. Im going to install all my addons and will do some long testing later that evening. Would be awesome to enjoy FSX without crashing after clicking in the menu sometime in the flight.I hope not to be disappointed by that solution; lets see what happens with longer testing. At least I didnt notice any disadvantage from having no u..dll.Thanks for your help again!

I have an HD4870X2 and the UIAutomationCore.dll fix did it for me.What version of the ATI/AMD CCC Driver are you using?Cheers,- jahman.

During my research on the internet I felt that the UIAutomationCore.dll fix solved the problem for everyone except me...good that it works for both of us now though. :)I always update it whenever there is a new version, currently I'm on AMD Catalyst 12.1 :)

DO I have to do that? The screen that activates on every vista boot tells me already that I have 8GB of RAM. Is it still needed? I used a version of vista where SP2 was already included. Probably is it installed already?

Yes, you do for 32 bit systems. See the explanation for this at the following link - http://www.simforums.com/forums/topic29041.html (scroll down about halfway down until NickN starts discussing memory management. He also provides details on how to implement the switches based on the version of Windows installed). Windows will always show you how much memory installed. Even though you have 8GB of memory, FSX cannot use more than 4GB (also explained in link above). It's an old program.

So you think the reason it works now is because I installed FSX on another partition and nothing else? I didnt explicitly try that, but it doesnt sound...reasonable to me. What do you recommend on getting it working on Win7? Format C and reinstall FSX on another partition? Wouldnt like that solution, but in case it works I would prefer it than switching the OS all the time.

I have FSX installed in the default folders on my C drive. I have UAC disabled though. Many people have found installing FSX on another drive works better for them as FSX will then avoid all the security issues caused by installing FSX in the default folder. I disagree with that theory but these people are much more smarter than me regarding computer programming and stuff like that. So, you would be wise to at least try it if nothing else works.

in case you got anymore hints please feel free to share them with me. :)

You have exhausted my knowledge already. Hopefully the uiautomationcore.dll fix you found above does work.Best regards,Jim