Finally.....Solved CTD issues... for those of us with < 32 GB ram

Up until a week ago I would have agreed with you, but changing the page file manually solved some crashing issues for me.

2 Likes

Must be something lying around in your OS. Since ALPHA I have rarely had a CTD now that we are on a more stable platform it still rarely CTDS with 32gb unless I do something silly like an unstable OC.

Leaving the OS manage the page file will allow it to automatically grow it when needed. If your issue is solved by a bigger page file then OS controlled would have done the same thing.

2 Likes

yep, that’s what should happen. For some obscure reason though, it’s not. Or maybe the OS is doing it too slow.

Still; fact is that my random crashes stopped happening after I set the cache manually. You can argue all you want with logic, doesn’t change the fact that it worked.

7 Likes

I don’t follow. This is my whole reason for posting the topic. Windows was managing my pagefile and I was ready to toss MSFS because it was unplayable. Perhaps letting the OS manage the pagefile works if you have 32 GB or more of physical mem but from my perspective, it doesn’t work.

2 Likes

yes… normaly “system-managed” mean that windows can increase the pagefile.
But the whole “internet” is full of reports that this not works in each case as expected and therefore the hint with manual setting.
I also not know why some users say “no” to users where this hint/setting helped.

There exist a rule in which way windows can increase the pagefile.
Possible the issues comes because of volume size on which the pagefile lies, in special for smaller SSD. But so far I know, it should also with a 250gig ssd still enough.

The docu about the rule can you find here. But I’am not sure whether this is realy the current one, seems outdated.

3 × RAM or 4 GB, whichever is larger. This is then limited to the volume size ÷ 8. However, it can grow to within 1 GB of free space on the volume if required for crash dump settings.

It most certainly works for me, exactly as you say.

I thought I would run a test to verify this.
I have, as you probably know, a 16 gig ram setup, and had previously set my system to manual values.

If I return my manual settings to “system managed”, in most situations, I can’t even start the sim, CTD.

When I am able, it doesn’t last too long, and will only boot up with default non-complex planes and default scenery.
Constant CTD with system managed, no CTD’s at all without.

1 Like

HI.
i9-9900K, GTX 1660ti, 32GB Memory 3400Mhz,
Samsung 970 EVO Plus M.2 NVMe SSD 500GB (C:\ = Win 10
@100GB, D:\ = FS2020 @ 400GB)

Additional 32 GB Memory 3600 Mhz added.

I really like it and was worth every penny.

In general, everything works quicker. Not faster. Just quicker responding it seems like.

Didn’t buy for general. Bought for FS2020.

For FS2020, I am amazed at the difference since the posts did not indicate there was much if any.

FS2020

  1. Mouse - Any mouse click or controller input results in a very fast
    response on the screen.
  2. Colors - There are additional colors or brighter colors on the
    screen and the cockpit seems easier to see
  3. Scenery - There is additional scenery and additional detail in the
    scenery. It looks more colorful. Hard to describe.
  4. Page file - None configured but both SSDs set to “Manage” by
    Windows.
  5. Memory Used - Was around 17GB before. Increased to 26GB
  6. CPU usage increased with scenery. Was previously always in the mid 20% while flying. Two pictures below, one was 48% and other was 34%.
  7. GPU usage seems to reduce from a previously always 100% to
    93% sometimes.
  8. Flying the Citation CJ4, external view, watching it on level flight,
    it seemed to float. Just a little slight bounce/nudge/wing dip
    slightly. I thought when I noticed it, maybe that is the air currents
    hitting it.
    I have spent many hours before behind it and it seemed fixed. As
    in, it would go up, down, roll left or right but did not show any
    results from air currents that I noticed.

The additional graphics and more vivid graphics and additional detail make this investment justifiable to me. I don’t know why. Same graphics card and CPU.

Two screenshots:
One taking off the runway at JFK, New York

One flying over New York City

And yes, flight is smooth even with 15 to 25 FPS.
I am pleased.

1 Like

it just no longer use the pagefile :wink:

Don’t forget that you can now, 64gig RAM, set your pagefile to e.g. 1Min/4Max. Otherwise windows will possible reserve 9Gig which you will never need.

MichaMMA,

I was just discussing with CasualClick.

What size page file should I use?[quote=“CasualClick, post:20, topic:250773”]
The use of a page file has it’s advantages, even if you’re operating in a DRAM (System RAM) rich environment. There are different types of read/write operations, temporary caching, that page files on disk (whether platter or SSD) can perform that RAM cannot or should not.
[/quote]

That is interesting to know. I did not know it.

It’s hard to see how any access via disk/SSD would be faster than memory.

I have 64 GB of memory. Windows is set to manage Virtual Memory (page files) on both the C:\ Win 10 and D:\ FS2020 NVMe SSD drives.

Win 10 has currently 18.944 GB allocated for both SSDs.

  • (min of 16 MB and recommended of 9077 MB (9.077 GB)

This seems okay (FS2020 flies okay).

What size page file should I set?

RAM is generally smaller in size than available disk space. Hence, it makes sense to move out data that’s resident in RAM to disk where appropriate. For example, you’re working on Application A for a long time, while Application B (say a web browser) remains open in the background. Windows will move the resident files in RAM associated with the browser session to disk because it detects it’s been an idle process (but open) for a while. That frees up RAM for active applications and other tasks.

Generally, you can’t go wrong for letting Windows manage the page file sizes on the different detected partitions/disks.

1 Like

Hi @MSFSRonS ,

yes… therefore NEVER disable pagefile completely :slight_smile:

I set it, as mentioned to 1Gig Min and 4Gig Max by 64 Gig RAM.

Windows itself never auto-increase the 1GiG. This is also what I expected.
Windows use some 100MB of these pagefile, but no need to use more by 64Gig RAM.

As you can see my settings :slight_smile:

image

And because of these, there are no big read/write operations.

1 Like

Thanks for the clarification.

I’ll manually change mine per your info. 1G to 4G

I don’t want to waste 14 GB allocated to a page file
if it doesn’t need it.

I wonder what else FS2020 will do with that 14 GB that it can use now.

I’m excited to see.

Edit - 18GB to 14 GB

hold data data data :grin:

If you see 18Gig used, the commited memory is about 30…

I posted here an example screenshot.

This was an incorrect statement that I made.
Latter and after several posts, I realized it.
But I could not remember where I had gotten it from.

Found it.

Now, I am confused.
Also, sorry but I can’t read your language in the screenshot.

My screenshot of my Virtual Memory. Per Windows 10 managed.
Luckily, I was just getting ready to change it.

And I have no idea what “Recommended” is and “Currently allocated” is twice as much?

Hi Guys,

I have one SSD which windows is installed on, and a larger SSD which MSFS is installed on and also a normal HDD with other games on.

Should I increase the page file on both my SSD or just the one which MSFS is installed on? I will not put a page file on my HDD. Any ideas? I have 16 GB ram. Thanks!

I have 16 gig as well.
I only have the sim on my SSD.
It’s a windows change, it doesn’t need to be put with MSFS.
I would probably put it where you have the most room.

Hi,

So do I just windows system manage the other SSD? Or do I completely remove any page file on that also?

You only need one file.
Set your own limits, normally your ram amount x 1.5 for the minimum, and x 4 for the max.
Note that windows often uses MB not GB so make sure you have the right value.

Are you familiar with changing these?