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

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

Thank you, w6kd. I will try what you suggest and let you know what happens. WilliamB

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

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.

ThomasAH, Thanks for your reply, I have FSX on my steam account and may have to go that direction. Also am considering buy boxed version. They can be found on Amazon and Ebay but hoped that would not be necessary. WilliamB

I just finished building new computer for FSX. Installed Windows 7 professional. Installed a boxed MFS Gold Edition of FSX and Acceleration. I have had this addition since it was purchased new around 2013. Installed on two other computers without problem. This time FSX installed and activated: No problem. However Acceleration will not activate. Activation screen comes up, I enter the activation code from from my boxed copy and get an error that says : you have exceeded the allowed number of activations. I have only used the software four or five times so excessive activations does not seem correct. I realize my issue is little different and I am late to reply but any help would be appreciated. WilliamB I

Jethro, I ran FSX after saving the shader files, deleting the shader files from FSX and running FSX with an empty FSX (shaders) folder. It did not solve the problem. It looks like the FSX program does not get far enough to populate shaders/subfolders as all are empty. It would be interesting to know what causes the Black aircraft selection screen as this is immediately present in the first FSX screen. I don't know if it matters but I am running FSX in fullscreen mode with AMD Eyefinity enabled on three screens. Initially I wanted to change FSX display to windows mode but am unable to get to the FSX control menu to make such changes. I can change resolution but this results in FSX running on three screens instead of an expanded screen with the same problem. It looks like my only option is to try the FSX repair option and if that does not work delete FSX/Addons and reinstall completely. Something I was hoping to avoid. Thanks for your thoughts time and effort. WilliamB

Thanks Jethro, I will proceed and let you know how it turns out. WilliamB

Hello Jethro, Thanks for your help. I did find an article in the FSX times about redoing the shaders caches but it did not offer much explanation. I must be running DX9 as the shaders10 folder is empty while the shaders folder has several other folders each filled with files. I definitely believe your advice regarding saving the Shaders folders is sound and will do it. I have two questions: 1. After saving the FSX folder with the shaders in it, should I delete the shaders folders and leave the empty FSX folder or just delete the FSX folder as well, 2. I have two shader cache lines in my FSX.cfg [graphics] area SHADER_CACHE_PRIMED_10=1693500672 SHADER_CACHE_PRIMED=1693500672 Should I delete them or leave them alone? I really appreciate your thoughts! WilliamB

MadDDogz, I am not familiar with shaders. I did see two shader cache lines under [graphics] in the FSX.cfg file but I don't know what they do or how to rebuild them. I don't have new card. I did, however, install a driver update. How does one rebuild shaders? Thanks for your thoughts. WilliamB

Charlie, I removed the dll.xml file from my FSX.cfg. Ran FSX and the same problem remained. I wish it had worked. Thanks. WilliamB

Charlie, I will be patient and see what other suggestions may come. I have looked at my FSX.cft file but will check it again. Also will review all FSX related files to determine what should be removed and saved in the event i have to do a repair. Thanks WilliamB

Thanks very much for your advise, Charlie! I am not familiar with the "repair" option. Is there a location that describes the process? Is it listed on the original FSX Gold Edition discs? WilliamB

After updating my AMD RX 580 graphics card, FSX initial screen opened but had completely black aircraft selection screen. All other items worked correctly. When the fly key was pushed the screen was black and vibrating, scenery loading was attempted, and FSX locked up. I restored my computer to an earlier time when FSX and the graphics driver were functioning. I uninstalled and reinstalled an old and new graphics driver several times. Neither action solved the problem. I searched several FSX forums and found this issue has occurred in past mostly on earlier MS Flight Simulater versions. No recommended solutions found solved my problem. I can like to avoid a complete reinstall of FSX and addons. I would appreciate any possible solutions to this problem anyone may have. Thank you. WilliamB Asrock Z97M OC Formula MB, lntel i7-4790 CPU@4.00GHz, 16GB RAM, Samsung SSD 850 EVO 1TB, AMD RX 580 8GB Graphics Card , Windows 7 Home Edition 64bit, Boxed Version FSX Gold Edition with Acceleration