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

Thanks for the info Micha. I appreciate you taking the time to try and work this out with me, that’s very nice of you. I reinstalled Windows 10 and MSFS last night and so far this morning I’ve made 2 flights without CTD which hasn’t happened since the last patch. I don’t why it’s working this time, just hope it continues. I really believe my issue had something to do with the Virtual Drive that the XBOX gaming service runs. Every crash was preceded by that “Xvd” virtual Xbox drive disappearing for a moment, then the VCRUNTIME140.dll error. This was the same sequence of events for every crash. Reinstalling windows and MSFS again seems to have sorted it that out for now. (Knock on wood) Of course now I’m afraid to install anything else on my machine now that it’s working, lol.

1 Like

hmmm… yes… we not realy find out why this happens.

I press all my thumbs too that the issue stay furthermore away.

1 Like

Has anyone tried a RAM disk for their swap file?
If you are limiting it to 4GB, or 8GB, it seems that with 32 or 64GB RAM, it would be faster and less wear on the SSDs (inc. NVMEs)

I realise persitance of RAM Disks can be an issue, but I used AMD Ramdisk and imdisk in the past for persistant drives, they both worked pretty well.

Never use SSD for high frequency data changes, it’s not build for that. Use it for all the static simulator data but not temporary data. RAM-Disks are a pretty good idea. MSFS can work with 32 GB pretty good, more is not necesarry.

Hey everyone, I’m still suffering from the CTDs and I think the virtual memory thing may be what I need to do. I’ll put up a pic of my settings that I did but I am a bit confused on setting my virtual memory correctly.

From what I’ve read, you only need ONE paging file and the best formula is INITAL = RAM x 1.5 x 1024 and MAX = RAM x 3 x 1024 to get GB to MB which the system uses.

In my system I have C: drive which is my windows drive
F: (SSD) where MSFS is installed and I am sure my fastest drive.
I have 32 GB of RAM

What I’ve seen so far is “You can have the custom size on your windows drive;” or “it should be on your fastest drive” or/but “should not be on an SSD drive.” MS support says in their instructions to increase the virtual memory (pagefile) on your system “Click to select the drive on which Win 10 is installed (by default C:) then select custom size” yadda yadda.

So you can see my confusion at this point.

So my questions:

  1. Do I only put the custom pagefile on my C: drive?
  2. Do I put the custom pagefile on both my C: and F: drive?
  3. If I put the pagefile on my F: drive, do I leave C: drive set to “system managed?”

I think that covers everything for now. Thanks for any insights to lock this down for me.

Mine Is the top box: Automatically manage all drives by Windows 10.

Seems to work ok.

For whatever reason Automatically manage all drives by Windows 10 doesn’t work correctly and it appears zendesk knows this thus their suggest in the website:

  • In the Windows Seach bar, type Advanced system settings and open the Control Panel.
  • Make sure you’re on the Advanced tab.
  • Click the Settings button from under the Performance
  • On the Performance Options box, go to the Advanced tab > Performance
  • Click on Settings
  • On the Virtual Memory box, uncheck the Automatically manage paging file size for all drives
  • Click to select the drive on which Windows 10 is installed (by default C:)
  • Click to select the Custom size radio button.
  • In the now-enabled fields, type the minimum and maximum size of the Pagefile in megabytes (MB) according to the physical memory present in your computer.
  • Click Set and then click OK.
  • Restart your computer.

However, they say put the page file on the C: drive but in other places people have said put it on the “fastest” drive and/or put it on both C: and where you have MSFS installed… I would like clarification as it looks like zendesk doesn’t take into account whether you have MSFS installed on another drive like an SSD.

I have 32 gb of RAM and I watched the RAM analytics last night in a multiplayer flight and sure as ■■■■ it was maxing out my memory! I increased my pagefile size I had no problems in a heavy multiplayer area with a lot of scenery.

