Jump to content
Sign in to follow this  
PhilH

Fresh FSX & fatal errors

Recommended Posts

Hello everyone,

 

Just to put you into context, here's my situation: I have been flight simming for a very long time using X-Plane. Near the end of 2009 though, I discovered some aircraft sytems were better modeled in FS9 for certain addon aircraft and decided to try it. Since then, I have been flying FS9 on VATSIM and I really love the experience.

 

As you can see on my Vataware page though (http://vataware.com/pilot.cfm?cid=1008468) I have not flown for a very long time. I basically ran out of time, and when I came back to FS9 about a year ago, my PC's performance discouraged me. (Back then, I was running an Intel P4 2.8 GHz with an nVidia GeForce 7600 GS, and Windows XP 32 bit. It wasn't that bad, but I didn't feel like spending hours tuning again.

 

Recently though, I upgraded my computer. Surely it's not the best out there, but I built it myself and it's really the best I could afford for now. At least I still have a lot of headroom for future upgrades, I am no longer limited by my old AGP slot and/or my unique motherboard socket type. My specs are on my profile.

 

I was about to install FS9 when I thought I might try FSX. Why not? My PC could maybe handle it quite well. Turns out it does!

 

 

Yes, I did do my research. I read the most popular guides online, did everything I was supposed to do and I am very impressed with the results! FSX runs really great, super smooth and never lags. I have not installed any addons or anything extra yet, just the basic FSX install with SP1 and SP2. I have the Deluxe version, not Acceleration.

 

Here's my problem - even though I've only played with it for about 1 or 2 hours, just flying around the default area in the default aircraft, I have been getting random Windows 7 fatal errors. I am running Windows 7 64 bit now. I did do a bit of research, but most threads seem to be telling people to remove X addon and try again - which is why I am starting my own thread, I have no addons!

 

There seems to be a lot of debate about this strange uiautomationcore.dll thing. I have not tried anything yet because there are 2 options I find on the web and I don't know what to do. Deactivate the file in system32 (by renaming it)?? Download the Vista 32 bit version and place it in my FSX directory?

 

Basically, I'm just asking to find out if I missed anything major. It's a one month old build, with fresh OS and clean FSX install. Any tips? Maybe this will help others getting random CTD after a clean system install.

 

 

Thank you very much for your time, I look forward to starting my long haul airline flights and sharing my screen shots again! Don't get me wrong, I am very happy with my FSX performance, but just wandering what my last tune-ups should be for the best Windows 7 64 bit crashless experience possible.

 

Regards,

 

Phil H

Share this post


Link to post
Share on other sites

Hello Phill

 

Windows Vista version of UIAutomationCore.dll (version 6.0.6001.18000, link from Word Not Allowed's) is a must.

Just place it on your FSX folder, nothing else to do.

(You don't want nor need to disable the one present on \System32 as Visual Studio and some other programs need it.)

 

Note: Programs use the first found instance of a *.dll they need to access, unless you force them, and since UIAutomationCore.dll will be on the same path as the fsx.exe executable, it will use that one. That is the way the operating system works)

 

You might also consider installing FSUIPC, free or registered (better), it will take care of many problems associated with FSX and CTD's, including the ones associated with g3d.dll.

 

After you get going, work your way up in your settings, one by one until you get a good performance/quality balance.

 

Once your system is “stable”, make a backup copy of the whole FSX thing (better safe than sorry).

 

Then apply Word Not Allowed’s tweaks if you want.

 

Lastly install your add ons.

 

Cheers

Share this post


Link to post
Share on other sites

Hi Phil,

Well written post! My advice in addition to Ramon's suggestions is to try to keep your system clean and don't install a 'tweak' unless you know what it does and that it will help. I do a lot of research through Google on FSX related crashes and/or computer system crashes and see a lot of people running into major issues with FSX that are not even FSX related. Overclocking, overheating, memory not configured properly in the BIOS, too low or too high CPU voltages are common causes of FSX to crash. The uiautomationcore.dll has fixed issues for a lot of flight simmers and has not for many others, including me. I have never installed this dll in my FSX folder and have not had a crash (other than the infamous g3d.dll crash which was mostly fixed by the FSUIPC.dll module). Many others who have had uiautomationcore.dll crashes have tried this fix and it has not worked for them. My suggestion is to download the freeware AppCrashView from http://www.nirsoft.net/ and run it. If you had any application crashes, like FSX, it will give you the complete details as to what was running when it crashed and the possible reason(s) for the crash. It is more complete than the Microsoft crash reporting program. You can also copy the contents of the crash and paste them to this forum and people like myself will review the crash report to see if there is a fix available.

 

I looked at your system on the Internet and you have a pretty basic system. It will run FSX well but you will want to keep your fsx settings down near the default, and I wouldn't recommend any tweaks at this time, except for maybe highmemfix=1 in the Graphics section of the fsx.cfg. That tweak works for some but not all. If you see any issues after installing this tweak, remove it. I have a high powered system but I recently rebuilt my fsx.cfg and wiped out all of my tweaks and left most of the settings at the default. FSX is running great and better than ever. I did it because I moved over to DX10 Preview as most of the issues with DX10 have been resolved.

 

Best regards,

Jim


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

Hi there,

 

Thank you for all your help! I seem to be getting much less CTD's now. All I did was the uiautomation.dll fix, I am still playing around with FSX's settings and the .cfg file. I am trying to figure out what to do with the BufferPool option.. there are so many opinions out there!

 

For now though, I am able to fly a default plane around LAX, with most settings on max (apart from Water Detail) and I still get 30 FPS. I do know that I won't get that frame rate with custom scenery and addon aircraft, but compared to my older P4, I am still amazed with the performance. I could barely run FS9 with medium settings before.

 

I am currently following your advice and copying my "Fresh and working" FSX folder to my external hard drive, as a backup. I also downloaded the AppCrash from Nirsoft. For your info, here is the detail from my last CTD, from last evening...

 

 

Version=1
EventType=APPCRASH
EventTime=129919897990513869
ReportType=2
Consent=1
UploadTime=129919897993523874
ReportIdentifier=b69a3fed-fd68-11e1-9aed-c86000708287
IntegratorReportIdentifier=b69a3fec-fd68-11e1-9aed-c86000708287
WOW64=1
Response.BucketId=1375473314
Response.BucketTable=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.61472.0
Sig[2].Name=Application Timestamp
Sig[2].Value=475e17d3
Sig[3].Name=Fault Module Name
Sig[3].Value=uiautomationcore.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=7.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4a5bdb1d
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0000e52a
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=4105
UI[2]=X:\Flight Simulator X\fsx.exe
UI[3]=A fatal error occurred.
UI[4]=Windows can check online for a solution to the problem and try to restart the program.
UI[5]=Check online for a solution and restart the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=X:\Flight Simulator X\fsx.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[7]=C:\Windows\syswow64\GDI32.dll
LoadedModule[8]=C:\Windows\syswow64\USER32.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\syswow64\LPK.dll
LoadedModule[15]=C:\Windows\syswow64\USP10.dll
LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[17]=C:\Windows\syswow64\ole32.dll
LoadedModule[18]=C:\Windows\system32\apphelp.dll
LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[20]=C:\Windows\system32\UxTheme.dll
LoadedModule[21]=C:\Windows\system32\WINMM.dll
LoadedModule[22]=C:\Windows\system32\samcli.dll
LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[24]=C:\Windows\system32\MSACM32.dll
LoadedModule[25]=C:\Windows\system32\VERSION.dll
LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[27]=C:\Windows\system32\sfc.dll
LoadedModule[28]=C:\Windows\system32\sfc_os.DLL
LoadedModule[29]=C:\Windows\system32\USERENV.dll
LoadedModule[30]=C:\Windows\system32\profapi.dll
LoadedModule[31]=C:\Windows\system32\dwmapi.dll
LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[35]=C:\Windows\syswow64\urlmon.dll
LoadedModule[36]=C:\Windows\syswow64\iertutil.dll
LoadedModule[37]=C:\Windows\syswow64\WININET.dll
LoadedModule[38]=C:\Windows\syswow64\Normaliz.dll
LoadedModule[39]=C:\Windows\system32\MPR.dll
LoadedModule[40]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[41]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[42]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[43]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll
LoadedModule[44]=C:\Windows\system32\mscms.dll
LoadedModule[45]=C:\Windows\system32\DDRAW.dll
LoadedModule[46]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[47]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[48]=C:\Windows\syswow64\IMM32.dll
LoadedModule[49]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[50]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[51]=C:\Windows\syswow64\NSI.dll
LoadedModule[52]=C:\Windows\system32\msi.dll
LoadedModule[53]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[54]=C:\Program Files\CheckPoint\ZAForceField\WOW64\Plugins\ISWSHEX.dll
LoadedModule[55]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[56]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[57]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[58]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[59]=C:\Windows\system32\ntmarta.dll
LoadedModule[60]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[61]=X:\Flight Simulator X\language.dll
LoadedModule[62]=X:\Flight Simulator X\API.DLL
LoadedModule[63]=X:\Flight Simulator X\ablscpt.dll
LoadedModule[64]=X:\Flight Simulator X\flight.dll
LoadedModule[65]=X:\Flight Simulator X\ai_player.dll
LoadedModule[66]=X:\Flight Simulator X\acontain.dll
LoadedModule[67]=X:\Flight Simulator X\controls.dll
LoadedModule[68]=C:\Windows\system32\DINPUT8.dll
LoadedModule[69]=X:\Flight Simulator X\fsui.dll
LoadedModule[70]=X:\Flight Simulator X\atc.dll
LoadedModule[71]=X:\Flight Simulator X\facilities.dll
LoadedModule[72]=X:\Flight Simulator X\demo.dll
LoadedModule[73]=X:\Flight Simulator X\main.dll
LoadedModule[74]=X:\Flight Simulator X\fe.dll
LoadedModule[75]=X:\Flight Simulator X\util.dll
LoadedModule[76]=X:\Flight Simulator X\simprop.dll
LoadedModule[77]=X:\Flight Simulator X\g2d.dll
LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[79]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[80]=C:\Windows\system32\d3d9.dll
LoadedModule[81]=C:\Windows\system32\d3d8thk.dll
LoadedModule[82]=X:\Flight Simulator X\g3d.dll
LoadedModule[83]=X:\Flight Simulator X\panels.dll
LoadedModule[84]=X:\Flight Simulator X\multiplayer.dll
LoadedModule[85]=X:\Flight Simulator X\ui.dll
LoadedModule[86]=X:\Flight Simulator X\sound.dll
LoadedModule[87]=X:\Flight Simulator X\sim1.dll
LoadedModule[88]=X:\Flight Simulator X\simscheduler.dll
LoadedModule[89]=X:\Flight Simulator X\visualfx.dll
LoadedModule[90]=X:\Flight Simulator X\window.dll
LoadedModule[91]=X:\Flight Simulator X\terrain.dll
LoadedModule[92]=X:\Flight Simulator X\weather.dll
LoadedModule[93]=C:\Windows\system32\DSOUND.dll
LoadedModule[94]=C:\Windows\system32\POWRPROF.dll
LoadedModule[95]=X:\Flight Simulator X\symmap.dll
LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dll
LoadedModule[97]=C:\Windows\system32\MSIMG32.dll
LoadedModule[98]=X:\Flight Simulator X\xuipc.dll
LoadedModule[99]=X:\Flight Simulator X\livingwater.dll
LoadedModule[100]=X:\Flight Simulator X\fs-traffic.dll
LoadedModule[101]=X:\Flight Simulator X\gps.dll
LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[104]=C:\Windows\system32\RICHED20.DLL
LoadedModule[105]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[106]=C:\Windows\system32\rsaenh.dll
LoadedModule[107]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL
LoadedModule[108]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[109]=C:\Windows\system32\dxgi.dll
LoadedModule[110]=C:\Windows\system32\nvd3dum.dll
LoadedModule[111]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[112]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[113]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[114]=C:\Windows\system32\d3d10_1.dll
LoadedModule[115]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[116]=C:\Windows\SysWOW64\dxdiagn.dll
LoadedModule[117]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[118]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[119]=C:\Windows\SysWOW64\d3d11.dll
LoadedModule[120]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[121]=C:\Windows\system32\wbemcomn.dll
LoadedModule[122]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[123]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[124]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[125]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[126]=C:\Windows\system32\winbrand.dll
LoadedModule[127]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[128]=C:\Windows\system32\WINSTA.dll
LoadedModule[129]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[130]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll
LoadedModule[131]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[132]=C:\Windows\SysWOW64\wer.dll
LoadedModule[133]=C:\Windows\System32\Wpc.dll
LoadedModule[134]=C:\Windows\System32\wevtapi.dll
LoadedModule[135]=C:\Windows\System32\msxml6.dll
LoadedModule[136]=C:\Windows\system32\SAMLIB.dll
LoadedModule[137]=C:\Windows\system32\netutils.dll
LoadedModule[138]=C:\Windows\system32\uiautomationcore.dll
LoadedModule[139]=C:\Windows\system32\OLEACC.dll
LoadedModule[140]=C:\Windows\System32\MMDevApi.dll
LoadedModule[141]=C:\Windows\System32\PROPSYS.dll
LoadedModule[142]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[143]=C:\Windows\system32\HID.DLL
LoadedModule[144]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[145]=C:\Windows\system32\wdmaud.drv
LoadedModule[146]=C:\Windows\system32\ksuser.dll
LoadedModule[147]=C:\Windows\system32\AVRT.dll
LoadedModule[148]=C:\Windows\system32\msacm32.drv
LoadedModule[149]=C:\Windows\system32\midimap.dll
LoadedModule[150]=C:\Windows\system32\dinput.DLL
LoadedModule[151]=C:\Windows\System32\wship6.dll
LoadedModule[152]=C:\Windows\System32\wshtcpip.dll
LoadedModule[153]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[154]=C:\Windows\system32\Secur32.dll
LoadedModule[155]=C:\Windows\system32\dnsapi.DLL
LoadedModule[156]=C:\Windows\system32\iphlpapi.DLL
LoadedModule[157]=C:\Windows\system32\WINNSI.DLL
LoadedModule[158]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[159]=C:\Windows\system32\msimtf.dll
LoadedModule[160]=C:\Windows\system32\msls31.dll
LoadedModule[161]=C:\Windows\system32\d2d1.dll
LoadedModule[162]=C:\Windows\system32\DWrite.dll
LoadedModule[163]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[164]=C:\Windows\system32\MLANG.dll
LoadedModule[165]=C:\Windows\system32\msadp32.acm
LoadedModule[166]=C:\Windows\system32\d3dx9_31.dll
LoadedModule[167]=C:\Windows\system32\RASAPI32.dll
LoadedModule[168]=C:\Windows\system32\rasman.dll
LoadedModule[169]=C:\Windows\system32\rtutils.dll
LoadedModule[170]=C:\Windows\system32\sensapi.dll
LoadedModule[171]=C:\Windows\system32\windowscodecsext.dll
LoadedModule[172]=C:\Windows\SysWOW64\jscript9.dll
LoadedModule[173]=C:\Windows\syswow64\imagehlp.dll
LoadedModule[174]=C:\Windows\system32\ncrypt.dll
LoadedModule[175]=C:\Windows\system32\bcrypt.dll
LoadedModule[176]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[177]=C:\Windows\system32\GPAPI.dll
LoadedModule[178]=C:\Windows\system32\cryptnet.dll
LoadedModule[179]=X:\Flight Simulator X\GAUGES\BoeingGeneric.DLL
LoadedModule[180]=X:\Flight Simulator X\GAUGES\Magnetic_Compass.DLL
Sec[0].Key=LCID
Sec[0].Value=4105
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=1375473314/nBucketTable=1/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft® Flight Simulator X
AppPath=X:\Flight Simulator X\fsx.exe

 

Seems pretty smooth for now! I will keep you posted with my installation of addons.

 

Thank you very much!

 

Phil

Share this post


Link to post
Share on other sites

Hi again guys,

 

It seems like the dll file fixed my CTDs, I haven't had any at all since! However, I have another concern. I haven't found many threads with solutions to this problem, but it seems like my FSX is eating up a hell of a lot of RAM. I have yet to have an OOM error, but I seem to have a memory leak. I mean, when starting FSX, on the menu, it might use about 600 mb, which isn't that bad considering I have 4GB, but after a flight or 2, it seems like the used RAM isn't getting "flushed".

 

Example: I played around a lot with FSX tonight, many different flights, returning to the menu once in a while. After maybe 2.5 hours of random flying, I started to get cracking sound and glitches. I checked and my FSX was using just under 2.8 Gb of RAM! I quit the sim and restarted it, all the issues were fixed.

 

This raises a few questions for me:

 

1) Is this normal? Does FSX really need that much memory?

2) Why does't the memory usage drop back down to 600 mb when I quit to the FSX menu?

