CTD after "low bandwidth" warning

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes

Provide extra information to complete the original description of the issue:

Same situation as already described on three flights now, exactly like in the video shown above. The bandwidth warning pops up, switch to offline mode occurs and the sim crashes even without actions taken on the dialogues.

The issue was encountered with multiplayer and traffic switched to off, Bing data and live weather was on.

If relevant, provide additional screenshots/video:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

A Fault Bucket ID is not provided on the first information after the CTD happened, however one is provided on the second information. The full details are provided as following:

Error
- <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-02-14T09:00:25.1381561Z" /> 
  <EventRecordID>18719</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="14572" ThreadID="18520" /> 
  <Channel>Application</Channel> 
  <Computer>DESKTOP-S03DAIQ</Computer> 
  <Security UserID="S-1-5-21-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX-1001" /> 
  </System>
- <EventData>
  <Data Name="AppName">FlightSimulator.exe</Data> 
  <Data Name="AppVersion">1.30.12.0</Data> 
  <Data Name="AppTimeStamp">63c582fa</Data> 
  <Data Name="ModuleName">FlightSimulator.exe</Data> 
  <Data Name="ModuleVersion">1.30.12.0</Data> 
  <Data Name="ModuleTimeStamp">63c582fa</Data> 
  <Data Name="ExceptionCode">c0000005</Data> 
  <Data Name="FaultingOffset">00000000012bfe43</Data> 
  <Data Name="ProcessId">0x52c0</Data> 
  <Data Name="ProcessCreationTime">0x1d9404bc95d4ddd</Data> 
  <Data Name="AppPath">C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe</Data> 
  <Data Name="ModulePath">C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe</Data> 
  <Data Name="IntegratorReportId">9e65eed9-f66d-4450-9c25-577ff379ca90</Data> 
  <Data Name="PackageFullName" /> 
  <Data Name="PackageRelativeAppId" /> 
  </EventData>
  </Event>
Information 1 - No Fault Bucket ID
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Windows Error Reporting" Guid="{0ead09bd-2157-539a-8d6d-c87f95b64d70}" /> 
  <EventID>1001</EventID> 
  <Version>0</Version> 
  <Level>4</Level> 
  <Task>0</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000000</Keywords> 
  <TimeCreated SystemTime="2023-02-14T09:00:28.0968941Z" /> 
  <EventRecordID>18720</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="14572" ThreadID="18520" /> 
  <Channel>Application</Channel> 
  <Computer>DESKTOP-S03DAIQ</Computer> 
  <Security UserID="S-1-5-21-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX-1001" /> 
  </System>
- <EventData>
  <Data Name="Bucket" /> 
  <Data Name="BucketType">0</Data> 
  <Data Name="EventName">APPCRASH</Data> 
  <Data Name="Response">Nicht verfügbar</Data> 
  <Data Name="CabId">0</Data> 
  <Data Name="P1">FlightSimulator.exe</Data> 
  <Data Name="P2">1.30.12.0</Data> 
  <Data Name="P3">63c582fa</Data> 
  <Data Name="P4">FlightSimulator.exe</Data> 
  <Data Name="P5">1.30.12.0</Data> 
  <Data Name="P6">63c582fa</Data> 
  <Data Name="P7">c0000005</Data> 
  <Data Name="P8">00000000012bfe43</Data> 
  <Data Name="P9" /> 
  <Data Name="P10" /> 
  <Data Name="AttachedFiles">\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ade7b3a7-9fa7-4d1a-b26a-a2485c929c6a.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ca30243d-ef02-4871-a0ac-6fb0f41c2002.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.3d8374b1-d960-48ac-8184-e1c7a2a46ea2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e2764377-b8b8-414e-8bbf-8044c507c5d5.tmp.txt \\?\C:\Users\Gener\AppData\Local\Temp\WER.a7f3c0bb-1d6f-4a99-9f50-0f45ff62ab9c.tmp.appcompat.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e790ecd3-ae3c-466e-9a10-92321d9f3950.tmp.xml</Data> 
  <Data Name="StorePath">\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FlightSimulator._44feed9a787ee6ac6d7a905c133041d21b7980b3_ec018cca_cab_805162fa-08b7-47c2-b825-0c425e3329cb</Data> 
  <Data Name="AnalysisSymbol" /> 
  <Data Name="Rechecking">0</Data> 
  <Data Name="ReportId">9e65eed9-f66d-4450-9c25-577ff379ca90</Data> 
  <Data Name="ReportStatus">4</Data> 
  <Data Name="HashedBucket" /> 
  <Data Name="CabGuid">0</Data> 
  </EventData>
  </Event>
