Crashes to desktop on Windows 10

[MH-Sim]

Hi,
I play FSX SE in window mode on Windows 10 install, where I often open the kneeboard, map and sometimes switch views to outside and back through the menu bar. After some time in flight, I usually get a freeze and a crash to desktop. From my search through the web this is a common problem and one of the causes is UIAutomationCore.dll, are there other known causes of this problem and do you know if there are any other UIAutomationCore.dll files default in Windows 10 applications which allow the sim to work without crashes if I would use them instead of that one default from the Steam install?

Thanks for your help

 

[dcox1825]

I used to have this happen to me, too, usually at the most inconvenient times (like on final in a B747 into HON after 6 hrs in the air). I found that increasing my computer's RAM from 8gb to 16gb helped tremendously.

 

[MH-Sim]

I currently have 12 GB of RAM, but also have about a hundred airplanes in SimObjects. Does FSX load all of them on start or just those I select for flight?

 

[MH-Sim]

Having to load about 9 gigabytes of airplanes every time would explain why it crashes a lot. But when I tested the crashes by loading a flight with a somewhat light on memory aircraft and then switching views like crazy it did not crash until I ended that flight and started a new one with another aircraft.

 

[Jax00319]

Same here, FSX doesn't like Windows 10 at all. So, I will be reverting back to Windows 8.1 just for FSX. And, it works very well. Plus, Win 8.1 starts up fast and loads FSX fast as well.

 

[stansdds]

FSX is a 32-bit program, so it has a virtual address space (VAS) of only 4GB. The more scenery it must load and the more memory it uses for aircraft means less memory available for the program to run. The boxed versions of FSX are exceptionally poor at managing this 4GB limit, the Steam Edition of FSX is much better at managing its VAS.

 

[Priller]

As soon as FSX crashes to desktop, open the eventviewer (administrative events) and see what made it crash.

 

[Patch84]

I tried a few fixes when I had Windows 10 and could never get the CTDs to stop, so I gave up on stopping crashes. Since I picked up a Windows 11 laptop in February, FSX-SE has been much smoother.

 

[Priller]

I tried a few fixes when I had Windows 10 and could never get the CTDs to stop, so I gave up on stopping crashes. Since I picked up a Windows 11 laptop in February, FSX-SE has been much smoother.

As someone who works in IT, I couldn't agree with you more. Windows 7/8.x/10 are liabilities. No longer supported and full of holes.

 

[MrZippy]

That's spooky, Jan!

 

[Sbob]

As someone who works in IT, I couldn't agree with you more. Windows 7/8.x/10 are liabilities. No longer supported and full of holes.

Win10 is still supported, you just have to know the right handshake.

Crunch time- Win10, Win11, FS9, and you.

I have read that a sign of insanity is doing the same thing over and over expecting a different result. If this is true Win11 is absolutely insane. Do those ossified craniums at Micro$oft actually think anyone out here is going to click a shortcut to start a program then click "no" on that...

sim-outhouse.org

Post #85.

 

[MH-Sim]

I heard that someone maybe fixed the crashes by using the UIAutomationCore.dll file from an old Windows program (probably Windows 7). Did anyone manage to do this successfully?

 

[Priller]

I heard that someone maybe fixed the crashes by using the UIAutomationCore.dll file from an old Windows program (probably Windows 7). Did anyone manage to do this successfully?

Before doing that, you should look into the eventviewer and tell us what the faulting module is. It could be all sorts. And if and when you do, you should backup the original dll.

 

[wolfebee89]

I heard that someone maybe fixed the crashes by using the UIAutomationCore.dll file from an old Windows program (probably Windows 7). Did anyone manage to do this successfully?

believe UIAutomationCore dll concerns menu crashes https://flyawaysimulation.com/ask/answers/fix-fsx-uiautomationcore-dll-menu-crashes/

here are several faulting module pertinent crash discussions, courtesy of Ian Stephens:

How do I fix an MSVCR80.dll crash in FSX?

Fix an MSVCR80.dll crash in FSX by resetting Logbook.BIN, isolating add-ons and repairing the correct Visual C++ 2005 runtime.

flyawaysimulation.com

How do I fix Sim1.dll crashes in FSX?

Fix Sim1.dll crashes in FSX and Steam Edition by isolating aircraft, saved flights and add-ons, resetting configurations, then repairing core files.

flyawaysimulation.com

How do I fix Terrain.dll crashes in FSX?

Fix Terrain.dll crashes in FSX by isolating faulty scenery, rebuilding scenery indexes, verifying files and reducing 32-bit memory pressure.

flyawaysimulation.com

How do I fix a Weather.dll error in FSX?

Fix FSX and Steam Edition Weather.dll and weather editor errors: test Clear Skies, reset .WX/.FLT files, disable injectors, then verify.

flyawaysimulation.com

in addition to and further to what is already remarked by @stansdds

FSX is a 32-bit program, so it has a virtual address space (VAS) of only 4GB. The more scenery it must load and the more memory it uses for aircraft means less memory available for the program to run. The boxed versions of FSX are exceptionally poor at managing this 4GB limit, the Steam Edition of FSX is much better at managing its VAS.

in light of your concerns

After some time in flight, I usually get a freeze and a crash to desktop

the following articles, again courtesy of Ian Stephens are likewise potentially also a worthwhile read:

Why does FSX freeze during flights, and how do I fix it?

Fix FSX freezes during flights by isolating scenery, aircraft, AI and weather, resetting fsx.cfg, and finding memory or add-on faults.

flyawaysimulation.com

Why does FSX crash or close to desktop mid-flight?

Find why FSX crashes or closes to desktop mid-flight, then isolate memory, add-on, scenery, configuration and graphics faults step by step.

flyawaysimulation.com

cheers!