So really, and MichaMMA maybe you can help here, where do I put the pagefile, on C: where windows is installed or do I put it on my fastest drive where I have MSFS installed, or on both drives? I have room on both so I’m not concerned about size requirements.

yep, we mentioned this already ( as also the other points you mentioned )… There are rules related to the system managed setting which depends on RAM size, free space on disc, etc. . Normaly you should not have an issue with this windows setting , but we see sometimes it’s necessary to change it. So you can simple set it so e.g. 32GIG max ( you don’t need 96GIG ). You can also choose drive C: for this, or if you want safe your main-drive a bit, you can set on C: eg. 1024-8000 and on your Game-SSD then 4096-32000.

Why you read sometime that SSD is not a good choice: because limited lifetime of a SSD. And because MSFS cause a lot of pagefile usage, it may be affect the lifetime of the SSD ( may be ).

PS.: you can use the ‘@’ char in front of user name, then the user got a message

1 Like

And what is your PROOF? Without knowing this thread I did the following:
Create a fixed sized 16 GByte pagefile.sys on my second SSD drive D:, that is in my case MSFS 2020 on C: .
Please bother other people.

Well, with “real” hard disks it makes sense to have the game on one hard disk and the page file on another hard disk. This speeds up “head positioning time”, see Positioning-time Meaning | Best 1 Definitions of Positioning-time

If you have two SSDs like me, you can do the same. A SSD has no moving parts, but bandwidth is limited between SSD and memory. The positive effect can be very little, maybe you can’t measure much.

Which means what?

1 Like

Question: What is the positive effect of having the pagefile.sys on a different SSD.
Answer: Use the game start time as a measurement.
Hypothesis: With pagefile.sys on a different SSD the game start time is shorter.

There IS a correlation between pagefile.sys and crash to desktop or even MS-Windows blue screen

I have MSFS 2020 game at drive C:, a SSD
I have 16 GByte fixed size pagefile.sys at drive D:, another SSD
I have 16 GByte RAM

  1. Test: Graphics mode Ultra, airplane B748. departure London Heathrow. I got a CTD after selecting the airplane, airport and before I was in the “game screen”. I used ressource monitor to watch the pagefile.sys. This was the only pagefile.sys activity and it was just before the CTD.
    Note: I took me some time to make the screenshot - I did not expect this. But in real live it was pagefile.sys activity and then CTD.

  1. Test like before but this time I was video recording the ressource monitor window. I got a MS-Windows blue screen (total system crash). The video file is corrupted, therefore no playback possible. But again pagefile.sys activity and then blue screen.

but not because ot the pagefile setting… blue screen is a completly other story as CTD.
I assume there is another reason for that, and this is may be your overcloacking (e.g.).

As the pagefile.sys has become quite an issue in some senses, I thought I would share how I do my systems pagefile and rollingcache.ccc

There are three files we need to be aware of:

manual cache files

There are a couple of things we need to take into account:
Size of pagefile needed
Which drives these are all stored on

The system is going to be writing to the pagefile all the time your computer is switched on. That is by far the most heavily used one.
For that reason, it might be better off being placed on a mechanical drive (HDD), rather than an SSD. I do not recommend that unless you need to due to another issue such as limited numbers of disks.
Similarly, it needs to be fairly fast access to be efficient copying to and from RAM - so a 7200RPM disk is much better than a 5400 one.
If you have it set to managed size, when your flight gets to a very dense city, the pagefile will increase in size, I have seen mine at 32GB plenty of times. The biggest I have seen it get to was 38GB
I find it is best to leave just one drive with a pagefile, the rest I turn off.
(If your drive were to fail, the system will just make a temporary one on a drive that has not failed, so you do not need to worry about that)

