What's in the Windows event viewer?  That might give an indication of whether it's a video subsystem issue or something else.

In other sims, a crash that seems to be regional in origin but does not occur in the same place is often attributable to a bad AI aircraft (usually a corrupt texture) that appears in that region.

Could be server-side issues as well...

33 minutes ago, Bob Scott said:

What's in the Windows event viewer?  That might give an indication of whether it's a video subsystem issue or something else.

 

Spoiler

This appears to be from the first crash:

Faulting application name: FlightSimulator.exe, version: 1.32.7.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.32.7.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000007a4509
Faulting process id: 0x0x51B4
Faulting application start time: 0x0x1D99B016E46C925
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.32.7.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.32.7.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 80c414ed-6785-4563-b321-5de53a56622a
Faulting package full name: Microsoft.FlightSimulator_1.32.7.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Second Crash:
Faulting application name: FlightSimulator.exe, version: 1.32.7.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.32.7.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000053367a7
Faulting process id: 0x0x37E8
Faulting application start time: 0x0x1D99B0BAFBB059D
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.32.7.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.32.7.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 0984f99c-8efb-4900-b3bc-2d00270ae13a
Faulting package full name: Microsoft.FlightSimulator_1.32.7.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

See the spoiler window

Edited June 10, 20232 yr by fppilot

Windows: the event viewer is mostly useless for this simulator and everything is pretty generic as "faults" go.

 

