1.37.19 Crashes Every Single Time - Ryzen + Radeon

User Support Hub Crashes (CTDs)
, ,
1

Totally clean MSFS 2020 without any add-ons.

Has been working flawlessly for years. Now, version 1.37.19 crashes (CTD) within few seconds after reaching the main screen (where you chose what you want to do).

Crash dump indicates the following:
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff73d02c840 (FlightSimulator+0x0000000001dfc840)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 1
Parameter[0]: 0000000000000000

PROCESS_NAME: FlightSimulator.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.

EXCEPTION_CODE_STR: 80000003

EXCEPTION_PARAMETER1: 0000000000000000

Is there a DebugBreak or a check somewhere in the release version?

1 Like
2

Hi @StopHalfling310 ,

Thank you for this report. 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

There are some topics on this error:

https://forums.flightsimulator.com/t/app-could-not-start-exception-code-0x80000003/635490

https://forums.flightsimulator.com/t/flightsimulator-exe-application-error-0x80000003-a-breakpoint-has-been-reached/334962

Or a search on ā€œ80000003ā€:
Search results for ā€˜80000003ā€™ - Microsoft Flight Simulator Forums

5

Seconded this error, although it CTDs for me after checking for updates but before the main menu. Loading bar is at approx 75%.

  • Nvidia Driver updated to latest version
  • Windows 11 23H2 22631.3737 fully up to date
  • MSFS fully up to date
  • Community folder and extra addons cleared out
  • Normal mode and safe mode have same CTD
  • Rebooted
  • Double checked .NET framework 3.5 is installed and up to date
  • Paging file set to automatic
  • Plenty of extra SSD space avaliable for the paging file to grow
  • Rebooted again

PC Specs

Processor 13th Gen Intel(R) Coreā„¢ i5-13600K 3.50 GHz
Installed RAM 32.0 GB (31.7 GB usable)
Motherboard ROG STRIX B760-A GAMING WIFI D4
GPU RTX 4070 Ti
GPU Driver ver 32.0.15.5599

Peripherials

KB Keychron K5
Mouse G502 Hero
HOTAS Saitek X52 Pro
VR Quest 3

Event viewer logs

Event ID 1000

Faulting application name: FlightSimulator.exe, version: 1.37.19.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.37.19.0, time stamp: 0x00000000
Exception code: 0x80000003
Fault offset: 0x0000000001dfc840
Faulting process id: 0x0x55A0
Faulting application start time: 0x0x1DAC129E204613E
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 2c602cf3-125f-42bd-bedb-bc78f70ce783
Faulting package full name: Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Event ID 1001

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

Problem signature:
P1: Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.37.19.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.37.19.0
P7: 00000000
P8: 80000003
P9: 0000000001dfc840
P10:

I also have MSFSReport-Crash.txt available but cannot upload due to being a new user.

6

Stumbled here because I was having CTDs on loading and wondering if anyone else had this issue. I think you and I might have the same issue. I loaded up fine the first launch, installed the small update, restarted the sim and now I get a CTD at about 75% before even reaching the main menu. Three tries now, twice after clearing SceneryIndexes, DCE, and cache folders, and CTD every time at the exact same spot before reaching the main menu.

Nothing has changed except the prompted update.

Faulting application name: FlightSimulator.exe, version: 1.37.19.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.37.19.0, time stamp: 0x00000000
Exception code: 0x80000003
Fault offset: 0x0000000001dfc840
Faulting process id: 0x0x3F38
Faulting application start time: 0x0x1DAC12FC1485B83
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 6a8330a9-dcfd-4247-abd0-22f7469761b4
Faulting package full name: Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

7

Thinking this might be an issue with todayā€™s patch because I am seeing a whole lot of activity on this error today including some much older threads getting necrod.

8

Empty add on folder.

I got the update this evening. Now the game is completely unplayable.

The title loads - the progress bar goes halfway, then CTD. No main menu.

