We’ve moved your topic into the Community Support category.
The Bug Reporting category is for posting suspected or confirmed bugs that other users are able to reproduce. Using the template is required in order to provide valuable information, feedback, and replication steps to our test team.
If you are not sure if your issue is a bug or need further input from the community, please use the Community Support category. If the community can replicate your issue, first search the Bug Reporting category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.
If you believe it is a new report, then create a new bug topic using the provided topic template.
All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.
A fix provided by Asobo would be nice … 4 CTD on the same day is a new sad record of MSFS … in my opionion moving to Community Support is totally wrong because it happens not due to something wrong with my driver settings etc… there is something wrong, a big bug, within msfs constantly crashing.
15.05.2023 07:54:02
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000025ca7b9
ID des fehlerhaften Prozesses: 0x0x4714
15.05.2023 08:56:52
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000025ca7b9
ID des fehlerhaften Prozesses: 0x0x4D28
15.05.2023 14:30:23
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000013262a3
ID des fehlerhaften Prozesses: 0x0x26F4
15.05.2023 17:10:08
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000025ca7b9
ID des fehlerhaften Prozesses: 0x0x30AC
As a test, have you tried flying for a bit without any addons in your Community folder.
You appear to be getting regular crashes, would you say flying for 2-3 days without any Community addons would be enough time to see if has made a difference?
If that doesn’t work we can move on to other things, such as possible overclocks of the GPU etc.
Could you perhaps post a full breakdown of your computers hardware i.e. CPU, GPU (including make/model), memory (and any XMP profiles you might be using)?
I have been getting regular CTDs over the past three days, as well… and I have never had them before in almost a year of using MSFS. The only thing that changed was a Windows update that I took a few days ago that seems to coincide with the CTDs. They seem to happen almost randomly - I had one that CTD’ed about an hour in to a flight, then yesterday I had one as I was setting up a flight from cold and dark. Different aircraft - one was the PMDG 739 and the other was in the default Citation. Wonder if the windows update was causing this? My fault code is a bit different than yours, though. From the windows event log. I see the same error every time I CTD.
The “0xc0000005” is a particularly horrible one. It’s an access violation error.
Essentially “FlightSimulator.exe” has accessed something that it shouldn’t, and crashed.
The only advice I could give is strip away anything that didn’t come with the sim, no community addons at all, and fly default aircraft. When you have established a base line of stability, and one flight without a crash doesn’t count here. You might need to fly for several days with the sim trimmed back like that.
Only then start to add addons back one at a time. Also, whichever addons you are using, make sure they are the latest version available. Don’t use an addon written for sim as it was a year ago, for example.
Thanks, but since MSFS im an expert in the 0xc0000005 … i read each google result…below the line: All but nothing…
If there would a way to get to know which file was the file with this access violation
Most times it happens when i look around, zoom in or out … today i try to look around less i can and didnt help at all with 4 ctd… it takes so much energy with this phantom error which can occur at any time anywhere
I can’t tell with yours as you never posted an entire log entry, but the one above posted by @Deelee6800 it is clear:
The reason however is much trickier. What I can say is about a year to two years ago I got these a lot, and now I never see them. I changed the things I had loaded alongside the sim, in the form of addons, and what connects to the sim, and they went away.
Another important line is the faulting module, that could be useful to see. Below is a crash from my work machine:
if there would be one …
15.05.2023 07:54:02
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.33.3.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.33.3.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000025ca7b9
ID des fehlerhaften Prozesses: 0x0x4714
Startzeit der fehlerhaften Anwendung: 0x0x1D986E80D2A99B6
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: dcd94fa7-64b8-472d-a511-0911304e019c
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.33.3.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
15.05.2023 08:56:52
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.33.3.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.33.3.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000025ca7b9
ID des fehlerhaften Prozesses: 0x0x4D28
Startzeit der fehlerhaften Anwendung: 0x0x1D986F70142432F
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: bc573c3b-22c8-4b62-8285-7f0e1967c552
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.33.3.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
15.05.2023 14:30:23
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.33.3.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.33.3.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000013262a3
ID des fehlerhaften Prozesses: 0x0x26F4
Startzeit der fehlerhaften Anwendung: 0x0x1D986FAE20AFD26
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: 40321c14-08f7-45c9-87d3-198813215821
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.33.3.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
15.05.2023 17:10:08
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.33.3.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.33.3.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000025ca7b9
ID des fehlerhaften Prozesses: 0x0x30AC
Startzeit der fehlerhaften Anwendung: 0x0x1D98729FBB53A42
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: 62b4ea2d-438e-415e-9962-e6216e2ad560
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.33.3.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
The 4090 base clock is 2235MHz. That card can boost to 2580MHz.
You may have some software installed may allow you to disable that boost temporarily. I’m not sure how that boost works though. Whether it dynamic as is needed, or is set to a boost level.
Want to discuss a theory about this “accessing error” … is there any connection to “page faults” of the virutal memory … could this raise 0xc0000005 exception ?
man, i cant use the sim anymore, only get frustrating with the ctd, any one else? any solution? could be the hardware or is the MSFS? i get Exception code: 0xc0000005 CTD almost any flights on any step…
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
