Hello,

I had a really good copy of FSX running on my previous machine. I was able to run on medium/high settings with addons airports that I was flying to activated no problem. However, the hardware reached the end of its life and I now have new hardware.

I have followed the avsim Install bible and have copied across the root folder from my old hardware to my new hardware and I also copied across the scenery.cfg. 

I tested the sim by loading in Edinburgh and it worked no problem. However when I try to load the sim in Miami or Tampa, I run into a OOM error at about 80% 

The new hardware is more capable then the previous hardware and the sim files are the same on both hardware. I'm stumped as to what could be causing this. Does anyone have any idea what could be causing this issues specifically in florida or the new hardware even though it works fine on the old hardware? 

21 hours ago, Mattie941 said:

Hello,

I had a really good copy of FSX running on my previous machine. I was able to run on medium/high settings with addons airports that I was flying to activated no problem. However, the hardware reached the end of its life and I now have new hardware.

I have followed the avsim Install bible and have copied across the root folder from my old hardware to my new hardware and I also copied across the scenery.cfg. 

I tested the sim by loading in Edinburgh and it worked no problem. However when I try to load the sim in Miami or Tampa, I run into a OOM error at about 80% 

The new hardware is more capable then the previous hardware and the sim files are the same on both hardware. I'm stumped as to what could be causing this. Does anyone have any idea what could be causing this issues specifically in florida or the new hardware even though it works fine on the old hardware? 

• What's your new hardware specs ?
• Also what version of FSX is being used ?

FSX is a 32 bit program meaning it has built in memory usage limits no matter how much ram your hardware has installed, personally I've used P3D v4.5 and I migrated my FSX SE collection over to that P3D version and have been able to fully load all my scenery and aircraft without any OOMs as P3D 4.5 is 64bit. I was even able to migrate a collection of FSX's default aircraft.

Here's the FSX default C172 migrated over to P3D x64

But back to FSX...

Typically the memory limits for the disk versions of FSX is 2 GB, or 4 GB if the Large Address Aware flag is set, noting the Steam FSX release is the only version I'm aware of that does have the LAA flag set by default.

Here's some links to further OOM info:

https://support.precisionmanuals.com/kb/a108/vas-management-stopping-out-of-memory-oom-errors.aspx

https://steamcommunity.com/app/314160/discussions/1/4149455258718448414

https://steamcommunity.com/app/314160/discussions/0/1291817208500306625/

Something else you might want to look at is JJ FSX's guide on "Install FSX on Windows 11 SUCCESSFULLY the first try...or the second if your already in trouble." available at the below link.

https://steamcommunity.com/id/JJFSX/myworkshopfiles/?section=guides&appid=314160

I also remember people in the Steam discussions talking about a customised Windows Virtual Memory configuration giving good results for OOM issues, you'd have to search for those topics yourself though...

Cheers 🙂 

hope the above helps and let us know how you get on.

I found the issue. I had copied some AIG traffic.bgl files over from my old machine using onedrive. I think some of them must have corrupted as re-downloading them and replacing them has fixed my issue. 

Edited January 5Jan 5 by Mattie941

No. I did not find the issue. I have upgraded to a MEDION Erazer Major from my Medion Erazer P6661.

I have installed FSX as per the bible and copied across game files from my old laptop. For reference, on my old laptop I could run 12 hour+ without OOM issues. However, on my new laptop I run into OOM issues after 1-2 hours. 

The game settings, FSX.cfg settings and nvidia settings are the same on both laptops. 

Why am I getting OOM issues on my newer, higher spec laptop?

I also have exactly the same issue running rFactor.

Edited January 16Jan 16 by Mattie941

On 1/17/2026 at 8:28 AM, Mattie941 said:

No. I did not find the issue. I have upgraded to a MEDION Erazer Major from my Medion Erazer P6661.

I have installed FSX as per the bible and copied across game files from my old laptop. For reference, on my old laptop I could run 12 hour+ without OOM issues. However, on my new laptop I run into OOM issues after 1-2 hours. 

The game settings, FSX.cfg settings and nvidia settings are the same on both laptops. 

Why am I getting OOM issues on my newer, higher spec laptop?

I also have exactly the same issue running rFactor.

I circle back to the two original questions asked, being...

• What's your new hardware specs ?
• Also what version of FSX is being used ?

The Erazer Major comes in several different hardware spec varieties, which one is it?

And what is the version of FSX?

