I noticed the sim will start fine and shutdown fine . But it does not always cause a CTD (rarely ever does at startup), It will during the sim shutdown present an error within 'Event viewer' (after closing normally). I only happened to notice this after a very recent CTD during startup. Running the latest NVIDIA 576.28 drivers (after a clean install using latest DDU. PC is up to date as well. Could you all check within your 'Event viewer' as well? The GPU drivers were installed cleanly using DDU in safe mode. This is with Windows 11 Home 24H2 26100.3915

Log Name:      Application
Source:        Application Error
Date:          5/6/2025 8:50:08 PM
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Keywords:      
User:          DESKTOP-AFGL0LD\usnao
Computer:      DESKTOP-AFGL0LD
Description:
Faulting application name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000
Faulting module name: D3D12Core.dll, version: 10.0.26100.3912, time stamp: 0x1e289019
Exception code: 0xc0000005
Fault offset: 0x000000000017da14
Faulting process id: 0xC78
Faulting application start time: 0x1DBBEFFD8DDF3AB
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\D3D12Core.dll
Report Id: 72dbb5c7-d9c2-4bf4-9240-7b211733296d
Faulting package full name: Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
    <EventID>1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2025-05-07T03:50:08.8029324Z" />
    <EventRecordID>34035</EventRecordID>
    <Correlation />
    <Execution ProcessID="15116" ThreadID="21292" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-AFGL0LD</Computer>
    <Security UserID="S-1-5-21-2400603791-3703659137-366786281-1002" />
  </System>
  <EventData>
    <Data Name="AppName">FlightSimulator.exe</Data>
    <Data Name="AppVersion">1.38.2.0</Data>
    <Data Name="AppTimeStamp">00000000</Data>
    <Data Name="ModuleName">D3D12Core.dll</Data>
    <Data Name="ModuleVersion">10.0.26100.3912</Data>
    <Data Name="ModuleTimeStamp">1e289019</Data>
    <Data Name="ExceptionCode">c0000005</Data>
    <Data Name="FaultingOffset">000000000017da14</Data>
    <Data Name="ProcessId">0xc78</Data>
    <Data Name="ProcessCreationTime">0x1dbbeffd8ddf3ab</Data>
    <Data Name="AppPath">C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data Name="ModulePath">C:\WINDOWS\SYSTEM32\D3D12Core.dll</Data>
    <Data Name="IntegratorReportId">72dbb5c7-d9c2-4bf4-9240-7b211733296d</Data>
    <Data Name="PackageFullName">Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe</Data>
    <Data Name="PackageRelativeAppId">App</Data>
  </EventData>
</Event>

Edited May 7, 20251 yr by udidwht

Have also attempted the following with same results....

 

Dism.exe /online /Cleanup-Image /checkhealth

Dism.exe /online /Cleanup-Image /scanhealth

Dism.exe /online /Cleanup-Image /Restorehealth

sfc /scannow

Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

Dism.exe /Online /Cleanup-Image /StartComponentCleanup

RESTART your computer as the last step. Then go for a test flight.

Switching to DirectX 11 yielded the following....

Log Name:      Application
Source:        Application Error
Date:          5/6/2025 10:03:12 PM
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Keywords:      
User:          DESKTOP-AFGL0LD\usnao
Computer:      DESKTOP-AFGL0LD
Description:
Faulting application name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000
Faulting module name: 190_E658703.dll_unloaded, version: 2.7.10.0, time stamp: 0x67940d50
Exception code: 0xc0000005
Fault offset: 0x000000000002ccc0
Faulting process id: 0x4B3C
Faulting application start time: 0x1DBBF0CDB9046A2
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: 190_E658703.dll
Report Id: c19c8ec5-7346-4e7f-b5b0-d215beafd7e7
Faulting package full name: Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
    <EventID>1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2025-05-07T05:03:12.8429402Z" />
    <EventRecordID>34124</EventRecordID>
    <Correlation />
    <Execution ProcessID="16988" ThreadID="12296" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-AFGL0LD</Computer>
    <Security UserID="S-1-5-21-2400603791-3703659137-366786281-1002" />
  </System>
  <EventData>
    <Data Name="AppName">FlightSimulator.exe</Data>
    <Data Name="AppVersion">1.38.2.0</Data>
    <Data Name="AppTimeStamp">00000000</Data>
    <Data Name="ModuleName">190_E658703.dll_unloaded</Data>
    <Data Name="ModuleVersion">2.7.10.0</Data>
    <Data Name="ModuleTimeStamp">67940d50</Data>
    <Data Name="ExceptionCode">c0000005</Data>
    <Data Name="FaultingOffset">000000000002ccc0</Data>
    <Data Name="ProcessId">0x4b3c</Data>
    <Data Name="ProcessCreationTime">0x1dbbf0cdb9046a2</Data>
    <Data Name="AppPath">C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data Name="ModulePath">190_E658703.dll</Data>
    <Data Name="IntegratorReportId">c19c8ec5-7346-4e7f-b5b0-d215beafd7e7</Data>
    <Data Name="PackageFullName">Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe</Data>
    <Data Name="PackageRelativeAppId">App</Data>
  </EventData>
</Event>

 

NVIDIA app was the culprit. Have had it for months without issue till now.