Just now, Bobsk8 said:

Yes, the same old, same old that I haven't seen in over a year. 

for me it's once a month since SU7. I did start to see a pattern recently... and the pattern is windows updates. Just had one WIN10 update today aaaand... CTD in the CJ4 after landing in Moscow. First CTD in a month.

I did sfc /scannow before I started the flight (because they say that's what you gotta do after a windows update), but that didn't help.

Just now, Fiorentoni said:

for me it's once a month since SU7. I did start to see a pattern recently... and the pattern is windows updates. Just had one WIN10 update today aaaand... CTD in the CJ4 after landing in Moscow. First CTD in a month.

I did sfc /scannow before I started the flight (because they say that's what you gotta do after a windows update), but that didn't help.

I had a windows update yesterday...

3 minutes ago, Bobsk8 said:

I had a windows update yesterday...

Try this just in case: https://forums.flightsimulator.com/t/ctd-fix-info/471880

34 minutes ago, Bobsk8 said:

I had a windows update yesterday...

I did as well but have not flown since then.  Q are you on SU9 or 10 Beta?  JIC that makes a difference here in the discussion.

How about, are u overclocking computer ? Maybe heat issue, happens to me when I get close to a major airport, on final, ex CYYZ and KBOS just to name a couple.

Just to report back, I have just finished my 7th flight after the 3 CTDs, first in over a year, and MSFS is back to the way it was before, with zero problems. I had already restarted the PC after each CTD, and changed nothing else. I am positive that something connected with the servers, either scenery, or possibly Real AI traffic, was causing this issue. I don't do Beta programs, so it wasn't that. 

Its summer - how about temps?

sp

I never had a problem with CTD's until a couple Nividia drivers ago (late May?) Those things were just junk. Rolled them back until new drivers were released and everything was ok again. 

Me too. Did you guys get a CTD without message? I got a couple of "memory cannot be read" errors with a CTD.

No CTDs here but flying only in Europe and with the Fenix or the Discus2C.

I am on Win 11.

I've been getting about 75% of flights crashing using Fenix.  PMDG has yet to CTD for me.  Hope the next update fixes things.

Server issues could be due to this perhaps?

https://www.bing.com/search?q=Google+Oracle+heatwave&efirst=3&filters=tnTID%3a"CD2C7838-6A0B-49da-95E9-96AC80884D4B"+tnVersion%3a"4672575"+Segment%3a"popularnow.carousel"+tnCol%3a"3"+tnOrder%3a"9aee6cf2-e70b-419e-83c6-59fe1dbb93f8"&form=HPNN01

sp

On 7/17/2022 at 9:35 PM, MaVe64 said:

I got a couple of "memory cannot be read" errors with a CTD.

I had several too in three months on a random basis and could never trace the issue, until last week, I realised that MSFS was still running normally in the background, so I gently pushed the error message to the left bottom side of my screen and hid it from my view, continued my flight and checked what was not working in my hardware setup (this is a hardware problem Kernel 141). It turned out that my keyboard was not working anymore, which was not important for me anyway since I have plenty of GoFlight modules to eliminate the need for a keyboard.

I completed my flight uneventfully, closed MSFS normally, verified the error message in the Windows error report, unplugged my keyboard and changed the USB plug to the 2.0 type. Problem solved. This came from the fact I bought three months ago a new PC with mostly USB 3.0 plugs which are not liked by a few hardware conceived before this new standard.

So the lesson is, before doing anything else, check your hardware connections - in particular USB -, next time you have an error message DO NOT click on OK or on the red cross at the top right, which would terminate your flight and MSFS, but do as I did if you see MSFS functioning with no other issue and analyse your hardware. You might be able to find the culprit easily.