Crash Analysis Report — MSFS 2020 SU16 Beta (Version 1.39.8.0)

Sim Update 16 Beta | MSFS 2020 SU16 Beta Discussion
1

:brain: Crash Analysis Report — MSFS 2020 SU16 Beta (Version 1.39.8.0)

Summary

The crash was triggered by a BREAKPOINT exception (0x80000003) at offset 0x1e8e132 within FlightSimulator.exe. This corresponds to an INT 3 instruction (0xCC), typically used for debugging. Its presence in a public beta build suggests either residual debug code or a corrupted instruction stream.

Exception Details

  • Exception Code: 0x80000003 — Breakpoint
  • Instruction Pointer: FlightSimulator.exe+0x1e8e132
  • Instruction at crash: INT 3 (0xCC)
  • Stack Trace: Ends immediately after the breakpoint, indicating a direct and unrecoverable crash.
  • Failure Bucket ID: BREAKPOINT_80000003_FlightSimulator.exe!Unknown
  • Dump Hash: {70b50acb-28da-95f7-d832-2dfe8a04f184}

Symbol and Module Status

  • Symbols for FlightSimulator.exe: Not loaded — timestamp verification failed.
  • Unverified DLLs at crash time:
    • WwiseLibPCx64P.dll (audio middleware)
    • libcurl.dll (networking)
    • WTF.dll (UI logic)
    • CoherentUIGT.dll, CoherentUIGTDevelopment.DLL, CoherentGTCore.dll (UI rendering)
    • XPlatCppWindows.dll, Wizzard.dll, pixie.dll (internal logic/rendering)

These modules failed checksum validation, suggesting potential corruption, version mismatch, or unstable loading during runtime.

Runtime Context

  • Process Runtime: ~85 minutes (Timeline.Process.Start.DeltaSec = 5147)
  • Memory Peak: 634 MB committed
  • CLR Version: .NET 4.8.9310.0 — indicates presence of managed code components
  • OS Version: Windows 10.0.26100.1 (ge_release branch)

Observations

  • The crash occurred in the USA region (KBNA to KPHX), consistent with other reports of CTDs during scenery loading or UI rendering in that area.
  • The presence of INT 3 in a production build is abnormal and may indicate:
    • A failed cleanup of debug instructions in SU16
    • Corrupted memory decoding an invalid instruction
    • External interference from third-party DLLs or injected code
2 Likes