I was initially really interested in MSFS ans was looking forward to using the product.  But after reading about the it's limitations and system problems ever since the release, I can only conclude that MSFS202 is not ready for prime time.  Maybe it's suffering from Covid.  

3 minutes ago, vonmar said:

Set up a flight, fly it and note where you were and what you were doing when it crashes.

Screenshots or a video would be helpful.

Tell me about the flight setup and I (and possibly other pilots) will see if I can fly the same flight and see what happens.

 

 

Honestly the CTD has never repeated itself once. I could get one 5mins into a flight or 3 hrs in. And move of the time I am away from my PC when it happens as I am in cruise. So I don't do anything particular and I fly alone. 

Just in case, I don't use latest version of FSUPIC but there could be a skeleton in a closet if one uses latest version. Check it out

https://forum.simflight.com/topic/91424-fsuipc-7-caused-msfs-ctd/

Edited December 31, 20205 yr by sd_flyer

6 minutes ago, Clem116 said:

Honestly the CTD has never repeated itself once. I could get one 5mins into a flight or 3 hrs in. And move of the time I am away from my PC when it happens as I am in cruise. So I don't do anything particular and I fly alone. 

Note the setup on all of your flights.

Just tell me about the one that crashes in 5 minutes.

I will test that one,

2 minutes ago, vonmar said:

Note the setup on all of your flights.

Just tell me about the one that crashes in 5 minutes.

I will test that one,

Will do! Honestly 5mins into a flight is very rare. Lately it's been anywhere from 1hr to 3hr. I don't do flights longer than 4hrs.

Reading this angers me because prior to my clean install I have always disabled the default defender. I decided to leave it on. Now I'm wondering if all my past CTDs (last few days) have been the result of having defender enabled. Defender was very problematic for me during my days with P3D.

Time to disable to see if my CTDs on approach to airports stop.

16 minutes ago, Clem116 said:

Will do! Honestly 5mins into a flight is very rare. Lately it's been anywhere from 1hr to 3hr. I don't do flights longer than 4hrs.

On the 5 min to one hour flight crashes were you still at the PC watching / doing the flight?

What happened?

Are you using real Wx, ATC , AI aircraaft and which aircraft on a typical flight etc... in other words what is the your basic flight setup?

 

55 minutes ago, marsman2020 said:

I can never understand why people who are not having a problem insist in coming into threads just to say they are not having a problem...

They don't 'insist on coming into the thread just to say they are not having a problem', they are pointing out that since they are not experiencing any issues, this would tend to indicate that its a user-related issue when people are experiencing issues, either hardware, a clash of some driver or other software, or a mod, or possibly any/all of these, for different people, not necessarily the same cause for all. 

This incidentally, is the case with me, I have a few payware things installed -  all the Carenado ones, the Kitfox and the Piaggio P.149, plus Maccosim's EGCC and EGBB - but third-part no mods to anything at all, and MSFS is as solid as a rock on my computer. It's not even a very flashy computer either - a i5 Kaby Lake processor, Radeon RX 480 8Gb GPU, Asus Prime Z240P motherboard, 44Gb of DDR4 memory and MSFS is installed on a dedicated SSD. 

Now the fact that it runs okay on my computer might not be much consolation to people who are having problems, but when a thread is started which is titled 'I am so sick of this', and people are suggesting it definitely is Asobo's fault, when it clearly isn't if there are people who can run the software with no issues -  such as me - then pointing out that you are not having issues on such a thread can inform people that they might want to investigate other avenues for causes on their end instead of simply assuming it is definitely the base program which is at fault, when it quite clearly is not as evidenced by the fact that some people are not having issues.

1 hour ago, marsman2020 said:

We had 50+ people do the Cannonball Run race from JFK to LAX on the 26th and there were numerous CTDs across that group.  I've never experienced CTDs in the sim, and I had one as well after about 6 hours.

This is a prime example of this kind of confirmation bias which can lead to incorrect assumptions with regard to the potential cause for problems. If fifty-plus people were in a multiplayer, but 'numerous' but 'not all' people had CTDs, then this would tend to indicate that a user-end issue combines with a problem with the software to cause a crash, since it didn't happen to everyone. Thus it would be incorrect to put it all on the software, because in this example, this quite evidently is not the case.

