Game and installer crashes when started RESOLVED

This is the event viewer log:
“Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60a521f7
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x3e14
Faulting application start time: 0x01d7524fe7c5a3bb
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 778caef1-cfce-4f41-a5d9-64c0963d3780
Faulting package full name: Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App”

I fully reinstalled my display drivers using DDU, I ran this sfc /scannow command and this DISM.exe /Online /Cleanup-image /Restorehealth command. I have reinstalled the game multiple times, every time the game starts it goes to a black screen then crashes.

This is an “Information” event in Event Viewer:

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

Problem signature:
P1: Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 0.0.0.0
P4: 60a521f7
P5: ucrtbase.dll
P6: 10.0.19041.789
P7: 2bd748bf
P8: 000000000007286e
P9: c0000409
P10: 0000000000000007

Attached files:

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER76BF.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER77D9.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER77EA.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER77EA.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER781A.tmp.txt

These files may be available here:

\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_ea4d47524037d37b7963d0f4ce718d984d5460_9a0a3099_cd1415ba-f2b3-4fb8-9eaf-ff1ef5f2b62d

Analysis symbol:
Rechecking for solution: 0
Report Id: 778caef1-cfce-4f41-a5d9-64c0963d3780
Report Status: 268435456
Hashed bucket: 6d05480e0af5cb828d3ed879a81b1af3
Cab Guid: 0”

I have seen one other person who has the same problem as I do, he has not found a solution either. I have contacted the support team but they have been slow in response and haven’t given me any real solutions yet.

I am also getting this issue and have also updated my graphics drivers to latest. Flight Sim has been installed and running fine for months. First time I’ve loaded it in a couple of weeks and I get the exact same issue as above.

You should submit a ticket to Asobo so they know about this.

I raised a support ticket and it was responded to pretty much immediately. Following the steps outlined I was able to identify the process that was running that was conflicting with Flight Simulator. In my case this was the SeaGate Toolkit application that is used to managed external USB hard drives. Stopping this application was all that was needed to get the game launching again.

If you have a similar issue go into Task Manager → Startup and disable all non-MS applications. Restart the computer and then launch Flight Simulator. If it loads correctly, exit the game and then start re-enabling the services in groups (I did two at a time) with a restart of the computer between each test. If it stops loading one of your recently enabled processes is the problem, if not enable more.

Eventually I was able to track down the single app causing the problem (you could have more than one) and also worked out that I didn’t need to stop it from running on startup and I could just stop the process before launching Flight Simulator.

Hopefully this helps others.

2 Likes

I am unable to test this right now, but I do use Toolkit to backup my computer. I will definitely try this.

1 Like

This fixed it, thank you so much.

Andy–you are a life-saver! I use ToolKit occasionally, and lo a behold, I decided to use it yesterday after the update.

I took ToolKit out of the startup menu, rebooted, and the sim came up fine!

I would have never thought about this as a conflict! Bravo! Thanks for sharing.

Topic moved into #bugs-and-issues:performance for installation problems.

Closed as issue resolved by OP.