1 hour ago, St Mawgan said:

So you still have CTD's after doing the above whereas for most of us, the CTD's have completely vanished without having to update Windows. It's a mystery! 

It's not a mystery at all. The ntdll.dll CTD has never happened to me but the memory access error and now this one:

will not go away.
They do say this:

Quote

Important note: this procedure only resolves the specific crash related to ntdll.dll on PC. It does not fix any other CTDs.

If anyone has any constructive ideas, please go ahead.

Edited August 24, 20223 yr by Reader

1 hour ago, St Mawgan said:

So you still have CTD's after doing the above whereas for most of us, the CTD's have completely vanished without having to update Windows. It's a mystery! 

Well, it's a different type of CTD. A different species sort of. The frequent CTDs during the weekend seem to have been ntdll.dll related, whilst "my" (gee I feel special) type of CTD is related to a memory address that can't be read because it doesn't exist. I.e. it's a "null error" based on my (very) limited understanding. I'm not a software engineer, so all you IT experts out there, please feel free to "fire at will". 

But yeah, to me this is certainly a mystery. Or to rephrase that: Perhaps Asobo's code works in mysterious ways?

 

27 minutes ago, Reader said:

It's not a mystery at all. The ntdll.dll CTD has never happened to me but the memory access error and now this one:

will not go away.
They do say this:

If anyone has any constructive ideas, please go ahead.

Ah yes, the exception breakpoint. Lol. I had that one too, but for some reason it does not prefer my system as much as the memory error. Come to think of it, I think my breakpoint is about to be reached. 

EDIT: Sorry, that was not very constructive. There is a thread on it here that you can vote on (and it's been "bug-logged"):

https://forums.flightsimulator.com/t/flightsimulator-exe-application-error-0x80000003-a-breakpoint-has-been-reached/334962

Edited August 24, 20223 yr by Cpt_Piett

2 hours ago, Paul K said:

Just done a flight of almost 6 hours without a problem, in an area where I had 4 CTDs in the last two or three days ( each CTD being after about 20 to 30 minutes ). I think I can safely say it's fixed, at least for me.

Try now one on 12hr.

19 minutes ago, peloto said:

Try now one on 12hr.

No, six hours is more than enough to prove the sim is stable.

1 minute ago, Paul K said:

No, six hours is more than enough to prove the sim is stable.

It depends on which CTDs you suffer from. As this thread most likely relates to the ntdll crashes, that seems to be fine for now. Other CTDs however, can appear very infrequently e.g. days in between. 

3 minutes ago, Cpt_Piett said:

It depends on which CTDs you suffer from. As this thread most likely relates to the ntdll crashes, that seems to be fine for now. Other CTDs however, can appear very infrequently e.g. days in between. 

Well, yes, I suppose it's based on one's own experience of the sim. The ntdll issue is the only persistent CTD issue I've had in 9 months of owning MSFS, with maybe a total of 4 or 5 others on start up - the sim always ran on the second try, however. I had a problem with stuttering, but that's resolved itself. Overall, for me at least, I'd consider it stable.

I don't know what solved your individual problem, but for me ntdll CTD was pretty much always an unstable overclock either CPU or RAM 

10 minutes ago, sonny147 said:

I don't know what solved your individual problem, but for me ntdll CTD was pretty much always an unstable overclock either CPU or RAM 

It can be, but in this case, lots of users had it occur over a number of days when it was previously stable.

The thread at the official forums was over a thousand posts long in no time.  it was a widespread issue.  Seems to be solved now anyway.

1 hour ago, Paul K said:

No, six hours is more than enough to prove the sim is stable.

For you.

It may be a matter of trust.  Will MS do anything to sabotage it's online gamig platform?  Probably not.  However some nefarious players might.  So we need to have a certain level of trust to enjoy our favorite sim.  

MS is not the enemy IMO.

sp

I have had maybe 4 CTD's in 500 hrs of using FS2020.

And none in the last few months, I have used it since day one.

Love it. Deleted X-plane more than a year ago.

I wrote this:

The ntdll.dll CTD has never happened to me but the memory access error and now this one:

will not go away.

Many thanks to @Cpt_Piett for this link, which solved the exception Breakpoint error at once.
Although it may not be the solution for anyone else, I finally uninstalled Nvidia Driver 516.94
and reverted to 516.40.
Since then, MSFS has run for three hours without a CTD.
Its previous record was around ten minutes.

 

Edited August 25, 20223 yr by Reader

I got the weekend CTDs but last night flew ECHK - LPPT with no CTD all smooth as silk in the Fenix.

Din't yet get that new "Breakpoint" plague 😕

Updates to the XBox App, and Gamining services this morning..