Also from me the question. Do you have the 3GB 580 version?

No. My GTX is with 1.5 GB.

No. My GTX is with 1.5 GB.

Ya man you have some problems with your set-up, but it can all me FIXED.I run a 2500K at 5.0gz and a GTX 480 and I have everything pretty much cranked and have the most stable FSX experience I've ever had. Dont worry we can fix your problems.

For the uiautomationcore.dll: there are TWO solutions for this problem.1. download and put in the fsx main root the uiautomationcore.dll, this is the one i use http://www.search-dll.com/dll-files/download/uiautomationcore.dll.html2.there are other two same files in windows 7, and you have to delete them with this method: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:WindowsSystem32uiautomationcore.dllcacls C:WindowsSystem32uiautomationcore.dll /G username:Ftakeown /f C:WindowsSyswow64uiautomationcore.dllcacls C:WindowsSyswow64uiautomationcore.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.Other things that could crash your fsx:the logbook.bin file in you documentsfsx files can become corrupt: if it happens, it will make fsx crash. to solve this, just delete it, and at next startup fsx will create a new and working one.Sometimes the fsx.cfg file makes your fsx crash. the best way to solve this is to delete it, start fsx, start a flight WITH A DEFAULT PLANE AND IN A DEFAULT SCENERY. THIS WILL AVOID FSX TO ADD ENTRIES THAT AREN'T DEFAULT. so you'll have a new, virgin fsx.cfg. tweak it with bojote's tweaking tool and put it in place.Download this www.kegetys.net/dl.php/d3d_antilag101.zip and put it in main fsx root (WARNING: it will disable an eventual enb series. there is a way to make them work together, but actually i don't know it). open the .ini file and set it so:RenderAheadLimit=2FPSlimit=0It's really effective.with all this job, i run fsx with an incredible smoothness, at least 20 fps in the ngx (perfectly working and also in heavy airports, like flytampa's tampa rebooted) and i can do 12 hours flights without being worried of crashes and similar, also playing a lot with menus, fullscreen and windowed.in two words, it WORKS PERFECTLY (oh, and i'm flying on a laptop )

The crash of the NGX.DLL has nothing to do with the uiautomationcore.dll of it doesn't crash when clicking the mouse only.Re-install it and drastically lower your graphic settings to see what happens.Bert Van Bulck

Have you overclocked your system? Are you absolutely positively sure that its 100% stable?And yes, this crash has nothing to do with uiautomationcore.dll. The previously mentioned method of replacing uiautomationcore.dll is also very ugly and I would highly recommend against using it. There's a reason why the uiautomationcore.dll in w7 64 is different than the 32bit vista version. Several windows applications depend on uiautomationcore.dll and using a vista 32 version on w7 64 is of course highly unrecommendable in these applications. I believe that windows media player (among others) is one of these applications

Have you overclocked your system? Are you absolutely positively sure that its 100% stable?And yes, this crash has nothing to do with uiautomationcore.dll. The previously mentioned method of replacing uiautomationcore.dll is also very ugly and I would highly recommend against using it. There's a reason why the uiautomationcore.dll in w7 64 is different than the 32bit vista version. Several windows applications depend on uiautomationcore.dll and using a vista 32 version on w7 64 is of course highly unrecommendable in these applications. I believe that windows media player (among others) is one of these applications

My system is overclocked to 4.1 GHz. I installed and activated now PMDG J41 and did medium flight. No crash even in the heaviest place Seattle area (PNW)I have problem only with the NGX and especially with "PMDG_737NGX.DLL".

But is it stable when you run prime95 for a few hours?

Have you overclocked your system? Are you absolutely positively sure that its 100% stable?And yes, this crash has nothing to do with uiautomationcore.dll. The previously mentioned method of replacing uiautomationcore.dll is also very ugly and I would highly recommend against using it. There's a reason why the uiautomationcore.dll in w7 64 is different than the 32bit vista version. Several windows applications depend on uiautomationcore.dll and using a vista 32 version on w7 64 is of course highly unrecommendable in these applications. I believe that windows media player (among others) is one of these applications

You forget that FSX is an 32 bit application!Here´s what Ryan said about this some months ago:/ Leffe"Here is the deal on the dll:It's a Windows OS library for creating user interface (UI) elements. It resides in the Windows\System32 folder. FSX calls it to create the menus and dialogs in the sim and it's also involved in view switching.There is an incompatibility between FSX and the Windows 7 x64 version of this file that can cause a crash after a certain amount of uses of the menus or view changes. A lot of crashes people assume are out of memory errors or whatever are actually this uiautomationcore.dll problem building up over the course of a flight - it can take several hours for enough actions to happen to trigger the freeze or crash with it.You can see it yourself by doing the following - load up any aircraft - default ultralight is fine. Without any replacement dll in your FSX folder, start bringing up the right-click menu over and over. After 20-30 times, the sim will crash - it's totally repeatable for me here.The replacement file is from Vista x64 I believe and doesn't have any issue with FSX.To answer an earlier question, the reason this works is because applications have a series of fallback "paths" where they automatically look for required dlls. The first place it checks is the same folder the exe is in... After that it'll look in the various Windows system folders, the side by side cache etc"Ryan Maziarz

What aircraft are you using as your start up aircraft ? When you get to the free flight screen, what aircraft is spinning around ? If it is anything but a deafault plane, that can cause major issues.Have you followed the set up guide by NickN @ simforums ? Re installing windows all the time is pointless, and if you follow Nick's guide, you should not have to do that.I run my fsx config with minimal tweaks, I too have a 2600K and a 580, and I only have Highmemfix and AF=14, and no problems. Don't over tweak your config, especially when trouble shooting.