Circling back to FSX being a 32 bit program, the disk version of FSX will only be able to access 2 GB of ram no matter how much ram your new machine has. You can however patch the fsx.exe to set what is known as the Large Address Aware flag to enable FSX to use the full 4 GB of ram a 32 bit program can access, the links previously provided do contain further info.

You can download a 4 GB patcher from https://ntcore.com/ noting there are other patching tools available, up to yourself really.

Note FSX-SE (The Steam edition) by default has the 4 GB patch applied (as well as a collection of fixes the disk version doesn't contain), hence the question of what version of FSX are you using? because if you're already using FSX-SE, then there would likely be something else going on. 

You're probably also experiencing the same issue with rFactor which is 32 bit, as compared to rFactor 2 which is 64 bit, if it's the 32 bit version try the 4 GB patcher on that too and see if it helps.

Could also be some weird hardware thing going on, bad ram for example, laptops will usually have a diagnostics option on boot up, might be worth investigating.

Cheers

PS. I just realised you've mentioned coping game files from one machine to the other, does this mean you're not actually running the FSX installer program?

Edited January 17Jan 17 by Rogen
PS

12 hours ago, Rogen said:

I circle back to the two original questions asked, being...

• What's your new hardware specs ?
• Also what version of FSX is being used ?

The new laptop is a MEDION Erazer Major 16 X1 16" Gaming Laptop – Intel® Core™ Ultra 9, RTX 5070 Ti, 2 TB SSD and I'm using the FSX boxed edition with FSX acceleration boxed. 

I have tried the 4GB patch but it doesn't seem to have made a difference. 

12 hours ago, Rogen said:

PS. I just realised you've mentioned coping game files from one machine to the other, does this mean you're not actually running the FSX installer program?

No. I installed the game as per The Bible (from chapter 4 onwards). I only copied across Addon Scenery, Effects, Textures, Simobjects, etc. 

 

13 hours ago, Rogen said:

You can download a 4 GB patcher from https://ntcore.com/ noting there are other patching tools available, up to yourself really.

I just tried the patch and it did not fix the issue. I still hit an OOM after ~1 hour

  

13 hours ago, Rogen said:

Could also be some weird hardware thing going on, bad ram for example, laptops will usually have a diagnostics option on boot up, might be worth investigating.

I've just run the Medion diagnosis tool and it did not find any errors. 

Edited January 18Jan 18 by Mattie941

On 1/18/2026 at 10:34 PM, Mattie941 said:

The new laptop is a MEDION Erazer Major 16 X1 16" Gaming Laptop – Intel® Core™ Ultra 9, RTX 5070 Ti, 2 TB SSD and I'm using the FSX boxed edition with FSX acceleration boxed. 

I have tried the 4GB patch but it doesn't seem to have made a difference. 

No. I installed the game as per The Bible (from chapter 4 onwards). I only copied across Addon Scenery, Effects, Textures, Simobjects, etc. 

Ok, that looks a good spec machine, I do know P3D is having issues with the display of certain special effects and 5000 series GFX cards, you can read about it at the below link.

https://www.prepar3d.com/forum/viewtopic.php?t=155789

Apparently LM have notified Nvidia and Nvidia are working on a resolution, that said there are many other bugs and inconsistencies in the 5000 series GFX card drivers affecting many different games, hopefully the drivers will mature and the majority of issues will be resolved sooner rather than later.

Note that although FSX is not P3D, the two sims are closely related and do have a high degree of inter-functionality of addins, do you see any of the issues reported at the forum link ?

 

The 4 GB patch would have set the Large Address Aware flag in the fsx.exe file headers, you can use Wumpbin to confirm and I would expect to see "Application can handle large (>2GB) addresses" in the file headers.

https://www.benf.org/other/wumpbin/index.html

 

Is the memory issue an actual OOM generated by FSX ? i.e. does a warning dialog open ? Or does it just crash outright ?

You might want to run a VAS monitoring tool, the links previously provided and Google should help you find a suitable tool, with a monitoring tool you can see when VAS is approaching limits and with the tool help identify what is using VAS to the point of running out.

Also the Windows Event Viewer will likely help as crash events are typically recorded in the Windows logs, use Google if needing help to understand the use of the Windows Event Viewer.

A process of elimination could be the ultimate troubleshooting path to follow, time consuming though... i.e. disable addins and test, then add each addin back one at a time and retest, I typically have a saved scenario for such testing purposes so as to replicate the same flying scenario each test.

I do recall not having OOMs with just default FSX and it wasn't until I'd began chocking up on addins (especially scenery) that I began to hit OOMs.

 

Unfortunately I'm unable to access the Bible link (login required), but if you're first installing FSX via its disks then all should be properly set up and if the laptop self diagnostics don't record any issue then all should be good in that regard.

I assume you've the HIGHMEMFIX=1 under the [GRAPHICS] heading in the fsx.cfg ?

The only other thing I can think of is to trial an alternate virtual memory configuration, like the one discussed at the below link.

https://steamcommunity.com/app/314160/discussions/0/787664259085542515/#c787664386892244402

 

Of course VAS OOMs are always going to be an issue with 32bit programs, that's why I went P3D x64 as soon as it was practical.

Cheers

On 1/19/2026 at 11:52 PM, Rogen said:

...I do know P3D is having issues with the display of certain special effects and 5000 series GFX cards...

That's interesting. I have raised a ticket with Nvidia. Lets see what they come back with. 

 

On 1/19/2026 at 11:52 PM, Rogen said:

Is the memory issue an actual OOM generated by FSX ? i.e. does a warning dialog open ? Or does it just crash outright ?

Yes. FSUIPC gives the OOM warning alarm for a period beforehand and then the sim crashes. 

 

On 1/19/2026 at 11:52 PM, Rogen said:

You might want to run a VAS monitoring tool, the links previously provided

Would a back to back test of this between my old and new laptops be useful?

 

On 1/19/2026 at 11:52 PM, Rogen said:

I assume you've the HIGHMEMFIX=1 under the [GRAPHICS] heading in the fsx.cfg ?

Yes I have added this 

 

On 1/19/2026 at 11:52 PM, Rogen said:

The only other thing I can think of is to trial an alternate virtual memory configuration, like the one discussed at the below link.

I'll give this setup a test and report back.

 

 

I have also installed a copy of Windows 10 that I can dual boot to. Windows 10 seems to be slightly more stable than Windows 11. The crashes happen after ~5 hours now instead of ~1 hour. 

I think I have managed to find a stable solution. Here's my fix for anyone that's also crazy enough to try and run FSX on modern hardware: 

• Install windows 10 as dual boot
• Do not install nvidia drivers and only use windows 10 with the igpu
• Set the page file limit to match the igpu (128MB)
• Reduce FSX screen resolution (I use 1680x1050)
• Disable full-screen optimizations in the fsx.exe properties
• add "MAX_ASYNC_BATCHING_JOBS=1" to the [SCENERY] section of the fsx.cfg:
• Add "AffinityMask=14" to the [JOBSCHEDULER] section of the fsx.cfg to limit the game to use 3 P-cores and avoid hyperthreading or E-cores
• Reduce some in game settings
• All other settings set as per The Bible previously referenced 

That's the challenges of running old games on new hardware I guess 🤷‍♂️

That's a lot of work.  I have the Steam Edition of FSX running on my Windows 10 system and it runs great.

Well i was wrong... I thought that had solved the issue but I ran into another error this evening. FSUIPC game the VAS chime and then the game crashed with the error message

"Your computer has run out of available memory. Please restart Flight Simulator and select different graphics, scenery or traffic settings."

I'm officially stumped. I have no idea how to get FSX working again 

It's almost certainly some bad scenery. You'll need to disable it one by one until you find the offender.

Cheers

I have done some testing and the problem is linked to when I am flying. When I fly, I run into an OOM error. When I'm parked at a busy airport with AI and other settings maxed out the sim runs for hours without OOM (it has not crashed yet in testing).

I can test with turning all scenery off. However, I have the same scenery on my current laptop that I had on my old laptop so I'm not sure why it would only be causing an issue now? 

Why would I be hitting OOM when flying but not when parked?

 

On 2/4/2026 at 12:05 AM, Mattie941 said:

Well i was wrong... I thought that had solved the issue but I ran into another error this evening. FSUIPC game the VAS chime and then the game crashed with the error message

"Your computer has run out of available memory. Please restart Flight Simulator and select different graphics, scenery or traffic settings."

I'm officially stumped. I have no idea how to get FSX working again 

One thing to consider is that maybe your new specs are too good? I had something similar happen to me when I upgraded my hardware : my new computer loaded scenery, etc. to efficiently and suddenly VAS became a problem (even with all my resized textures, etc.). Maybe try lower your settings quite a bit? Personally, I finally gave up on FSX at that point and moved to P3Dv5.4. 

Edited February 6Feb 6 by Blasb