3) Are there any known fixes?

 

In the worst case, I could buy more RAM, but considering this is a fairly new build, I was hoping to have enough with 4GB.

While I have not done this yet, I am used to (and enjoy) flying long IFR airline flights. I don't want to plan a flight for an hour and end up getting an OOM after 3 hours of flying. I am too nervous to attempt one, my RAM issues trouble me.

 

I have started adding addons by the way, but I had to same issues at first I believe.

 

Thank you very much!

 

Phil

Share this post


Link to post
Share on other sites

This raises a few questions for me:

 

1) Is this normal? Does FSX really need that much memory?

2) Why does't the memory usage drop back down to 600 mb when I quit to the FSX menu?

3) Are there any known fixes?

 

I believe the memory usage is normal. You have a 64 bit system that manages memory much better than 32 bit systems so would not be too concerned. There's a monitoring program that monitors processes as you run FSX (Process Monitor - http://technet.microsoft.com/en-us/sysinternals). You can run it and see exactly what is running and what might be taking up so much memory while running FSX. It could be an addon. It could be the system running different services. Lots of possibilities. FSX will use up to 4GB's while running with a 64 bit system. If you have more memory, it will be used for other processes. So with your 4GB's, FSX is probably using between 2 and 3 GB's and the rest, including virtual memory, is being used for other processes. It should not be a cause for concern. If you get an out-of-memory error (extremely rare for 64 bit systems) it is most likely because you don't have the right page file (virtual memory) settings.

 

