Exception code 0xc0000005 ruins EVERY FLIGHT (vanilla or with addons)

User Support Hub Crashes (CTDs)
,
1

:wave: 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.

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

Yes and it didn’t help

Brief description of the issue:

I get CTD’s 80 to 10Nm from any destination, IFR flights

Provide Screenshot(s)/video(s) of the issue encountered:

No

Detailed steps to reproduce the issue encountered:

EDDB-LOWW in the Fenix A320 or PMDG 737s, same thing over and over

Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version (Learn how to find your current graphics card driver version):

I tried the current Nvidia driver and rolled back one version. No difference.

PC specs and peripheral set up:

9700K watercooled, 3090ti watercooled, 64GB RAM, 1000W PSU, all SSDs, good airflow and temps

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

Fehlerbucket 1691296138668117975, Typ 4

Build Version # when you first started experiencing this issue:

Current version, no beta

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

MSFSReport.txt (19.3 KB)

Hello you beautiful people,
I am in dire need of help. I can’t enjoy MSFS right now AT ALL.
1-2 hour flights, same thing over and over and over again. CTD mid-flight or JUST
infront of any airport. Even seconds after landing.

I limited my CPU to 95%
cleared nvidia cache
MSFS rolling cache is off
I did an SFC scan
XMP is where the maximum of my CPU, so 2666
Believe me I did ALL steps recommended by Zendesk for CTD trouble shooting.

I get the same errors. PLEASE help me, I love you.

Windows Event Viewer:
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.33.8.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.19041.3155, Zeitstempel: 0x5212ece5
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000a22c7
ID des fehlerhaften Prozesses: 0x5900
Startzeit der fehlerhaften Anwendung: 0x01d9c45def1661be
Pfad der fehlerhaften Anwendung: F:\SSD2 GAMES STEAM\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: 7820b19a-7742-4ea8-9c82-9e728e7eef27
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Fehlerbucket 1691296138668117975, Typ 4
Ereignisname: APPCRASH
Antwort: Nicht verfĂĽgbar
CAB-Datei-ID: 0

Problemsignatur:
P1: FlightSimulator.exe
P2: 1.33.8.0
P3: 00000000
P4: ntdll.dll
P5: 10.0.19041.3155
P6: 5212ece5
P7: c0000005
P8: 00000000000a22c7
P9:
P10:

2

Hello mate
I will try to help you.
But I’m going to need some screenshots to really understand what’s going on.
Go to your task manager and click on performance and processes and send a screenshot.
Also in graphics simulator settings and send screenshots of all your settings.

3

Attach dxdiag report.

Open and run DxDiag.exe - Microsoft Support

4

This means that your RAM is unstable. In many situations it’s not possible to achieve the advertised XMP frequencies with 64 GB.
Try to test your RAM with https://www.ocbase.com/ - Most probably you will see that the CTDs are not caused by MSFS. If that’s the case, you have to turn down the memory frequency to a more conservative XMP profile or scale down to 32 GB (2 DIMM).

1 Like
5

Thanks so much you guys…

As I continue testing, this is the same with SAFE MODE. Asobo A320 from EGLL to EDDK.
Crash right before landing…

My Traffic is always off and my XMP is set down to the maximum, supported by my 9700K,
so 2666. I can try turning XMP off all together, although I don’t see much sense in having
too much ram???

I always get those 2 exceptioncodes, the one from the title and this:
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.33.8.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: dxgi.dll, Version: 10.0.19041.2311, Zeitstempel: 0xe3f3eb09
Ausnahmecode: 0xc0000409
Fehleroffset: 0x0000000000026eeb
ID des fehlerhaften Prozesses: 0x5548
Startzeit der fehlerhaften Anwendung: 0x01d9c462cd999f69
Pfad der fehlerhaften Anwendung: F:\SSD2 GAMES STEAM\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\dxgi.dll
Berichtskennung: e8c729b6-39dc-470e-9dec-dcc2fbd6f4ce
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Fehlerbucket 1349183608437968628, Typ 5
Ereignisname: BEX64
Antwort: Nicht verfĂĽgbar
CAB-Datei-ID: 0

Problemsignatur:
P1: FlightSimulator.exe
P2: 1.33.8.0
P3: 00000000
P4: dxgi.dll
P5: 10.0.19041.2311
P6: e3f3eb09
P7: 0000000000026eeb
P8: c0000409
P9: 0000000000000002
P10:

DxDiag.txt (112.0 KB)

1b464f0b-ef8c-48f0-896b-81c6009b96a5
1b464f0b-ef8c-48f0-896b-81c6009b96a51249Ă—1116 127 KB

FlightSimulator 2023-08-01 13-31-55-337
FlightSimulator 2023-08-01 13-31-55-3371920Ă—1080 143 KB

FlightSimulator 2023-08-01 13-31-50-128
FlightSimulator 2023-08-01 13-31-50-1281920Ă—1080 148 KB

FlightSimulator 2023-08-01 13-31-40-648
FlightSimulator 2023-08-01 13-31-40-6481920Ă—1080 156 KB

6

