SU5 was working for me for couple of days, until one day the game would not load to main menu anymore. I can’t be sure is it beacuse of Windows 10 update or something. I had updated windows after that 1 more time, NVIDIA drivers are latest.
I tried to reinstall the game couple of times, now I can constantly reproduce this:
Install MSFS in steam → press “Play” button → game loading to screen where it usually check for updates (I can see UI windows at loading) → Crash To Desktop happening here.
Steam Version
Hello @RUSweok .
Posting the event log from event viewer may help users to provide support.Zendesk or searching for other solutions on the MSFS forum may help. Maybe this topic can also help.
Thank you, I will try some things, can anything except of Windows reinstallation.
What particular info would be helpful from event log?
In Event Viewer/Windows Logs/Application, there might be an error logged like:
Log
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
You can just post such a log.
I wonder why CPU overclock cause my game CTD after around 40min of flight.
CPU overclock does give me more frames especially at ground.
Is there anyway to avoid CTD with overclock? I know a lot of people recommend turning off overclock for more stablility.
Surely if the game can run smoothly for 40min with overclock, I think the CTD can be avoid with some tweak.
Below are my PC spec.
CPU: Ryzen 5800x (stable when PBO2 but CTD when using clocktuner with hybrid mode 4.6Ghz all core and 4.65Gh…
Well, the good news is that the sim’s performance is probably smoother and better than it has ever been. The bad news is that the good feeling doesn’t last more than five minutes. I can’t complete a trip of more than ten miles in the Cessna 172 without it crashing to desktop. What a mess. And yes, my Community folder is clean.
Thanks, have 3 logs for you, including one you mentioned:
Summary
Faulting application name: FlightSimulator.exe, version: 1.18.15.0, time stamp: 0x00000000
Fault bucket 1909894803270961945, type 4
Problem signature:
Attached files:
These files may be available here:
Analysis symbol:
Version=1
Ok so your exception code is the relatively generic: 0xc0000005 :(.
P.s. you should be able to hide details by writing:
1 Like
Thank you very much, I will update post if I will find solution.
I am having the exact same issue. I have tried 5 times in a row and it continues to crash while loading. Looking forward to a solution.
Cheers, Pete
The only thing we can try is this, mentioned before:
Hello everyone.
This is an unofficial list of references to CTD solutions with the purpose of collecting the most helpful solutions that are scattered in the forums or are found by users, as I would hate it if such valuable information got lost.
This topic is a Work In Progress and if this topic does not work out, or becomes irrelevant, it may be removed in the future.
READ BEFORE POSTING To keep this topic organized, I would kindly ask you to please only comment/reply to this topic with eithe…
Looks like there will be no fix for that since noone can really identify what is going on. Will try later to do some fixes. It is very bad that it possible fix only with OS reinstallation.
2 Likes
Note: WU6 is planned to release on the 7th, but unfortunately I can not say if this will improve your situation.
1 Like
Apparently, it means that there was an access violation.
Hello, can you specify what you mean and is there any possible solution?
1 Like
This is problematic. I don’t have the computer expertise to do all of this troubleshooting. The program should work as intended. I had no problems for close to a year, and now this issue has reared its ugly head.
Cheers, Pete
1 Like
The crash logs from software called AppCrashView label the error as an access violation. This could mean one of two things. Either it isn’t allowed to access a certain area of ram, or it isn’t allowed to access a certain simulator file. I only started receiving the error after modifying the file en-US.locPak and have since not been able to play even after reverting the file and checking that the software had permission to access it. The file is located in the Official package set under a folder called fs-base. I don’t know how to fix it and am still unable to play Microsoft Flight Simulator.
We shouldn’t have to look at cryptic error reports, upon crash the simulator should tell us exactly what the faulting file, data value, or code was so that we can act accordingly.
2 Likes
Looks like I found an easy solution for installation crash. Thanks to links provided and fellow simmers who suggest that this is about files accessing. I performed very clean uninstallation for simulator, it is more about common sense and oldschool:
Uninstall game via Steam menu
Delete all leftovers in simulator folder, move into another folder your Community folder with any mods if you don’t want to reinstall them later by hand.
Important Clean leftovers on your system drive, especially in: user - AppData - Roaming - MicrosoftFlightSimulator - delete whole folder.
Important Restart system and run everything under full administrative rights (Run as Administrator) in my case it is a Steam version.
Install simulator in clean, freshly created folder.
My simulator reinstalling complete 124.88 GB of data which mean that before, somehow, uninstallation didn’t performed clean uninstall.
UP: this worked, simulator works for now, will update if it will broke again.
1 Like
I did the same thing yesterday (but with the windows store version) and it now works fantastically!
2 Likes
I am very glad, that you were able to get MSFS running again.
As the issue seems resolved, I am closing this topic. Contact a moderator if you need it reopened.
1 Like
