CTD

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
 
I'm tired. :dizzy:

(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.16.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__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-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.16.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.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: e08f98ef-ada7-431c-976d-c2403a25900c
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-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.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
<Data Name="ModulePath">C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.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.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 53ea0ef3-a0a0-4225-aa21-9b2a3f75d553
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-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.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
<Data Name="ModulePath">C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.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
 
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
 
Alright, after reading post over at the main MSFS bug report forum until I was blue in the face, this seemed to work for me (there were pages of discussion on how to fix it.


Screenshot (36) by Donald McCann, on Flickr


One person reported to go to your Apps and find the Xbox app icon, right click on it, go down to app settings and select repair.

Just did a flight of 2 hrs duration in the default "Dodge" Caravan covering 300 + NM and no CTD.

I can only assume that piling all of those Microsoft updates into Windows 11 must have busted something.

We'll see how it goes over the next couple of days.

- Don
 
I think you're (almost) there Don. Especially with Win11, keeping the rig up to date is crucial for MSFS.

Keep us posted!

Priller
 
Nope, Nope, Nope!

It was going so well, did another flight for about an hour in the Cirrus SR22 ===>>>> CTD ====>>>> now I'm flying in Safe Mode in the Caravan and pull up to the parking spot put on the brake =====>>>> CTD

Turn off 'puter, restart MSFS in Safe Mode.... less than 5 NM after take-off in the Caravan ====>>>> CDT. Look at Event viewer. The first 3 logs are (2) minutes apart, I don't know why.



Log Name: Microsoft-Windows-Kernel-EventTracing/AdminSource: Microsoft-Windows-Kernel-EventTracing
Date: 10/27/2023 5:24:31 PM
Event ID: 3
Task Category: Session
Level: Error
Keywords: Session
User: SYSTEM
Computer: Flame
Description:
Session "NVIDIA-NVTOPPS-NVLOGS" stopped due to the following error: 0xC0000188
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}" />
<EventID>3</EventID>
<Version>1</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>14</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2023-10-27T22:24:31.0703856Z" />
<EventRecordID>176</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="16068" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>Flame</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionName">NVIDIA-NVTOPPS-NVLOGS</Data>
<Data Name="FileName">C:\ProgramData\NVIDIA Corporation\nvtopps\nvlog.etl</Data>
<Data Name="ErrorCode">3221225864</Data>
<Data Name="LoggingMode">8388609</Data>
<Data Name="FailureReason">0</Data>
</EventData>
</Event>


Log Name: System
Source: Service Control Manager
Date: 10/27/2023 5:26:10 PM
Event ID: 7023
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Flame
Description:
The NVIDIA LocalSystem Container service terminated with the following error:
A generic command executable returned a result that indicates failure.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7023</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2023-10-27T22:26:10.3224723Z" />
<EventRecordID>2843</EventRecordID>
<Correlation />
<Execution ProcessID="956" ThreadID="13620" />
<Channel>System</Channel>
<Computer>Flame</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">NVIDIA LocalSystem Container</Data>
<Data Name="param2">%%14109</Data>
<Binary>4E00760043006F006E007400610069006E00650072004C006F00630061006C00530079007300740065006D000000</Binary>
</EventData>
</Event>



Log Name: System
Source: Service Control Manager
Date: 10/27/2023 5:26:10 PM
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Flame
Description:
The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7031</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2023-10-27T22:26:10.3224723Z" />
<EventRecordID>2844</EventRecordID>
<Correlation />
<Execution ProcessID="956" ThreadID="1488" />
<Channel>System</Channel>
<Computer>Flame</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">NVIDIA LocalSystem Container</Data>
<Data Name="param2">1</Data>
<Data Name="param3">6000</Data>
<Data Name="param4">1</Data>
<Data Name="param5">Restart the service</Data>
<Binary>4E00760043006F006E007400610069006E00650072004C006F00630061006C00530079007300740065006D000000</Binary>
</EventData>
</Event>


OK, OK ====>>> d/l newest Nvidia driver 545.92



Log Name: Application
Source: Application Error
Date: 10/27/2023 5:55:17 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: 0x000000000240a38a
Faulting process id: 0x0x103C
Faulting application start time: 0x0x1DA0925FAD1F07B
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 5d9069cf-3ebb-4804-95b5-38dad62441f5
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-27T22:55:17.4416719Z" />
<EventRecordID>1303</EventRecordID>
<Correlation />
<Execution ProcessID="1636" ThreadID="9240" />
<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">000000000240a38a</Data>
<Data Name="ProcessId">0x103c</Data>
<Data Name="ProcessCreationTime">0x1da0925fad1f07b</Data>
<Data Name="AppPath">C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
<Data Name="ModulePath">C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
<Data Name="IntegratorReportId">5d9069cf-3ebb-4804-95b5-38dad62441f5</Data>
<Data Name="PackageFullName">Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe</Data>
<Data Name="PackageRelativeAppId">App</Data>
</EventData>
</Event>




Reboot PC, restart MSFS in Safe Mode, another CDT ..... in Safe Mode of all things.





Log Name: Application
Source: Application Error
Date: 10/27/2023 6:30:14 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: CoherentUIGT.dll, version: 2.9.5.0, time stamp: 0x63a184e2
Exception code: 0xc0000005
Fault offset: 0x00000000000c9f3a
Faulting process id: 0x0x2588
Faulting application start time: 0x0x1DA0929325BC629
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\CoherentUIGT.dll
Report Id: 373a9120-b07c-4f73-aa44-54e7e0ee227a
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-27T23:30:14.6417293Z" />
<EventRecordID>1306</EventRecordID>
<Correlation />
<Execution ProcessID="13536" ThreadID="3152" />
<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">CoherentUIGT.dll</Data>
<Data Name="ModuleVersion">2.9.5.0</Data>
<Data Name="ModuleTimeStamp">63a184e2</Data>
<Data Name="ExceptionCode">c0000005</Data>
<Data Name="FaultingOffset">00000000000c9f3a</Data>
<Data Name="ProcessId">0x2588</Data>
<Data Name="ProcessCreationTime">0x1da0929325bc629</Data>
<Data Name="AppPath">C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
<Data Name="ModulePath">C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\CoherentUIGT.dll</Data>
<Data Name="IntegratorReportId">373a9120-b07c-4f73-aa44-54e7e0ee227a</Data>
<Data Name="PackageFullName">Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe</Data>
<Data Name="PackageRelativeAppId">App</Data>
</EventData>
</Event>



Now, the above log is new: Faulting module name: CoherentUIGT.dll, version: 2.9.5.0,

I'm done for the evening.

- Don
 
XMP is off.

Just completed 750+ NM flight in Cirrus SR22, 4 hrs. 58 minutes duration.

NO CTD

We'll see how the weekend goes, thanks Priller! :applause:

- Don
 
After reading all the trouble you've been having, Don, I was worried about what would happen with my new rig. The 1st flight, in the Savage Cub, from Brown Field KSDM in San Diego, Ca. to Mojave Regional KMHV, 160nm, 1:59:xx. My flight lasted 38+ min and then froze. Locked up. Needed ctrl+alt+Del to bring up task master to shut off MSFS. Then, I read about throttleing my internet. I noticed that my lockup occured right at the point where my scenery went from cached to needing renewed/downloaded. After checking my internet speed, fast, 800-900mbs, I set my modem to 100mbs as instructed, rebooted computer, took my memory off of the XMP, rebooted again, and went for a flight. Changed to the default Cessna 172 with Garmin1000, and flew the same flightplan. 2 hours, no problem. So, hopeing for the best.(Aren't we all?)
 