ok ok thanks so you can see your CPU is working a lot. we are going to try to take work do you have traffic on…? aircraft, boats, cars and fauna I have all that at zero (I don’t need it to enjoy a good flight) I only have 10% airport staff I also see that you have V-Sync activated. how big is your monitor…? if it is 60hz I recommend that you set the frame rate limit to 50% then I have the glass cockpit refresh on low. I also see that it has many processes. I recommend that you look at this tool and go to the tweks section in my desktop case and run tweaks once all that is done, restart the PC. I also always recommend that you delete the content of SceneryIndex and FlightSimulator before starting the simulator, I put the path of said folders.
C:\Users\YourUser\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes

C:\Users\YourUser\AppData\Local\FlightSimulator
(Don’t worry, they will create themselves when you start the simulator)

Link Tool

PowerShell como administrador y pegar
You will see the command in the video description

7

I have a 9700k and it clocks up to 4.6ghz when using MSFS at default bios settings, yours seems to not be speeding up when needed and causing a substantial amount of use on all the cores, something seems off to me. Also 2666 ram speed is also the normal rated speed without xmp, so not sure what’s going on with that either.

Best thing is to reset bios to default values, make sure your bios is fully updated and you have the right chipset drivers installed and try again, firstly with a purely vanilla sim. Then report back.

1 Like
8

The RAM speed was the issue. I had 2 problematic scenarios and routes,
Fenix A320 from EGLL to EDDK (payware airport)
PMDG 737 from EDDB to LOWW (payware airport)

I did push XMP off and before that I set the DRAM speed down to 2100, this is what it also shows in my task manager for RAM speeds. So far I could complete BOTH of those scenarios without CTDs and thats thanks to the recommendation to slow down my RAM.

I will continue testing, so far everything is up and running strong. I could even run SkyDolly, Bandicam and MSI Afterburner while doing those scenarios no problem.

If you guys have any other advices, feel free to futher analize the issue. I will treasure this thread near
and dear to my heart because I spent a lot of time in testing. THANK ALL OF YOU.

3 Likes
9

Outdated BIOS.
Your BIOS dated 2019-02-22 v 1.50 (7B51v15)
Latest BIOS 2022-10-23 v 1E (7B51v1E) - so download latest BIOS and flash the BIOS

msi.com/Motherboard/MPG-Z390-GAMING-PLUS/support

Also update GPU drivers.

10

Forgive my ignorance.
Where do I see my version in the BIOS…?
It’s an Aorus Z-390 Ultra.
Thank you

11

Go to BIOS setting > System tab

  • BIOS version
1 Like
12

I have ordered a USB stick to be able to update my bios.
Although I can’t imagine an old bios being the cause of this… My PC literally never crashes
in any other applications. Never…

I still get the CTD’s after further testing, but now ntdll.dll is at fault.
Does that tell a different story, other than the RAM instability?

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.33.8.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.19041.3155, Zeitstempel: 0x5212ece5
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000a22c7
ID des fehlerhaften Prozesses: 0x4f08
Startzeit der fehlerhaften Anwendung: 0x01d9c49055a81c0c
Pfad der fehlerhaften Anwendung: F:\SSD2 GAMES STEAM\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: 75a6d443-7b6c-4312-ab32-28d5a2b32e14
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

13

You can update via MSI Center or MSI Dragon Center.
msi.com/Motherboard/MPG-Z390-GAMING-PLUS/support#utility

14

Moved to Tech Talk which is more appropriate whilst other users help you troubleshoot :+1:

2 Likes
15

I am getting the same type of crashes. I have tried to downclock my ram even lower than default and still getting the crash… I am on 64Gb also.

Description
Faulting Application Path: G:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: FlightSimulator.exe
Application Version: 1.33.8.0
Application Timestamp: 00000000
Fault Module Name: FlightSimulator.exe
Fault Module Version: 1.33.8.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 00000000007a0459
OS Version: 10.0.19045.2.0.0.256.48
Locale ID: 1033
Additional Information 1: a37e
Additional Information 2: a37e1b6b1a6a73112f9ddc5f223b3507
Additional Information 3: 9976
Additional Information 4: 997665caa40e5c88f2f70553c1344fda

Extra information about the problem
Bucket ID: 41d51948f1e11861e99306641c84396b (1842823699569588587)

16

I don’t think it’s only unstable ram that gives this error. It’s when the software can’t allocate or recall the ram or disk storage (reading) it needed. It’s an MSFS issue not hardware IMO.

I get this error sometimes but I’ve done multiple hour long stress tests on my hardware and it’s fine.

It’s the game or the way an external app that talks with the game engine is working and tripping over I think.

1 Like
17

Have you tried OCCT? https://www.ocbase.com/

18

Strange thing about it is it crashes always in about an hour or two like a memory leak of some sort.

19

Yes, I did stress-test my whole system with AIDA64 and I found nothing but great temps and
no hick-ups… Still getting the message.

20

Updated my BIOS, and made sure I actually increased my pagefile size from 16gb to 61gb
Not sure what that did but lots of research did advise to do that. So far I’m on my 3rd successful flight with heavy addon usage, I’m now even testing the salty simulations 747 which I usually would never bother to download.

For people increasing the pagefile size, make sure you restart the PC and check the size, you gotta click the correct button to save your changes. I put my CPU back up to 100% and so far everything is going good… I’ve been testing all day.

Important is that I also updated SkyDolly, the replay tool. I was on V12 but its now on V16 or something. That certainly helped too.

For everybody else with the issue, let me know if I can be of help too.

So far it works again. Finally, after DAYS of hustling and testing.

2 Likes