• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Question on FSX stability

WarHorse47

WarHorse47

SOH-CM-2024
My experience with FSX since February has been fairly enjoyable, but the more I fly the more I encounter instability. I've had many long and short flights without problems as long as I don't attempt to change anything like switching aircraft. Some times the littlest thing will trigger an OOM or a "Microsoft Flight Simulator X has stopped working..." message.

Just awhile ago I took a short flight from KOLM Olympia to W16 Monroe Firstar in the FSAddon Hudson. I had to reference the map from time to time as the Hudson is without a GPS. When I attempted to adjust my heading using the map feature, I got the warning message and had to shut down FSX before finishing my flight.

My computer and video card is more than capable to handle FSX, so there has got to be another solution.

I've read where some have solved the problem by copying utautomationcore.dll from their Windows system directory (system64 in my case) to their root FSX directory. Has anyone tried that, and if so, what are the results?? Is there anything else I should consider such as removing my pagefile or disallowing Windows to mange the page file size??

Again I've read a lot on other forums, but since I frequent SOH a lot I'd like to hear from some of you on what you've done to get FSX stabilized.

Again, your input and responses are always appreciated.
 
WarHorse47 said:
My experience with FSX since February has been fairly enjoyable, but the more I fly the more I encounter instability. I've had many long and short flights without problems as long as I don't attempt to change anything like switching aircraft. Some times the littlest thing will trigger an OOM or a "Microsoft Flight Simulator X has stopped working..." message.

Just awhile ago I took a short flight from KOLM Olympia to W16 Monroe Firstar in the FSAddon Hudson. I had to reference the map from time to time as the Hudson is without a GPS. When I attempted to adjust my heading using the map feature, I got the warning message and had to shut down FSX before finishing my flight.

My computer and video card is more than capable to handle FSX, so there has got to be another solution.

I've read where some have solved the problem by copying utautomationcore.dll from their Windows system directory (system64 in my case) to their root FSX directory. Has anyone tried that, and if so, what are the results?? Is there anything else I should consider such as removing my pagefile or disallowing Windows to mange the page file size??

Again I've read a lot on other forums, but since I frequent SOH a lot I'd like to hear from some of you on what you've done to get FSX stabilized.

Again, your input and responses are always appreciated.
Click to expand...
Do not use the uiautomationcore.dll from the system folders. FSX is already using them!
The uiautomationcore.dll that may fix the mouse/menu crashes is an older Vista file.

First, verify that the UIAutomationcore.dll is indeed the cause: Control Panel-> Administrative Tools-> Event Viewer, select Custom Views-> Administrative Events. In the source column will be "Application Errors" to sift thru.
One of the listed events will be for your CTD.

On the "general" tab will be a synopsis of the event. What you are looking for is the "Faulting module name: ????"

If you are getting UIAutomationcore.dll as the Faulting module, put the UIautomationcore.dll version 6.0.6001.18000 or UIAutomationCore.dll version 6.0.5840.16386 in your main FSX folder.

Nowhere else.

FSX will find it there and use it, without affecting any other programs.
Some folks have success with one, and other folks have success with the other. Try one. If it works: great. If not try the other.

It isn't a catch all fix, and won't help if the faulting module is something else...Don
 
WarHorse47 said:
My computer and video card is more than capable to handle FSX, so there has got to be another solution.
Click to expand...

Often it is not the computer but the fact that FSX is a 32 bit programme (the English spelling:mixedsmi:) that causes the OOM.
A huge amount has been written about this and I am sure you will have read some of it yourself.
I do not pretend to be an expert, however the less virtual address space that FSX uses, the less likely there is to be a consequent OOM.

One very effective way to lower the use of VAS is to only load scenery for the area in which you are flying.
There is a very good and free bit of software called Scenery Config Editor which can be used to create
custom scenery.cfg files which can be loaded individually, rather than always loading all your addon scenery
and the default.

http://sourceforge.net/projects/fs-sceditor/

Regards,
Nick
 