Alienware m15 R4
|ā€”|ā€”|
|Processor|Intel(R) Coreā„¢ i7-10870H CPU @ 2.20GHz 2.21 GHz|
|Installed RAM|32.0 GB (31.8 GB usable)|
|Device ID|
|Product ID|00326-10000-00000-AA236|
|System type|64-bit operating system, x64-based processor|
|Pen and touch|No pen or touch input is available for this display|

Edition Windows 11 Home
Version 23H2
Installed on ā€Ž2/ā€Ž14/ā€Ž2023
OS build 22631.3593
Experience Windows Feature Experience Pack 1000.22700.1003.0

NVIDIA(R) GeForce RTXā„¢ 3080 8GB GDDR6
2TB (2x 1TB PCIe M.2 SSD) RAID 0 [Boot] + 512GB PCIe M.2 SSD [Storage]
32GB DDR4 2933MHz
10th Generation Intel(R) Core( TM) i7-10870H (8-Core, 16MB Cache, up to 5.0GHz Max Turbo Frequency)
Killerā„¢ Ethernet E3100X 10/ 100/1000Mbps/2.5Gbps NIC
Killerā„¢ Wi-Fi 6 AX1650 802. 11ax 2x2 Wireless LAN and Blue tooth 5.1

image

9

Same here. Uninstalled game, reinstalled. Same result CTD when loading bar is approx. 75%

10

Iā€™m running into the same symptoms following this recent update. Seems to happen sometime around the 75% loading point or at the menu. Once I managed to get to the menu and select airports from the World Map but it crashed on loading in. Most of the CTDs have been at the 75% mark though. These are consistent in the following situations:

  • ā€œNormalā€ start up.
  • ā€œSafe Modeā€ start up.
  • Cleared out community folder.
  • Also tried removing fs-base, fs-base-genericairports, and fs-base-ai-traffic folders based on another support article. The sim redoanloaded them and promptly had the same problem.

The Event Viewer points to a crash log which indicates a ā€œFiberErrorā€.

11

Same as others have posted above. Installed latest updates, restarted computer, loaded up FSX and about 75% loading it crashes.

Thought ok Iā€™ll try FSX safe mode then, 75% and boom crash to desktop.

12

Hi Guys

Mine is not working either, this afternoon I was Flying and MSFS just closed with no alerts or errors, yesterday was running smoothly but today I tried at to different times and with different flights but at the end just got CTD I updated today to Version 1.37.19

13

This is clearly an issue affecting multiple people after installing the latest update today (17JUN24). Iā€™m also seeing people complain of constant CTDs during loading on other forums over the past few hours. Oddly enough, no complaints when the patch was initially released.

It would be nice to get this issue escalated to Asobo so theyā€™re aware, as Iā€™m sure thereā€™s going to many complaints tomorrow if this issue persists.

2 Likes
14

i been having this issue too i even did a clean install and sometimes i hit 75% and crashes other time i reach the menu and then it crashes

15

I have the same issues here. Menu shows up for 2 seconds and then CTD. But before that I was able to start MSFS a few times, but some of the purchased marketplace aircraft and some of the premium content didnā€™t show up, although the content manager showed them as installedā€¦ Weirdā€¦

1 Like
16

