Jump to content
Sign in to follow this  
Followers 0
PilotPete99

Constant CTD all of a Sudden

By PilotPete99, in Microsoft Flight Simulator (2020)

Recommended Posts

fppilot    4,459

fppilot
Posted

My eventual cure was to turn off all MSFS airplane traffic.  I reverted to that previous nVidia driver twice, 531.29 and eliminated traffic.  CTD's ceased. Added back traffic.  Occasional CTD's again. Updated driver, eliminated traffic.  Smooth sailing.  Important to keep in mind that each of us may experience individual maladies.  I had an 18 month CTD-free experience, even with 40-45% offine traffic, up until early June this year.  Sure wish we had an in-flight autosave-at-invervals utility for MSFS.

  • Like 1

Frank Patton
MasterCase Pro H500M; MSI Z490 WiFi MOB; i7 10700k 3.8 Ghz; Gigabyte RTX 3080 12gb OC; H100i Pro liquid cooler; 32GB DDR4 3600;  Gold RMX850X PSU;
ASUS VG289 4K 27" Monitor; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener.  
Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126
                        "I will never put my name on a product that does not have in it the best that is in me." - John Deere

Share this post

Link to post
Share on other sites

ErichB    3,674

ErichB
Posted (edited)
9 hours ago, Brocky120 said:

 

On Windows Search, Type in Event Viewer > Windows Logs > Applications Logs.

Look for a Red exclamation mark around the time of the crash and look at the faulting module name and the exception code, copy or post it here and will help to see the cause.

 

Seems like GSX (Couatl) is one of the causes.  I had a few crashes yesterday trying different scenarios.  These are the logs.

 

EventData
    AppName couatl64_MSFS.exe
    AppVersion 4.8.0.5251
    AppTimeStamp 648730d4
    ModuleName ntdll.dll
    ModuleVersion 10.0.22621.2134
    ModuleTimeStamp eee69ec7
    ExceptionCode c0000374
    FaultingOffset 000000000010c239
    ProcessId 0x3f04
    ProcessCreationTime 0x1d9cea6743b14df
    AppPath C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe
    ModulePath C:\Windows\SYSTEM32\ntdll.dll
    IntegratorReportId 9cafa6cf-3d73-4eee-a5fa-713f4e827e0a

 

EventData

    AppName FlightSimulator.exe
    AppVersion 1.33.8.0
    AppTimeStamp 00000000
    ModuleName nvcuda64.dll
    ModuleVersion 31.0.15.3699
    ModuleTimeStamp 64cd7941
    ExceptionCode c0000409
    FaultingOffset 0000000000507405
    ProcessId 0x40e8
    ProcessCreationTime 0x1d9cea46daba3c5
    AppPath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
    ModulePath C:\Windows\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_1ddf203f8d876fdf\nvcuda64.dll
    IntegratorReportId 32067309-f3e4-4b74-ad25-db7ea4068b37
    PackageFullName Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe
    PackageRelativeAppId App

 

 

 

EventData
    AppName FlightSimulator.exe
    AppVersion 1.33.8.0
    AppTimeStamp 00000000
    ModuleName WwiseLibPCx64P.dll
    ModuleVersion 0.0.0.0
    ModuleTimeStamp 60a67fd2
    ExceptionCode c0000005
    FaultingOffset 0000000000266d52
    ProcessId 0x794
    ProcessCreationTime 0x1d9ceaa805e1150
    AppPath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
    ModulePath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe\WwiseLibPCx64P.dll
    IntegratorReportId 6b48631f-c1ed-444a-a7a9-e1cb1ec06f8e
    PackageFullName Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe
    PackageRelativeAppId App

 

  EventData
    AppName couatl64_MSFS.exe
    AppVersion 4.8.0.5251
    AppTimeStamp 648730d4
    ModuleName ntdll.dll
    ModuleVersion 10.0.22621.2134
    ModuleTimeStamp eee69ec7
    ExceptionCode c0000374
    FaultingOffset 000000000010c239
    ProcessId 0x1c0c
    ProcessCreationTime 0x1d9cec28ad89237
    AppPath C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe
    ModulePath C:\Windows\SYSTEM32\ntdll.dll
    IntegratorReportId 3c785565-1bf5-4460-b711-7784db2314e2
    PackageFullName  
    PackageRelativeAppId  