Information 2 - Fault Bucket ID = 1750722401064664326, Typ 4
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Windows Error Reporting" Guid="{0ead09bd-2157-539a-8d6d-c87f95b64d70}" /> 
  <EventID>1001</EventID> 
  <Version>0</Version> 
  <Level>4</Level> 
  <Task>0</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000000</Keywords> 
  <TimeCreated SystemTime="2023-02-14T09:00:32.0119211Z" /> 
  <EventRecordID>18721</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="23216" ThreadID="14192" /> 
  <Channel>Application</Channel> 
  <Computer>DESKTOP-S03DAIQ</Computer> 
  <Security UserID="S-1-5-18" /> 
  </System>
- <EventData>
  <Data Name="Bucket">1750722401064664326</Data> 
  <Data Name="BucketType">4</Data> 
  <Data Name="EventName">APPCRASH</Data> 
  <Data Name="Response">Nicht verfügbar</Data> 
  <Data Name="CabId">0</Data> 
  <Data Name="P1">FlightSimulator.exe</Data> 
  <Data Name="P2">1.30.12.0</Data> 
  <Data Name="P3">63c582fa</Data> 
  <Data Name="P4">FlightSimulator.exe</Data> 
  <Data Name="P5">1.30.12.0</Data> 
  <Data Name="P6">63c582fa</Data> 
  <Data Name="P7">c0000005</Data> 
  <Data Name="P8">00000000012bfe43</Data> 
  <Data Name="P9" /> 
  <Data Name="P10" /> 
  <Data Name="AttachedFiles">\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ade7b3a7-9fa7-4d1a-b26a-a2485c929c6a.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ca30243d-ef02-4871-a0ac-6fb0f41c2002.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.3d8374b1-d960-48ac-8184-e1c7a2a46ea2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e2764377-b8b8-414e-8bbf-8044c507c5d5.tmp.txt \\?\C:\Users\Gener\AppData\Local\Temp\WER.a7f3c0bb-1d6f-4a99-9f50-0f45ff62ab9c.tmp.appcompat.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e790ecd3-ae3c-466e-9a10-92321d9f3950.tmp.xml</Data> 
  <Data Name="StorePath">\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FlightSimulator._44feed9a787ee6ac6d7a905c133041d21b7980b3_ec018cca_805162fa-08b7-47c2-b825-0c425e3329cb</Data> 
  <Data Name="AnalysisSymbol" /> 
  <Data Name="Rechecking">0</Data> 
  <Data Name="ReportId">9e65eed9-f66d-4450-9c25-577ff379ca90</Data> 
  <Data Name="ReportStatus">268435456</Data> 
  <Data Name="HashedBucket">f08f45e075b406dba84bd0bf7fc73d06</Data> 
  <Data Name="CabGuid">0</Data> 
  </EventData>
  </Event>

Additional information:

Recent DxDiag report

DxDiag.txt (111.3 KB)

