Not technically a CTD but placed my question on AVSIM CTD Forum instead of AVSIM FSX Forum.  I placed this on the Orbx Forum as the error could involve Orbx scenery.   But am also placing it here as error c0000005 may envolve within App (FSX) processor error calling for memory location unavailable.

I have been flying with the Misty Flying Club (MFC) a virtual airlines that is part of Return to Misty Moorings website.  I have been actively flying since before Covid.  MFC flights start in Alaska and proceeded south down west coast of Canada and the United States.  All Orbx regions were flown through.  No problems occurred on any of these flights until reaching the Southern border of the US.  On reaching San Diego our routes turned to the East.   The fatal error occurred on a flight leg that flew north on the eastern edge of New Mexico starting in Dell City Muni (2ES) with stops at KCNM and KATS ending at Roswell Intl (KROW).  The error first occurred enroute from 2ES and required a restart of the simulator.  I began trouble shooting and found that any flight initiated at KCNM, KATS, or KROW caused the fatal error to occur while on the ramp.  Further trouble shooting indicated; that if you draw a line on the Map north and south from Regina, Saskatchewan to Rapid City, South Dakota to Denver, Colorado-to Roswell, New Mexico all flights flown from airfields west of that line do not cause the fatal error and all flights initiated from airfields east of that line cause the error.

Information given on error:    

Problem Event Name:    APPCRASH
  Application Name:    fsx.exe
  Application Version:    10.0.61637.0
  Application Timestamp:    46fadb14
  Fault Module Name:    weather.dll
  Fault Module Version:    10.0.61637.0
  Fault Module Timestamp:    46fadb59
  Exception Code:    c0000005
  Exception Offset:    0001542f
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033

 

Information on error code: c0000005 indicates it can be caused when an APP calls a memory location that is not present or too small.

I have restored my computer to an earlier time with no success.  I have a system image that is 2years old but would rather not use it if a solution can be found.  Am also considering the repair feature on my FSX disc?

Thank you for any help or thoughts.

WilliamB

System:

Win 7 Pro, i7-4790K, AMD RX580 8GB, 32GB Ram, FSX-10.061637.0, Orbx Central v4.1.39, Global Base Pack, Vector, Trees, Open LC North America, All North America Regions, Tongass Fjords,many Orbx Airports, Airport Pack.

 

 

 

 

 

 

 

17 minutes ago, WilliamB said:

Am also considering the repair feature on my FSX disc?

You will very likely run afoul of the FSX install validation routine, which is not longer available.  I ran into the validation issue about a year ago to date after building a new system.  I found that I needed to spring the $25 or so for FSX Steam Edition.  If you find it necessary to restore or reinstall from the disc then it is likely the course you will need to take.

Thanks for your information fppilot.  I thought that might be case as I had several problems setting up my FSX from disc several years ago.  I have installed FSXSE on another computer but have not fully set it up yet.  Am hoping to be able to correct this installation as it was working so well before this fatal error.  Looks like everything is working except for airports in eastern U.S and Canada.

Thanks again

WilliamB 

It's the weather.dll crashing--there's a pretty well-known problem with that dll crashing the sim when the wxstationlist.bin file gets corrupted, usually after the sim has experienced a disorderly shut down.  If you move that file (IIRC it's in the Weather folder under the FSX base directory) to another folder, FSX should re-create a new clean one next time you start it up.

Thank you,  w6kd.

I will try what you suggest and let you know what happens.

WilliamB

w6kd

I did as you suggested and on rerunning FSX without wxstationlist.Bin file in place a new file was not created.  I am not sure why.

I found an old backup of my FSX directory (5/18/2020).  I replaced the wxstationlist.Bin file and the weather.dll file with the same files from my older installation.  FSX still crashed.

I believe as you the problem has something to do with corrupt weather....files.  I was not aware of the weather folder until your reference.  I noticed a wxmapping.bin file in the weather folder.  It is interesting that the fatal error only occurs when the operating the Sim in eastern NAmerica and Canada.  Everything is fine in western NA and Canada?    

I think I recall that for some system files there is a specific way corrupt files must be handled to successfully replace them? 

I appreciate any further thoughts you may have.

Thanks for your help.

WilliamB

 

I discovered an earlier posting (March 15 2014) by jddelano  "Weather.dll Problem-FSUIPC4.dll   Support Pete Dawson Modules.  Pete indicated FSUIPC was not the problem but the program is one of the few in FSX that writes to .WX files and the wxstationlist.bin flies.  If any of these files are corrupt you will get a fatal.  One  solution is as w6kd stated above delete the wxstationlist.bin file found in the same folder as the FSX.CFG file.  Another solution is the delete the .WX files found in the documents "Flight Simulator X folder.  A final solution is to set the WeatherReadFactor in FSUIPC4.ini file (found in the Modules folder found in the main FSX folder) to zero.  This keeps FSUIPc from writing the Weather files.  It turned out that problem was a corrupt wxstationlist.bin file which I deleted and a new wxstation.bin was created the second time.

Thanks for your responses,  Saved me from reinstalling FSX or getting FSXSE

Edited October 8, 20214 yr by WilliamB
accidently posted before complete