I never had CTD in MSFS until SU6 (if I remember well) was launched. And I have been using Lasso for 6 years now without any issues on any game.
The only reason why MSFS crashes is MSFS itself. It has no sense that game crashes when only 50% of RAM and less than 75% of your VRAM is used. It even crashes while you are installing it on a vanilla setup with no mods or when you install a new marketplace item. There are tons of users reporting CTDs everyday with different setups and different platforms. It even crashes on Xbox and they don´t use Lasso there. So it´s clear that there is a problem.
That’s 99% the case for me as well. The other 1% is Nvidia drivers or Hardware Accelerated GPU Scheduling. Lately I have no problems with HAGS, but I had in the past. I have yet to experience a single crash in MSFS with SU9 beta (that means zero).
sorry… can absolutly not confirm that and it is just wrong. I have zero crashs at my system. Not one single CTD since the second update or so ( ages ago ). If you check the forum you might notice that a lot of users run into strange driver issues, strange conflicts caused from other tools like capture one, overcloacking, hardware stuff, installed experimental mods, and on…
But , where we spoke about Crashs in general ?.. The topic is the pagefile size and the recommendations about. And here I want to mentioned , in special for @Syarasd , that there other recommendations in forum exists and that some kind of mentioned tools, in special Process Lasso, can cause strange issues till crashs.
you mean the pagefile ? I have the packages folder on a second drive…
The recommendation for the pagefile not depends on that. Usually the setting “System Managed” works well. You can run into issues in case the drive on which you configured the pagefile ( usually main drive ) becomes full. Then windows does not increase the pagefile and users with less than 32G run often into an issue.
That’s fair. MSFS itself is not the only reason MSFS crashes, but for me it was. The release notes are always mentioning crash bugs getting fixed, so that’s good.
I was lucky since game launch up to the end of 2021. Literally no CTD at all. Now I lost the faith. Forum has a CTD section and each beta has a CTD section as well. That´s not casual. They are aware of the problem.
yes, that I want to say with my comment and just put a little bit attention on tools which already known as making ( at least once before ) trouble … Intension was just to mention: a lot of these super-fancy tools are not necessary and cause more issues as they are helpfull. Issues which we then search here in huge topics and at the end the users mention “and, ah,. I forgot I have this installed …”
EDIT: @geloxo of course… msfs is not free of issues. But a not less amount of issues is caused from the user-system ( for me the best issues, because these we can fix )
the recommendation depends then how much RAM you own and how much space is on your maindrive.
If you own also 64GB RAM, just dont worry to much about the pagefile setting. Best let it on System Managed. As mentioned, I “optimized” it and so I safe 8GIG disc space ( not that I need that ). The system never ever increased the pagefile over my minimum setting.
I down’t know what happens,
I have SDK 0.18
I always get CTD if i make a Taxipoint and try to move to another Location.
Now 3 restarts an always CTD.
Pagefile is 24GB Fix on Drive C
hello,i just want to share some information,if anyone of you still experience CTD’s until now,my solution is(probably works with others)i delete the World Update 8 via Content manager,and my ctd is gone,hope this works
So… You were right MichaMMA. I decided to set page file to auto in windows (I had it disabled) and then my total RAM usage went from 50% to 75%, with a pagefile set by system around 5Gb. Even better: Feelthere KLGA (La Guardia), which systematically crashed on my system since months ago, now loads well.
Definitely I was completely wrong in having page file disabled in Windows. I never had problems with any games for years, but clearly now MSFS needs it.
not sure that I understand it correctly and would like ask to be sure:
If you choose “System Managed” then Windows will create in your case a 65GIG pagefile ??
If so, this should not happen. The default size in your case should be 8~9GIG and this is because the rule behind ( /8 ). The maximum size depends on your free disc space.
If you see a 65GIG pagefile, then maybe there was a application with a memory leak. I had this one time with DCS in multiplayer where it fills completely the RAM in a few seconds and then of course my pagefile runs out too. But, here you can also see that my max “safe” me in these situation too. There is no “game” which consume these amount of memory and so it was only 4GIG filled instead 65GIG filled on my ssd.
I still can recommend for 64GIG users a manual setting like:
Minimum: 1024 and Maximum: 4098/8192/… ( jsut how you feel good, but you will usually not need it )
Or… wait… I get an idea…
Did you have crash/memory dump creation enabled ??
If yes, this might explain the huge pagefile in System Management setting, because pagefile is just necessary for that. If you choose “complete memory dump”, then the pagefile is bit more in size as your amount of RAM. With “auto memory dump” the increasment of pagefile will happens after some( or one) crashs only ( cant remember all rules ). Mostly you not realy need a full memory dump. Just choose “the mini dump” setting.
Aside from the well known memory leaks, MSFS uses a lot more RAM than most other apps and games and this can often highlight issues with faulty ram in the higher registers that never otherwise shows up, even sometimes in “ram tests”.
A classic example is some idiot that refuses to take even the most basic static precautions when installing ram as they believe the whole static thing is a myth (it is not). Static rarely kills the ram outright, but if it does they blame faulty ram and complain loudly online about the ram manufacturer. Of course more often than not the damage is subtle and may take months or years to show up, or only effect the ram under heavy load. Ram damaged in that way is likely to only play up with ram intensive apps like MSFS.
With regard to Process Lasso, it gives access to parameters and setting that Windows has locked out on the assumption that most users do not know enough about what they are doing to allow them access. The issues with MSFS arose when a patch last year started to directly play with the process priorities of the CPU to try and improve performance. If users had tried to use Process Lasso to set the same priorities the game refused to start.
yes u’re were right i contact the MSFS team and they gave me a attachment,it’s says savedumpslocally.zip it’s only 400-500 Kb tho, so i unzip the file and put install it to my C drive,and after 1 days playing fs2020 and the game crashed,and when i checked the page file settings it bumped up to 65gb,and also i have “complete memory dump” instead auto,i changed it
… Intension was just to mention: a lot of these super-fancy tools are not necessary and cause more issues as they are helpfull. Issues which we then search here in huge topics and at the end the users mention “and, ah,. I forgot I have this installed …” 
). The system never ever increased the pagefile over my minimum setting.