The crash dump analysis indicates that the problem is related to a breakpoint exception in the FlightSimulator.exe program. Below is the relevant information:

  1. Exception Address:
  • ExceptionAddress: 00007ff73d02c840 (FlightSimulator+0x0000000001dfc840)
  • This indicates that the exception occurred at a specific memory address within the FlightSimulator.exe process.
  1. Exception Code:
  • ExceptionCode: 80000003 (Break instruction exception)
  • The code 80000003 corresponds to a breakpoint instruction, suggesting that the program reached an intentional breakpoint or a debug point.
  1. Exception Flags:
  • ExceptionFlags: 00000000
  • There are no special flags associated with this exception.
  1. Number of Parameters:
  • NumberParameters: 1
  • There is one parameter associated with this exception.
  1. Exception Parameter:
  • Parameter[0]: 0000000000000000
  • The parameter value is 0, which could be a default value or irrelevant in this context.
  1. Process Name:
  • PROCESS_NAME: FlightSimulator.exe
  • The process that caused the exception is FlightSimulator.exe.
  1. Error Code:
  • ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
  • The error code 0x80000003 confirms that a breakpoint was reached.
  1. Exception Code (String):
  • EXCEPTION_CODE_STR: 80000003
  • This is a string representation of the exception code, which is also 80000003.
  1. Exception Parameter 1:
  • EXCEPTION_PARAMETER1: 0000000000000000
  • The first (and only) parameter is 0.

Interpretation and Possible Causes

The 80000003 exception is generally used for debugging and means that the program stopped at a breakpoint. This can happen for several reasons:

  1. Intentional Breakpoint:
  • Developers may have left an intentional breakpoint in the code for debugging purposes. If you are running a development version or a version with debug symbols, this could be normal.
  1. Debugger Attached:
  • If a debugger was attached to the process when this exception occurred, it is possible that the debugger set the breakpoint.
  1. Code Errors:
  • In some cases, breakpoints may be reached due to errors in the code where developers leave breakpoints to detect and diagnose problems.

Possible Solutions

  1. Run a Non-Debug Version:
  • Ensure you are running a production version of the software without debug symbols.
  1. Check for Updates:
  • Check if there are any available software updates that might have fixed this issue.
  1. Consult Developers:
  • If it is development software, report this issue to the developers so they can review the code and remove unnecessary breakpoints.
  1. Debugger:
  • If you are using a debugger, review and remove any unnecessary breakpoints.

(Analyzed by ChatGpt)

1 Like
17

Iā€™m getting this exact same thing. Gets to around 75% then the audio cuts out, chops a couple of times and straight to desktop. ONCE in a while I can get into the menu.

Fresh install and everything. Tried turning off pretty much every service/feature while rebooting each time. Uninstalled basically everything. Unplugged all peripherals. Verified everything .net, swap file, etc was good. Iā€™m at a loss at this point.

|Processor|12th Gen Intel(R) Coreā„¢ i9-12900K 3.20 GHz|
|Installed RAM|32.0 GB (31.7 GB usable)|
AMD 6800XT

|Version|23H2|
|Installed on|ā€Ž10/ā€Ž6/ā€Ž2023|
|OS build|22631.3737|
|Experience|Windows Feature Experience Pack 1000.22700.1009.0|

18

Hello
You can try disabling everything that has to do with live data and try.
Traffic, real time, Azure, photogrammetry etcā€¦ etcā€¦

19

Add me to the list. Worked earlier today but tonight Iā€™m CTDing about halfway down the runway on takeoff. Earlier I was getting stuck waiting about 20-30 minutes at the Checking for updates stage. However, that has now cleared up. I get to the World Map screen enter my flight parameters click on FLY and get to the READY TO FLY screen. Get on the runway and takeoff and never make it to the end of the runway. CTD. It has now occurred 6 separate times with 6 different aircraft, 6 different airports, and 6 different loaded routes.

The community folder was renamed and is empty. System is an Alienware Aurora R16, 14th generation i9-14900KF, 32GB of RAM, NVIDIA RTX 4070 Ti.

System is running Windows 11 Professional Version 23H2 (OS Build 22631.3737)
Nvidia is using Driver Version 555.85.

20

Hello, the last 2 nvidia drivers were causing issues in games (i confirmed that by reading their forum). Try reversing back to the driver that ends with .44 and then try again

21

Okay, Iā€™ll give that a try, although I havenā€™t had any issues with the .55 driver since I installed it. For that matter I havenā€™t a CTD since January and that was due a faulty processor that Dell replaced.