Hello!I have recently started getting serious problems with FSX, mostly during descend/initial approach. Fsx stops responding, and remains in a frozen state until I get enough and close it. This is happening mostly on flights over 2,5h. If it occurs on shorter flights, FSX usually comes back alive after a couple of minutes. Although this is also a serious problem since I fly on Vatism. This evening i flew the NGX from LPFR to ENGM. Aerosoft scenery for both airports, GEX, REX and UTX. After approximately 4h 5m in the air, on 4000ft intercepting the ILS, fsx stops responding and the screen turns all white. It seems rather logical that the problem is related to overload when the scenery is loading, since aerosoft Olso takes rather hard on the computer. My specs are as following:Asus Sabertooth P67 MotherboardIntel Core i5 2500k @ 4,3Ghz running at approx. 45 degrees Celsius after 4 hours in FSX, cooled by a Cooler Master Hyper 212+Gigabyte GTX560TiCorsair Vengeance CL9 1600MHz 8 GigabytesCorsair TX 650W PSUCould it be hardware related? If that's the reason, what should I think about upgrading?Thanks in advance!

Try at stock speeds and see what happens.

I will try that and report back

Okay. I'm back. I clocked the CPU back down to 3,3Ghz and flew the same route. This time it froze multiple times during descend. CTD at around 5000ft :(

I assume you're using Windows 7, and if so - go herehttp://dl.dropbox.com/u/52676345/UIAutomationCore.place_in_fsx_root.dlland download this version of the UIAutomationCore.dll.Rename it to UIAutomationCore.dll, and place it into the root folder of FSX. It will stop this 'freezing' from happening.

delete your fsx.cfg file

I assume you're using Windows 7, and if so - go herehttp://dl.dropbox.co...in_fsx_root.dlland download this version of the UIAutomationCore.dll.Rename it to UIAutomationCore.dll, and place it into the root folder of FSX. It will stop this 'freezing' from happening.

I also had some CTD´s cause of that UIAutomationCore.dll. I put the dll with version number 6.0.6001.18000 in my FSX folder. But your´s is a different file version. Will there be any difference?

Yeah, Steffen: the 18000 runs ok - almost as well as the 16386, but it did have a freeze or two over six months. I don't remember the 386 having a crash at all.

Since this is happening on long flights, most likely an overheating issue and/or virtual memory is not set to "system managed size". You are getting crashes too on short flights but the system recovers and this is probably caused by having your FSX settings too high plus virtual memory not set to system managed size. It's a memory issue in the long run. Also be advised that not having all the required dotnet versions could cause problems too with your memory. You should have most versions (from dotnet 1 to dotnet 4) installed as FSX is an old program and was programmed with dotnet versions earlier than the latest version (dotnet 4). They are not backward compatible and Microsoft dotnet framework has, as one of its many functions, to manage memory for your applications. Normally, the proper versions are installed with the FSX addon, such as Orbx/FTX scenery or with FSX and FSX Acceleration. Hope this helps.Best regards,Jim

Yeah, Steffen: the 18000 runs ok - almost as well as the 16386, but it did have a freeze or two over six months. I don't remember the 386 having a crash at all.

Ok, thanks. I´ll keep the other version if I have any problems with my current one.

I assume you're using Windows 7, and if so - go herehttp://dl.dropbox.co...in_fsx_root.dlland download this version of the UIAutomationCore.dll.Rename it to UIAutomationCore.dll, and place it into the root folder of FSX. It will stop this 'freezing' from happening.

Thanks! I'll try that

Since this is happening on long flights, most likely an overheating issue and/or virtual memory is not set to "system managed size". You are getting crashes too on short flights but the system recovers and this is probably caused by having your FSX settings too high plus virtual memory not set to system managed size. It's a memory issue in the long run. Also be advised that not having all the required dotnet versions could cause problems too with your memory. You should have most versions (from dotnet 1 to dotnet 4) installed as FSX is an old program and was programmed with dotnet versions earlier than the latest version (dotnet 4). They are not backward compatible and Microsoft dotnet framework has, as one of its many functions, to manage memory for your applications. Normally, the proper versions are installed with the FSX addon, such as Orbx/FTX scenery or with FSX and FSX Acceleration. Hope this helps.Best regards,Jim

Hi!Okay, how do I set "System Managed Size"? I will try to lower the settings a bit plus installing .NET 1-3.

Okay, how do I set "System Managed Size"?

If you haven't gone in there to change anything, it probably is already set to system managed size. However, to check, click on the Start button and type virtual memory in the search bar then look up in the Menu and you'll see How do I change virtual memory settings? Click on that and follow the directions.Best regards,Jim

Yup, it's already set to System managed size. Thanks!