Yes, I have the details as I checked the error report and have copied the dll to my desktop to collect the file version.

Faulting module path: C:\Windows\SYSTEM32\uiautomationcore.dll

File version 7.2.9200 16384

I'm running Windows 8, 64-bit.

I do not have a lot of addon scenery. Basically ORBX PNW and several of their addon airports, and a few others. Nothing compared to what I have in FS9.

View attachment 89699
 
I am also running Windows 8 64 bit.
I have the UIAutomationcore.dll fix detailed by fxsttcb installed and do not
experience this error at all.
I also have FSUIPC (unregistered) which removes the 3d dll error and use the SCE
which has rid me of the OOM errors.

With all this, FSX runs as well as it ever has, not problem free, but it never was, except
perhaps with default everything which no one wants.

Regards,
Nick.
 
Hokay. Thanks guys. I'll give it a shot.

@fxsttcb - what is the difference between the two downloads? I have them both and with try the first one mentioned first.

@ncooper - I've got a registered version of FSUIPC. So what did you do to remove the 3d dll error and use the SCE rid of the OOM errors? Any settings I need to look at?

Thanks again.
 
Just having FSUIPC installed addresses the g3d.dll error.
If you are curious, look in your FSX\Modules folder at FSUIPC4.log
and you will see this line.
"297 G3D.DLL fix attempt installed ok"
So that one is already fixed.

If you wish to download the SCE, once you have read the manual,
it can be used to create much smaller scenery library entries, thus
loading less scenery and helping to reduce the FSX VAS.

I expect that your problem will go away once you have applied the
uiautomationcore.dll fix.
Good advice from dhasdell.

Regards,
Nick
 
WarHorse47 said:
My experience with FSX since February has been fairly enjoyable, but the more I fly the more I encounter instability. I've had many long and short flights without problems as long as I don't attempt to change anything like switching aircraft. Some times the littlest thing will trigger an OOM or a "Microsoft Flight Simulator X has stopped working..." message.

Just awhile ago I took a short flight from KOLM Olympia to W16 Monroe Firstar in the FSAddon Hudson. I had to reference the map from time to time as the Hudson is without a GPS. When I attempted to adjust my heading using the map feature, I got the warning message and had to shut down FSX before finishing my flight.

My computer and video card is more than capable to handle FSX, so there has got to be another solution.

I've read where some have solved the problem by copying utautomationcore.dll from their Windows system directory (system64 in my case) to their root FSX directory. Has anyone tried that, and if so, what are the results?? Is there anything else I should consider such as removing my pagefile or disallowing Windows to mange the page file size??

Again I've read a lot on other forums, but since I frequent SOH a lot I'd like to hear from some of you on what you've done to get FSX stabilized.

Again, your input and responses are always appreciated.
Click to expand...




Have the same problem since a couple of days. Could not complete flights exceeding 45 minutes. Did some testing with altering the fsx.cfg. If you google "HIGHMEMFIX=1" you will find some suggestions as well.
i have tried it and have completed flight which formerelry ended into a freeze. Might be luck as well...
 
WarHorse47 said:
Hokay. Thanks guys. I'll give it a shot.

@fxsttcb - what is the difference between the two downloads? I have them both and with try the first one mentioned first.
Click to expand...
There are minor differences in code. They are both early Vista files. IIRC, they were included in updates to Vista. Beware of later Vista uiautomationcore.dll files.
The later Vista updates included a Win 7 "like" version that will not work.
The 6.0.6001.18000 version is in the *.zip. The 6.0.5840.16386 is the file itself and needs to be renamed "uiautomationcore.dll" before placing it in the FSX folder.

Odd stuff. The 6.0.6001.18000 version works on this new rig, but not my other 'puter, and 6.0.5840.16386 works on the other, but still crashes on this one...Don

This thread has links to FSX tuning guides from most of the recognized "Masters of the Black Arts" AKA; FSX tweaking Gurus...
http://www.flightsim.com/vbfs/showthread.php?259352-FSX-P3D-Software-and-Hardware-Tweaking-Guide
 
