Ok thanks, however, it was working fine until I installed the newest update.
Time to purchase a new computer I guess.
Thanks
I’d be more concerned about other forum members being unwilling to help you, then offending anyone’s eyes.
1 Like
No, I don’t use FSUIPC7.
Yeah, I agree that it could be software. I was just encouraged by the success after disabling XMP. I’m gonna move the AI traffic back to 25% and cross my fingers.
Thanks - do you use any other sort of add-ons that might make use of the SDK?
I’ve now done a handful of flights and had no further CTDs, although of course it’s hard to know the difference between a successful diagnostic and good fortune! I think I’m going to raise a bug with Asobo anyway, as something isn’t right here.
QQ since the last update I am crashing CTD. about 70% loaded not even getting to any menu’s is anyone else seeing this?
No. I don’t think I have any add-ons that use the SDK. I use the modified aircraft, like the DA62 and CJ4. I successfully completed a flight at 25% AI traffic. As you said, prob just good fortune.
uninstalled, reinstalled Nvidia drivers - fixed my problems… (though made some small tweaks according to the “how to”.. CTD guidelines)
1 Like
Why is there so much misery after the update 1.12.13.0 while everything worked fine before!!! Customers must have the option to return to the previous version by a simple choice button at the start of msfs2020.
I cannot understand that things worsen so badly and that the team developpers were not aware of the expected results. Did they tested not enough on many different configurations? Older vs newer… as an airline engineer, i really cannot understand that so many effects are seen in the negative evolution. Performance losses on gpu’s, heavier loads, older drivers crashing, dll’s involvement… i’m glad that we, engineers, in the real aviation world don’t make such mistakes, as it would be payed with lives. 
i’ll hope that the developpe team don’t let us in the cold and bring the issues back to what they were before. One rule has again be confirmed… never change something what works fine. Updates have the goals to improve things. Its defenitely not reached with the latest patch. It missed his objectives and goals quiet hard. And for the most of the customers, which are not computer experts, they rely on the expertise of the developpers and are not able to look for trouble shootings by there own. So, many of them cannot fly anymore and stare day by day to the update sxreen, hoping on a new STABLE patch.
2 Likes
Effectively, I stopped using fsuipc 7 and SLC and no more worries (for the moment) of ctd.
several flights and ctd each time!
XMP enabled on the other hand …
this is what we told so often and also why we told it so often:
we check only CTDs here where you have NO MODS INSTALLED 
Example: the A32NX was a known CTD reason for 1.12.13.0..
Because the users allways ignore that point, it might be helpfull that we get a new category in forum about : e.g. “Issues in case Mods installed”
2 Likes
I don´t have any mod installed. And I only make it rarely into the cockpit. As it makes no sense making a list of what crashes, I tell you what works: Pitts and Cessna at free flight.
My hardware is good enough as I get perfect frame rates at that rare occasions.
The game is still in alpha phase.
Do you have the “OneStore” packages on another drive?
It wasn’t until I moved the 100+Gb OneStore to another location that my CTD’s started.
MS tells you to edit the last line in the User.cfg file to reflect the new location. Don’t do it, you will get CTD with 0xc0000005 errors.
I resolved the problem by using symbolic links to point to the remote OneStore folder. Since I started using symbolic links, no CTD’s whatsoever.
The “official” advice of editing the User.cfg file to point to the new location is complete rubbish. Leave the User.cfg alone and just use symbolic links. It solved my problems.
It seems that Msfs has trouble accessing other drives.
you have installed the game into a network-synced folder ? ( I hope I understood this wrong 
)
No, I have the game installed on C: drive and I have the “OneStore” folder on my D: drive to save drive space on C:.
But it seems that Msfs will CTD while trying to access across drives resulting in a 0xc0000005 error.
Symbolic links solved my CTD problem.
but why should MSFS try to access your D: if you have installed the whole game in C: ?
Let you backup your C: to the OneDrive ? You meant that ?
I purchased my copy through the Microsoft store. Since the last update, the game crashes during the middle of every flight. This happened occasionally during prior updates, but now it is consistent with every flight. Yesterday I deleted and reinstalled the game and did not add any add-ons (previously I only had some third party liveries). I have a 2-month old computer, and specs aren’t the problem; other than crashing, the game runs smoothly at high graphics. I updated my graphics card driver two days ago. I receive no error message when I crash to desktop.
Geting also CTD’s every flight flying from 7uuu-7ggg in a CJ4 Longitude. CTDS randomly… in de beginning from the take off… and midflight… unplayable… waiting for fixing since the release.
Asobo fix that CTS its not funny flying a 1 or 2 hour flight ,short of the end the Sims Crashes without errors…
I not need any World update or other feature things… Only Bug fixing CTDs then Planes . The weather and the the rest of the bug so things all is fine… But not a another worldupdate Please…
Greets from germany…
1 Like
I was about to start taxiing and I got my last chrismas gift from Asobo (i mean CTD, sorry)
This is what Event viewer is showing:
Faulting application name: pilot_core_fs2020.exe, version: 0.0.0.0, time stamp: 0x5fc8d5d3
Faulting module name: ucrtbase.dll, version: 10.0.19041.546, time stamp: 0x43cbc11d
Exception code: 0xc0000409
Fault offset: 0x000000000007287e
Faulting process id: 0x1f40
Faulting application start time: 0x01d6dadedf58278e
Faulting application path: C:\Users\Victor-PC\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\IVAO\PilotCore\pilot_core_fs2020.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 70ad6530-25b3-4aba-8d7d-d83905306892
Faulting package full name:
Faulting package-relative application ID:
Looks like it was IVAO
It is IVAO, when I open the PilotCore it crashes immediately