FSX compromised after power outages

BoeingvsAirbusNKL

Charter Member
Hey, I haven't been posting due to computer issues thanks to power outages... and fsx is one of the programs compromised.

In terms of things, it does more crash to desktops than normal and sceneries that was updated before the outages no longer work properly.

What should i do to get it back to normal?
 
It would be helpful if you would post the error messages in the eventviewer of windows that your get after a CTD!

Priller
 
Sorry, I cannot get the error messages... event viewer cannot create the snap-in.
It also sucks that my computer is also compromised due to vandals severing Xfinity network in Chester County, PA.
 
Can you tell us something about your rig? Hardware, Windows version and so forth?

Reason I ask is because I think that you're looking at a reinstall of your machine.

Priller
 
I have an ASUS PC, started at Windows 7 but upgraded to Windows 10, amount of RAM is unknown but plentiful, but it cant be upgraded to Windows 11 due to age of the computer and compatibility issues.

As for actual errors, the sim crashes when i am coming in to land at the predetermined airport... but i can takeoff and fly fine, but frame rate is not optimal.
 
Every PC can be installed with Win11 mate!


The tool that is discussed in that thread, Rufus, I use it myself. Not for bypassing the hardware checks, but for the privacy, local account and telemetry.

Priller
 
Does your computer/FSX make periodic single beeps when you are reaching the end of a flight by any chance? Is it always the same aircraft that it crashes with? Are you running complex add-on scenery packages/airports?

I am wondering if you are encountering the dreaded 'Out of Memory' error (OOM) which can happen with FSX (a lot) and is the main reason I finally moved to P3D towards the end of last year. We are not talking about the amount of physical RAM on your memory sticks but the amount of virtual RAM that Windows uses which is known as the Virtual Address Space or 'VAS'. With a 64 bit operating system and a 32 bit sim like FSX you will have roughly 4 Gb of VAS available. As you use your sim on a flight this VAS allocation starts to fill up with all the scenery textures and building models you fly over but it doesn't get emptied again until you re-start a flight. Sometimes the scenery is so complex that it fills all the available space and you hit the OOM error.

It's not only scenery files that can cause it though as some complex aircraft can cause OOM errors too. Myself and another SOH member discovered that a particular payware aircraft had a major issue in multiplayer. If we used the aircraft alone we never saw an OOM error but if we were both in the same aircraft in multiplayer then one or both of us would have a sim crash with an OOM error within a couple of minutes of flying together! It turns out that the aircraft has a 'memory leak' on one of the gauges or DLLs in multiplayer and it gobbles up the VAS at an alarming rate. The only work around we found was that if we both wanted to fly that particular aircraft in multiplayer we would have to put the other player into a different aircraft in the multiplayer tool we were using to make the connection (i.e. FSHost or JoinFS). As long as we didn't see two of the same aircraft in the sim we were good to go.

Here is an article I just found that may explain the issue more for you: https://kostasfsworld.wordpress.com/fsx-oom-and-addon-vas-usage/

The fact that the problem occurs towards the end of a flight could indicate an OOM problem even if you don't get a beep.
 
Following in tako's line of thought, if you had your system crash, there may be remnant scraps of files in your VAS.

Here is a tutorial for cleaning this space out.

Snuffy, I did the process with registry editor. FSX now works! Thank you for the suggestion.
 
Back
Top