Replicated once again.
- Tried to load MSFS. Since the previous flight (C152 over Yosemite) had ended gracefully, I didn’t expect a main menu CTD. I was right, so I was then able to load a flight using CJ4 WT this time.
- Again MSFS crashed while pushing back CJ4 with all systems running.
- Next attempt to load MSFS failed because it CTD’ed during the transition from the initial loading screens to the main menu. Again this is a pattern I’m almost always seeing after a previous CTD.
- Restarted Windows, tried to load MSFS, had the exact same CTD (during the transition to main menu).
- Loaded X-Plane, played for a couple of minutes and quit. Didn’t change anything else.
- Loaded MSFS, this time it reached the main menu just fine, so it let me start a flight.
Go figure. At least I’ve found a consistent way to exit the main menu CTD loop, which I suppose counts for something. Now it’ll be easier to start experimenting with different AMD drivers (e.g. go back from 21.3.2 to 21.3.1 WHQL which are considered more stable).
Because I suspect the vcruntime errors I’m seeing may be the result of more than one root causes and these driver timeout/DLL errors are just generic, because MSFS/Windows/AMD drivers or all of them together cannot handle some exceptions or have conflicts between them or whatever. So the reason why MSFS sometimes crashes in the main menu before or after a flight, may be different than in-flight CTDs, despite me getting the same errors in event manager. At this point anything’s possible really. Goblins included.