Best regards,

Jim


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

The amount of RAM you need for FSX depends on what you have added on. 4GB is more than enough for a stock FSX but if you try to fly something like the 737 NGX over a Horizon Gen-X scenery city you will get OOM errors even on a 64 bit system. I know this for a fact as I have just recovered from CTD issues. See my thread "FSX FATAL ERROR" I run with 8GB of DDR3 at 1600mhz, (4 x 2GB) I found two bad modules that are now RMA so I am temporarily running on 4GB and I do get OOM errors under full load but not with my normall 8GB.

 

With regard to your page file, as Jim says, check your settings assuming that your OS is on a conventional HD. If your OS is on a SSD you can disable the page /swap file as SSD'S dont need it because of their speed.

 

Stress test your memory with Memtest, you might have a dodgy module.

 

Hope this helps. Buster.

Share this post


Link to post
Share on other sites

I have a basic RAM percentage monitor on my desktop. Whenever I revert back to FSX menu the RAM consumption remains high. It doesn't drop back down unless I quit FSX altogether. I presume, therefore, that this is normal as it has never caused me any problems. Since I moved to W7-64bit I stopped shutting down other processes before starting FSX, the O.S seems to manage the memory quite well. Probably unrelated but I would monitor the temperature of that GPU, I have the same model and it runs quite hot under load if airflow is restricted. I had to do some "fiddling around" in the case to help keep it cool.

 

http://www.techpowerup.com/gpuz/

 

On another note, my processor (i7-860) is a few years old and FSX runs like a dream with plenty of add-ons and sliders to the right. However, if I start up PMDG 737NGX at a busy airport I'm into slideshow territory, I've decided to wait for an upgrade before taking things any further with that particular set-up. However, Orbx, REX, and GA add-ons pose no problems at all. I just thought I would share that with you.

Share this post


Link to post
Share on other sites

I seem to have solved the "Fatal Error" in FSX by placing the UIAutomotionCore.DLL file into the FSX folder and then changing the properties of the FSX.exe file to Windows XP SP2 compatability mode.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...