Again, I would use the famous addon linker and use it's built-in programs to detect scenery conflicts. It will automatically rename them. It sounds like SamScene's scenery is conflicting with something else as it unloads from the area (as you're leaving it) is my guess. I had a very similar issue. Anywhere from New York and headed in any direction. Dulles, Midway, Omaha etc etc etc.I used the addon linker built in apps and I am now able to fly anywhere. It was very annoying until I got it fixed.

It's not snake oil or garbage advice as with some of the stuff on the internet. I won't say any names.

The others giving advice on other 3 party programs is a good idea as well.

Edited June 10, 20232 yr by Sonosusto

CTDs have been happening to me since last Christmas in probably 9/10 times. I have done multiple removals and reinstalls with and without adding to the community folder. It has got to the point that I have parked msfs2020.

That said in the next 2/3 weeks i will be updating my machine (cpu, mb etc) and a fresh install of windows.

It will be interesting to see if the problem remains.

One thing is for certain and that is XP11 & 12, P3dV3 continue to run like a swiss watch. 

7 minutes ago, dbw1 said:

CTDs have been happening to me since last Christmas in probably 9/10 times. I have done multiple removals and reinstalls with and without adding to the community folder. It has got to the point that I have parked msfs2020.

That said in the next 2/3 weeks i will be updating my machine (cpu, mb etc) and a fresh install of windows.

It will be interesting to see if the problem remains.

One thing is for certain and that is XP11 & 12, P3dV3 continue to run like a swiss watch. 

I would actually really like to help you solve this. The overwhelming majority of CTD's for this simulator are addons (of any kind conflicting with another) and settings in sim, MS or Nvidia.

Edited June 10, 20232 yr by Sonosusto

Just now, Sonosusto said:

I would actually really like to help you solve this.

Greetings from Winnipeg,

Thank you for your kind offer.

Would in 2-3 weeks when I have a fresh windows install and fresh M.2 drives etc  work for you? The tech who for the last 10 years at my local computer store who is also a gamer and is incredibly sharp is on paternity leave and will return to work shortly. 

After trouble shooting to the best of my ability, I'm not the sharpest when if comes to computers, i have been wondering if there is something in my 5 year old Windows10 install (but faithfully updated) that msfs2020 has decided to take issue with. 

Take care. Dave

6 minutes ago, Sonosusto said:

I would actually really like to help you solve this.

Okay.  Found and watched this video:
https://forums.flightsimulator.com/t/fixed-ctd-exception-code-0xc0000005-crash-to-desktop/266671

I realize I made a recent change to AI Traffic.  Found and watched this video and that seems in context to what I experienced yesterday.  So my first step is to address what I changed, though I made no notes about the change. Or simply turn AI traffic off.

1 minute ago, dbw1 said:

Greetings from Winnipeg,

Thank you for your kind offer.

Would in 2-3 weeks when I have a fresh windows install and fresh M.2 drives etc  work for you? The tech who for the last 10 years at my local computer store who is also a gamer and is incredibly sharp is on paternity leave and will return to work shortly. 

After trouble shooting to the best of my ability, I'm not the sharpest when if comes to computers, i have been wondering if there is something in my 5 year old Windows10 install (but faithfully updated) that msfs2020 has decided to take issue with. 

Take care. Dave

I would bet that little to none of your issues have to do with an MSFS or Windows installation. I can help you then as well. It wouldn't hurt to install it now and you can PM me or something.

Just now, Sonosusto said:

I would bet that little to none of your issues have to do with an MSFS or Windows installation. I can help you then as well. It wouldn't hurt to install it now and you can PM me or something.

Are you responding to me?

1 minute ago, fppilot said:

Okay.  Found and watched this video:
https://forums.flightsimulator.com/t/fixed-ctd-exception-code-0xc0000005-crash-to-desktop/266671

I realize I made a recent change to AI Traffic.  Found and watched this video and that seems in context to what I experienced yesterday.  So my first step is to address what I changed, though I made no notes about the change. Or simply turn AI traffic off.

I think some of that could have been relevant 3 years ago but that exception code is mostly related to addons from my experience.

Again, I will reiterate to use the addon linker tools and it will help rename those files. No need to delete scenery, change settings, reinstall anything or setting your traffic to 0. It likely has little to nothing to do with your issues.

 

1 minute ago, fppilot said:

Are you responding to me?

Both of you.

4 minutes ago, Sonosusto said:

Again, I will reiterate to use the addon linker tools

Are you referring to Addons Linker "addons checker"?

32 minutes ago, Sonosusto said:

Windows: the event viewer is mostly useless for this simulator and everything is pretty generic as "faults" go.

I disagree--in this example, the faults are not coming from an nvidia or AMD driver dll, which is an important datapoint when trying to determine if there's a GPU/driver-related problem or something else.

The C0000005 fault is a fairly common memory protection error.  As Frank has already alluded, it's good to start with that which has changed recently and either undo those changes or disable the potentially offending add-on(s) to try and isolate the problem.  And from there, it's the age-old drill of isolating add-ons to try and establish a link between the problem and a particular add-on.

Unfortunately, given that no two MSFS sessions are the same due to the vagaries of its server-client architecture, the problem could well be a transitory server-related issue.  So if a problem add-on does emerge as an apparent cause, it's prudent to re-enable it again and see if a repeat occurs.  It takes multiple hits to reach a reasonably solid conclusion when you can't establish a control case by reproducing a scenario where the error occurs.

Just to remember to those using the Rolling Cache, it's a good practice to re-generate it after each SU (and WUs too, if you fly frequently over the region that's being updated). Regenerating the RC solved a CTD issue I had at every flight over the NYC/New Jersey area (with the Longitude in my case) after SU11.

4 minutes ago, Bob Scott said:

I disagree--in this example, the faults are not coming from an nvidia or AMD driver dll, which is an important datapoint when trying to determine if there's a GPU/driver-related problem or something else.

The C0000005 fault is a fairly common memory protection error.  As Frank has already alluded, it's good to start with that which has changed recently and either undo those changes or disable the potentially offending add-on(s) to try and isolate the problem.

Unfortunately, given that no two MSFS sessions are the same due to the vagaries of its server-client architecture, the problem could well be a transitory server-related issue.  So if a problem does emerge as an apparent cause, it's prudent to re-enable it again and see if a repeat occurs.  It takes multiple hits to reach a reasonably solid conclusion when you can't establish a control case by reproducing a scenario where the error occurs.

You make a good argument but for me, I suffered from a lot...a lot of....insufferable CTD's and none of them had anything to do with memory faults. At least for me. I am not a computer expert by any means and the fault/exception codes did not help me, personally.

I guess the scenery conflicts can mess a lot of things up. Hence me keep mentioning the addon linker tools. They really helped me solve this issue.

 

Edited June 10, 20232 yr by Sonosusto