In sim graphical settings
{Video
	Adapter "NVIDIA GeForce RTX 2080 Ti"
	Monitor 0
	Windowed 1
	FullscreenBorderless 1
	WindowActive 0
	Resolution 3440 1440
	FullScreenResolution 3440 1440
	PosX 0
	PosY 23
	AntiAliasing DLSS
	DLSSMode DLAA
	DLSSG 0
	Reflex ON
FSRMode BALANCED
	PrimaryScaling 1.000000
	SecondaryScaling 1.000000
	SharpenAmount 1.000000
	ReprojectionMode 0
	WorldScalePercentVR 100
	AntiAliasingVR TAA
	DLSSModeVR PERFORMANCE
	DLSSGVR 0
	ReflexVR ON
FSRModeVR PERFORMANCE
	PrimaryScalingVR 0.800000
	SecondaryScalingVR 1.000000
	SharpenAmountVR 1.000000
	VSync 1
	HDR10 0
	Raytracing 0
	PreferD3D12 0
}
{Graphics
	Version 1.1.0
	Preset Custom
	{Texture
		MaxAnisotropy 16
		Quality 0
	}
	{SuperSampling
		SuperSampling 2
	}
	{Terrain
		LoDFactor 2.000000
	}
	{OffscreenTerrainPreCaching
		Enabled 1
		Quality 3
	}
	{ObjectsLoD
		LoDFactor 1.500000
	}
	{Shadows
		MaxSliceCount 4
		Size 8192
		DLightContributionCullingThresholdS0 0.100000
		DLightContributionCullingThresholdS1 0.100000
		DLightContributionCullingThresholdS2 0.100000
		DLightContributionCullingThresholdS3 0.100000
		OmniContributionCullingThreshold 0.000000
	}
	{HeightFieldShadows
		Enabled 1
		Size 2048
	}
	{SSRaytracedShadows
		Enabled 1
		Quality 3
	}
	{Water
		FFTSize 512
	}
	{VolumetricClouds
		Enabled 1
		Quality 3
	}
	{VolumetricLights
		Enabled 1
		Quality 3
	}
	{ReflectionProbe
		Size 256
	}
	{SSR
		Enabled 1
		HalfRes 0
		Quality 3
	}
	{WindShield
		Quality 3
	}
	{SSAO
		Enabled 1
		Quality 3
	}
	{Bloom
		Enabled 1
	}
	{DOF
		Enabled 1
		Quality 3
	}
	{MotionBlur
		Enabled 1
		Quality 3
	}
	{Buildings
		Enabled 1
		Quality 3
	}
	{VegetationLarge
		Enabled 1
		Quality 3
	}
	{VegetationSmall
		Enabled 1
		Quality 3
	}
	{TextureSynthesis
		Quality 3
	}
	{PostProcess
		Enabled 1
		EyeAdaptation 1
		ColorGrading 1
		Sharpen 1
		Fringe 1
		LensDistortion 1
		Dirt 1
		LensFlare 1
		FilmGrain 1
		Vignette 1
		LensBlurMultiplier 1.000000
		FringeMultiplier 1.000000
	}
	{VectorDataTessellation
		Enabled 1
		Quality 2
	}
}

Experiencing the same as OP and other users, since a couple of weeks now. Speedtest is giving me 150Mbps up and 35Mbps down with a ping of 19 ms.

Same issue.

I get these bandwidth warnings all the time despite having a solid 300 Mbps internet connection. They always say ‘reconnected’ within 5 seconds.

I just really, really wish they’d make these pop ups less intrusive. It shouldn’t be locking flight controls requiring you to click a button or disabling online scenery like this; it’s so frustrating, especially if it happens on final and you end up crashing. Just make it a little notification with no interaction.

1 Like

I had the same issue. I removed the ROLLINGCACHE.CCC file in my main MSFS directory (my directory cache) and created it again from scratch in the Rolling Cache Settings menu in the sim. Then I renamed the ROLLINGCACHE.CCC file to MANUALCACHE.CCC, and then created the ROLLINGCACHE.CCC file in the Sim again.
Now, I have two files MANUALCACHE.CCC and ROLLINGCACHE.CCC. It helped me get rid of CTD.

you tell the sim that the former RCache file is now the Manuall.Cache file ? I assume that Manual…ccc will be ignored, at least we not know whether both have same file-format.

In each case, dont set the size of RC to a useless high value. If you assume issues, disable RCache or set a low size, e.g. 2gig. There are topics about problems in special where users set the RCache file size to extrem values, which nobody need.

I’ve had this CTD twice now, I get a low bandwidth warning (despite having a solid and secure internet connection) and bing maps disables itself. Both times when I’ve turned it back on it’s caused a CTD. I was flying PER-LHR and was 30 minutes out as well from the 17 hour flight. What a kick in the teeth!