modelr said:
After reading all the trouble you've been having, Don, I was worried about what would happen with my new rig. The 1st flight, in the Savage Cub, from Brown Field KSDM in San Diego, Ca. to Mojave Regional KMHV, 160nm, 1:59:xx. My flight lasted 38+ min and then froze. Locked up. Needed ctrl+alt+Del to bring up task master to shut off MSFS. Then, I read about throttleing my internet. I noticed that my lockup occured right at the point where my scenery went from cached to needing renewed/downloaded. After checking my internet speed, fast, 800-900mbs, I set my modem to 100mbs as instructed, rebooted computer, took my memory off of the XMP, rebooted again, and went for a flight. Changed to the default Cessna 172 with Garmin1000, and flew the same flightplan. 2 hours, no problem. So, hopeing for the best.(Aren't we all?)
Click to expand...


Hi , if you running 4k with High settings in MSFS it´s no wonder it freezes now and then , try 1440p instead ~ Desktop Screenshot 2023.10.07 - 06.00.54.95.png



HB
 
modelr said:
After reading all the trouble you've been having, Don, I was worried about what would happen with my new rig. The 1st flight, in the Savage Cub, from Brown Field KSDM in San Diego, Ca. to Mojave Regional KMHV, 160nm, 1:59:xx. My flight lasted 38+ min and then froze. Locked up. Needed ctrl+alt+Del to bring up task master to shut off MSFS. Then, I read about throttleing my internet. I noticed that my lockup occured right at the point where my scenery went from cached to needing renewed/downloaded. After checking my internet speed, fast, 800-900mbs, I set my modem to 100mbs as instructed, rebooted computer, took my memory off of the XMP, rebooted again, and went for a flight. Changed to the default Cessna 172 with Garmin1000, and flew the same flightplan. 2 hours, no problem. So, hopeing for the best.(Aren't we all?)
Click to expand...


This chart can be helpful . 318507479_185020384109732_2902818957523029773_n.jpg
 
@ Brytskiva,

That is an interesting chart, thanks for posting it.

My monitor's maximum resolution is 1440 (2560x1440) so that is what I sim with.

I had another 6+ hour, 1400+ NM flight in the Cirrus SR22 from UK2000's KARR, Auroa, Illinois and a layover in KANW, Ainsworth, Nebraska for fuel, then onto KJAC. Jackson Hole Wyoming.

NO CTD :wavey:

-Don
 
You must log in or register to reply here.
Back
Top