3 hours ago, orchestra_nl said:

My case is different then, since it happens mostly enroute.In my last attempts I had CTD's in the middle of the North Sea, with no land whatsoever within 75 NM. A few times I had CTD's on approach to KBTR, but is not a very large airport.

This is similar to what I have experienced. All my crashes since the last update were enroute in the middle of nowhere in brazil (part of my around the world tour). I am thinking that there are two different ctd issues. One issue is approach and I would bet there event log for this says the faulting module (not application name) is FlightSimulator.exe. The enroute issue (at  least for me) says the faulting module is VCRUNTIME140.dll. I would also bet that right before either ctd, that there would be an event viewer Warning for Display saying, "Display driver nvlddmkm stopped responding and has successfully recovered.". Or something similar for AMD cards. This would lead me to believe that the time-out Vaccine is a temporary cure for both issues.

I have not tried it myself as I have now had 6 flights with no crashes after I deleted my rolling cache, rebuilt it, flew somewhere else, and then went back to where I had the ctds.

The approach issue reminds me of when the sim first released. I would get stutters and an occasional crash when going from downwind to base and my copilot announced my position. I have not had this since the second sim update?? That sounds like a sound or azure issue?

Great to hear that some of you actually got some flying done. After weeks, I am quite sceptical with every fix, since I tried so many.

@Bobsk8: I tried the Anti CTD vaccine but it didn't help. In fact, the sim crashed a bit earlier enroute.
Sofar, It doesn't seem to make a difference whether I have rolling cache disabled or not. Without AI, I still get CTD's but perhaps a bit later in flight.

I am now flying the exact same route (ESUE -> EGPN), with every USB device I can think of unplugged, except mouse and keyboard, let the AI pilot take of and then switch on the autopilot. It normally crashes after ~1 hour inflight.
There are no large airports along that route, and often the sim crashes above the North Sea. Except for oil rigs and ships there is no scenery to cause a crash.

I am probably frustrating myself by trying the same flight everytime, but at least I get more or less consistent crashes this way. I have tried many fixes before which sometimes seemed to solve the problem, only to find out they did not.

Off course I could fly another route and perhaps avoid a CTD that way, but I am not sure the problem is scenery related. Besides, when I purchased MSFS I was under the impression that we could fly anywhere in the world, instead of having to meander around unknown CTD areas.

It could be that this specific error code is actually a generic one, and is generated whether you have a scenery issue, a caching issue, an USB issue or just a bad day (or weeks).

 

2 minutes ago, Maladoror said:

This is similar to what I have experienced. All my crashes since the last update were enroute in the middle of nowhere in brazil (part of my around the world tour). I am thinking that there are two different ctd issues. One issue is approach and I would bet there event log for this says the faulting module (not application name) is FlightSimulator.exe. The enroute issue (at  least for me) says the faulting module is VCRUNTIME140.dll. I would also bet that right before either ctd, that there would be an event viewer Warning for Display saying, "Display driver nvlddmkm stopped responding and has successfully recovered.". Or something similar for AMD cards. This would lead me to believe that the time-out Vaccine is a temporary cure for both issues.

I have not tried it myself as I have now had 6 flights with no crashes after I deleted my rolling cache, rebuilt it, flew somewhere else, and then went back to where I had the ctds.

The approach issue reminds me of when the sim first released. I would get stutters and an occasional crash when going from downwind to base and my copilot announced my position. I have not had this since the second sim update?? That sounds like a sound or azure issue?

I just get the 0xc0000005 error in the application log. I will have to check whether it says 'faulting module' or not. I don't have any other errors or warnings around the same time (not in application log AND system log) except for a 'disk x has been surprise removed', which might be the rolling cache disk that the sim is using.

If I get any other warnings or errors, it is when I happen to be running a simconnect application when the sim crashes, because some of these will be taken down along with MSFS. LNM usually doesn't crash, but NeoFly always does, usually with a  .Net error.
But the sim will crash even when I am not running these programs.

I am starting to believe that, although we all get the same specific error code, the cause of these crashes could be entirely different. The sim always crashes the same in the same way though, with the sound starting to waver just before the crash. One of myriad of suggestions is to disable Azure ATC, but even turning ATC off completely hasn't solved the issue in my case.

 

 

I was getting these CTDs and error code, turns out I had set the windows virtual mem to a fixed value some time back, putting this back to system managed and I havent had another CTD after 4 hrs buzzing around London 

As a side also running the very latest win10 21H1 

Well, first CTD in days, and it was exactly at the location i had reported after Sim update 2 (at 39k passing a waypoint very close to LFRS enroute to LFBZ from EGLL) I have tried that route 3 times now, and everytime to nearly the same spot bam! CTD. reported it yet again

All other flights ok.

I just installed the Vaccine and am retrying a flight that crashed on approach a couple of hours ago. 

