CTD after "low bandwidth" warning

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