CTD on startup - d3d11.dll

Ever since I installed FS2020 months ago I’ve been getting CTD on startup every time, with errors that seem to indicate DirectX is the problem. I’ve just tried a Microsoft app to reinstall DirectX and get a new error.

FS2020 version: 1.12.13.0

Original error is first, followed by the new error

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5fda32ba
Faulting module name: d3d11.dll, version: 10.0.19041.746, time stamp: 0xfc177b9d
Exception code: 0xc0000005
Fault offset: 0x00000000001764a0
Faulting process ID: 0x28a4
Faulting application start time: 0x01d6f0c81b3279b4
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d11.dll
Report ID: dc2372bb-92e6-41b7-8691-3264645205b8
Faulting package full name: Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5fda32ba
Faulting module name: VCRUNTIME140.dll, version: 14.28.29231.0, time stamp: 0x5f4c66c9
Exception code: 0xc0000005
Fault offset: 0x000000000000167c
Faulting process ID: 0x2868
Faulting application start time: 0x01d6f173f375ac22
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.29231.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll
Report ID: 311ba86e-f2b5-4f4e-907e-9829fc128c30
Faulting package full name: Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Thanks for looking

Hi,

Install the Visual C++ Redistributable

Visual C++ Redistributable Runtimes All-in-One

If you want to help, report back to ZENDESK in detail, too.

you mention two different kind of issue at your system…

The first “d3d11.dll” points to an issue with your graphicscard. Please use search function, then tell us what you tried related to already existing hints.

AND: you have already your own thread about:
https://forums.flightsimulator.com/t/ctd-on-startup-possibly-directx-11-related/273249

The second “VCRUNTIME140.dll” is also so many times mentioned withint the forum, with threads which exactly called “VCRUNTIME140.dll”. Thus also here: plesae use search function and join to existing threads.

PS.: and an additional hint… informations about your system specs / driver versions / etc. are essentiell necessary that we can analyse somewhat.

I’ve installed the VC Runtimes as suggested by TedStriker, and am back to the d3d11 error. My graphics card is borderline but a) I can’t afford to upgrade it yet and b) they seem to be in short supply anyway.

I’d consider this thread closed until I can do some upgrades

Thanks for all replies

hmmm… can you tell us which kind of card you own ?

I’am right that you never played MSFS since you reported the issue the first time ( 09/2020 ) ?

It’s an Nvidia Quadro P400, I thought it had more memory than it does, and no, I’ve never been able to play FS2020

hmmm… a Quadro…not really made for gaming :slight_smile:
We had a similar discussion allready somewhere in the forum with e.g. a GT 710.

The FAQ mention a GTX 770 ( GTX, not GT ) with 2Gig as Min:

Your Quadro P400 has 2gig ram and is bit better as the former mention 710, but it is still soooooo far away from a performance of a GTX 770…

I’am really not sure about.

What kind you CPU you have ?

EDIT: and I forgot to ask… what driver you have installed ?

Please close this thread, I’ve looked at the required specs for other components, and would need a new PC. That’s not going to happen for a very long time

1 Like

Yes… think same… would makes more fun with new hardware.

Hope you not have to wait so long :slight_smile:

I have the same issues, and my gpu is a 1080ti, even after last update, the issues still happen.

Nome do aplicativo com falha: FlightSimulator.exe, versão: 1.13.16.0, carimbo de data/hora: 0x602a34d1
Nome do módulo com falha: d3d11.dll, versão: 10.0.19041.746, carimbo de data/hora: 0xfc177b9d
Código de exceção: 0xc0000005
Deslocamento da falha: 0x000000000012e980
ID do processo com falha: 0x2600
Hora de início do aplicativo com falha: 0x01d7093f925e5940
Caminho do aplicativo com falha: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Caminho do módulo com falha: C:\WINDOWS\SYSTEM32\d3d11.dll
ID do Relatório: 027914ab-33f1-4499-9415-228b9fb2d06a
Nome completo do pacote com falha:
ID do aplicativo relativo ao pacote com falha:

what is nvidia driver version ?

Having similar issues with a brand new 6800XT using all AMD drivers from November until now (all 8 versions). So it can’t be GPU or drivers specific, athough it’s a generic error probably coming from a driver timeout. If you check Event Manager logs make sure to check both Application and System as the drive timeout error will only appear in the latter a few seconds before the d3d11.dll crash.

Happens 100% of the time on startup.

this can be due to bad drivers (any driver!) or bad ram or corrupted files

for file errors, do drive scan (chkdsk) and see s.m.a.r.t. status of your drive (crystaldiskinfo) and also check for windows files if they arent corrupted (sfc /scannow command)
for ram errors run memtest
as for drivers, try reinstall all you hardware drivers (chipset, soundcard, gpu, etc)

In my case I’ve done a full Windows reinstall, using the latest drivers across all peripherals. scf /scannow is fine. Memory tests are fine. Tried all 8 versions of AMD drivers since November. Everything else (games included) is working fine so can’t be hardware related. I’m not getting random crashes on Windows or in games. It’s only MSFS that crashes all the time at the exact same place (2-5" into the main menu) and that only after the latest update of March 9th.

sorry, then i’m at the end with my knowledge. it’s just strange that with many there are no problems and then with others nothing works at all. have you already forwarded this to zendesk?