MSFS2020 CTD when use navigraph navdata

User Support Hub Crashes (CTDs)
,
1

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

  • One for iteration (msfs-2020 )

  • One for platform (ms-store,)

  • One for aircraft if related (Asobo boeing747)

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

Since I updated msfs2020 to version 1.39.9.0, once I install and use the msfs basic navigation data published by navigraph (with “navigraph-navdata” and “navigraph-navdata-base” folders installed in the Community directory), there is a probability of over 90% of crashing when running msfs2020. However, as long as I remove these two folders from the Community directory and delete the corresponding two index cache data files (navigraph-navdata. dat and navigraph-navdata-base. dat) in the Microsoft. FlightSimulator_8wekyb3d8bbwe \ LocalCache \ CeneryIndexes directory, there will be no more crashes.

I reinstalled my MSFS2020 yesterday (which is a huge project), and after installation, all settings (including general settings and auxiliary settings) were restored to their default configuration, without installing any third-party plugin models or plugin scenery.
The configuration of the computer is as follows:
1 CPU：amd7800x3d
2 GPU：Nvdia 4070tis， Driver version 577.00
Under the above configuration, use the default 747 model of msfs2020 to fly from zsam to zspd (default scenery). We conducted the following tests in sequence:

  1. The community directory only has two folders, “navigraph-navdata” and “navigraph-navdata-base” (version 2511 rev.3 installed through navigraph hub): msfs2020 crashes after running for more than 10 minutes.

  2. The community directory only has’ navigraph-navdata ‘. Remove’ navigraph-navdata-base 'and recreate the landscape index for msfs2020: msfs2020 crashed after running for about 50 minutes.

  3. Continue to delete ‘navigraph-navdata’ from the community directory and rebuild the sceneryindex of msfs2020: I have made three round trips between zsam and zspd without any crashes.

  4. Put the folders’ navigraph-navdata ‘and’ navigraph-navdata-base 'back into the community directory. About 30 minutes after ZSAM take off, MSFS2020 crashed.
    After each crash, the error logs collected in the application logs of the operating system are as follows:

出错应用程序名称： FlightSimulator.exe，版本： 1.39.9.0，时间戳： 0x00000000
出错模块名称： FlightSimulator.exe， 版本： 1.39.9.0，时间戳： 0x00000000
异常代码： 0xc0000005
错误偏移： 0x00000000002b95a6
出错进程 ID： 0x19DC
出错应用程序开始时间： 0x1DC5513FAD28AF1
Faulting 应用程序路径： C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting 模块路径： C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID： 34e75d03-f027-4a4a-9ef9-b2b9bed1fd0d
Faulting 包全名： Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe
Faulting 程序包相对应用程序 ID： App 个

The attachment is the crash report generated by the msfs2020 program

AsoboReport-Crash-917670024.txt (23.6 KB)

FREQUENCY OF ISSUE

90%

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Initialize the installation of msfs2020 (without installing any third-party plugins or world updates, city updates);

  2. Install AIRAC 2511 rev.3 using Navigraph Hub

  3. Use Asobo747 to operate flights between ZSAM and ZSPD (other airports are also available)

[PC ONLY] FAULT BUCKET ID

If you experienced a crash on PC, sharing your Fault Bucket ID would be extremely helpful. You can learn how to find that ID here: How to find your Fault Bucket ID after a crash [PC]

FAULT BUCKET ID information:

故障存储段 2172019034039847645，类型 5
事件名称: MoAppCrash
响应: 不可用
Cab ID: 0

问题签名:
P1: Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.39.9.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.39.9.0
P7: 00000000
P8: c0000005
P9: 00000000002b95a6
P10:

附加文件:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a805f1a0-6da7-428f-aee4-e7f8ead688ef.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.67990be5-772a-4e40-8515-c470c605d153.tmp.WERInternalMetadata.xml
WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20251114_1_EC_0_inject.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.612f2402-710b-4a66-a36b-a2a0a48a1648.tmp.etl
WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.51eff1d1-ecc9-4016-9038-0081e3543926.tmp.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bbe7dce6-5937-4f4c-9290-0c4b5eb41841.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c24a4bcc-31cd-4aff-98ee-16a07c6b369b.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4a502fcf-2dd3-4da4-b7ea-5f2c3ad2bfcc.tmp.xml

可在此处获取这些文件:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_10a21f353f335cde8a7aa0af7911e022489241b_586ca05b_1072648e-2176-4a22-b9e6-a211c6c8eea0

分析符号:
重新检查解决方案: 0
报告 ID: a21047ce-90f6-456d-9dcd-5280722b12d3
报告状态: 268435456
哈希存储段: 4a9c98b665e9adc1be248fcdb9550add
Cab GUID: 0

YOUR SETTINGS

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 User Support Hub.

What peripherals are you using, if relevant:

[PC Only] not using Developer Mode

[PC, MSFS 2020 Only] DX11

[PC Only] What GPU (Graphics Card) do you use:nvdia 4070tis,driver 577.00

[PC Only] What other relevant PC specs can you share:CPU amd7800X3D,mem32G