EventData
    AppName FlightSimulator.exe
    AppVersion 1.33.8.0
    AppTimeStamp 00000000
    ModuleName KERNELBASE.dll
    ModuleVersion 10.0.22621.2134
    ModuleTimeStamp c42b59fb
    ExceptionCode c0000409
    FaultingOffset 00000000000b76ff
    ProcessId 0x220c
    ProcessCreationTime 0x1d9ce821d0fa3d6
    AppPath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
    ModulePath C:\Windows\System32\KERNELBASE.dll
    IntegratorReportId 4884df10-c659-4188-9492-7c0be6810f16
    PackageFullName Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe
    PackageRelativeAppId App
Edited by ErichB

Share this post

Link to post
Share on other sites

Brocky120    65

Brocky120
Posted (edited)
1 hour ago, ErichB said:

 

Seems like GSX (Couatl) is one of the causes.  I had a few crashes yesterday trying different scenarios.  These are the logs.

 

 
Spoiler

 

EventData
    AppName couatl64_MSFS.exe
    AppVersion 4.8.0.5251
    AppTimeStamp 648730d4
    ModuleName ntdll.dll
    ModuleVersion 10.0.22621.2134
    ModuleTimeStamp eee69ec7
    ExceptionCode c0000374
    FaultingOffset 000000000010c239
    ProcessId 0x3f04
    ProcessCreationTime 0x1d9cea6743b14df
    AppPath C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe
    ModulePath C:\Windows\SYSTEM32\ntdll.dll
    IntegratorReportId 9cafa6cf-3d73-4eee-a5fa-713f4e827e0a

 

EventData

    AppName FlightSimulator.exe
    AppVersion 1.33.8.0
    AppTimeStamp 00000000
    ModuleName nvcuda64.dll
    ModuleVersion 31.0.15.3699
    ModuleTimeStamp 64cd7941
    ExceptionCode c0000409
    FaultingOffset 0000000000507405
    ProcessId 0x40e8
    ProcessCreationTime 0x1d9cea46daba3c5
    AppPath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
    ModulePath C:\Windows\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_1ddf203f8d876fdf\nvcuda64.dll
    IntegratorReportId 32067309-f3e4-4b74-ad25-db7ea4068b37
    PackageFullName Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe
    PackageRelativeAppId App

 

 

 

EventData
    AppName FlightSimulator.exe
    AppVersion 1.33.8.0
    AppTimeStamp 00000000
    ModuleName WwiseLibPCx64P.dll
    ModuleVersion 0.0.0.0
    ModuleTimeStamp 60a67fd2
    ExceptionCode c0000005
    FaultingOffset 0000000000266d52
    ProcessId 0x794
    ProcessCreationTime 0x1d9ceaa805e1150
    AppPath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
    ModulePath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe\WwiseLibPCx64P.dll
    IntegratorReportId 6b48631f-c1ed-444a-a7a9-e1cb1ec06f8e
    PackageFullName Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe
    PackageRelativeAppId App

 

  EventData
    AppName couatl64_MSFS.exe
    AppVersion 4.8.0.5251
    AppTimeStamp 648730d4
    ModuleName ntdll.dll
    ModuleVersion 10.0.22621.2134
    ModuleTimeStamp eee69ec7
    ExceptionCode c0000374
    FaultingOffset 000000000010c239
    ProcessId 0x1c0c
    ProcessCreationTime 0x1d9cec28ad89237
    AppPath C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe
    ModulePath C:\Windows\SYSTEM32\ntdll.dll
    IntegratorReportId 3c785565-1bf5-4460-b711-7784db2314e2
    PackageFullName  
    PackageRelativeAppId  
EventData
    AppName FlightSimulator.exe
    AppVersion 1.33.8.0
    AppTimeStamp 00000000
    ModuleName KERNELBASE.dll
    ModuleVersion 10.0.22621.2134
    ModuleTimeStamp c42b59fb
    ExceptionCode c0000409
    FaultingOffset 00000000000b76ff
    ProcessId 0x220c
    ProcessCreationTime 0x1d9ce821d0fa3d6
    AppPath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
    ModulePath C:\Windows\System32\KERNELBASE.dll
    IntegratorReportId 4884df10-c659-4188-9492-7c0be6810f16
    PackageFullName Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe
    PackageRelativeAppId App

 

 

