My sim, which ran fine from when I purchsed in December 2020 to about May this year, now constantly crashes to desktop, often immediately when I use the map screen, or sometimes during a flight.
I have tried everything I can think off, including a complete reformat of Windows, update mobo bios and GPU drivers, removing community folder, unplugging peripherals and VR.
I just cannot fix it
Iâm all out of ideas so wondering if anybody knows what the following error messages mean?
I have posted reports a few times in the tech help / bug section over the past months but never had any reponses hence me posting in this forum.
I just want to know I interpret the error messages to get an idea what is causing the issue? One potential glimmer of hope is that the error code and fault bucket seem to always be the same, maybe pointing to a single, specific problem?
Fault bucket 1236062886058525194, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Quick update, I wondered what would happen if I asked ChatGPT, and he/it was surprisingly helpful. Itâs given me a bit of an idea at least where to start lookingâŠ
The provided event log represents a Windows Error Reporting event related to a crash of the application âFlightSimulator.exe,â which appears to be Microsoft Flight Simulator. Hereâs an interpretation of the relevant information in the event:
Provider Name: âWindows Error Reportingâ - This is the component responsible for managing error reports in Windows.
EventID: 1001 - This is the specific event ID for an application crash report.
TimeCreated: This indicates when the crash occurred.
EventData: This section contains various data related to the crash:
Bucket: A unique identifier for the crash report.
BucketType: 4 - This suggests that itâs a crash bucket report.
EventName: âAPPCRASHâ - The type of event, indicating an application crash.
P1: âFlightSimulator.exeâ - The name of the executable that crashed.
P2: â1.33.8.0â - The version of the application.
P3: â00000000â - Additional information related to the crash (possibly an error code or flags).
P4: âFlightSimulator.exeâ - Same as P1, indicating the executable that crashed.
P5: â1.33.8.0â - Same as P2, indicating the version.
P6: â00000000â - Additional information related to the crash.
P7: âc0000005â - This is an exception code (0xC0000005) which typically represents an access violation.
P8: â00000000025c4dc9â - A memory address associated with the crash.
AttachedFiles: Paths to various files related to the crash (crash report, dump files, metadata, etc.).
StorePath: Path to where the crash report is stored in the Windows Error Reporting system.
ReportId: A unique identifier for this specific crash report.
ReportStatus: 268435456 - Status code related to the report.
HashedBucket: A hashed value of the bucket identifier.
CabGuid: 0 - A unique identifier associated with the crash report.
From this information, it seems that FlightSimulator.exe crashed with an access violation exception (c0000005) at a specific memory address (00000000025c4dc9). This kind of crash could be due to a variety of reasons, such as memory corruption, driver issues, or software bugs.
To troubleshoot and resolve this issue, you might consider the following steps:
Check for Updates: Ensure that you are using the latest version of Microsoft Flight Simulator.
Update Graphics Drivers: Update your graphics card drivers to the latest version.
Check System Requirements: Ensure that your system meets the minimum and recommended requirements for the game.
Disable Overclocking: If youâre overclocking your system, try running at default clock speeds.
Verify Game Files: If the game has an option to verify or repair game files, use it to ensure all game files are intact.
Check for Windows Updates: Make sure your Windows operating system is up to date.
Contact Support: If the issue persists, consider contacting Microsoft Flight Simulator support for further assistance.
Keep in mind that crashes can be caused by a wide range of factors, so the above steps are just general suggestions. If the problem persists, you might need to provide more detailed information to the gameâs support team or forums for more specific guidance.
