I would do the following, John, because you have been fighting these CTDs for a while now. 

- No add-ons.
- No config file tweaks
- No USB devices attached except your keyboard and mouse installed. 
- Make sure Windows is fully up to date. This requires checking for new updates over and over. Until you see nothing. 
- Make sure your system is not overclocked at all. No CPU, memory or GPU overclocks. You can save profiles for your motherboard so you can restore it later. But make sure it is vanilla for now.  
- Make sure you are not running any optimizer software like Process Lasso or MSI Afterburner. 
- In the MSFS Marketplace avoid installing NXi, FBW or WT mods. Don't even install any 3rd party add-ons you may have purchased. Keep it to Asobo / Standard add-ons only. 

If you can run the sim without issues you want to do one thing at a time. Maybe put your MB OC profile back, then do a thorough retest. If that passes, check that off the list you wrote down, then add one more thing back. If you do get a CTD try to reproduce it, then post your steps so we can confirm the issue.  

Good luck! 

 

5 hours ago, Moria15 said:

set render settings to 100.    Render settings below 100 looses lights,  render settings above 100 adds ghost lights.  Asobo aware and are investigating if a hotfix is possible.

Graham

Brilliant thanks a lot Graham!

Showcase camera views, changing views left to right wing view shows objects popping up.

External camera view, fast panning, no issues.

Anyone else?

Any advise?

2 hours ago, RobJC said:

I would do the following, John, because you have been fighting these CTDs for a while now. 

- No add-ons.
- No config file tweaks
- No USB devices attached except your keyboard and mouse installed. 
- Make sure Windows is fully up to date. This requires checking for new updates over and over. Until you see nothing. 
- Make sure your system is not overclocked at all. No CPU, memory or GPU overclocks. You can save profiles for your motherboard so you can restore it later. But make sure it is vanilla for now.  
- Make sure you are not running any optimizer software like Process Lasso or MSI Afterburner. 
- In the MSFS Marketplace avoid installing NXi, FBW or WT mods. Don't even install any 3rd party add-ons you may have purchased. Keep it to Asobo / Standard add-ons only. 

If you can run the sim without issues you want to do one thing at a time. Maybe put your MB OC profile back, then do a thorough retest. If that passes, check that off the list you wrote down, then add one more thing back. If you do get a CTD try to reproduce it, then post your steps so we can confirm the issue.  

Good luck! 

 

Thank you, Rob.

I did 90% you say.

I've re-installed MSFS from scratch (now is installing the scenic updates).

I read from another user that has the same problem: the CTDs always occur when we are near a big city, never in places far away of populated areas (we can fly hours and hours in places like Okawango or the Andes).

What it can be?

 

7 minutes ago, John Fields said:

What it can be?

I'm guessing here but buildings, trees and photogrammetry are significantly denser near population centres, and subsequently tax the sim and your hardware more.

If you haven't yet, would also suggest you could follow all these steps in sequence (these articles were updated as recently as yesterday):

https://flightsimulator.zendesk.com/hc/en-us/articles/360015893879-All-versions-Crashing-CTDs-issues-Checklist

https://flightsimulator.zendesk.com/hc/en-us/articles/4406280399250-All-versions-Crashing-CTDs-issues-Basic-Troubleshooting

https://flightsimulator.zendesk.com/hc/en-us/articles/4406280653202-All-versions-Crashing-CTDs-issues-Advanced-Troubleshooting

30 minutes ago, John Fields said:

Thank you, Rob.

I did 90% you say.

I've re-installed MSFS from scratch (now is installing the scenic updates).

I read from another user that has the same problem: the CTDs always occur when we are near a big city, never in places far away of populated areas (we can fly hours and hours in places like Okawango or the Andes).

What it can be?

 

Could be bad RAM. When you approach big cities you might be accessing areas of your RAM that you don't use in less dense areas. But first things first, after you install the sim fully do some testing. Please let us know the 10% you have not done so we can comment. But honestly John, I think you need to go 100%. If you need help, let us know. 

1 minute ago, RobJC said:

Could be bad RAM. When you approach big cities you might be accessing areas of your RAM that you don't use in less dense areas. But first things first, after you install the sim fully do some testing. Please let us know the 10% you have not done so we can comment. But honestly John, I think you need to go 100%. If you need help, let us know. 

No, Rob.

I discovered this:

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>  

I think the best I can do is to uninstall and re-install windows.

Tomorrow... what a day!

 

 

2 minutes ago, John Fields said:

No, Rob.

I discovered this:

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>  

Maybe try reinstalling the dynamic link library (.dll):

https://answers.microsoft.com/en-us/windows/forum/all/app-crash-with-ntdlldll/9aa59f80-99a1-4f3c-b2f0-7eb72df05b2a

15 minutes ago, March Hare said:

Maybe try reinstalling the dynamic link library (.dll):

https://answers.microsoft.com/en-us/windows/forum/all/app-crash-with-ntdlldll/9aa59f80-99a1-4f3c-b2f0-7eb72df05b2a

Definitely give that a shot first! Reinstall Windows? Ugh. 

Reinstall windows takes only around 30 Mins on today’s computers. It’s the programs like flightsim that takes hours afterwards 

12 minutes ago, Ianrivaldosmith said:

Reinstall windows takes only around 30 Mins on today’s computers. It’s the programs like flightsim that takes hours afterwards 

Still, it makes more sense to try reinstalling the .dll in case it's as simple as that.

Might be obvious, but don't have any programs running when you do it, John.

Edited September 8, 20214 yr by March Hare

John, quit screwing around and do what you're thinking:  wipe the drive and reinstall Win 10.  BEFORE doing that, use tools to fully evaluate your RAM, hard drives, etc.  

I LOVE IT! I have it set to ultra and the difference is night and day. Thanks, Asobo!

58 minutes ago, Ianrivaldosmith said:

Reinstall windows takes only around 30 Mins on today’s computers. It’s the programs like flightsim that takes hours afterwards 

Unfortunately Windows and MSFS are only part of the puzzle. I have a lot of other software to install to get this rig back. It's an all day/multiday adventure to get things back to normal.