I've had this before, and it's actually incorrect as it's virtually impossible for GSX to crash the sim believe it or not. Couatl64 is crashing because MSFS is crashing, you'll notice that MSFs will crash first, and the couatl64 will always be above it as it crashes after.

 

Do you use Process Lasso? Try the steps I mentioned here and let me know if you get stuck with anything

 

Edited by Brocky120
add info
  • Like 1

Share this post

Link to post
Share on other sites

ErichB    3,674

ErichB
Posted
9 hours ago, Brocky120 said:

Do you use Process Lasso?

I don't, no.

 

Share this post

Link to post
Share on other sites

Brocky120    65

Brocky120
Posted (edited)
1 hour ago, ErichB said:

I don't, no.

 

Do you use RealTek audio drivers? Disable it from Device Manager, and see if you can still get Audio to work, unsure of your setup, if you can get audio with that driver disabled, uninstall it. I thought I needed it and it caused me random crashes, uninstalled it as it turns out i did not need it and it definitely helps.

 

Any crashes with couatl64, ignore them and look at the previous event which will be FlightSimulator.exe.

Edited by Brocky120
add info
  • Like 2

Share this post

Link to post
Share on other sites

ErichB    3,674

ErichB
Posted (edited)
7 minutes ago, Brocky120 said:

Do you use RealTek audio drivers? Disable it from Device Manager, and see if you can still get Audio to work, unsure of your setup, if you can get audio with that driver disabled, uninstall it. I thought I needed it and it caused me random crashes, uninstalled it as it turns out i did not need it and it definitely helps.

 

Any crashes with couatl64, ignore them and look at the previous event which will be FlightSimulator.exe.

Yes, I believe Realtek audio is my default for the main speakers.  I have tried other options in the list but they do not provide audio from my main speakers.

 

Edited by ErichB

Share this post

Link to post
Share on other sites

ErichB    3,674

ErichB
Posted (edited)
9 hours ago, Brocky120 said:

Do you use RealTek audio drivers? Disable it from Device Manager, and see if you can still get Audio to work, unsure of your setup, if you can get audio with that driver disabled, uninstall it. I thought I needed it and it caused me random crashes, uninstalled it as it turns out i did not need it and it definitely helps.

 

Any crashes with couatl64, ignore them and look at the previous event which will be FlightSimulator.exe.

HI again

 

