CTD

[Aircanuck]

Have experienced at least 3 Crash to Desk Top since the last last update, typically happens after about 1.5 hrs worth of flying. Recently updated the drivers from Nividia. Anybody have the same concerns ?

[FlameOut]

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

[Aircanuck]

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

"No warning" No explanation" ... Exactly !! Gosh I feel better, kinda 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 !!

[Priller]

"No warning" No explanation" ... Exactly !! Gosh I feel better, kinda 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 !!

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

[Aircanuck]

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.

[Tom Clayton]

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]

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

[Aircanuck]

Posted screen shot as per Priller, hope it sheds some light on the problem I'm experiencing.

[Aircanuck]

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

[Aircanuck]

Spoke to soon, back to square one !?@#$&

[Priller]

Posted screen shot as per Priller, hope it sheds some light on the problem I'm experiencing.

I'm afraid that isn't the one. It really has to be the CTD, not the shutdown after that.

Priller

[vipgroup]

Well, not quite CTDs in my case, but immediate blue screen of death when flying MSFS for more than ten minutes or so! Then unable to even use computer for a day..... I think this is a computer problem for me... Off to the repair shop maybe?

[Aircanuck]

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 !

[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]

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

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

[Aircanuck]

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

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.

[udidwht]

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.

[FlameOut]

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.1 6.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__8wekyb3d8 bbwe
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.1 6.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

[udidwht]

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.1 6.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__8wekyb3d8 bbwe
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.1 6.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".

[boez]

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...orldmap/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...map/607606/175

[FlameOut]

Ok, did as instructed.

If you see my reply (post # 2) up above, how could things get screwed up so soon? I'm on a brand new install of Windows 11 onto a new 4TB NVMe drive with a fresh install of MSFS!

Anyways, I ran the command line: sfc /scannow 1st. thing, here is the result ======>>>>

Screenshot (20) by Donald McCann, on Flickr

As you can see, it did not find any errors and I was also over at boez's provided links to see about turning down the internet speed, (I have 350MB/s).

I ran all of the command line instructions, got a couple of ERROR 87's where I had typed something incorrectly or left out that important "space". Here is the result ====>>>>

Screenshot (23) by Donald McCann, on Flickr

I also located that log file that it referenced @ C:\Windows\Logs\CBS\CBS.log good grief 137,020 lines of stuff. Who wants to read all of that!

Screenshot (25) by Donald McCann, on Flickr

Now why did sfc /scannow find errors at this point? Turned off 'puter and restarted.

We'll see if this will fix these random CTD.

- Thanks, Don

[FlameOut]

I forgot to post this screenie, I was also looking up what my specific application error code was all about.

Screenshot (22) by Donald McCann, on Flickr

- Don

[FlameOut]

I'm tired.

(3) CTD since last post, I went to Microsoft Store and all Apps in my Library were updated on these dates:

10-18-2023 ...................................... The day of my new MSFS installation

10-20-2033

10-26-2023 ...................................... XBox Game Bar

Here is application error # 1

Log Name: Application
Source: Application Error
Date: 10/26/2023 9:28:43 AM
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: 0x0x28A4
Faulting application start time: 0x0x1DA081249469839
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.1 6.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 831e6e63-ddb4-4648-940a-417c92b6da2f
Faulting package full name: Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8 bbwe
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-26T14:28:43.1047889Z" />
<EventRecordID>900</EventRecordID>
<Correlation />
<Execution ProcessID="13176" ThreadID="11440" />
<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">0x28a4</Data>
<Data Name="ProcessCreationTime">0x1da081249469839</Data>
<Data Name="AppPath">C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.1 6.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
<Data Name="ModulePath">C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data Name="IntegratorReportId">831e6e63-ddb4-4648-940a-417c92b6da2f</Data>
<Data Name="PackageFullName">Microsoft.FlightSimulator_1 .34.16.0_x64__8wekyb3d8bbwe</Data>
<Data Name="PackageRelativeAppId">App</Data>
</EventData>
</Event>

================================================== ============================================


Here is application error # 2


Log Name: Application
Source: Application Error
Date: 10/26/2023 10:49:50 AM
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: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000002293a22
Faulting process id: 0x0x14E4
Faulting application start time: 0x0x1DA081E80FADD95
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.1 6.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.1 6.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: e08f98ef-ada7-431c-976d-c2403a25900c
Faulting package full name: Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8 bbwe
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-26T15:49:50.4747579Z" />
<EventRecordID>952</EventRecordID>
<Correlation />
<Execution ProcessID="13888" ThreadID="5252" />
<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">FlightSimulator.exe</Data>
<Data Name="ModuleVersion">1.34.16.0</Data>
<Data Name="ModuleTimeStamp">00000000</Data>
<Data Name="ExceptionCode">c0000005</Data>
<Data Name="FaultingOffset">0000000002293a22</Data>
<Data Name="ProcessId">0x14e4</Data>
<Data Name="ProcessCreationTime">0x1da081e80fadd95</Data>
<Data Name="AppPath">C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.1 6.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
<Data Name="ModulePath">C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.1 6.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
<Data Name="IntegratorReportId">e08f98ef-ada7-431c-976d-c2403a25900c</Data>
<Data Name="PackageFullName">Microsoft.FlightSimulator_1 .34.16.0_x64__8wekyb3d8bbwe</Data>
<Data Name="PackageRelativeAppId">App</Data>
</EventData>
</Event>



================================================== ===========================

Here is application error # 3

Log Name: Application
Source: Application Error
Date: 10/26/2023 1:07:27 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: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000240a378
Faulting process id: 0x0x1818
Faulting application start time: 0x0x1DA08308BC49B71
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.1 6.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.1 6.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 53ea0ef3-a0a0-4225-aa21-9b2a3f75d553
Faulting package full name: Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8 bbwe
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-26T18:07:27.3710036Z" />
<EventRecordID>969</EventRecordID>
<Correlation />
<Execution ProcessID="14248" ThreadID="13176" />
<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">FlightSimulator.exe</Data>
<Data Name="ModuleVersion">1.34.16.0</Data>
<Data Name="ModuleTimeStamp">00000000</Data>
<Data Name="ExceptionCode">c0000005</Data>
<Data Name="FaultingOffset">000000000240a378</Data>
<Data Name="ProcessId">0x1818</Data>
<Data Name="ProcessCreationTime">0x1da08308bc49b71</Data>
<Data Name="AppPath">C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.1 6.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
<Data Name="ModulePath">C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.1 6.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
<Data Name="IntegratorReportId">53ea0ef3-a0a0-4225-aa21-9b2a3f75d553</Data>
<Data Name="PackageFullName">Microsoft.FlightSimulator_1 .34.16.0_x64__8wekyb3d8bbwe</Data>
<Data Name="PackageRelativeAppId">App</Data>
</EventData>
</Event>


- Don

[tiger1962]

There's a new driver out today from nVidia, maybe that'll help?

[Priller]

Don,

Is your windows up to date?

Moreover, check your ram speeds. ntdll.dll errors frequently point to memory speed errors. When I installed my current rig, I had similar issues. After a lot of frustration and research, it became clear that the random crashes I had were due to the fact that by default, my mobo has the RAM speeds set at maximum. Setting them at auto did the trick.

But first update your windows and see what gives.

Cheers,

Priller