Crashes to desktop on Windows 10

MH-Sim

Members +
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
 
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.
 
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?
 
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.
 
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.
 
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.
 
As soon as FSX crashes to desktop, open the eventviewer (administrative events) and see what made it crash.
 
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.
 
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.
 
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. :wavey:


Post #85.
 
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?
 
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.
 
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:

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:

cheers!
 
Do you get an Out of Memory error message?
I read this often in posts, and for all my years with FSX, bought FSX-Gold when it was released, on numerous Windows laptops with Windows up through Win11, I can say I've never had this happen. Others seem to get it all the time. So I'm interested to understand this more also, really trying to figure why it has never happened here. OK, probably just jinxed mysef.
 
OOMs were one of the reasons I finally switched to P3D v4.5 a couple of years ago and it's the best flight sim related decision I've made in YEARS! I had the boxed version and the Steam version and even FS2004 before that.

I found I could get repeatable OOM errors by using complex aircraft from companies like Carenado, Milviz, etc. which had lots of custom gauges, hi-res textures and lots of eye candy while flying over complex scenery like FTX Global and with complex WX from Active Sky. It would take a while but the OOMs would come. They could be triggered faster by swapping aircraft a couple of times as the memory allocation would not get re-allocated to the new aircraft so memory slots were still holding the previous aircraft data and therefore the Virtual Address Space filled up rapidly with aircraft swaps.

I even discovered an oddity with one particular aircraft when flying in multiplayer (which I do on an almost nightly basis). A group of us were flying online together one night when we decided to try a different plane just because we could. The chosen plane was the Lionheart Creations Bellanca Super Viking and within 5 minutes of sitting on the ground discussing the next flight several of us experienced an OOM error and CTD within seconds of each other. We did some experimenting and discovered that when you are in a multiplayer session with that aircraft you MUST use the 'substitute' feature within JoinFS to put the other players into something other than the Viking! Apparently there is a 'memory leak' in that aircraft in a multiplayer environment which causes everyone to CTD with an OOM error in less than 5 minutes. Each individual can be in the Viking on their own PC but they must display the other players in a different aircraft to prevent the OOMs. It's a very odd occurrence for sure.
 
Back
Top