I realise that it is annoying to have software which won't run, I had that issue with Mount and Blade Bannerlord, and it took me a couple of weeks to finally figure out, after a very long, frustrating and tiresome investigation, that a minor language pack setting in Windows was making it crash. But in the end it was indeed a problem on my end which was causing it, a stupid and annoying one which the developers of the game should have been more careful with investigating or patching, but it was still my computer's settings which were causing it nonetheless, and the reason I knew this and investigated it until I found a solution, rather than giving up, was because I knew people were running it without problems, so it therefore had to be something on my end.

1 hour ago, Chock said:

They don't 'insist on coming into the thread just to say they are not having a problem', they are pointing out that since they are not experiencing any issues, this would tend to indicate that its a user-related issue when people are experiencing issues, either hardware, a clash of some driver or other software, or a mod, or possibly any/all of these, for different people, not necessarily the same cause for all. 

Or the sim is just an incredibly complicated piece of software which combines legacy Aces Studio code, a modified Forza game engine, and new Asobo physics engine code, and there are bugs which some people encounter and others do not.

I've done numerous 3-5 hour flights in the past with these exact same settings with no problems.  I even set the Longitude to unlimited fuel and let it go over the entire Atlantic overnight one time.  Same exact setup. Nothing changed to cause the CTD that I had.

And the OP specifically said 'Vanilla', which I take to mean no mods, no FSUIPC, etc.

If you think the fact that SOME people are not having issues with MSFS means that all of these problems are just the user's fault, I've got some oceanfront property in Arizona (with great beautiful water masks!) to sell you.

Edited December 31, 20205 yr by marsman2020

27 minutes ago, marsman2020 said:

Or the sim is just an incredibly complicated piece of software which combines legacy Aces Studio code, a modified Forza game engine, and new Asobo physics engine code, and there are bugs which some people encounter and others do not.

I've done numerous 3-5 hour flights in the past with these exact same settings with no problems.  I even set the Longitude to unlimited fuel and let it go over the entire Atlantic overnight one time.  Same exact setup. Nothing changed to cause the CTD that I had.

And the OP specifically said 'Vanilla', which I take to mean no mods, no FSUIPC, etc.

If you think the fact that SOME people are not having issues with MSFS means that all of these problems are just the user's fault, I've got some oceanfront property in Arizona (with great beautiful water masks!) to sell you.

We can have this argument until we are blue in the face, but the bottom line is, there is something with your hardware or some software on your computer the sim does not like.  Who's at fault? another argument. But I tend to side with chock on this.  Anytime I have had a CTD since day one (about 3 after 150 hours of flight), it has been something that asobo has mentioned would cause it and fixed it, or something the community has pointed out to cause a CTD.  Like recently, simconnect is causing CTD.  I know its frustrating to pin down whats causing it if its not obvious.  

5 hours ago, sd_flyer said:

It could be GTX1080 is not up to task.

My 1080ti is well up to the task.  Where does this stuff come from????

 

42 minutes ago, marsman2020 said:

If you think the fact that SOME people are not having issues with MSFS means that all of these problems are just the user's fault, I've got some oceanfront property in Arizona (with great beautiful water masks!) to sell you.

I didn't say that at all. Try reading what I wrote rather than what you think I wrote.

I was having that issue when playing Apex legends through steam, was driving me nuts. now Im not sure if how i fixed that issue is relevant but ill tell you just in case! Seems the issue was with GeForce experience. I uninstalled everything Nvidia from my pc through the uninstall apps, the absolute lot, manually., came in in safe mode and run driver cleaner, then CC cleaner for the registry.

After all that I installed the newest GeForce driver WITHOUT GeForce experience, and voila, haven't had an issue since. 

Edited January 1, 20215 yr by Spam3d

19 minutes ago, fppilot said:

My 1080ti is well up to the task.  Where does this stuff come from????

 

I didn't have Ti.. And when I was flying over beautiful forest sim would slow down to slide show and crashed. Things changed when I upgraded to RTX2080 Super

Edited January 1, 20215 yr by sd_flyer

OMG just F**** CTD 100ft before touching down after a 3hr flight. offensive initials not allowed!!!! I got a freeze and 10sec later boom CTD. Same F*** error.