Ok perfect so you can leave the parameters on C:
(the more space you have on your disk, the better the virtual memory settings will work)
Ok perfect so you can leave the parameters on C:
After getting constant CTD I kind of had enough. It was reproducible for me, by starting for example at LEMG malaga airport, the game would crash 99% of the time. Also approaches would often CTD for me. I tried multiple things, limiting FPS, different drivers, empty community folder, safe mode, etc. Nothing really helped.
I decided to re-install my whole machine, with a clean windows 10 installation. Just installed video drivers (without geforce experience), downloaded MSFS from the windows store, before running the installer I copied my previous MSFS directory over so I didn’t have to download anything.
And I’ve been flying without CTD the whole weekend… The same community mods, the same CPU overclock, etc. In the meantime I’ve installed a bunch of other software. So far so good. Not sure if this is useful to someone, might be worth trying as a last resort. I’m starting to think for me at least, something was messed up with my windows install.
I have resolved my issues. No CTDs and was able to download all updates with no issues.
Totally shut OFF AVG Antivirus.
Removed and reinstalled all C+++ Redistributable’s.
Opened TASK MANAGER and shut down anything that may possibly conflict with MSFS.
Emoty community folder can now be gradually repopulated one item at a time.
Increased PAGE FILE to 32000.
I hope this helps someone.
Just to share that formatting my SSD where the game was installed (Steam) from ExFAT to NFTS seemes to have solved all my CTD issues. Game was crashing every single time I hit fly. Sometimes also just randomly in the menu.
I also solved my CTDs, after many many unsuccessful tries. I did 2 things yesterday in the evening, but I was too tired to try them:
-uninstalled my latest Nidia driver (471.96) with DDU and installed 471.41 - found this suggestion in one of the CTD threads
-“reinstalled” the US english language in Win10: installed my native language, set it as default, removed US english, added US english again and switched back to it as I prefer all my stuff in English for easier troubleshooting
Today I could fly many hours without any issues in VFR on ultra settings with lens correction, motion blur, etc turned off (I don’t like those effects), I could even put all the stuff back into the community folder (livery megapack, pushback tool, nohandlebar, sceneries). Right now I’m flying KSAN-KSFO for testing high density areas and IFR with ILS approach, performance is stable and everything is fine so far, I just contacted Oakland center, will update later how it ended.
Edit: I could also set my previous UV/OC settings for my VGA and I’m using my XMP profile for my RAMs (4x8GB 3200MHz) and I want to restore my CPU OC settings after this flight as it seems my issues were not related to these.
Edit2: Landed at KSFO, 0 issues.
If you have Capture One installed on your system, check the thread here:
Since WU6, CTDs are permanently present in my case. Before today they took place while entering the main menu after the flight. Now they are random (after take-off, cruise, approach).
Lot of free space, fresh setup, barely no community mods (only A & B points of the trip). It is becoming annoying.
Not sure about that, I’ve had MSFS running sweetly on PC-3200 @ 4400Mhz even though Windows 11 stopped responding behind it. However the overclock profile I used inadvertently pushed my CPU speeds way past their normal boost clock which was both unexpected and hopefully useful once I have a proper gpu and cooling installed.
Not I don’t get anything…Never the less I still CTD like hell.
in case of a CTD you get a message in windows event viewer.
Also a more general info:
there is a new faulty application found which let crash MSFS. Just in case for users which own Capture One : CTD caused by Capture One 20 codec
well well thought i was one of the lucky ones only had 1 ctd until now,bristol to malaga flight going smooth 100 miles to go ctd,so so frustrating,looked in the event viewer and yeah its what most ppl are having that 000005,i do hope this will be fixed
That basically just tells you that you had a CTD but I would assume you already knew that?
I have officially given up. I have used this “game” for some time now beginning as an ALPHA tester. While there were many frustrating issues during its development, CTD’s where never one of them.
UNTIL WU5. Since then I can no longer complete a single flight.
I’ve tried all the “fixes” to no avail.
Tonight I uninstalled this “GAME” and will not install it again until ASOBO can get their act together.
Check the info level entry in the event viewer right after the error, it tells a bit more details sometimes.
Hello guys, it’s been a month since I couldn’t play it, CTD directly after launch.
I opened a support request, but they closed it saying this is Process lasso interfering, but process lasso is not runing…
Since last update I started from scratch, downloaded the 120Go files and It runned! twice…
Now it is crashing again at start, this is really annyoning
I have an intel 9900k, nvidia RTX2080 , 32Go ram and samsung 1T ssd, I should be playing it nicely.
What made them think that Process Lasso was running? It must have been something you submitted to them, like the crash log from Event Viewer perhaps.
I had similar issues and tried almost everything… I have a 1080ti and it turned out the new 471.XX drivers don’t like MSFS. I reverted to 466.77 and my CTD’s disappeared! (Except the ones when exiting the game). Hopefully it will help some of you as well.
I have 471.96 installed, and hardly ever have crashes now. The last two times it happened, one was a hang on loading the sim, so not really a crash per se, and the other was a crash as the flight loaded. I restarted the sim, and the same flight loaded correctly.
Hello, Did you reinstall any mods?