1 minute ago, Car147 said:

Well, first CTD in days, and it was exactly at the location i had reported after Sim update 2 (at 39k passing a waypoint very close to LFRS enroute to LFBZ from EGLL) I have tried that route 3 times now, and everytime to nearly the same spot bam! CTD. reported it yet again

All other flights ok.

Years ago, if memory serves me correctly, FSX used to have that issue and it was usually a faulty or duplicate BGL file. 

30 minutes ago, Bobsk8 said:

Years ago, if memory serves me correctly, FSX used to have that issue and it was usually a faulty or duplicate BGL file. 

MSFS is now less than 7 months post-release and is in an ultra-dynamic pace of development.  I think it's wise to expect these sorts of things for the coming year or so.  IOW, align your expectations with this reality else be surprised and disappointed.  And yes, be sure to harken back to FSX in its early months to put this in context.

47 minutes ago, Bobsk8 said:

I just installed the Vaccine and am retrying a flight that crashed on approach a couple of hours ago. 

This time, post vaccine , flight went smooth as silk.  keeping fingers crossed. 😃

11 minutes ago, Noel said:

MSFS is now less than 7 months post-release and is in an ultra-dynamic pace of development.  I think it's wise to expect these sorts of things for the coming year or so.  IOW, align your expectations with this reality else be surprised and disappointed.  And yes, be sure to harken back to FSX in its early months to put this in context.

I do . and there's no problem. As you say these things are going to happen and they are frustrating, but as it matures hopefully they become less noticable.

It's also a testimony to just how much many already deeply like what they see in MSFS, and no doubt seriously.  If it wasn't so compelling there would not be so much hand-wringing w/ these hiccoughs, and that is what they are I believe.  It helps to have the old girl still functioning, P3D that is, which I enjoy immensely still, despite its own warts, which I've dealt with using the new mRNA DimPhotonX vaccine which works wonders for my experience.  Really, it's PMDG and FSCaptain that are responsible for the immensely because without both of those, I'd be doing more hand-wringing in the MSFS Forums.  I'm very glad to be able to participate in MSFS' development for half the cost of my first dose of P3D v2 way back when.  Actually, that's not true.  To get P3D v2 tolerable scenery-wise it was another $500 worth of Orbx and planes from PMDG, but then we dialed back so much of it anyway to allow stutter free smooth performance at reasonable frame rates it was hardly worth the cost for the scenery upgrades.  In fact now, w/ a new machine functioning at nearly 150% of the performance of the prior box we're back to landclass w/ Orbx Global only + high quality payware airports, because that is all that is needed for a fabulous experience provided you've been properly vaccinated.

Nailed it @Noel, it is a fantastic experiance, and can only improve. Once the bugs have gone there will be no holding this sim back. It's got the visuals, as more and more aircraft built and utilising all MSFS can offer with more complex systems this will be the go to flight sim.

Yes, when it works, this sim is a great experience. I still remember the panic when I found myself flying VFR inside a thick cloud layer. The panic felt quite real when I lost situational awareness, never had this with any other sim.

The good news about my third testflight is that it made it all the way to my destination. Without USB controllers the AI pilot had to do the work off course. I had tried without USB controllers before, but forgot to disconnect the USB hub inside my monitor, which has 2 webcams connected, and I left another USB hub (empty) connected.as well.
The next test will be the same route but with Little Navmap and perhaps Neofly running, to rule out Simconnect being the cullprit.

If it is really USB, I have ordered an USB 3.0 addon card which hopefully allows me to use the controllers in the future and hopefully AMD will come up with a solution as well.

Just an update on my situation with this error:
I have been able to narrow down the reason for the CTD in my end, and it is pretty clear an USB issue.

I have done the same flight several times now, and the twice was I able to complete the flight. Both times I had all USB devices disconnected except a keyboard an mouse through an USB 2.0 hub. All flights flown with the same configuration (AI offline 70%, Azure ATC, graphics at Ultra, rolling cache on, and the same set of community addons, like GNS530 and G1000 mod).
The second flight I also had 4 external programs with simconnect running.

After those 2 succesfull flights I reconnected my USB devices but as before I let the AI pilot take off and use autopilot enroute. After ~30 minutes, I had a CTD again.
So I am pretty sure my CTD's are caused by something USB related, whether a specific device or the USB controller in the x570 chipset.

I still have some troubleshooting to do, to find out whether I can solve this by using different USB ports, or an external USB card etc. Perhaps some USB related BIOS settings or a patch from AMD might be neccesary as well.

I want to thank you all sofar. I had almost given up since I had done so mucht troubleshooting already, tried dozens of fixes that didn't fix it etc. Upon reading this thread I got some new energy to try again. It isn't solved yet but at least I have a clue as to the cause.

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 unusual CTD's from time to time.

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.

 

Edited March 8, 20215 yr by bobcat999