the_jovian

Haven't tried any of the latest workarounds, just updated to the latest patch. Looks like I'm also crashing on mission end now, not at mission start.

I'm going to try the W8 compatibility mode too. Initial tests look promising... When DCS crashes, it dumps out the loaded modules in the following way: 2021-05-15 22:04:29.929 INFO DCS: enumerating loaded modules 2021-05-15 22:04:29.929 INFO DCS: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe, 21838176 bytes, created 14:4:2021-15.47.58, written 14:4:2021-15.47.58, accessed 15:5:2021-22.4.30 2021-05-15 22:04:29.929 INFO DCS: C:\Windows\SYSTEM32\ntdll.dll, 2024728 bytes, created 29:4:2021-15.34.41, written 29:4:2021-15.34.41, accessed 15:5:2021-22.4.30 Is there any way to get the same output from DCS when the game doesn't crash?

Yeah, although I originally thought that the WIndows patch helped, I don't think it actually did anything at all related to this. Here are some theories that I have on what might be happening based on previous hard to pin down crashes. I think the key issue is that only some users are affected. Therefore it has to be something in these specific user's machines that is different than the dev teams. So what could it be? Libraries: if the Windows 8 compatibility actually works, then this might be the case. I've seen strange crashes when clients have had old/different versions of .NET environment installed. I don't think this could be the case here, but maybe another library? See also https://superuser.com/questions/133746/how-does-the-compatibility-mode-in-windows-work Localisation: I've seen strange crashes when there is a conflict in, e.g., what decimal separator is used. For example, one library pulling it from Windows region settings and another assuming a period. Then you could, e.g., get a conflict between comma and a period, leading to string-number conversion errors. This could then lead to a crash if you try using the result in dynamic memory allocation. I just remembered that I'm using a comma as the separator so I'll try switching it to a period for giggles. [edit]: tried this, no luck Environment, like installation paths or usernames. Sometimes I've seen bugs where a fixed array just overflows if the path name is unexpectedly long. But my username isn't long at all. Maybe something different? Files gathering somewhere in the system causing some type of overflow. That's what we're trying to fix with deleting the temporary archives. I haven't really had much success with this though. I wonder if we've identified all the temporary folders where DCS is writing stuff? Drivers: but this crash seems to be happening with all kinds of configurations. Maybe we all share some kind of a (virtual?) peripheral that's causing this? For example I'm using vJoy with Joystick Gremlin, could something like that be causing it? Settings: but all kinds of driver and DCS settings have been suggested with no luck. Modules: I have a feeling that the F-14 is particularly crashy, but could it be that there's some module which if installed is causing this? One possibility to keep in mind is that when you compile code with a non-release configuration, there's might be some extra stack space available. Also variables might get initialized to zero which won't happen in production. I've had this happen a couple of times, see, eg., https://stackoverflow.com/questions/186237/program-only-crashes-as-release-build-how-to-debug .I'm sure there's a bunch of other differences as well. But I think the closed beta testers like @Flappie will have a release build, so this seems pretty unlikely. I'm not a professional software developer by any means. Can you think of any other avenues of investigating this?

As far as I can tell KB5001330 should be automatically uninstalled via WIndows Update. See this article for details: https://www.bleepingcomputer.com/news/microsoft/microsoft-pushes-emergency-fix-for-windows-10-kb5001330-gaming-issues/

For whatever reason, the creashes have returned with a vengeance. None of the workarounds seem to work now.

I also haven't had crashes. DCS has hung a couple of times (once per few days) when loading a mission but this seems like a different issue.

Cautiously optimistic again. The F-14B Carrier Case 1 mission is no longer crashing the second time I load it! Note that to get the Windows updates I had to use "Check for Updates" from the start menu -> "View Optional Updates". Might be worth a shot for someone else as well...

Just an FYI that I've had greatly reduced crashes lately, and the major change that I had was that I downloaded all the optional Windows 10 updates. In particular, the 20H2 update (and associated fixes which included the KB5001330 rollback. Fingers crossed...

AV settings didn't help, neither did deleting what Flappie suggested. Hmm. I'm out of ideas at the moment but will keep sending crash reports.

I did a diff of my crash log and yours, ignoring the differences in time stamps, usernames, and install folders. I've attached the common rows that we had. Hard to say what would result in the crash, but these look a bit suspicious: 2021-04-27 18:28:44.020 ERROR VISUALIZER: ILV for cockpit 'F14B_Cockpit' not found 2021-04-27 18:28:44.770 ERROR COCKPITBASE: Cockpit: failed to init geometry, pointer was not found. 2021-04-27 18:28:45.090 WARNING LOG: 2 duplicate message(s) skipped. 2021-04-27 18:28:45.114 ERROR COCKPITBASE: Cockpit: Clickable - Wrong connector name PNT_MCB I'll try your suggestion about the AV settings. I'm using different AV software though. common-f14-crash-log.txt

I haven't got MSFS2020 installed and this is a pretty fresh system, only about 2 months old. That did give me an idea, though this is just a shot in the dark. @Flappie, what version of .NET are you running? I'm using 4.8.4084.0 .

I'm running the standalone, but it might be somewhere in C:\Program Files (x86)\Steam\steamapps\common , there's probably a DCS folder somewhere there. Maybe under Eagle Dynamics? This didn't help for me unfortunately, even though I thought it did at first.

I can consistently crash every time I try to refly the F-14B Training mission "Basics - Carrier Case-1 Trap". I don't think I've ever been able to refly this successfully. Can anyone else try this one?

This seems to have fixed it for me. I was able to "fly again" multiple times in a row. Has anyone else tried this? Spoke too soon, started crashing again.

This doesn't help unfortunately. Crashing pretty consistently the second time I load a mission. I've been submitting my crash reports.

There's an issue where pressing the keybind for the INS CRS CW/CCW causes the course line to spin continuously when the keybind is pressed once. The behavior is the same if you press the bound joystick button once. It almost looks as if the keybind is being treated as an on/off button instead of a momentary switch. Video here. Note that I'm not holding the button down, just pressing it once. Notice that when I press the hotkey, the cockpit button is ever so slightly offset from the center position during the rotation. Pressing the cockpit button works fine, and it also stops the course line rotation. Track file attached. cw-ccw-issue.trk