FSX crashing

Thanks for that info, Hasan.  So, I assume that you have the HIGHMEMFIX=1 entry in your [Graphics] section: this is mandatory.  So without using FSXWX, your Error Log shows  uiautomationcore.dll as the faulting module.  However, the version you have is the correct version (you must have put this in at some stage previously as this .dll is not normally located here). So that should be okay, though there is another version that can be used (ending with  .18000), but we won't worry about that for now. 

You're giving the information that whenever FSXWX updates, the error comes up. Firstly, can you go into your FSXWX Settings & have it set so that FSXWX does not do updates for altitudes below 10,000 feet?  If you can't adjust that setting, is there anything else in the program that will lessen the load on FSX at this critical point (of landing, when a lot of VAS is used): such as lowering the radius for how many weather stations are seen & downloaded?

See how you go with the above first before we try other things. You may need to experiment with another type of free weather program to test.

Chris

Hi Hasan,

Unfortunately, the error log doesn't give the faulting module name but gives the exception code (Exception code: 0xc0000005) which many people get. This can indicate a problem that comes up for a variety of reasons, so it is hard to pinpoint, except by experimenting.

So it could be FSXWX, your installed aircraft, or something else that might be causing this Memory Access Violation. Firstly, I would put the following new line into your  fsx.cfg  if you haven't got it already.  To find your  fsx.cfg, go here:  Your Drive Letter:\Users\Your Name\AppData\Roaming\Microsoft\FSX\fsx.cfg (not the fsx.cfg.txt).   Open this up & scroll down to [Graphics] and insert  HIGHMEMFIX=1  after the last entry under the Graphics heading.  Save this  fsx.cfg  file and close it. This entry is mandatory, which the FSX designers forgot to include, and this deals with proper memory allocation in FSX.  After you do this, then take some flights to see whether you still get your FSX crashing.

If this doesn't fix the problem, you will just have to experiment further.  First make sure that all your drivers, especially your video card, are up to date.  Also, if your Virtual Address Space is being depleted (and this usually shows up nearer to landing when a lot of graphics shows up & you don't have the VAS available to cope with it), then try turning down some of your FSX settings, especially Scenery Complexity, Autogen Density, use Simple Clouds & Air/Road traffic.  Remember, you're doing these as an experiment to find out what is causing the error - once you can pinpoint the issue, then you will have a better idea as what to do about it.

If the error still comes up, then it could be something that has been installed, such as FSXWX, a particular installed aircraft or scenery, etc.  You may have to go back to using a default aircraft and/or uninstall the other add ons and take flights to experiment.  You could also try deleting that  fsx.cfg  file altogether as there could be a problem in it, and FSX will automatically rebuild a new one when it starts next.  However, any changes you've made to it (including the HIGHMEMFIX entry) will be removed & will need to be added in later.

So that's all I can suggest for now - see how you go & if you're doing the above changes, do it one at a time to find out if the problem stops because of a particular change you make.  Let me know how you go with this.

Chris

Chris, 

So this is the event viewer log and the error i got. 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x00000000

Faulting process ID: 0x934

Faulting application start time: 0x01d6bceacb9fb9a3

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: unknown

Report ID: 942fd691-28e3-11eb-8359-3863bbcbd7a8

Faulting package full name:

Faulting package-relative application ID:

Thank you for writing back Chris, Yes i do have additional aircraft, I had deleted FSX from the system for about one year so i reinstalled it recently and after installing fsxwx it has been giving me the problem so will let you know about error code.

Hi Hasan,

It would be interesting to see whether your Event Viewer shows anything for the time of the error.  To get to Event Viewer, type it in your Search Box at the Windows Orb, open it up & then go to Custom Views > Administrative Events.  This information will take a little while to populate.  Scroll down to the date & time of the event & see if there is any error popping up about this event in FSX.  You could let me know the Error Code showing there, Faulting Module, etc.

Also, apart from FSXWX, do you use any other addons (aircraft, scenery, airports, etc.)?  Has this problem been happening for some time, or do you know if it started after you made a change in some way to FSX?

Chris