Constant CTD, ucrtbase.dll, 0xc0000409

User Support Hub Crashes (CTDs)
1

I’m getting really tired and frustrated over constant CTD on almost every flight, sometimes early in the flight sometimes during or sometimes on descent, it seems random. This has only started recently but I keep getting the ucrtbase.dll error crash. I feel like I’ve read everything on the MSFS/Avsim/Reddit forums to try and resolve this error but so far, nothing has helped. Sort of at my wits end now.

I’ve removed all mods, reinstalled MSFS, reinstalled VC++, restored bios, tried two different sets of RAM sticks, installed the US language pack and set locale as US (even though I am in the UK), cleared caches, reinstalled drivers, uninstalled audio drivers, uninstalled afterburner, Riva, removed the exe.xml, changed power management settings in Device Manager etc. I just don’t know what else to do…I’m wondering if this even my issue at this point or an issue with MSFS itself…

I have 5800X3d, 4080, 32GB RAM.

Can I ask, regarding the language pack, does everyone else’s show as 0mb for the speech pack. I’ve spent about 2hours uninstalling and reinstalling stuff but still shows as 0mb, not sur if this is an issue or not

image
image494×286 5.37 KB

If anyone has any ideas, i’m really at a loss now. I’ve been trying to troubleshoot this all week and pretty fed up.

Faulting application name: FlightSimulator.exe, version: 1.35.21.0, time stamp: 0x00000000
Faulting module name: ucrtbase.dll, version: 10.0.22621.2506, time stamp: 0x097c794c
Exception code: 0xc0000409
Fault offset: 0x000000000007f61e
Faulting process id: 0x0x2688
Faulting application start time: 0x0x1DA4AC6232F425F
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 1cd58e6e-a9f6-4fec-a628-c37074b68a4c
Faulting package full name: Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App


Fault bucket 1830094896882087754, type 5
Event Name: MoBEX
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.35.21.0
P4: 00000000
P5: ucrtbase.dll
P6: 10.0.22621.2506
P7: 097c794c
P8: 000000000007f61e
P9: c0000409
P10: 0000000000000007

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.0626c086-eae3-4557-91c1-1de7d598cb5a.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.04325956-ee66-4d8a-98f3-bd8a0c0e0e0a.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.294f0c04-996e-4244-856b-07b4f7dea30c.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.cf8208b6-33f1-4527-8717-14321bfcc745.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e857d691-fcf9-4947-8786-7399f9718e74.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_cd19f181db6e3ff10638890021d313634ee385_698655e8_2f8e0a58-86f9-4267-86a9-3e0e597ee597

Analysis symbol: 
Rechecking for solution: 0
Report Id: 1cd58e6e-a9f6-4fec-a628-c37074b68a4c
Report Status: 268435456
Hashed bucket: 8295a08313195f69a965cd9cc9e9774a
2

There are numerous articles in here on this error code.
Here is a link to one:

3

A lot of that is from 2 years ago so might not be relevant now after updates, also seems that is more for users how can’t actually start the game. I can start the game now worries, most of these crashes occur mid flight

4

Same here, and I don’t have this issue:

image
image466×193 7.83 KB

5

Thank you, ok thats one thing I can rule out as an issue

1 Like
6

I have the same MSFS CTD here, same offset (x7F61E), same exception, same DLL, etc. I have been trying to solve it for months. It also can occur anywhere from minutes to hours into a flight, maybe even after being parked up at the end. I have tried many fixes, including the language pack, but I still have the issue.

Faulting application name: FlightSimulator.exe, version: 1.35.21.0, time stamp: 0x00000000
Faulting module name: ucrtbase.dll, version: 10.0.22621.2506, time stamp: 0x097c794c
Exception code: 0xc0000409
Fault offset: 0x000000000007f61e

7

My issue seemed to be related to using popout screens. I had two spare tablets that i set up using Spacedesk and moved the pop screens to those. After a week of exhaustive troubleshooting and testing, not using Spacedesk and pop out screens has seemingly fixed the issue. I’ve done four 2-3 hour flights with no crashes anymore.

It’s probably a very niche issue but just in case anyone else comes across this and is using pop out screens, this was seemingly my issue. I’m not sure if the issue lies with Sapcedesk or having 4 pop out windows however…either way the actual funcitonality was a novelty rather than essential and not worth the stress

8

So you just stopped using those programs, rather than finding a way to make it work with them?

If confirmed, that might be a useful one to be added to one of the troubleshooting pages on the Support site, either Basic or Advanced.

9

I spent a week trying to find a way to make it work but couldn’t find any workaround or fix that gave consistent stability…and believe me I tried pretty much everything I could find to try to prevent the crashes. So ultimately yeah, I stopped using Spacedesk and the two tablets and since then all has been solid, no more crashes.

What I don’t know is if it was Spacedesk, using 2 tables or having 4 pop out screens that MSFS didn’t agree with. Suppose I could test with just one screen but the last week was so tedious and I’m happy being able to fly again.

1 Like
10

This is interesting, because I’ve got the same CTD, same exception, same DLL, same offset, yet I don’t have Spacedesk. I too have made some progress in stability over the last few days, but in my case stopping use of Shift-Z-Stats (FlightSim.To) appears to be the turning point. Perhaps there is something fragile here in MSFS which can be provoked by a number of different applications. I am using a pop-out manager (https://flightsim.to/file/35759/msfs-pop-out-panel-manager) to bring 6 displays from a PMDG 737-800 onto secondary displays, but that seems to be rock solid.

11

Yeah i was using the pop out manager for my pop outs. Interesting that it works well for you. How are your displays connected your PC? Is it direct or are you using software to extend the screens?

12

Single PC setup, all displays directly connected, twin GPU (RTX4090 plus RTX3060). No extra software to extend the screens, just standard Windows 11 extended desktop.

13

Further testing here of the CTD FlightSimulator.exe in ucrtbase.dll, exception 0xc0000409, offset x7f61e:

Another product creating a screen overlay (other than Shift-Z-Stats), also appears able to provoke the same MSFS vulernability and CTD footprint. Here, AIDA64’s performance dashboard seems to do the same. Again, it can take many hours for it to occur, or it can in much shorter periods.

Additionally, I am seeing that after any of these particular MSFS CTDs at x7F61e, unless the PC is rebooted before restarting MSFS, the risk of a further CTD goes up. The frequency of CTD here increased after each individual CTD - until a reboot.