CTD in MSFS 2020 On Start-up. Microsoft/Nvidia Issue (DLL 190_E658703)

ISSUE DESCRIPTION

MSFS 2020 will crash during startup just slightly beyond halfway on the status bar. To fix I must remove the DLL 190_E658703 from C:\ProgramData\NVIDIA\NGX\models. I realize there are other similar threads but your “How to Post” [sic] instructions are so convoluted and confusing I decided to post it myself.

FREQUENCY OF ISSUE

Always CTD if the referenced DLL above not removed prior to start.

REPRODUCTION STEPS

Double-click the MSFS 2020 icon. That’s it.

[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]

Do not experience fault bucket or error message but pulled it up anyways.

Log Name: Application
Source: Application Error
Date: 11/19/2025 15:11:36
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: MSI\”edited-removed”
Computer: MSI
Description:
Faulting application name: FlightSimulator.exe, version: 1.39.9.0, time stamp: 0x00000000
Faulting module name: 190_E658703.dll_unloaded, version: 2.8.12.0, time stamp: 0x689e388b
Exception code: 0xc0000005
Fault offset: 0x00000000000376a0
Faulting process id: 0x49AC
Faulting application start time: 0x1DC59A94B755C1B
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: 190_E658703.dll
Report Id: 499e8392-99e5-40fe-9b5b-c96780a9f3d7
Faulting package full name: Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:

1000
0
2
100
0
0x8000000000000000

6475

Application
MSI

FlightSimulator.exe
1.39.9.0
00000000
190_E658703.dll_unloaded
2.8.12.0
689e388b
c0000005
00000000000376a0
0x49ac
0x1dc59a94b755c1b
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
190_E658703.dll
499e8392-99e5-40fe-9b5b-c96780a9f3d7
Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe
App

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. Happens with or without.

What peripherals are you using, if relevant: n/a

[PC Only] Are you using Developer Mode or have you made any changes to it? No.

[PC, MSFS 2020 Only] Are you using DX11 or DX12? DX11

[PC Only] What GPU (Graphics Card) do you use? Nvidia RTX4060 Driver ver. 581.80 (under Driver tab in Device Manager shows: 32.0.15.8180)

[PC Only] What other relevant PC specs can you share? Packages are on external SSD.

MEDIA

Please add a screenshot or video of the issue occurring. n/a

There currently is an issue with using DX11 with the latest Nvidia drivers.
Switching to DX12 or reverting to older drivers fixes the issue.

Thank you. That worked after two whole months of losing my mind and pulling my hair out. Only problem now (and it didn’t happen this time) is DX12 sometimes “ghosts” or “trails” when moving mouse, moving control surfaces and/or aircraft in general when viewed from outside, and sometimes the instruments (needles) themselves. I think that may happen however when Super DLSS or whatever it’s called is selected. I have always preferred TAA which make instruments clearer and more legible. TAA’s what I normally use. Thanks!

1 Like

DX12 starts just fine. This is more of a question related to your answer. I have tuned/balanced my CPU/GPU for best performance with the frame rate counter (based a “2020 FSer’s” tutorial on YouTube). My setup works best with DX11 selected due to DX12 eating up the GPU headroom. As such I have to do the Windows+R and then delete the 190_E658703 thing every time before startup. Is there a way I can be notified when MS/Nvidia fix the DX11 bug or is it just a “surprise it works again!” sort of thing someday? Thanks for any insight.

Framegen causes the ghosting turn it off.