Ugh! Not me!  I annotate my CTDs in my excel logbook.  Last one was all the way back on January 8th of 2022.  Almost a year and a half ago.  Had two today. Both crashes all the way to desktop.  No messages or dialogs.  Have not installed anything new.  Have made no driver updates.  What a mystery.  For a 100 minute flight the first CTD was about 40 minutes in.  Second attempt CTD was 80 minutes in.  Both occurred when using external views, each a great distance apart in location.

Deleted my rolling cache; cold booted system; started MSFS, and reestablished rolling cache between the two flights.  Go figure.  Last week for the first time in ages I had two consecutive flights with bad stutters.  That cleared up for several ensuing flights.

Warmer weather.  Maybe something is overheating?

Did you recently change your vidcard driver?  Any other recent config changes?

1 hour ago, fppilot said:

Have made no driver updates. 

 

6 minutes ago, Mace said:

Did you recently change your vidcard driver? 

????

9 minutes ago, fppilot said:

 

????

I just finished working all day, by 6 pm local my IQ is slashed by half.

3 hours ago, fppilot said:

Ugh! Not me!  I annotate my CTDs in my excel logbook.  Last one was all the way back on January 8th of 2022.  Almost a year and a half ago.  Had two today. Both crashes all the way to desktop.  No messages or dialogs.  Have not installed anything new.  Have made no driver updates.  What a mystery.  For a 100 minute flight the first CTD was about 40 minutes in.  Second attempt CTD was 80 minutes in.  Both occurred when using external views, each a great distance apart in location.

Deleted my rolling cache; cold booted system; started MSFS, and reestablished rolling cache between the two flights.  Go figure.  Last week for the first time in ages I had two consecutive flights with bad stutters.  That cleared up for several ensuing flights.

It's incredibly frustrating when it's out of nowhere. I take it you fly that same route often? Or has it been a while on that flight plan?

It could be video card drivers as one other here mentioned.

Otherwise, since I used addon linker and renaming some files through the program my CTDs have stopped so far.

Which plane was it? Any GNS related mods? What area did this happen?

1 hour ago, Sonosusto said:

I take it you fly that same route often?

No.  First time.  New York Lagaurdia to Chicago Midway.  Fly into Midway often.  First flight I can recall out of NYC and had some sophisticated NYC scenery loaded.  But first CTD was 30 minutes out.  The second was 80 minutes out of NYC.  So timing was not similar.  Both CTDs occurred over areas of sparse scenery density.

1 hour ago, Sonosusto said:

It could be video card drivers as one other here mentioned.

But I clearly stated I have made no recent changes.  

1 hour ago, Sonosusto said:

Which plane was it?

Plane is I do not believe an issue.  Will not name it here.  It is a test version but I have already logged 11 flights and 30 hours on this version without incident. My previous CTD was 1-08-2022, a long time ago, and I have logged over 300 hours in test and released versions of the aircraft.  Will also mention that I have not even once seen the model associated with anyone else's CTD.

1 hour ago, Sonosusto said:

What area did this happen?

See response to first quote above.

Tomorrow I will vacuum clean my CPU case.  I do note some accumulation of dust which may be restricting airflow.  However when I have checked my system temps previously during flights my CPU was not above the mid-50's and GPU 72° to 76°.  Have not checked it recently.  My system specs are below in my signature.

Ah. Highly doubt its hardware or heat related then.

New York to Chicago did have issues for me several times. Frame drops, random CTDs. I used addon linker and used its several added functions to rename lib files or model files..As it turns out, there was a lot scenery conflicting on the way to Chicago.

I did that and my CTDs stopped. Overwhelming amount of CTDs are addon related.

Also, try a different plane on the same room as well.

Edited June 10, 20232 yr by Sonosusto

New York to Chicago?  You're just asking for trouble.

I would be surprised if I did not get a CTD.

sp

Remove all MSI, EVGA, etc. programs such as Afterburner, Precision X1, etc. Not just unable them, but uninstall them. Then open nVidia Control panel’s 3D settings and reset them all to default.

 

See if that fixes the problem.

11 hours ago, fppilot said:

No.  First time.  New York Lagaurdia to Chicago Midway.  Fly into Midway often.  First flight I can recall out of NYC and had some sophisticated NYC scenery loaded.  But first CTD was 30 minutes out.  The second was 80 minutes out of NYC.  So timing was not similar.  Both CTDs occurred over areas of sparse scenery density.

Ok let's see if my brain is working today.

In the past, have you flown into, or out of NYC with this "sophisticated scenery" loaded?  Or is this the first time in or out of NY with it?   Is it SamScene NY?

5 minutes ago, Mace said:

In the past, have you flown into, or out of NYC with this "sophisticated scenery" loaded?  Or is this the first time in or out of NY with it?   Is it SamScene NY?

 

11 hours ago, fppilot said:

No.  First time.  New York Lagaurdia to Chicago Midway. 

LOL!  
Yes. SamScene.  Note again however with the first CTD I was over 30 minutes up off KLGA heading NW.  With the second CTD I was 80 minutes after departure from KLGA.  Can a scenery in MSFS left that far in arrears still cause a CTD?

Do the CTD happen no matter which aircraft you were using?

28 minutes ago, fppilot said:

 

LOL!  
Yes. SamScene.  Note again however with the first CTD I was over 30 minutes up off KLGA heading NW.  With the second CTD I was 80 minutes after departure from KLGA.  Can a scenery in MSFS left that far in arrears still cause a CTD?

My thought was that something could be happening when the scenery is unloaded.

I never use rolling cache, and never have a CTD.