Hello I have Microsoft Flight Simulator X Steam edition. 

Running on 1024x768x32 resolution

Highmemfix=1 is enabled in my config

I track my VAS with procexp program. I see that it crashes exactly at 2000mb. I am running WINDOWS 10 64BIT, but why i am limited to 2gb VAS, shouldn't it be 4gb VAS? 

I have only FSLABS CONCORDE X, no other add-ons. And yes, my license is legal.

If there's no message, how do you know it's an OOM?

1 minute ago, Bob Scott said:

If there's no message, how do you know it's an OOM?

Because I monitor procexp and I see that it crashes exactly on 2000mb VAS. Additionaly, I made my FSX run as windows 7 and now it works just fine

32 minutes ago, Metrooff said:

Because I monitor procexp and I see that it crashes exactly on 2000mb VAS. Additionaly, I made my FSX run as windows 7 and now it works just fine

When VAS is dangerously low FSUIPC would start beeping. Do you have a registered version? What offset is that program monitoring?

I fly that aircraft in P3D v3.4 with Windows 10 but the same VAS rules apply. It only becomes unstable once < 300Mb of VAS remains. And it doesn’t just CTD. A message will be displayed.

1 minute ago, Ray Proudfoot said:

When VAS is dangerously low FSUIPC would start beeping. Do you have a registered version? What offset is that program monitoring?

I fly that aircraft in P3D v3.4 with Windows 10 but the same VAS rules apply. It only becomes unstable once < 300Mb of VAS remains. And it doesn’t just CTD. A message will be displayed.

Ok so it turns out that it was actually not VAS error. I just got crashed again

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: MSVCR80.dll, version: 8.0.50727.9672, time stamp: 0x5db2b1b8
Exception code: 0xc000000d
Fault offset: 0x00008aa0
Faulting process id: 0x4b58
Faulting application start time: 0x01d9a4fdd2196a87
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9672_none_d08f9da24428a513\MSVCR80.dll
Report Id: 14d4ddcf-fe0c-4f68-8fd4-c0830c3caef1
Faulting package full name: 
Faulting package-relative application ID: 

I do have FSUIPC, but not registered one.

 

Also, have you tried verifying your game files for FSX-SE?  Never hurts!

To verify your game files please do the following:

1. Load the Steam platform and log into your account
2. Click the Library tab in the menu at the top of the screen
3. Click the List View from the view options on the top right of the screen
4. Right click on Microsoft Flight Simulator X: Steam Edition to bring up a popup menu
5. Click on Properties from the popup menu to bring up another popup box
6. Click on Local files from the popup box menu
7. Click on Verify integrity of game cache from the Local file options
8. Wait for the progress bar to finish verifying your files. Additional files may download
9. Restart Steam
10. Restart Microsoft Flight Simulator X: Steam Edition 

or

1. Log on to Steam
2. Select "View Games Library" from the "Games" menu
3. Right-click the Microsoft Flight Simulator X: Steam Edition icon and select "Properties"
4. Select the "Local Files" tab and click on "Verify Integrity of Games Cache"
 

3 minutes ago, Metrooff said:

Faulting module name: MSVCR80.dll, version: 8.0.50727.9672, time stamp: 0x5db2b1b8

I doubt Googling that dll will reveal much info. How far into a flight is the problem happening? You must start FSX with a default aircraft. The Cub is ideal. Then at the Flight screen where you can choose airport, aircraft etc. select Concorde there.

Make sure you run with Admin rights. Essential when FSX is in the Program Files (x86) folder.

1 minute ago, Ray Proudfoot said:

You must start FSX with a default aircraft. The Cub is ideal.

I thought that apply only for P3D.

1 minute ago, Ray Proudfoot said:

How far into a flight is the problem happening?

25 Mins. Reaching 1.7M (Not every time though, sometimes while being on ground).

20 minutes ago, Metrooff said:

I thought that apply only for P3D.

25 Mins. Reaching 1.7M (Not every time though, sometimes while being on ground).

Absolutely not. It applies to all 32-bit versions of FSX and P3D. You can usually tell there are problems as the primary instruments don’t function correctly.

Change your startup flight and use the Cub. That should sort it.

For info, the 64-bit FSL Concorde is currently in beta. You’ll need P3D v5.

My default flight for FSX was the Baron58 setup for a cold and dark start.  I NEVER started FSX using my default flight!

1 minute ago, charliearon said:

My default flight for FSX was the Baron58 setup for a cold and dark start.  I NEVER started FSX using my default flight!

Unless you’re loading a complex 3rd party aircraft that will never be a problem. But Concorde is extremely complex and the simplest aircraft needs to be loaded until the Flight screen where you can select another. Concorde eats several hundred Mb of VAS.

4 hours ago, Metrooff said:

Ok so it turns out that it was actually not VAS error. I just got crashed again

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: MSVCR80.dll, version: 8.0.50727.9672, time stamp: 0x5db2b1b8
Exception code: 0xc000000d
Fault offset: 0x00008aa0
Faulting process id: 0x4b58
Faulting application start time: 0x01d9a4fdd2196a87
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9672_none_d08f9da24428a513\MSVCR80.dll
Report Id: 14d4ddcf-fe0c-4f68-8fd4-c0830c3caef1
Faulting package full name: 
Faulting package-relative application ID: 

I do have FSUIPC, but not registered one.

 

That crash is happening in the Visual C Runtime library...I'd start by reinstalling all of the runtimes (they exist in parallel in what Windows calls side-by-side libraries).

See: https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/

Then I'd run sfc /scannow and dism to check for any other system-level file corruption.

Highmemfix is no longer needed in FSX:SE, as it's set by default without a config file entry.

A four-hour run of Memtest86+ to make sure your RAM is stable wouldn't be a bad idea either.

Now I catched it! Event logger is not showing any type of errors. I was in midflight, around 1 hour and 20 min. At 1980mb all instruments stopped working. I did as Ray said - first load piper and then the Concorde.

Load the Piper and locate to your chosen airport. Note the amount of memory used.

Now load Concorde. How much does it change?

It’s unusual to run out of VAS mid flight. Are you over ocean when it happens? What are your departure and destination airports?

A little trick to recover VAS. Toggle in and out of windowed mode.

Did you do as Bob suggests? If you’re going to stay with FSX I would encourage you to buy a FSUIPC licence. You will be able to monitor VAS which is not the same as available memory.

Alternatively, lower your settings. What works for a simple aircraft won’t for Concorde.

35 minutes ago, Ray Proudfoot said:

Load the Piper and locate to your chosen airport. Note the amount of memory used.

968,368mb

37 minutes ago, Ray Proudfoot said:

Now load Concorde. How much does it change?

After loading concorde - 1799,344mb

So 830,976mb difference.

39 minutes ago, Ray Proudfoot said:

Are you over ocean when it happens? What are your departure and destination airports?

EGLL - KJFK

Over the ocean, around 300nm from land

39 minutes ago, Ray Proudfoot said:

Did you do as Bob suggests?

Yes

40 minutes ago, Ray Proudfoot said:

Alternatively, lower your settings.

My resolution is the lowest that could ever be. 

Everything is set to the lowest possible settings.