Faulting application name: FlightSimulator.exe, version: 1.30.12.0, time stamp: 0x63c56d8f
Faulting module name: ntdll.dll, version: 10.0.22621.900, time stamp: 0xa97a9ed6
Exception code: 0xc0000374
Fault offset: 0x000000000010c249
Faulting process ID: 0x0x149C
Faulting application start time: 0x0x1D94BC45BD40CCA
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 1b04bb1f-c86e-4f03-8fbc-dbfa9b1a7a45
Faulting package full name: Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

CTD when enable automatically (why is msfs disabling it at all) disables online service after this pseudo “you are offline” warning …

It su…ck.s soo much…

Fehlerbucket 2285944949597019760, Typ 5

Protokollname: Application
Quelle: Application Error
Datum: 03.03.2023 21:56:31
Ereignis-ID: 1000
Aufgabenkategorie:Anwendungsabsturzereignisse
Ebene: Fehler
Schlüsselwörter:
Beschreibung:
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.30.12.0, Zeitstempel: 0x63c56d8f
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.30.12.0, Zeitstempel: 0x63c56d8f
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000027c8466
ID des fehlerhaften Prozesses: 0x0x9E08
Startzeit der fehlerhaften Anwendung: 0x0x1D94E04654F2A2F
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: 09364969-64e8-41b8-a2fe-8af08d5eb0f9
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
Ereignis-XML:



1000
0
2
100
0
0x8000000000000000

15333


Application


FlightSimulator.exe
1.30.12.0
63c56d8f
FlightSimulator.exe
1.30.12.0
63c56d8f
c0000005
00000000027c8466
0x9e08
0x1d94e04654f2a2f
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
09364969-64e8-41b8-a2fe-8af08d5eb0f9
Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe
App

Stack
[0x0] ntdll!NtWaitForMultipleObjects + 0x14
[0x1] KERNELBASE!WaitForMultipleObjectsEx + 0xe9
[0x2] KERNELBASE!WaitForMultipleObjects + 0xe
[0x3] kernel32!WerpReportFaultInternal + 0x587
[0x4] kernel32!WerpReportFault + 0xbe
[0x5] KERNELBASE!UnhandledExceptionFilter + 0x3db
[0x6] ntdll!RtlUserThreadStart$filt$0 + 0xac
[0x7] ntdll!_C_specific_handler + 0x97
[0x8] ntdll!RtlpExecuteHandlerForException + 0xf
[0x9] ntdll!RtlDispatchException + 0x286
[0xa] ntdll!KiUserExceptionDispatch + 0x2e
[0xb] FlightSimulator!FlightSimGetProcessId + 0x1338526
[0xc] FlightSimulator!FlightSimGetProcessId + 0xea8989
[0xd] FlightSimulator!FlightSimGetProcessId + 0xea83dc
[0xe] FlightSimulator!FlightSimGetProcessId + 0x1013d01
[0xf] FlightSimulator!FlightSimGetProcessId + 0x100d88b
[0x10] FlightSimulator!FlightSimGetProcessId + 0xc1e97a
[0x11] FlightSimulator!FlightSimGetProcessId + 0xc1e576
[0x12] FlightSimulator!FlightSimGetProcessId + 0x129420f
[0x13] FlightSimulator!FlightSimGetProcessId + 0x1294048
[0x14] FlightSimulator!FlightSimGetProcessId + 0x91edb6
[0x15] kernel32!BaseThreadInitThunk + 0x1d
[0x16] ntdll!RtlUserThreadStart + 0x28

I had this once several hours ago and I’m pretty certain it was a genuine server error as opposed to an internet drop out, a rare occurence for me but it can happen. Restarting MSFS and toggling online services brought things back to life after a few seconds delay.

But, if you flew several hours … and getting “offline scenery”, means that the world just looks blurry, i want to switch world data back on … or msfs should stop turning it off by itself. what should never happen is that just turning it back on that msfs CTD… They should fix the reason for the red “offline warning” and not make the warning gone auto switch data offline … thats weired… they should disable this red warning message without switching something offline and make the ctd when i want to switch it on.

Please fix this,it is more importand as any new worldupdates or other stuff!!!

