2 hours ago, fogboundturtle said:

it's an issue with your windows C++ Distribution. Uninstall and try the latest one

https://support.microsoft.com/en-us/topic/the-latest-supported-visual-c-downloads-2647da03-1eea-4433-9aff-95f26a218cc0

I have 18 of these listed, any idea why that would be the case? I had no CTD's before SU5 and get them very frequently ever since and it seems to be worse with WU6!

Hi,

After re-installing MSFS I'm having the same CTDs!

It's a ntdll.dll module problem

This is what I found:

Log Name:      Application
Source:        Application Error
Date:          8/9/2021 20:25:48
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Clásico
User:          N/A
Computer:      DESKTOP-QDP607N
Description:
Nombre de la aplicación con errores: FlightSimulator.exe, versión: 0.0.0.0, marca de tiempo: 0x00000000
Nombre del módulo con errores: ntdll.dll, versión: 10.0.22000.120, marca de tiempo: 0x50702a8c
Código de excepción: 0xc0000005
Desplazamiento de errores: 0x00000000000357ae
Identificador del proceso con errores: 0x1eec
Hora de inicio de la aplicación con errores: 0x01d7a4ddebbbc919
Ruta de acceso de la aplicación con errores: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Ruta de acceso del módulo con errores: C:\WINDOWS\SYSTEM32\ntdll.dll
Identificador del informe: 2f200415-078e-4a7d-b147-a4965bb1b1dd
Nombre completo del paquete con errores: Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe
Identificador de aplicación relativa del paquete con errores: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-09-08T18:25:48.7610016Z" />
    <EventRecordID>10543</EventRecordID>
    <Correlation />
    <Execution ProcessID="19332" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-QDP607N</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FlightSimulator.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.22000.120</Data>
    <Data>50702a8c</Data>
    <Data>c0000005</Data>
    <Data>00000000000357ae</Data>
    <Data>1eec</Data>
    <Data>01d7a4ddebbbc919</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
    <Data>2f200415-078e-4a7d-b147-a4965bb1b1dd</Data>
    <Data>Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>  

48 minutes ago, michap7 said:

Ah, ok I´ll give it a try, thans a lot!

Hi,

After re-installing MSFS I'm having the same CTDs!

I think is the same problem as you have.

It's a ntdll.dll module problem

John, NTDLL are windows kernel issue. That's not good.  Your windows is corrupted somewhow.

2 minutes ago, fogboundturtle said:

John, NTDLL are windows kernel issue. That's not good.  Your windows is corrupted somewhow.

Thank you, my friend.

I know now what to do: uninstall and reinstall windows.

Oh, lord!

Tomorrow will be the day.

 

Edited September 8, 20214 yr by John Fields

20 minutes ago, John Fields said:

Hi,

After re-installing MSFS I'm having the same CTDs!

I think is the same problem as you have.

It's a ntdll.dll module problem

Sometimes I´m having this ntddl.dll problem too - instead of clr.dll... 

 

19 minutes ago, John Fields said:

Thank you, my friend.

I know now what to do: uninstall and reinstall windows.

Oh, lord!

Tomorrow will be the day.

 

So, good luck and please report back to tell us if reinstalling windows helped curing the CTDs.... I´m shure it should do....

22 minutes ago, John Fields said:

I know now what to do: uninstall and reinstall windows.

Windows re-install’s are fairly quick and easy. Just make sure you back up data on the C drive. Do not simply install a fresh Windows on the old one. Let Windows format/partition the drive so it is a total clean installation that wipes the entire drive. Then take it slow, get all your drivers up to date and check your Device Manager sto confirm that all hardware is working with proper drivers. Best way to install Windows is using the media creation tool.

https://www.tenforums.com/tutorials/2376-create-bootable-usb-flash-drive-install-windows-10-a.html

 

In another thread I asked if there was a way to check or correct failed or missing files in Windows 10, without having to do a re-installation.

And someone gave me an answer. Google this:

sfc /scannow windows 10

And you will find a way to replace corrupted files.

7 hours ago, Republic3D said:

In another thread I asked if there was a way to check or correct failed or missing files in Windows 10, without having to do a re-installation.

And someone gave me an answer. Google this:

sfc /scannow windows 10

And you will find a way to replace corrupted files.

I did that already, unfortunately it did not show any corrupted files to fix...

@michap7 Again Micha - bit the dust and make a clean new install of Windows.

For how long do you have this problems now? - Since months if I remember correctly. How much time did you invest to solve it?

If you have problems with the Windows Media Tools follow this instructions here: How to download the Windows 10 2004 ISO from Microsoft (bleepingcomputer.com) . You will get an ISO with the latest version (all updates included).

And ladies and gents - remember in always make a backup (recommend incrementel) from your system drive (Windows) and the MSFS2020 folder after important updates (Windows / MSFS WU/SU). In case something goes wrong you can always restore to the last functioning version. I'm using AOMEI. You can get the basic version for free. Restoring the system drive and the MSFS Folder takes about 30 minutes, no hassle with endless searching for failures .... (except hardwareproblems of course).

And for all having CTD's when flying over dense populated areas - try to switch off Bing Data first.

Best regards

Detlef

1 hour ago, stratone said:

@michap7 Again Micha - bit the dust and make a clean new install of Windows.

For how long do you have this problems now? - Since months if I remember correctly. How much time did you invest to solve it?

If you have problems with the Windows Media Tools follow this instructions here: How to download the Windows 10 2004 ISO from Microsoft (bleepingcomputer.com) . You will get an ISO with the latest version (all updates included).

(...)

yes, I might have to reinstall Windows, I know that. I´ll have to wait until my new motherboard and cpu arrive, next month. The problems began with SU5, that is what lead me to believe in a MSFS problem at first...

Hi everyone ... 

Having read through the entirety of this post can you chaps having this issue tell me whether you are using a Z590 motherboard or not please? 

Paul 

i also get CTD since WU6.. Nothing changed since SU5 wich was running fine..

 

This is ther erroe:

 

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000001ed5b06
ID des fehlerhaften Prozesses: 0x3ffc
Startzeit der fehlerhaften Anwendung: 0x01d7a4e80915012b
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: d7a7c617-1841-4cd9-8216-19bfa72d94d1
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe
 

Any ideas on it ?

Carsten

11 hours ago, michap7 said:

 

So, good luck and please report back to tell us if reinstalling windows helped curing the CTDs.... I´m shure it should do....

Yes,

I re-installed Windows. 

Now I’m re-installing MSFS (23% already). As soon as the process finishes I will let you know.

By the way, thank you to all of you for your support.

Regards.