Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Virtual Memory error.

Featured Replies

You're getting a virtual memory error because the sim is requesting more virtual memory from the operating system than Windows is making available on its default automatic setting. Definitely change your Windows virtual memory from automatic to manual -- at least 16GB (I set it on my main C drive and the drive where the sim is installed). This has stopped all crashes on my PC. You have to set minimum and maximum VM, and it should be in line with your real RAM. You have 16GB physical RAM, so set VM to max 16GB (value 16000 in the settings) and a minimum of 8GB (value 8000 in the settings).

Setting max VM to 16GB is "the same as" installing an extra 16GB of physical RAM, except that it's slower than your physical RAM. But it will work and costs nothing.

Obviously you need to be able to spare the 16GB on your drive; if you only have 4GB of disk space left, you can't set VM higher than that (and wouldn't recommend setting it anywhere near the limit of your available hard drive/SSD space).

Edited by March Hare

12 minutes ago, March Hare said:

You're getting a virtual memory error because the sim is requesting more virtual memory from the operating system than Windows is making available on its default automatic setting. Definitely change your Windows virtual memory from automatic to manual -- at least 16GB (I set it on my main C drive and the drive where the sim is installed). This has stopped all crashes on my PC. You have to set minimum and maximum VM, and it should be in line with your real RAM. You have 16GB physical RAM, so set VM to max 16GB (value 16000 in the settings) and a minimum of 8GB (value 8000 in the settings).

Setting max VM to 16GB is "the same as" installing an extra 16GB of physical RAM, except that it's slower than your physical RAM. But it will work and costs nothing.

Obviously you need to be able to spare the 16GB on your drive; if you only have 4GB of disk space left, you can't set VM higher than that (and wouldn't recommend setting it anywhere near the limit of your available hard drive/SSD space).

How long do you play, what are your settings, what are you flying and where? Your fix is not a guaranteed fix and not entirely accurate though it doesn't matter. I have done everything you have said just like I stated in my comment before this and it changes nothing except time and even then it isn't guaranteed. It should at the very least buy the OP some time and hopefully allow him to get a good 20-30min depending on his settings but everything I have seen so far shows it will still fill the pagefile and crash eventually. If I set a max of 16GB it will fill the 16GB then crash. If I set 50GB it will fill 50GB then crash. If I leave it system managed it will sometimes last longer but will eventually fill the drive completely and crash. Completely thrashing the ssd the pagefile is on. The longer you play the bigger it gets. That is at least the case for many of us. Chances are people that haven't looked at that or didn't know what you said have a system manged pagefile that will get as big as it needs to. My last crash from FS thanks to vm says "flightsimulator.exe (13728) consumed 20701437952 bytes". That is over 20GB of pagefile and at that time of crash the game was requesting an additional 36GB of pagefile showing a total of ~57GB commited in HWinfo. 

For the people having VM problem, curious to know what GPU's and CPU's you are using? Running RAM set to XMP in UEFI/BIOS? Keep in mind that the VM overflow is a resultant symptom of another problem, not the problem itself. Adjusting the VM size will then have little effect, other than perhaps delaying the inevitable crash by a few minutes. If your system is relying so heavily on VM, it is going to be slow. Even on an SSD, VM is far slower than RAM. 

 

 

 

GregH

Intel Core i7 14700K / Palit RTX4070Ti Super OC / Corsair 32GB DDR5 6000 MHz / MSI Z790 M/board / Corsair NVMe 9500 read, 8500 write / Corsair PSU1200W / CH Products Yoke, Pedals & Quad; Airbus Side Stick, Airbus Quadrant / TrackIR, 32” 4K 144hz 1ms Monitor

I'm betting that we have a few wild pointers in the code, and fiddling with the pagefile just moves the "hit" spot to somewhere less volatile.

Specs: Win10, 4790K, nVidia 1080ti, Saitek Yoke+Quadrant+Radio/Switch and AP panels, VRInsight 737 overhead, Virtual Avionics 737 MCP. 3 x 1440*900 main display + 1024*600 VDU display. NLR V3 Motion seat. Oculus DK2 CV1 HTC Vive VR headsets.

1 hour ago, Mrcrunch said:

How long do you play, what are your settings, what are you flying and where? Your fix is not a guaranteed fix and not entirely accurate though it doesn't matter. I have done everything you have said just like I stated in my comment before this and it changes nothing except time and even then it isn't guaranteed. It should at the very least buy the OP some time and hopefully allow him to get a good 20-30min depending on his settings but everything I have seen so far shows it will still fill the pagefile and crash eventually. If I set a max of 16GB it will fill the 16GB then crash. If I set 50GB it will fill 50GB then crash. If I leave it system managed it will sometimes last longer but will eventually fill the drive completely and crash. Completely thrashing the ssd the pagefile is on. The longer you play the bigger it gets. That is at least the case for many of us. Chances are people that haven't looked at that or didn't know what you said have a system manged pagefile that will get as big as it needs to. My last crash from FS thanks to vm says "flightsimulator.exe (13728) consumed 20701437952 bytes". That is over 20GB of pagefile and at that time of crash the game was requesting an additional 36GB of pagefile showing a total of ~57GB commited in HWinfo. 

Obviously I've misremembered information from days gone, but all I can say is it's worked for me. Not had a crash since I made these changes.

I'm researching page filing/VM at the moment. I appear to be correct in terms of it acting as a RAM overflow but slower than physical RAM of course, and correct to have set up VM on more than one drive to improve performance (SSD and M.2 SSD). Recommendation from a couple of sources is now to set the VM minimum at 1.5 times your physical RAM (and Windows certainly doesn't do that on its automatic default).

But what I've done is working for me right now. On ultra settings, flying for a couple of hours in different locations, sometimes in different Cessna's and also in the A320neo.

On 8/21/2020 at 11:47 AM, Bilal2104 said:

have 16gb ram but software shows i only ever use like 11gb or so. 

This is for a couple of reasons, the most obvious one is that running your flight sim is not the only thing your PC has to do, it has to run the O/S, any other programs you are using, etc.

But, that's not the major reason you won't see your sim using all of the RAM for this procedure, t's because when your computer is pushing data bout all over the place, it needs to keep some back for running the sim, as well as having some for doing that page file process.

Alan Bradbury

Check out my youtube flight sim videos: Here

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.