I flew from Iceland to Dublin Intl this weekend trying to get a CTD but no luck. I really wonder what is so different between your setup and mine.

35 minutes ago, bobcat999 said:

I remember MSFS had a few USB related issues early on.  One where it wouldn't even start.  I wonder if it is a spill over from that, as quite a few of us have them.

If you think it is USB related, I suppose you have tried all the common things to look at?
Set Legacy USB from the BIOS if there is a setting.
Install the latest motherboard drivers.
Turn off power saving features on the USB ports from your power profile.

Other than that, it might just be a USB device that has gone a bit bad.  I had it recently.  An old Thrustmaster joystick started disconnecting and reconnecting every few minutes, and MSFS would freeze sometimes.

Thanks for the tips. I had turned off power saving for all devices (quite a list to go through) and using the latest motherboard drivers already. I could look into settings thingst to legacy, but that might create problems using a USB keyboard on startup..

MSFS just CTD'd again with just my controllers connected, so I have to unplug them one a time to find out if there is a specific one. If so, I hope it's my CH quadrant as I am planning to replace it anyway.

MSFS indeed had USB issues and in my experience a patch often works around the problem instead of eliminating it entirely, solving it for most but not all cases.

Three days after CTD vaccine, and not one CTD. That is a record for me. 

I guess FS never let you get bored.

I never experienced CTD's in MSFS (I guess I was lucky)... until now. Today, on my second CRJ flight, right on the approach to LGAV, I got exactly this type of CTD and it happened exactly as it is described in this thread - first there were 1 second pauses with no sound and when I was about to land - CTD. Exception code 0xc0000005. The flight was about 2 hours long. I was doing 4 hour flights without issues until now.

Since this post is a few months old - was there ever a reason or a solution for this issue?

 

Edited August 20, 20214 yr by Tomaz Drnovsek

32 minutes ago, Tomaz Drnovsek said:

I guess FS never let you get bored.

I never experienced CTD's in MSFS (I guess I was lucky)... until now. Today, on my second CRJ flight, right on the approach to LGAV, I got exactly this type of CTD and it happened exactly as it is described in this thread - first there were 1 second pauses with no sound and when I was about to land - CTD. Exception code 0xc0000005. The flight was about 2 hours long. I was doing 4 hour flights without issues until now.

Since this post is a few months old - was there ever a reason or a solution for this issue?

 

For me it was dumping my AMD GPU and getting a Nvidia GPU. 

Just FYI, I reported a repeatable CTD (same Exception code) with the CRJ700 using the Flightbeam KDEN (after removing the ASOBO KDEN) to Aerosoft just yesterday. I tried the same flight (KASE LINDZ9 LINDZ IDENE JNETT SSKII2 KDEN at 25K ft) with the CJ4 and the TBM and no CTD. Their answer was "That things happen with the CRJ only is not too surprising as it is the first aircraft created in C++ and not Javascript.".

Not sure what that means as far as a solution as this may have nothing to do with the KDEN scenery. I asked whether a solution was forthcoming, but no reply yet. BTW, I use an NVIDIA RTX 3080 ti.so I don't think this is an AMD issue

40 minutes ago, rwilsonlj said:

Just FYI, I reported a repeatable CTD (same Exception code) with the CRJ700 using the Flightbeam KDEN (after removing the ASOBO KDEN) to Aerosoft just yesterday. I tried the same flight (KASE LINDZ9 LINDZ IDENE JNETT SSKII2 KDEN at 25K ft) with the CJ4 and the TBM and no CTD. Their answer was "That things happen with the CRJ only is not too surprising as it is the first aircraft created in C++ and not Javascript.".

Not sure what that means as far as a solution as this may have nothing to do with the KDEN scenery. I asked whether a solution was forthcoming, but no reply yet. BTW, I use an NVIDIA RTX 3080 ti.so I don't think this is an AMD issue

Yeah, I have RTX 2080Ti. From what you say I assume it's a CRJ issue. As I said, I can do 4 hour flights in other aircraft, never had an issue. Lately I started to fly the CRJ and this appeared. 

Ok, in my case it's not CRJ.

This was not actually a test but just a coincidence. I first made a flight with CRJ to LEAM, 2 and a half hours long. No issues. Then I made the same flight with TBM, only that in second case I used time acceleration. Right on the approach, about 1000ft AGL, CTD.

I'm sure this is purely MSFS issue. No matter how long the flight is, 1,5 hours, 2,5 hours,... whatever aircraft, it CTDs on the approach about 1000ft AGL. Don't tell me it's just a coincidence that whatever would be wrong on my side it always "brakes", purely by magic, when on approach. I also don't have any addons active, no AI traffic.

Hello Tomaz,
I haven't gotten rid of the CTDs entirely, but the situation is much less critical. Let's say now I can expect a CTD every 10 flights.

My three tips are the followings:

1/Rename the Community folder and create a new, empty one. Most CTDs are caused by outdated or incompatible mods.
2/Delete Content.xml and let MSFS create a new one.
3/ And above all, remove all overclocking from your PC and check that your drivers are up to date.
Hope it helps.

Edited August 21, 20214 yr by David Roch

40 minutes ago, David Roch said:

2/Delete UserCfg.opt and let MSFS create a new one.

Deleting or renaming Usercfg.opt on my system prompts MSFS (Microsoft Store version) to ask for a full reinstall.
Do you mean Content.xml?

 

Edited August 21, 20214 yr by Reader

Ohhh, my bad!
Yes, of course, sorry for the confusion!

Post edited.

Edited August 21, 20214 yr by David Roch

In my case after SU5 the CTDs showed up, but i had not really tried to use MSFS seriously until my PC upgrade arrived, combined with much better and smoother FPS. I started off by putting my CPU and RAM back to stock settings, and removing all add-ons from the community folder. I still had CTDs. They occurred every other flight. Then i removed Track IR. That eliminated almost all of them, and now i could fly much longer without issues. But i still got them sometimes, ultimately linked to FlightBeam’s KDEN. Removed that and every other add-on i had installed via marketplace that wasn’t official Asobo or MSFS.. At this point i could not get my system to CTD. All stock MSFS. 

I can confirm that on my system Track IR, FB KDEN, and FBW A320 cause CTDs on my PC. In the case of FBW A320 just having that mod enabled caused CTDs, as i do not need to actually select it for a flight to get a CTD.

Today i fly without CTDs and have not had one for many flights. 

Edited August 21, 20214 yr by RobJC

Humor me...

How can addons, PC overclock, USB peripherals, mods, Big Mac and sunny weather cause the sim to CTD always, I repeat, always on approach, no matter how long the flight is? One hypothetical explanation why one of those things would cause CTD always in the same manner and not MSFS itself?

6 minutes ago, Tomaz Drnovsek said:

Humor me...

How can addons, PC overclock, USB peripherals, mods, Big Mac and sunny weather cause the sim to CTD always, I repeat, always on approach, no matter how long the flight is? One hypothetical explanation why one of those things would cause CTD always in the same manner and not MSFS itself?

I will bet that someone will say that there is a fault in your PC that causes this problem. It digital circuits know  when you are about to land...LOL....

Edited August 21, 20214 yr by Bobsk8

Big Macs cause overweight, not CTDs, unless you add hot spicy sauce and then, you can really crash yourself onto your desktop.

I was very skeptical, like you are, but I've learned from my mistakes and I can assure you that all the above can lead to instability and strange things like crashes "only" during approach phase.
Up to you to follow/or not these elementary tips, just want to save you some hard time 😉.