App could not start, Exception code: 0x80000003

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, both new installed windows and FlightSimulator

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.

Fresh new system and FlightSimulator.

Brief description of the issue:

After the last FlightSimulator upgrade, my app could never run as the video link below.
The FlightSimulator was working perfectly on my PC but not now. Even I do fresh install the windows serval times.

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

https://youtu.be/Te2prKqDWjk

Detailed steps to reproduce the issue encountered:

Just on a new Windows 11 system and new install FlightSimulator.

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):

Asus Strix LC RTX4090 OC 24G. Nvidia Game Ready Driver version 551.86 and other versions tested the same.

Tried newly installed Windows 10 and a fresh new flight simulator, all works fine. This issue for me happened on Windows 11 ONLY.

PC specs and peripheral set up:

CPU: tried both i9-14900k and i5-14600k
Motherboard: Asus Strix Z790-A D (Bios v 2002 and v 2102 are tested)
Ram: 64G (32Gx2)
GPU: Nvidia 4090 24G

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

Fault bucket 2249776710998971622, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.FlightSimulator_1.36.2.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.36.2.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.36.2.0
P7: 00000000
P8: 80000003
P9: 0000000001de1610
P10: strong text

Build Version # when you first started experiencing this issue:

: Microsoft.FlightSimulator_1.36.2.0_x64

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

2

Hi @XiaoHuX2610 ,

Weā€™ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup 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 User Support Hub category. If the community can replicate your issue, first search the Bug 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 and no duplicate exists, 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.

3

Check out that topic:

Also those existing ones in User Support Hub Crashes (CTDs) :
https://forums.flightsimulator.com/search?q=0x80000003%20%23user-support-hub%20in%3Atitle

4

Thanks [DementedCorn327]
Tried the setting manage virtual memory to ā€˜Automatic manage paging file sizeā€™ and ā€˜Custom sizeā€™ and ā€˜System managed sizeā€™. as the topic described. None of these methods work.

Tried to ā€˜uninstall update kb5033375ā€™ I do not have this update in my WIn11 system (23H2 22631.3296)

Also Tried to swap RAM and do swap CPU, didnā€™t fix.

Tried to swap another 4090 VGA card, all the same.

Tried to use the CPUā€™s VGA port (Intel ARC) nothing changed.

Meantime, I ran Shadow of the Tomb Raider and Rise of the Tomb Raider for a few hours as a comparison, and they all worked perfectly.

5

How far along in the start process does the sim get?

6

As video link above. In most cases it goes to just before Home Pageļ¼ˆtile menuļ¼‰ shows or in some cases just show Home Page few seconds then crash.

1 Like
7

Good news, I found the solution.

Install .NET Framework 3.5
Then it must be upgraded to Windows 11(X64), version 23H2 (KB5034467), this is the KEY.

February 13, 2024-KB5034467 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 and Windows 11, version 23H2

After the patch is done, power cycle the PC.
Enjoy.

Thanks to my friends, I couldnā€™t have discovered this method without your help.

1 Like
8

Great to hear, I have marked your last post as the solution.
Happy flights !

9

Iā€™m having the same error message:

Faulting application name: FlightSimulator.exe, version: 1.36.2.0, time stamp: 0x65a6e79d
Faulting module name: FlightSimulator.exe, version: 1.36.2.0, time stamp: 0x65a6e79d
Exception code: 0x80000003
Fault offset: 0x0000000001f42032
Faulting process id: 0x0x7D30
Faulting application start time: 0x0x1DA9279ECF092F2
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: 52357222-fc74-48ba-922c-2fd9d3294bbc
Faulting package full name:
Faulting package-relative application ID:

Iā€™ve tried everything i can find online. Iā€™ve check that I have .Net up to date and latest Windows 11.

Still, my game crashes while checking for update.

11

I am not sure we have the same problem.
If your Windows 11 is newly installed you may try:

  1. Update this Windows 11 (Win ā†’ Settings ā†’ Windows Update ā†’ Check Updates)
  2. Install ā€œ.NET Framework 3.5ā€ MANUALLY, this will NOT be installed by Windows default by Windows update or by installing the Flight Simulator App. (Win ā†’ Settings ā†’ System ā†’ Optional features ā†’ More Windows features ā†’ tick ā€œ.NET Framework 3.5 (includes .NET 2.0 and 3.0)ā€ ā†’ ā€œOKā€)
  3. Update .NET Framework 3.5 to ( 2024-KB5034467 or higher ) as item 1 described.
  4. Reboot Windows