The calculations for the size of the pagefile.sys is one of the most heavily over-discussed things in my opinion. The formulae go on and on and vary quite a bit, so here I can only give my opinion.
I have never seen mine ask for more than 38GB in my current system. I have 16GB RAM
The most usual I have seen it at (displayed on my G19 screen live) when using MSFS2020 is 32GB. I have a monitoring prog on my system that shows me the usage of my drives to my little screen on my G19 keyboard. I use that to decide where things go. While I have been writing this, my T: drive has been in use constantly, flicking on every twenty seconds or so, and when flying, I can see the reeads and writes to my three drives as I sit at an airport/fly/land etc.

I have experimented with various combinations of size and disk locations, for all the parameters of these storage files and devices.
I recommend this for your pagefile setting:
1/4 your RAM size as minimum
3.5x your RAM size as maximum
pagefile.sys on an SSD
Turn the rest off.
I have been using my C: as my pagefile for over two years, since I built this PC.
In all that time, my C: drive SSD life now says 92%. My PC is on 18-20 hours avg. a day probably.

The second highest use will be your rollingcache.ccc, unless your manual cache covers the whole area you fly.
This will be used as you fly around the virtual world, caching the details of scenery and objects from the downloaded data, and keeping it in to hand until you fly so many places that it wipes over itself.
SImilarly, you may need to adjust the size to keep or lose more data, depending on your flight patterns.

Lastly, the manual cache. This is only made bigger by hand, so the only concern is reading speed and access.

So, we have to balance the pagefile.sys and rollingcache.ccc and drive usage.

Put them on different drives
The pagefile.sys should be the one demoted to HDD - If anything is demoted to HDD, the pagefile.sys gets the most usage, and is always used when the PC is on.
The rollingcache.ccc is more read from than written to once you fly a lot
Partitions are not drives, so if you have two physical drives, C with one partition, and one is an HDD that has two logical drives D & E on it, putting one file on D and one on E will not help - in this case, if you have two physical drives, put one of them on the other physical drive
If you have three physical drives or more (C, D & E) with D as your MSFS 2020 drive, put the files on the drives that do NOT have your MSFS 2020 on it (C & E).
The rollingcache.ccc can be turned off - try it without it. If you have a good internet speed, then you might find you don’t need it.

My rollingcache.ccc is set to 20GB, and I don’t have a manual cache.

All in all, it works far better than having my pagefile.sys on my HDD when flying, as that takes away about 30% faps, dropping me from 24-28 to 16-18 and makes it all as stuttery as hell. I have tried setting my pagefile at 32GB, turning it off completely apart from 2GB on my C:, I have tried turning off the rollingcache, turning on the manual cache, just about every combination of them all.

I have my set up like this:
C: SSD WIndows and pagefile.sys
D: SSD MSFS 2020
G: SSD Steam games and MSFS2020’s rollingcache.ccc
T: HDD User files documents folder etc. (also used for recording video from Radeon ReLive)

This means that when I am flying MSFS 2020, the rolling cache, game files and pagefile are all read from separate disks, and if I start recording, that too is on a separate disk.
It is unlikely that I will play a steam game and MSFS2020 at the same time, and the same when I use a steam game, that will use the pagefile in my C:

I agree with this idea, if both drives are equally fast. I have an old and slow SSD (drive C:) and a new and fast SSD (drive D:). Therefore I put pagefile, rollingcache and MSFS 2020 on the fast SSD.

About the sizes: I follow the simple idea of “same size as RAM”. I have 16 GByte RAM. This is the size of pagefile and rollingcache. By the way, the RAM load was maximum 13 GByte in graphics mode Ultra and of this 13 GByte, 2 GByte are needed for the operating system. MSFS 2020 does not need more then 16 GByte RAM.

To keep things simple I have no manual cache.

Last but not least: Setting “AI offline” is the biggest FPS eater in my setup. Sometimes this setting makes no FPS degradation, sometimes it is a pain. See this video:

This is a 3 minute vid on correctly setting up page file size to match your ram…wow, did it work. Hope it helps!

1 Like

What the heck is RAM load?

Ram load…:roll_eyes:

Ressource monitor, memory, used memory. The green part of the bar. See: