Same for me, when the game was released it was an alpha full of bugs … but no CTDs which was a better situation than we have now.
Btw … debugging the game with WinDbg is real fun 
it’s not like I am not trying really hard to find the root cause of the CTDs.
(1a44.43f8): Illegal instruction - code c000001d (first chance)
*** A stack buffer overrun occurred in D:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe -FastLaunch:
This is usually the result of a memory copy to a local buffer or structure where the size is not properly calculated/checked.
If this bug ends up in the shipping product, it could be a severe security hole.
The stack trace should show the guilty function (the function directly above __report_gsfailure).
*** enter .exr 00007FFCA1876EE0 for the exception record
*** then kb to get the faulting stack
(1a44.43f8): Break instruction exception - code 80000003 (first chance)
ntdll!RtlUnhandledExceptionFilter2+0x364:
00007ffc`a180d5d4 cc int 3
0:000> g
(1a44.43f8): Security check failure or stack buffer overrun - code c0000409 (!!! second chance !!!)
Subcode: 0x2 FAST_FAIL_STACK_COOKIE_CHECK_FAILURE
ntdll!_GSHandlerCheck+0x13:
00007ffc`a1799413 b801000000 mov eax,1
0:000> g
WARNING: Continuing a non-continuable exception
(1a44.43f8): Illegal instruction - code c000001d (!!! second chance !!!)
KittyHawkx64_Steam_PCSUB!FlightSimGetProcessId+0x88654b:
00007ff6`9180a28b 07 ???
0:000> g
(1a44.43f8): Illegal instruction - code c000001d (first chance)
*** A stack buffer overrun occurred in D:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe -FastLaunch:
This is usually the result of a memory copy to a local buffer or structure where the size is not properly calculated/checked.
If this bug ends up in the shipping product, it could be a severe security hole.
The stack trace should show the guilty function (the function directly above __report_gsfailure).
*** enter .exr 00007FFCA1876EE0 for the exception record
*** then kb to get the faulting stack
(1a44.43f8): Break instruction exception - code 80000003 (first chance)
ntdll!RtlUnhandledExceptionFilter2+0x364:
00007ffc`a180d5d4 cc int 3
Pretty funny is this statement from the debugger:
This is usually the result of a memory copy to a local buffer or structure where the size is not properly calculated/checked.
If this bug ends up in the shipping product, it could be a severe security hole.
So yeah, we are obviously back to testing an alpha 
not even malware meant to overflow buffers causes as many buffer overflows as you see when starting FS