2 Likes

I’ve no idea but if you are in the beta as I am they may well be trying different possible fixes for assorted problems not all of which may work as intended, just one of the risks you sign up for by joining the insider hub … If that’s not the case you can still be sure they are still working behind the scenes on fixes for common problems.

No, i dont join the beta flighting anymore… still on the official release version

Then assuming your internet connection is all well and good sending a detailed bug report is all you can really do. MS/Asobo do prioritise, acting on both telemetry and the information we give them.

Last time i contacted them by zendesk i just got a “ms like “try sfc /scannow” answer… the dump files were not needed^^”

What makes me mad about this bug is just the “persistance of the red box” they introduced with SU11 (the pseudo offline messages were there since day 1)… and after the community complained about the “red box” they “pseudo-fixed” it by disabling online data… they should fix the causes for the red box rather than the symptons (the online services)… its a insidious maneuver turn the online data off for “let the red box magically disapear” and let crash MSFS if the users turns online services back on… thats the point

Zendesk aren’t doing the fixes though and standard replies are par for the course almost everywhere, I certainly don’t like them either however MSFS has so many users it would be impossible for them to act on individual complaints. But they do see the numbers and the crashcodes and for common problems they are as good if not better than any dump file could be (although for obscure or trivial complaints things will be different. I hasten to say it but reckon many of these would stem from the user anyway). Unfortunately people are not very reliable when it comes to testing as instructed and even less so when it comes to conveying results so there should be tools to do this but with a moving target like MSFS it would likely need a whole new bespoke program like no other app, safe mode is about all we can expect. Of course MS have all the tools they need in house but we mortals will never get to use them … which IMO is probably just as well or no doubt we’d all have no hair left.

And again today

Fehlerbucket 2285944949597019760, Typ 5
Ereignisname: MoAppCrash
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.30.12.0
P4: 63c56d8f
P5: FlightSimulator.exe
P6: 1.30.12.0
P7: 63c56d8f
P8: c0000005
P9: 00000000027c8466
P10:

And again your f****** warning … disabled online services … try to enable it… ctd

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.30.12.0, Zeitstempel: 0x63c56d8f
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.22621.885, Zeitstempel: 0xe3dee9a7
Ausnahmecode: 0xc0000374
Fehleroffset: 0x000000000010c249
ID des fehlerhaften Prozesses: 0x0x3974
Startzeit der fehlerhaften Anwendung: 0x0x1D952C93C69B38A

Fehlerbucket 1927164177951927597, Typ 5
Ereignisname: MoAppCrash
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.30.12.0
P4: 63c56d8f
P5: StackHash_7aa0
P6: 10.0.22621.885
P7: e3dee9a7
P8: c0000374
P9: PCH_09_FROM_ntdll+0x000000000009F954

And, same procedure as multiple times a day … red warning box, msfs turns online bing data off, i have to turn it back on to get fly flight finished (but it doesnt work either) and CTD … so much crash dumps now i need more hdd space … it sucks most

EDIT: If was thinking about it… the warning and that msfs sets itself offline happend while running msfs for couple of hours… it happend always on the 3rd, or 4th leg… today it was on the 3rd Leg, so after 3 flights and a msfs running time around 4 hours…

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.30.12.0, Zeitstempel: 0x63c56d8f
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.30.12.0, Zeitstempel: 0x63c56d8f
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000027c8466
ID des fehlerhaften Prozesses: 0x0x1AA4
Startzeit der fehlerhaften Anwendung: 0x0x1D9532EE0C01F19
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: 241d0b46-c34a-4f8e-ac00-198259036e64
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

Fehlerbucket 2285944949597019760, Typ 5
Ereignisname: MoAppCrash
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: Microsoft.FlightSimulator_1.30.12.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.30.12.0
P4: 63c56d8f
P5: FlightSimulator.exe
P6: 1.30.12.0
P7: 63c56d8f
P8: c0000005
P9: 00000000027c8466
P10:

1 Like

No bandwidth warnings happening now.

Particular crash instance closed as fixed in Sim Update 13: Release Notes - Sim Update 13 [1.34.16.0] Available Now