Hello fellow nerds,

I have recently had a problem with flying long-haul flights. Many times when I leave the computer unattended for a long period of time during the flight it gives me either the usual OOM error or a Microsoft Runtime error. Yesterday I flew from Zurich to Tokyo in real time over the whole day (almost 12 hours) and I had no issues at all since I was using my pc over the whole period (mostly watching YouTube or Twitch on Google Chrome whilst keeping an eye on the sim). After finishing that flight I wanted to fly back yesterday evening over the night. So I did everything as usual and started the flight, put the aircraft on Auto-Cruise (Auto stepclimbs and pause at top of descent) and went to bed to then land in the morning. This morning I then saw that apparently FSX had run "out of memory" and would of course close.

Now obviously you might think I didn't keep an eye on my VAS (Virtual Address Space) for FSX not exceeding 4GB. The aircraft I was using was the PMDG 777-300ER and the sceneries I use for Tokyo Narita and Zurich are only AFCADS, so no high quality textures. I also don't use any global texture add-ons or similar stuff. Also after I had taken off at Narita and was at cruise level I saved the flight, closed the sim disabled the RJAA scenery and opened it up again to load and continue the flight. At this point the only add-on scenery the sim has to load is the AFCAD for Zurich and everything continued normally at this point. All of this meaning that the last time I checked the VAS before leaving the sim unattended to go to sleep was around 2,6-2,8GB or so... 

At that time I was 100% sure that if the sim was to crash during the night, it would not be caused because of an OOM error. Well, here I am :)

I have done similar flights were I would leave the sim unattended in the same way and I had no erros whatsoever and could land with enough VAS left to spare.

All in all my problem is here: Why would FSX crash with an OOM if all measures were taken to eliminate that exact problem?

I just don't understand...

But of course we all still flying FSX have to treat it with patience and love to make this 2006 game worth, which I think it really is :)

Thank you for your time even for only reading through this.

 

Welcome to Avsim!

Not sure what happened to make FSX:SE crash, but perhaps a background program updated itself or antivirus software started an automated scan and caused FSX:SE to crash.  FSX is well known for VAS management problems, FSX:SE is better at VAS management, but not immune to OOM errors.

42 minutes ago, stans said:

Welcome to Avsim!

Not sure what happened to make FSX:SE crash, but perhaps a background program updated itself or antivirus software started an automated scan and caused FSX:SE to crash.  FSX is well known for VAS management problems, FSX:SE is better at VAS management, but not immune to OOM errors.

Hi 🙂

After posting this a few hours ago I took a look at the Windows Event Viewer and apparently Windows tried to install an update... so that might be the reason for this rather surprising crash of FSX...

I turn off all automatic updates.

On 2/17/2021 at 3:20 AM, Eaglemotion said:

All in all my problem is here: Why would FSX crash with an OOM if all measures were taken to eliminate that exact problem?

It's why people moved on to 64bit to eliminate crashes on long haul flights and complex aircraft/scenery. There is no explanation and years of research.