12

Update infoļ¼š
There is a possibility that Intel causes the 0x80000003 error code
If you are using an Intel 14xxx serials (14th) CPU and find symptoms like the following (any one):

  1. The login time is much longer than normal (for me the normal is 2~5 minutes), but after the CPU got a problem, the log-in time is 20+ minutes.

  2. The start time from the Home Page to go to the actual flying page is longer than normal (for me the normal is around 1 minute), but after the CPU got a problem, this time would be 10+ minutes.

  3. There is a chance to start the game but after you close the game you may need to reboot the computer then you can start the game again otherwise the game will be CTD.

  4. You can play the game properly but after you re-install a new Windows system, the game cannot start again or start randomly.

  5. You can not play the game but you can find there are .NET Framework insufficient permissions warring before [0x80000003] occurs.

  6. You can play the game but the in-game market is always on Gray, and can not purchase any items.

  7. Using the Intel CPU check tools and shows nothing wrong.

  8. For other applications (not MSFS) and other 3D games, you may find it all works or just CTD rarely.

You may have the same problem as me.
I have 14900k, 14700k, and 14600k and bought two sets of PCs, with ASUS-4090 video card and with all symptoms as item 1~8 show. It took me 3 weeks to find this hardware-related problem and install a clean Windows 11/10 system more than 60 times, replaced all hardware with a new one, even a power supply.
Finally, I bought a new 14700k, all the problems are goneā€¦ if I put the old 14900k, 14700k, and 14600k back and the symptoms are back. Old CPUs are bought in Apr and May 2024. The new CPU has been on board for about 10 days and works all good (Hope this one can work for the next few years).

I donā€™t know if there are similar problems with 13th Intel CPUs, but Intel did say their 13th and 14th CPUs may have a big problem. I am unlucky on the 14th CPU. Waiting for Intelā€™s next announcement.

I updated all hardware firmware to the latest version and tried even older versions with new and old microcode. Tried Windows 10 and 11 with or without updates. Tried motherboard BIOS settings with and without intelā€™s limited performance settings.

1 Like
13

Thank you very much for sharing the solution!

Could you provide the batch numbers of the faulty CPUs?
This will help us in diagnosing our own CPUs.

Please describe your issue with CPUs and its solution in the topic on Reddit and the Intel forum, links below.

Reddit - Intel Core 13th/14th Gen desktop processors Stability issue

Intel - July 2024 Update on Instability Reports on Intel Core 13th and 14th Gen Desktop Processors

Intel - Clarification Update on Intel Core 13th/14th Gen Desktop Processor Support Process

Your insights will help the community!

Also reach out to Intel Customer Support.

15

Sorry for the long delay, I just got the replacement CPU from Intel today.
The batch numbers for my faulty CPUs

  1. i9 14900k
    X334P425
  2. i7 14700k
    X352M221
  3. i5 14600k
    X334P563
2 Likes
16

Thank you very much for providing the batch numbers for the CPUs.
Intel offered me a new CPU or a refund. I chose refund and I am currently waiting for the refund for the i9 13900K - X246G324

17

Intel are currently facing the possibility of a Class Action for the 13/14th gen. CPU problems.

The issue is that so much power is being supplied to the silicon To MaKE tHeM FaStRer!11!!111 that it is literally destroying the processors.

Once the damage has begun, it can not be stopped.

The only solution is to avoid any 13/14th gen Intel CPU (they are all bad, as it is a design problem).

18

Nope.
The issue youā€™re describing actually stems from manufacturing errors, particularly related to oxidation and microcode bugs. These problems caused 13 and 14-gen processors to report higher vcore voltage requirements, not wattage, as a result of these faults. So, the problem isnā€™t about the processors drawing excessive power to increase performance but rather incorrect voltage demands due to microcode issues.

Intel 13 and 14-gen CPU sends a signal to the motherboard indicating how much vcore it needs at any given moment. Therefore, if there is an issue with the microcode CPU may request higher voltage.
This issue was supposed to be fixed with the new microcode 0x129 along with BIOS updates.
Intel decided not to fix this through a Windows update as they had done in the past.

Nope.
The production issues related to the via Oxidation manufacturing issue affected some early Intel 13-gen processors not the 14th generation.
Itā€™s not true that all 13 and 14-gen CPUs are bad.

1 Like