*system32. In that folder, I have the ui automationcore ending in 16385.

46 minutes ago, Jim Young said:

Forgot to mention that the Microsoft.net version you stated was in your Win32 folder is one less version than the really old 2005 version.  You didn't put an old version of the uiautomationcore.dll in your System32 folder did you?

Jim, everything is updated, non-corrupted, good to go. I am having no issues with other programs like DCS, etc. Apphangb1 now happens 100% of the time within about a minute. I did't place a UIautomation.dll anywhere, the one in sys32 is: 6.1.7600.16385, size 733kb, dated 7/13/09. I doubt the issue is related to uiautomationcore.dll due to the similarity/time of the issue no matter which one is in there. Net framework is up to date, visual is up to date, dirext x installed is 11. The apphangb1 freeze manifest itself either during the loading of the flight or initialization of the PMDG NGX. If I switch to windowed mode and open an addon program sush as GSX, EZCA, etc, I usually get a hang as well. 

You need to run the Microsoft.net Repair Tool and make sure you have versions 2.0 and the latest version installed.  You might be able to see this if you look in Windows/Microsoft.net/Framework and look at the versions installed (X86).

FSX does not use DX11 even though your video card is capable of running DX11.  FSX can run DX9 and DX10 if you have SP2 or Acceleration installed.

When you startup FSX, the first thing to load is the modules loaded by your dll.xml.  Might give you a hint as to what is causing your crashes.  Again, FSX will not even start up if you do not have Microsoft Visual C++ 2005 installed and/or Microsoft.net 2.0. 

Best regards,

Jim

 

Ran the repair tool and testing...

So last night I had a good run, I loaded a flight, and changed locations several times trying to indice an apphang...didn't happen. I exited and reopened FSX about 6 times, each time loading a different complex aircraft (PMDG) in different HIFI airports; no crashes. Today I start my computer and can't even load a flight anywhere without an apphangb1. 

Based upon all the material I have read regarding the apphangB1 crash, I'm convinced its an issue outside of FSX and inside windows. Notably, sometimes when I boot into windows 7 64 the last 1.5 weeks, I have been receiving a warning message on screen: AisuiteIII: Access violation at address 002AA689. Read of address 002AA689. Almost every time I see that, I get apphangb1's in FSX. Most of the time, if not all the time, if I don't see that message, I only get apphangb1's if I push FSX to. Also, when I don't get the message, the FSX flight set up screen is much more responsive. I think I'm getting closer to resolving this. I have a feeling this may be related to the most recent nvidia drivers.