CTD
- Thread starter Aircanuck
- Start date
FlameOut
SOH-CM-2024
I purchased a new 4TB NVMe M.2 SSD on Amazon Prime Day. October 11, 2023, Wednesday of last week.
I just completed a new Windows 11 install + all the updates on this past Tuesday.
I just completed a new MSFS install + d/l all of my stuff from the Marketplace on this past Wednesday & Thursday.
Nivida driver 545.84
Yesterday I was flying around in the default TBM 930, low level and kind of fast ...... I was looking at my desktop in about 10 minutes time!
Today I left UK2000's EGPF Glasgow to MSFS default EHAM Amsterdam in the default Baron .... never made it across the Channel, I was looking at my desktop.
NO warning, NO explanation
... just poof!
It is a good & clean install, I did NO copy & paste.
Just a few hours ago my faithful TrackIR 5 Pro went tits up! Grrrrrrrrrrrrrrr
-Don
I just completed a new Windows 11 install + all the updates on this past Tuesday.
I just completed a new MSFS install + d/l all of my stuff from the Marketplace on this past Wednesday & Thursday.
Nivida driver 545.84
Yesterday I was flying around in the default TBM 930, low level and kind of fast ...... I was looking at my desktop in about 10 minutes time!
Today I left UK2000's EGPF Glasgow to MSFS default EHAM Amsterdam in the default Baron .... never made it across the Channel, I was looking at my desktop.
NO warning, NO explanation
... just poof! It is a good & clean install, I did NO copy & paste.
Just a few hours ago my faithful TrackIR 5 Pro went tits up! Grrrrrrrrrrrrrrr
-Don
"No warning" No explanation" ... Exactly !! Gosh I feel better, kindaI purchased a new 4TB NVMe M.2 SSD on Amazon Prime Day. October 11, 2023, Wednesday of last week.
I just completed a new Windows 11 install + all the updates on this past Tuesday.
I just completed a new MSFS install + d/l all of my stuff from the Marketplace on this past Wednesday & Thursday.
Nivida driver 545.84
Yesterday I was flying around in the default TBM 930, low level and kind of fast ...... I was looking at my desktop in about 10 minutes time!
Today I left UK2000's EGPF Glasgow to MSFS default EHAM Amsterdam in the default Baron .... never made it across the Channel, I was looking at my desktop.
NO warning, NO explanation
It is a good & clean install, I did NO copy & paste.
Just a few hours ago my faithful TrackIR 5 Pro went tits up! Grrrrrrrrrrrrrrr
-Don
Lets hope someone can come onboard with some thoughts and a possible remedy. I've downloaded nothing exotic other than a handful of airport upgrades and some A/C textures. Did bump into a fellow Simmer on Facebook complaining the other day with the same issue !!
"No warning" No explanation" ... Exactly !! Gosh I feel better, kinda
Right after the CTD's, try checking the eventviewer in the administrative events and see what is listed as errors there. post it here, and I'm quite sure more than a few people will be able to help.
Cheers,
Priller
Thank you, will give it a try.
The official forum is also a good place for troubleshooting crashes. Some of the people there have some deeper knowledge of the sim's inner workings.
Cazzie
SOH-CM-2024
Most all CTDs in MSFS are caused by 3rd party add-ons. REX Advanced AccuSeason did it to mine. Would not be in the air 1 minute before CTD. Did like Priller said and checked the event viewer and AccuSeason Advanced was there at the top, I had just updated it from the older version. I uninstalled REX AccuSeason Advanced and all Registry files associated with it and not one problem after that. I'm using the Bijon seasons until MS can do better.
Check your latest 3rd party installation.
Cazzie
Check your latest 3rd party installation.
Cazzie
Update
Deleted the "Rolling Cache" folder within the sim and then cleaned out under the "Internet Properties" folder in Windows 11 all cookies, temporary internet files and history. So far so good, managed to bang out a solid 2.5 hr's of flying with no issues .... its Miller Time
Deleted the "Rolling Cache" folder within the sim and then cleaned out under the "Internet Properties" folder in Windows 11 all cookies, temporary internet files and history. So far so good, managed to bang out a solid 2.5 hr's of flying with no issues .... its Miller Time
I'm afraid that isn't the one. It really has to be the CTD, not the shutdown after that.
Priller
Oops ... let me ring the IT dept and see if we can sort this out. Put together two flights today, the first lasted all of ten minutes and crashed, the next was three hours in duration with no issues, go figure !
Now that's a good pointer. See what the difference in those two flights was with regard to addons used. I'm pretty sure it was one of the addons used in that first flight that was the culprit.
Priller
Bushpounder
SOH-CM-2024
I've been saying this since FS98! 90-95% of the time, it was an earlier add-on that was screwing with FS. Holds true with every version since. That's why designing back then (I guess now as well, in many cases) was so tough. It will hold true with this one and the next one as well.
Don BP
The good news is I was flying the Blackbox Islander ( twin engine ) on both occasions, this is my "go to" flyer and has been for longest time. The flight was under real world time and weather. I think for the time being we'll continue to monitor this concern, hate like heck to delete the addon if indeed its the problem, although it may get bumped if the up coming MU2 preforms as good as she appears. As always, appreciate all your thoughts and contributions dealing with this bug.
For those having any CTD issue/s try the following…
Run the following commands…
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.
Run the following commands…
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.
FlameOut
SOH-CM-2024
Well, I achieved about 12 hrs. of flight time since my last post until now.
I hate Event Viewer; it is not easy for us common folks to understand the thing! I fooled with it for about a 1/2 hour and somehow clicked on the correct thing. I want Event Viewer to say: Hey stoopid your flight sim stopped because of XYZ
Copy & Paste:
Log Name: Application
Source: Application Error
Date: 10/25/2023 12:14:13 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: FLAME\Flame
Computer: Flame
Description:
Faulting application name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.22621.2428, time stamp: 0x806d3ecf
Exception code: 0xc0000005
Fault offset: 0x000000000008eb62
Faulting process id: 0x0x194C
Faulting application start time: 0x0x1DA0753C6D3461F
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: ed32051d-dd7f-4635-b9b9-5d4240e743bd
Faulting package full name: Microsoft.FlightSimulator_1.34.16.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="2023-10-25T17:14:13.9954844Z" />
<EventRecordID>821</EventRecordID>
<Correlation />
<Execution ProcessID="8128" ThreadID="5168" />
<Channel>Application</Channel>
<Computer>Flame</Computer>
<Security UserID="S-1-5-21-2678431857-1290678594-3773624301-1001" />
</System>
<EventData>
<Data Name="AppName">FlightSimulator.exe</Data>
<Data Name="AppVersion">1.34.16.0</Data>
<Data Name="AppTimeStamp">00000000</Data>
<Data Name="ModuleName">ntdll.dll</Data>
<Data Name="ModuleVersion">10.0.22621.2428</Data>
<Data Name="ModuleTimeStamp">806d3ecf</Data>
<Data Name="ExceptionCode">c0000005</Data>
<Data Name="FaultingOffset">000000000008eb62</Data>
<Data Name="ProcessId">0x194c</Data>
<Data Name="ProcessCreationTime">0x1da0753c6d3461f</Data>
<Data Name="AppPath">C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
<Data Name="ModulePath">C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data Name="IntegratorReportId">ed32051d-dd7f-4635-b9b9-5d4240e743bd</Data>
<Data Name="PackageFullName">Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe</Data>
<Data Name="PackageRelativeAppId">App</Data>
</EventData>
</Event>
It's all Greek & Chinese to me.
@ udidwht, I've fooled around with those command line instructions before. Go to my profile and look at my old post and you'll see I didn't learn anything using those either! Oh, and thanks for the post on the head tracker IR thing in the other thread.
- Don
I hate Event Viewer; it is not easy for us common folks to understand the thing! I fooled with it for about a 1/2 hour and somehow clicked on the correct thing. I want Event Viewer to say: Hey stoopid your flight sim stopped because of XYZ
Copy & Paste:
Log Name: Application
Source: Application Error
Date: 10/25/2023 12:14:13 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: FLAME\Flame
Computer: Flame
Description:
Faulting application name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.22621.2428, time stamp: 0x806d3ecf
Exception code: 0xc0000005
Fault offset: 0x000000000008eb62
Faulting process id: 0x0x194C
Faulting application start time: 0x0x1DA0753C6D3461F
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: ed32051d-dd7f-4635-b9b9-5d4240e743bd
Faulting package full name: Microsoft.FlightSimulator_1.34.16.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="2023-10-25T17:14:13.9954844Z" />
<EventRecordID>821</EventRecordID>
<Correlation />
<Execution ProcessID="8128" ThreadID="5168" />
<Channel>Application</Channel>
<Computer>Flame</Computer>
<Security UserID="S-1-5-21-2678431857-1290678594-3773624301-1001" />
</System>
<EventData>
<Data Name="AppName">FlightSimulator.exe</Data>
<Data Name="AppVersion">1.34.16.0</Data>
<Data Name="AppTimeStamp">00000000</Data>
<Data Name="ModuleName">ntdll.dll</Data>
<Data Name="ModuleVersion">10.0.22621.2428</Data>
<Data Name="ModuleTimeStamp">806d3ecf</Data>
<Data Name="ExceptionCode">c0000005</Data>
<Data Name="FaultingOffset">000000000008eb62</Data>
<Data Name="ProcessId">0x194c</Data>
<Data Name="ProcessCreationTime">0x1da0753c6d3461f</Data>
<Data Name="AppPath">C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
<Data Name="ModulePath">C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data Name="IntegratorReportId">ed32051d-dd7f-4635-b9b9-5d4240e743bd</Data>
<Data Name="PackageFullName">Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe</Data>
<Data Name="PackageRelativeAppId">App</Data>
</EventData>
</Event>
It's all Greek & Chinese to me.
@ udidwht, I've fooled around with those command line instructions before. Go to my profile and look at my old post and you'll see I didn't learn anything using those either! Oh, and thanks for the post on the head tracker IR thing in the other thread.
- Don
Well, I achieved about 12 hrs. of flight time since my last post until now.
I hate Event Viewer; it is not easy for us common folks to understand the thing! I fooled with it for about a 1/2 hour and somehow clicked on the correct thing. I want Event Viewer to say: Hey stoopid your flight sim stopped because of XYZ
Copy & Paste:
Log Name: Application
Source: Application Error
Date: 10/25/2023 12:14:13 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: FLAME\Flame
Computer: Flame
Description:
Faulting application name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.22621.2428, time stamp: 0x806d3ecf
Exception code: 0xc0000005
Fault offset: 0x000000000008eb62
Faulting process id: 0x0x194C
Faulting application start time: 0x0x1DA0753C6D3461F
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: ed32051d-dd7f-4635-b9b9-5d4240e743bd
Faulting package full name: Microsoft.FlightSimulator_1.34.16.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="2023-10-25T17:14:13.9954844Z" />
<EventRecordID>821</EventRecordID>
<Correlation />
<Execution ProcessID="8128" ThreadID="5168" />
<Channel>Application</Channel>
<Computer>Flame</Computer>
<Security UserID="S-1-5-21-2678431857-1290678594-3773624301-1001" />
</System>
<EventData>
<Data Name="AppName">FlightSimulator.exe</Data>
<Data Name="AppVersion">1.34.16.0</Data>
<Data Name="AppTimeStamp">00000000</Data>
<Data Name="ModuleName">ntdll.dll</Data>
<Data Name="ModuleVersion">10.0.22621.2428</Data>
<Data Name="ModuleTimeStamp">806d3ecf</Data>
<Data Name="ExceptionCode">c0000005</Data>
<Data Name="FaultingOffset">000000000008eb62</Data>
<Data Name="ProcessId">0x194c</Data>
<Data Name="ProcessCreationTime">0x1da0753c6d3461f</Data>
<Data Name="AppPath">C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
<Data Name="ModulePath">C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data Name="IntegratorReportId">ed32051d-dd7f-4635-b9b9-5d4240e743bd</Data>
<Data Name="PackageFullName">Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe</Data>
<Data Name="PackageRelativeAppId">App</Data>
</EventData>
</Event>
It's all Greek & Chinese to me.
@ udidwht, I've fooled around with those command line instructions before. Go to my profile and look at my old post and you'll see I didn't learn anything using those either! Oh, and thanks for the post on the head tracker IR thing in the other thread.
- Don
The command lines will ensure that Windows is corrupt free. Did you run them and reboot afterwards?
As for the event viewer the one that stands out is the 'ntdll.dll' file which is a Windows core file. Also make sure all your apps from within the MS store are up to date. Open the store and click at lower left click 'Library' then top right....'Get updates".
IF you’ve generally had a stable system until the past few days AND you’ve a high speed internet connection > 100mbps then there is a thread on the official forum describing the issue…
https://forums.flightsimulator.com/t/sim-crashes-when-zooming-in-at-the-worldmap/607606
Its gotten long to read from the beginning but basically I suspected it is due to having a high speed connection and so my workaround is to limit your LAN card link speed to 100mbps (just while running MSFS!). My theory and workaround appears to be sound but its a small data set of just a dozen users.
See around this post for my settings change
https://forums.flightsimulator.com/t/sim-crashes-when-zooming-in-at-the-worldmap/607606/175
https://forums.flightsimulator.com/t/sim-crashes-when-zooming-in-at-the-worldmap/607606
Its gotten long to read from the beginning but basically I suspected it is due to having a high speed connection and so my workaround is to limit your LAN card link speed to 100mbps (just while running MSFS!). My theory and workaround appears to be sound but its a small data set of just a dozen users.
See around this post for my settings change
https://forums.flightsimulator.com/t/sim-crashes-when-zooming-in-at-the-worldmap/607606/175