10 hours ago, DAD said:

No you are not. Same here and like you it happened around major airports, either after takeoff or before landing. Though I only tried third party airports, namely LOWW, EDKK and EKCH. Last time tonight in the default neo, yes I even deleted the FBW mod just to rule everything out and now my /community is empty. Yet I had a CTD right after leaving LOWW to EKCH. Multiplayer, photogrammetry and real air traffic are off anyway. Only live weather on. Tomorrow I will try some low and slow in the King Air or TBM at „smaller“ airports and see how that goes 

Isn't it utterly frustrating? I already renamed my Airbus to Scarebus 🙂 Oh well, hopefully the good folks at Asobo will come with a fix pretty soon. I filed a bugreport with them and, as someone here in this forum mentioned, there are a lot of conversations about this phenomenon going on in Microsoft's flight simulator forum as well.

8 hours ago, Flyfaster_MTN002 said:

have you read the CJ4 thread? Did you use the MSFS flight planner?

No, I used Simbrief's planner

 

49 minutes ago, Virtual-Chris said:

I went back to the last driver I was using in early December... 457.51

Unfortunately I cannot rollback to a previous driver, I guess disk cleanup took care of removing the previous one. NVidia's website only provides their latest driver, which is the allegedly offending one. I will search the net for 457.51.

Later: Found and installed 457.51. Will give it a go later today and report back if indeed this driver solved the problem.

Edited December 26, 20205 yr by hvw

After installing NVidia driver 457.51 and let MSFS2020 run for 2 hours without any intervention, I did two flights, EPWA-EDDK and EDDK-LSZH. No problems whatsoever were encountered, albeit that on my approach into LSZH it was pretty hard to get the FBW A320's speed down.  

5 hours ago, hvw said:

NVidia's website only provides their latest driver

Not sure where you were looking on NVidia's website, but I can see (and download) driver versions going back to 456.55 - Release Date: Mon Sep 28, 2020. This is where I go: https://www.nvidia.com/en-us/geforce/drivers/. Specify your system info and do a manual search.

Also, it is highly recommended that if one is rolling back drivers manually that one should use DDU (https://www.guru3d.com/files-details/display-driver-uninstaller-download.html) to remove all traces of the current driver. Not doing so may result in bits and pieces of the newer driver not being replaced by the same bits of the older driver. Here's a video on what it does and how to use it: 

 

Hope that helps,

...jim

 

Edited December 26, 20205 yr by JimBrown
Add YouTube link

Thanks Jim, I guess you didn't read the note I posted fully or carefully 🙂

 

Didn't see it until just now, I guess you posted while I was writing and researching. 😉

Glad all is working!

...jim

 

3 hours ago, hvw said:

After installing NVidia driver 457.51 and let MSFS2020 run for 2 hours without any intervention, I did two flights, EPWA-EDDK and EDDK-LSZH. No problems whatsoever were encountered, albeit that on my approach into LSZH it was pretty hard to get the FBW A320's speed down.  

Good that solved your problem. The real issue now is... are we going to have to test various driver and MSFS combos going forward for stability? I know I don’t have time for that nonsense. 

Not sure that a simple thing as changing a video driver solved the problem. It's just a gut feeling that it isn't.

When I look at the error report in EventViewer it clearly states that the offending application is flightsimulator.exe. If it was a video driver issue, the error message would be a different one. When I Google the errorcode that is in the errorreport, I find this here: Exception code 0xc0000005 is an Access Violation. An AV at fault offset 0x00000000 means that something in your service's code is accessing a nil pointer. 

The fault offset was at 0x000000000060e4d5. (Just fyi 🙂 ).

If I hear back from Zendesk or if I find more on this matter I will of course post it here.

 

 

 

OK, I had a response from Zendesk. They asked me to perform the usual steps, like removing all add-ons from the Community folder, turn off overclocking (my system is not overclocked), check antivirus software, update graphic drivers (which at my system seemed to be one oi the culprits (see above)), update Windows 10 (I am at the latest version already) and check that the English Language Package is installed correctly. Well, all of this is in perfect working order on my system, but then they also stated that I should disable rolling cache. And that's what I haven't done yet. I will do so tomorrow and see what happens (or doesn't happen). Anyway, if I run into CTD's again they asked me to send them an Msinfo and dxdiag report for further investigation. 

Well, they were pretty (better said very) fast in responding. Perhaps the above will help all others that suffer from these CTDs as well. If it doesn't, file a bug report at Zendesk as well, perhaps it all can or will lead to a fix.

2 hours ago, hvw said:

Not sure that a simple thing as changing a video driver solved the problem. It's just a gut feeling that it isn't.

When I look at the error report in EventViewer it clearly states that the offending application is flightsimulator.exe. If it was a video driver issue, the error message would be a different one. When I Google the errorcode that is in the errorreport, I find this here: Exception code 0xc0000005 is an Access Violation. An AV at fault offset 0x00000000 means that something in your service's code is accessing a nil pointer. 

The fault offset was at 0x000000000060e4d5. (Just fyi 🙂 ).

If I hear back from Zendesk or if I find more on this matter I will of course post it here.

 

 

 

There's no doubt that the symptom is MSFS crashing.  The cause, at least in my case, was related to the GPU driver.  It seems clear to me that the combination of the latest MSFS update and the latest Nvidia driver are not working well.  Unfortunately, we can't roll-back the MSFS update.  I'll be interested if you CTDs continue after updating your driver again.

12 hours ago, Virtual-Chris said:

I went back to the last driver I was using in early December... 457.51

11/22/2020  is the date on that driver.

12 hours ago, Virtual-Chris said:

I went back to the last driver I was using in early December... 457.51

11/22/2020  is the date on that driver.

1 hour ago, Virtual-Chris said:

There's no doubt that the symptom is MSFS crashing.  The cause, at least in my case, was related to the GPU driver.  It seems clear to me that the combination of the latest MSFS update and the latest Nvidia driver are not working well.  Unfortunately, we can't roll-back the MSFS update.  I'll be interested if you CTDs continue after updating your driver again.

Yes, there is or must be a causal connection between the last FS update and the latest NVidia driver. Tomorrow I will install the latest NVidia driver again and also disable rolling cache as well and see where that leads me to. Will post the result here again.

34 minutes ago, Fielder said:

11/22/2020  is the date on that driver.

Thank you. Yes, that's the one that I've got currently installed.