MEDIA

Please add a screenshot or video of the issue occurring.

2

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

same issue

4

However, as you can see, this issue has been present since I upgraded from 1.38.2.0 to 1.39.9.0 in August (this problem had never occurred before 1.38.2.0), and I have also posted several posts seeking technical assistance on the MSFS forum. However, there is no technical support available to handle or answer this problem on the MSFS forum, and I even left a message saying that any issues related to third-party plugins need to be addressed by a third party.
Similarly, I consulted with the official website of Navigraph regarding this issue, and they provided me with many solutions. Although they did not completely solve the problem, they provided a solution plan. The most likely reason is that there is partial incompatibility between MSFS and Navigraph data.
Moreover, not everyone who uses navigraph navigation data experiences this issue. If everyone experiences the same problem, then I can understand that navigraph should bear the blame. However, the current situation is indeed quite complex, and both msfs and navigraph should have a common and positive attitude towards analyzing this issue. After all, MSFS is not a completely closed platform and does not allow the use of any third-party plugins. Since it is allowed and open, it is necessary to help users analyze compatibility issues, even if they cannot provide a final solution, they can provide some analytical ideas.

5

I have a crash issue ONLY when trying to update the navdata in the Just Flight RJ series. Update the RJ, fly ANY plane and I’ll eventually get a crash. Uninstall the navdata from Navigraph for the RJ only…Zero issues. I have yet to find another person with this issue with Navigraph and the Just Flight RJ. I guess the poor RJ will never have up to date data!

6

You definitely have an issue somewhere, I have not had that happen, nor seen it mentioned here.
Did you contact Navigraph in this regards, they are very good with service issues.

7

I have had this same issue for over a year. MSFS will crash with Navigraph installed, as soon as I uninstall it works like a treat

9

Yes, I have also consulted with Navigraph, but they have not been able to provide a more effective solution yet. However, they are still actively providing some problem-solving ideas. But the emergence of this problem should be focused on the issue of data compatibility between msfs2020 and navigraph, or the problem of read conflicts when the operating system processes these data in memory.
Since I updated msfs2020 from 1.38.2.0 to 1.39.9.0, as long as I installed navigraph navigation data in msfs2020, every crash occurred in the stage of descending and landing airport preparation, and every error log was identical (provided in the message I raised the question). I have never encountered this issue in version 1.38.2.0. I even tried using Navigraph data from issue 2504 in version 1.39.9.0, which was released in August, but the problem still persists.
What other information do I need to provide to help you further analyze this issue?
From other people’s comments, it seems that I am not the only one who has encountered this issue. Although the scope of occurrence is small and the affected population is small, it is indeed a significant problem that greatly affects the user experience of MSFS. Think about it, when I prepared, pushed out, taxied, took off from the cockpit, flew for 2 hours or even longer, and finally prepared to land, MSFS collapsed. How the player’s mood must have collapsed…

10

When your MSFS crashes, what does the error log look like? Is it the same as mine?

11

AsoboReport-Crash-612094609.txt (31.0 KB)

12

The fault code when you crashed is the same as mine. 0xC0000005.

if you delete navigraph-navdata and navigraph-navdata-base,will msfs still crash？

13

First, I would run DX12, not DX11.
Nvidia and DX11 do not play well together with FS2020, and does lead to CTD’s.
There are many articles here on that issue.

The code you mention causing the issue, 0xC0000005, is very generic and difficult to track down.
There is an article here that does contain some tips on how to cure it.
I experienced this code myself, and oddly enough, not using these forums when running MSFS2020 was the answer.

How to troubleshoot faulting module ucrtbase.dll and/or exception code 0xc0000005 crashes

I hope this is some help!

14

Thank you very much for your reply. I will refer to the information you provided and try again.
I always crash when installing navigraph navigation data, whether I use DX11 or DX12

15

Delete nav data，without any crashes。

16

Yes, after deleting the Navigraph Navdata, it won’t crash anymore. However! The default navigation data in MSFS is quite inaccurate for some airports, so Navigraph Navdata is necessary to compensate.

17

I have tried all the methods mentioned in the guide, but still have not solved the issue of 0xC0000005. I even tried unplugging a memory and reinserting my GPU. The problem still exists.

18

I noticed this newer article in the Sim Support tab, it may apply as well:

I’m not so sure that this is an issue with Navigraph, as if that were the case we would be seeing lots more posts on this issue.
However another thing you could do though, is contact Navigraph.
They may have more info on the issue.

19

Wait a few more days，the next cycle navdate released，may be the issue has been solved。

20

No, this issue only started to occur after MSFS was updated from 1.38.2.0 to 1.39.9.0 in August. It has been several months now and the problem has not been resolved. Using any cycle of navigraph navigation data will cause crashes. As expected, the Navigraph Airac 2512 still cannot solve this problem, but let’s wait and see.
This is indeed a problem that exists among a very small minority of people, but it is indeed a fatal problem.

21

Yes, I have also sought help from Navigraph regarding this issue, but have not yet found an effective solution.
This is the post I posted on navigraph: