This is the exact same fault offset I’m getting too:
I suggest enabling a full memory dump and sharing it, with this file, the MS/Asobo devs can see exactly where the program crashed, so it’s way more useful than the event report.
Open registry (Start > Windows Administrative Tools > Registry Editor Or Start > Run > regedit)
-
Navigate to - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps (If LocalDumps is not present, right-click on Windows Error Reporting > New > Key and name that as LocalDumps)
-
Right-click on the LocalDumps key and create new Key with name as “Flightsimulator2024.exe”
-
Under the new key Flightsimulator2024.exe, create a new “Expandable String Value” with name as “DumpFolder” and set the value to any folder where you want the dump file to be generated (on crash)
-
Under the new key Flightsimulator2024.exe create a new “DWORD (32-bit) Value” with name as “DumpType” and set the value to 2 (decimal) to it
-
Under the new key Flightsimulator2024.exe create a new “DWORD (32-bit) Value” with name as “DumpCount” and set the value to 10 (decimal) to it