So I did a DDU for the Nvidia drivers and .cmd prompt suggestions you had provided.  Installed new Nvidia driver (clean install), and used Addon Linker to add only The FBW A320 with everything else as default.   I thought this was going to work but sadly, 10 mins into the flight again the sim crashed.  Took off from Gatwick and just did some general flying around default London.    Looked at the error logs.  (In time order from top to bottom),  Not sure why Couatl shows up as there is nothing related to GSX is in the Community folder (even though you say it's not suspicious in relation to the crash).

 

You had mentioned earlier in another post the ExceptionCodec0000005 is RAM/CPU related.  Might I have a faulty (or failing CPU) as this exception code has shown up almost every time.

 

AppName FlightSimulator.exe
    AppVersion 1.33.8.0
    AppTimeStamp 00000000
    ModuleName unknown
    ModuleVersion 0.0.0.0
    ModuleTimeStamp 00000000
    ExceptionCode c0000005
    FaultingOffset 000000000000005d
    ProcessId 0x1f04
    ProcessCreationTime 0x1d9d06b7585b653
    AppPath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
    ModulePath unknown
    IntegratorReportId bced0e85-e9e4-4323-97bf-0fe6170ccf4d
    PackageFullName Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe
    PackageRelativeAppId App
EventData
    Bucket 2295527374334827620
    BucketType 5
    EventName MoBEX
    Response Not available
    CabId 0
    P1 Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe
    P2 praid:App
    P3 1.33.8.0
    P4 00000000
    P5 StackHash_12a0
    P6 0.0.0.0
    P7 00000000
    P8 PCH_6F_FROM_ntdll+0x000000000009F8A4
    P9 c0000005
    P10 0000000000000008
    AttachedFiles \\?\C:\Users\flybe\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MSFSReport-Crash.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a3be603d-10d0-4cc8-b88d-3832cbe6ea7b.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d474fa8d-32e8-4f8a-ae9c-6fd3500e6b35.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ed42e13d-ad4c-4fab-ae5c-d1f8bbc783b0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9b45a14c-fe27-44f9-acb3-da05930b79d0.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.14bb0dc3-4d08-4ce0-8390-ab84f0c7957f.tmp.xml
    StorePath \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_d940fb2032a48bf96f3a9948638bd633fbfc2f72_8db61175_699b49fc-4339-46d2-a63f-aec133cdc922
    AnalysisSymbol  
    Rechecking 0
    ReportId bced0e85-e9e4-4323-97bf-0fe6170ccf4d
    ReportStatus 268435456
    HashedBucket 4d76296d4348ab6e0fdb59fc17699c64
    CabGuid 0

 

- EventData
    AppName couatl64_MSFS.exe
    AppVersion 4.8.0.5251
    AppTimeStamp 648730d4
    ModuleName ntdll.dll
    ModuleVersion 10.0.22621.2134
    ModuleTimeStamp eee69ec7
    ExceptionCode c0000374
    FaultingOffset 000000000010c239
    ProcessId 0x3fe4
    ProcessCreationTime 0x1d9d06bcc80a85d
    AppPath C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe
    ModulePath C:\Windows\SYSTEM32\ntdll.dll
    IntegratorReportId a88c0b98-613d-49ef-bded-229bb7c79bf2
    PackageFullName  
    PackageRelativeAppId  

 

Edited by ErichB

Share this post

Link to post
Share on other sites

Bob Scott    7,782

Bob Scott
Posted

I believe Couatl is loaded via a symbolic link placed in the community folder directly by the FSDT installer.

The 0xC0000005 error code is a memory access violation, and can be caused by a wide variety of problems, both software and hardware related.  Unfortunately I see no smoking gun that would point you in a particular direction.

If you're overclocking, an iffy overclock could explain your problem.  A memory module going south is another possibility.  Or overheating of a component (CPU, GPU, other).  Or a power rail on your PSU drooping the voltage.  Or an iffy power connection on your GPU. etc etc.

If you're using DX12, try DX11.  Turn off, or at least delete/rebuild your rolling cache.  Try to recreate the problem in a different location and acft to eliminate a scenery or acft issue.  Monitor power use/voltages/temps with HWInfo64.

  • Like 1
  • Upvote 1

Bob Scott | President and CEO, AVSIM Inc
ATP Gulfstream II-III-IV-V

System1 (P3Dv5/v4): i9-13900KS @ 6.0GHz, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090
Samsung 55" JS8500 4K TV@30Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU, 1.2Gbps internet
Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro
PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box

Sys2 (MSFS/XPlane): i9-10900K @ 5.1GHz, 32GB 3600/15, nVidia RTX4090FE, Alienware AW3821DW 38" 21:9 GSync, EVGA 1000P2
Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, 2x TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case

Portable Sys3 (P3Dv4/FSX/DCS): i9-9900K @ 5.0 Ghz, Noctua NH-D15, 32GB 3200/16, EVGA RTX3090, Dell S2417DG 24" GSync
Corsair RM850x PSU, TM TCA Officer Pack, Saitek combat pedals, TM Warthog HOTAS, Coolermaster HAF XB case

Share this post

Link to post
Share on other sites

Brocky120    65

Brocky120
Posted (edited)
1 hour ago, ErichB said:

HI again

 

So I did a DDU for the Nvidia drivers and .cmd prompt suggestions you had provided.  Installed new Nvidia driver (clean install), and used Addon Linker to add only The FBW A320 with everything else as default.   I thought this was going to work but sadly, 10 mins into the flight again the sim crashed.  Took off from Gatwick and just did some general flying around default London.    Looked at the error logs.  (In time order from top to bottom),  Not sure why Couatl shows up as there is nothing related to GSX is in the Community folder (even though you say it's not suspicious in relation to the crash).

 

You had mentioned earlier in another post the ExceptionCodec0000005 is RAM/CPU related.  Might I have a faulty (or failing CPU) as this exception code has shown up almost every time.

 

AppName FlightSimulator.exe
    AppVersion 1.33.8.0
    AppTimeStamp 00000000
    ModuleName unknown
    ModuleVersion 0.0.0.0
    ModuleTimeStamp 00000000
    ExceptionCode c0000005
    FaultingOffset 000000000000005d
    ProcessId 0x1f04
    ProcessCreationTime 0x1d9d06b7585b653
    AppPath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
    ModulePath unknown
    IntegratorReportId bced0e85-e9e4-4323-97bf-0fe6170ccf4d
    PackageFullName Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe
    PackageRelativeAppId App
EventData
    Bucket 2295527374334827620
    BucketType 5
    EventName MoBEX
    Response Not available
    CabId 0
    P1 Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe
    P2 praid:App
    P3 1.33.8.0
    P4 00000000
    P5 StackHash_12a0
    P6 0.0.0.0
    P7 00000000
    P8 PCH_6F_FROM_ntdll+0x000000000009F8A4
    P9 c0000005
    P10 0000000000000008
    AttachedFiles \\?\C:\Users\flybe\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MSFSReport-Crash.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a3be603d-10d0-4cc8-b88d-3832cbe6ea7b.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d474fa8d-32e8-4f8a-ae9c-6fd3500e6b35.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ed42e13d-ad4c-4fab-ae5c-d1f8bbc783b0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9b45a14c-fe27-44f9-acb3-da05930b79d0.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.14bb0dc3-4d08-4ce0-8390-ab84f0c7957f.tmp.xml
    StorePath \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_d940fb2032a48bf96f3a9948638bd633fbfc2f72_8db61175_699b49fc-4339-46d2-a63f-aec133cdc922
    AnalysisSymbol  
    Rechecking 0
    ReportId bced0e85-e9e4-4323-97bf-0fe6170ccf4d
    ReportStatus 268435456
    HashedBucket 4d76296d4348ab6e0fdb59fc17699c64
    CabGuid 0

 

- EventData
    AppName couatl64_MSFS.exe
    AppVersion 4.8.0.5251
    AppTimeStamp 648730d4
    ModuleName ntdll.dll
    ModuleVersion 10.0.22621.2134
    ModuleTimeStamp eee69ec7
    ExceptionCode c0000374
    FaultingOffset 000000000010c239
    ProcessId 0x3fe4
    ProcessCreationTime 0x1d9d06bcc80a85d
    AppPath C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe
    ModulePath C:\Windows\SYSTEM32\ntdll.dll
    IntegratorReportId a88c0b98-613d-49ef-bded-229bb7c79bf2
    PackageFullName  
    PackageRelativeAppId  

 

I assume Couatl would crash as it will be running as a process even though you may not technically be using it in MSFS.

 

Did you update your Visual C++ from the github link?

Did you use Disk Cleanup?

Delete the content.xml and .dat files located here: https://flightsimulator.zendesk.com/hc/en-us/articles/4408886545938-How-to-restore-the-sim-to-its-vanilla-state-to-get-back-in-game 

Microsoft Store/Game Pass version
C:\Users\YourUsername\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache

Steam version
C:\Users\YourUsername\AppData\Roaming\Microsoft Flight Simulator


Retail boxed version
C:\Users\YourUsername\AppData\Local\MSFSPackages

 

Another thing is delete everything in the SceneryIndexes folder: https://flightsimulator.zendesk.com/hc/en-us/articles/360017133940-How-to-install-a-new-update-safely 

Microsoft Store/Game Pass version
C:\Users\YourUsername\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes

Steam version
C:\Users\YourUsername\AppData\Roaming\Microsoft Flight Simulator\SceneryIndexes

Retail boxed version
C:\Users\YourUsername\AppData\Local\MSFSPackages\SceneryIndexes

More help here: 

https://flightsimulator.zendesk.com/hc/en-us/articles/4412295717650-Read-first-Windows-10-11-troubleshooting

https://flightsimulator.zendesk.com/hc/en-us/articles/4406280399250-Basic-Troubleshooting-How-to-troubleshoot-crashing-CTDs-issues-

https://flightsimulator.zendesk.com/hc/en-us/articles/4406280653202-Advanced-Troubleshooting-How-to-troubleshoot-crashing-CTDs-issues

 

0xc0000005 is the worst to diagnose unfortunately. Try and run flightsim in safe mode when it crashes and see how you get on with that. I get that error time to time, but very rare.

 

Hope this helps and let us know how you get on!

Edited by Brocky120
add info
  • Like 1

Share this post

Link to post
Share on other sites

udidwht    139

udidwht
Posted

Give the following a try:

 

Run the following commands in Powershell (admin rights)…

Go through each of the following steps one at a time. Copy each line, one at a time , paste it into the Dos window (crtl + V) and press return

and it will then run. Wait until each runs and finishes before you move on to the next one.

When you are completely finished, Restart your computer and then try to see in MS2020 will start and run properly

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.

  • Like 1

Win10Pro 22H2-19045.4474/IntelCorei7-3770K/GigabyteGA-Z68XP-UD3/32GBGSkillCL7-8-8-24/AsusRTX2070OC8GB/1TBCrucialMX500SSD/2 TB PNY CS900/(x3)1TBRAWMushkinSSDs/LGBlueRayBurner/RosewillChallengerTowerBlack/CorsairRM750wPSU/X56HOTAS/TtesportsCommanderKeyboardMousecombo/TrackIR5Pro/34inUltraWideScreenLG2560x1080p/TM2xMFDCougar/OculusQuest2/InateckKU5211PCIe3.2/LTERIVERPCIeG2S4/TMobileHomeInternet5G

MSI Codex Series R2 B14NUC7-095US/Windows 11 Home 22H2 22631.3593/i7 14700F/MSI Pro B760 VC Wifi II/RTX 4060/32GB DDR5 5600mhz/650w Gold PSU

Share this post

Link to post
Share on other sites

ErichB    3,674

ErichB
Posted (edited)

Bob, Brock, Udidwht

Thanks so much for help with this.  I will try all of these suggestions tonight again. 

It is definitely not location/scenery specific, or aircraft specific, as I've tried with the FBW and the Fenix in different world locations with the same result.

If none of these other remediation actions work, it may just accelerate my upgrade to a new machine. My current one can still hold its own with MSFS (when it works) but I have a new spec in mind which I was planning on building in June.

Anyway, I will let you know how I get on.

Edited by ErichB

Share this post

Link to post
Share on other sites

Brocky120    65

Brocky120
Posted (edited)
45 minutes ago, ErichB said:

Bob, Brock, Udidwht

Thanks so much for help with this.  I will try all of these suggestions tonight again. 

It is definitely not location/scenery specific, or aircraft specific, as I've tried with the FBW and the Fenix in different world locations with the same result.

If none of these other remediation actions work, it may just accelerate my upgrade to a new machine. My current one can still hold its own with MSFS (when it works) but I have a new spec in mind which I was planning on building in June.

Anyway, I will let you know how I get on.

 

It's unlikely to be your machine to be honest, in my opinion that would be a last resort. It's very frustrating and I've spent tens of hours diagnosing issues for myself. We should all jump in to create a sticky thread based of everything + more in this topic

Edited by Brocky120
add info

Share this post

Link to post
Share on other sites

ErichB    3,674

ErichB
Posted (edited)
23 minutes ago, Brocky120 said:

We should all jump in to create a sticky thread based of everything + more in this topic

I was thinking the same thing.  There should be a sticky denoting the order of remediation items to apply in such cases.  There is so much good information in small pieces lying all over these forums and others relating to this very issue.  In fact, I'm going to cut and paste all of these suggestions into a document for myself which I can reference in future.  I can never remember them, especially because these issues are now few and far between.

If I don't sort this issue out by the weekend, it would mean that I have to go out and be sociable, which would be awful 🤣

Edited by ErichB

Share this post

Link to post
Share on other sites

ErichB    3,674

ErichB
Posted
12 hours ago, Brocky120 said:

Did you update your Visual C++ from the github link?

Did you use Disk Cleanup?

Delete the content.xml and .dat files located

 

12 hours ago, Brocky120 said:

Another thing is delete everything in the SceneryIndexes folder: https://flightsimulator.zendesk.com/hc/en-us/articles/360017133940-How-to-install-a-new-update-safely

 

12 hours ago, udidwht said:

Dism.exe /online /Cleanup-Image /checkhealth

Dism.exe /online /Cleanup-Image /scanhealth

All tried.  So far, same result.

Share this post

Link to post
Share on other sites

Brocky120    65

Brocky120
Posted (edited)
1 hour ago, ErichB said:

 

 

All tried.  So far, same result.

Hmm, RealTek audio driver could still be an issue (there are a lot of threads on it). Are you able to uninstall it and play with no sound and see if the issue still occurs?

Failing that, download Prime95 and running a stress test on Large FFT's for 30 minutes to see if any CPU cores fail or stop, and as @Bob Scott mention keep an eye on your temps using Hwinfo.

 

Edited by Brocky120
add info

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0
Go To Topic Listing

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...