Lots of good advice. :applause:

fxsttcb - I'm testing 6.0.6001.18000 version to see if things improve, and if not I'll give the 6.0.5840.16386 a try.

@KelltB - the api.dll patch intrigues me, so I may give that a try as well.

@mjrhealth - No, I'm not overclocked.

@narah - Yes, one of the first things I did when I installed FSX was to add the "HGHMEMFIX=1"entry. The majority of my settings overall are a mix of ORBX recommended settings, and personal preferences.
 
FSUIPC will only catch and fix one particular g3d.dll error, so others may still crash FSX, but it's worth having.
 
ncooper said:
Thanks, it's the Latin spelling, used by the English and the French and possibly
others but not by those whose first language is American.:salute:

The linked fix is specific to 32 bit operating systems.

Regards,
Nick
Click to expand...
Nick, can you explain further. The api patch is specific to FSX, which doesn't matter if its running with a 32 bit or 64 bit system. So are you saying that if I apply the patch and am running FSX in a 64 bit system, that I'm wasting my time??
 
I'll try....

FSX is a 32 bit app ( to avoid using the P word again:icon_lol:) and in a standard 32 bit Windows Operating System,
it and any other 32 bit app can use up to 2GB of Virtual Address Space.

The fix allows FSX or any other app to use up to 3GB of VAS in a 32 bit Windows OS,
just to be clear, it doesn't fix FSX, it fixes the OS.

However, in a 64 bit Windows OS, a 32 bit app can use up to 4GB of VAS, unfortunately
that's the limit and there is no fix which can allow the use of more.

It is the using up of all the VAS which causes the OOM error message.

Regards,
Nick.
 
Believe it or not.. I understood that. Thanks, Nick.

So I will discard using the api.dll, and just stick with experimenting with the uiautomation.core.dll for now and see what happens.
 
Apologies if you already know this.

In your first post you mentioned that the Hudson is without a GPS.
It is very easy to add one if you would prefer not to have to
reference the map view.

Open the Hudson\panel\panel.cfg file with Notepad and in the
[Window Titles] section, under the bottom entry add
WindowXX=GPS where XX is the next available number.

Then scroll down to the [Window00] etc entries and after the last
one, copy and paste the text below into the .cfg file.
Once again, changing the XX to the next available number.


[WindowXX]
size_mm=545,354
window_size=0.5,0.3625
position=2
BACKGROUND_COLOR=0,0,0
VISIBLE=0
ident=GPS_PANEL

gauge00=fs9gps!gps_295, 0,0

This entry is straight from the default DC 3 and will place a GPS in the top right hand corner
of your screen.
To see it, simply press Shift and one number above your [WindowXX] entry, so if it is [Window04]
for example, press Shift +5. Doing this again will close the 2D window.

On the subject of the api.dll fix, I was slightly wrong, in as much as what it does is to suppress the OOM warning message.
It doesn't, however stop the OOM from happening, so the end result is that FSX stops working anyway, it just doesn't tell
you that it's going to.
Either way, it is for 32 bit Windows and doesn't work in 64 bit ones.

Regards,
Nick
 
ncooper said:
I'll try....

FSX is a 32 bit app ( to avoid using the P word again:icon_lol:) and in a standard 32 bit Windows Operating System,
it and any other 32 bit app can use up to 2GB of Virtual Address Space.

The fix allows FSX or any other app to use up to 3GB of VAS in a 32 bit Windows OS,
just to be clear, it doesn't fix FSX, it fixes the OS.

However, in a 64 bit Windows OS, a 32 bit app can use up to 4GB of VAS, unfortunately
that's the limit and there is no fix which can allow the use of more.

It is the using up of all the VAS which causes the OOM error message.

Regards,
Nick.
Click to expand...

That's as clear as day, Nick. Thanks for the explanation. I hadn't realized (though I should have) that it applied to the os rather than individual applications.
 
You must log in or register to reply here.
Back
Top