Early access, no one seems to talk about the Xbox CTDs and the influencers can’t really say anything bad as they were invited by MS. Maybe it gets patched today, who knows.
Early access streams.
and out of topic here
Who else is hoping SU5 magically fixes all CTDs?
Secondary follow up question:
Who else is reinstalling XP11 just to get flying dependably again?
please… let us speak about EXISTING CTDs and not oracle about the future. Its not the topic for that ( also not XPlane 11)
If there are any CTD fixes delivered in SU5 they would only be fixes for the CTDs reported through ZenDesk. I haven’t submitted any tickets for my recent CTDs so I’m not expecting much. I always hope for PFM though.
But I thought Xbox was just another PC with the same sim code running?
that’s more or less true… but the msfs xbox release will come today for fist time and no users can currently have an issue with that. Later on we should also better not mix the issues with a “real” PC , with that of a xbox.
( remember: there are some users in forum which use the amount of posts in this thread here as a proof how worst msfs is. Thus we should realy stay strictly at topic ).
At the end of the day the error you are getting is pertinent to your set up be it hardware, software or even just an unfortunate compatability issue and yes there will be others with similar problems but if it’s not fixable to Asobo then what can they do? Without stating the obvious VCRUNTIME140.dll is Microsoft software rather than Asobo so maybe that’s where you should be directing your ire. For sure Asobo will get higher priority but if it’s a Windows issue they still have to put in a ticket just like anyone else.
With all the respect, I’m not sure you understand the VCRUNTIME140 issue properly.
The exception is occuring there, in memcpy, because the caller is sending a null pointer as the destination. It has nothing to do with Microsoft as any piece of code sending a null destination pointer to this function is going to generate an access violation.
According to many forum posts, and especially thos who took the time to get a decent crash dump, a significant amount of crashes are generated by the Renoir library - accounting for more than 90% of my CTDs. Again, this is a 3rd party piece of code used by Asobo.
I am sorry, but in 2021 (and even decades before), exception handling has been available to developers to prevent application crashes. Clearly, this library does not, in the offending area:
- Make sure it does not send a null pointer to memcpy.
- Protects this code section with exception handling.
As usual, without the source code, it’s hard to provide a proper analysis.
Anyhow, this remains an Asobo issue, either by asking its provider to fix their sh1t or by getting rid of this library.
I still hope this discussion will become obsolete after SU5.
Yes that just about sums it up. It is obviously an essential process or they would get rid to be sure but how come it only affects some users? Surely there must be a common denominator for those that are struggling?
Well i really do, and i already reinstalled Xp11 although i really would prefer msfs due to the better scenery and interface. But i can’t get it to work or even install anymore.
Well said. Exactly the same here. Everything was perfectly fine for the first 4 months or so, and since then it’s constant CTD.
and have you in meanwhile tried to disable your overclocking setting ?
: VCRUNTIME140.dll Error - #219 by kityatyi
Overclocking was present on release day.
Same here, I never had C2D and now it always crashes. I fixed and reset the app. After installing the last driver it lauch but now, it won’t. I would start it to update, maybe the patch is in the update…
There is something changed somewere in windows. Maybe an update. The xbox bar crashed too, and after fix and reset, it launch but no luck with MFS.
“now” means these:
?
Just wait a moment and try to let install the update again.
EDIT
PS: I mean the whole topic, not in special these post. But @sneaky74 like it, so I let the link stay
I tried on Sunday and it won’t launch. After nivida driver update it worked bur I lauched it one time. I don’t know if the issue was resolved.
You think, it crashes now because of the MS server overload ?
ah… Sunday… then these was an older issue.
To be sure whether you now run into the update-issue, which some users affects:
Can please you open the windows event viewer and searching the exact logged error message ?
That would be my guess yes.
There was a potential work around in the previous post’s link which involved starting MSFS from the Xbox Store app and waiting for the update screen to find the download - if it reports needing 22.92 GiB additional disk space instead of 0 GiB then you should be good to go.
Thanks for your help.
I have this :
Nom de l’application défaillante FlightSimulator.exe, version : 0.0.0.0, horodatage : 0x00000000
Nom du module défaillant : AudioDevProps2.dll, version : 2.6.4.0, horodatage : 0x60b0a9e5
Code d’exception : 0xc0000005
Décalage d’erreur : 0x000000000001ba66
ID du processus défaillant : 0x3b5c
Heure de début de l’application défaillante : 0x01d7830c132d209c
Chemin d’accès de l’application défaillante : C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Chemin d’accès du module défaillant: C:\ProgramData\A-Volute\A-Volute.SonicStudio3\Modules\ScheduledModules\x64\AudioDevProps2.dll
ID de rapport : c09f2f29-63e0-48ef-8635-6c1ccb8a8dda
Nom complet du package défaillant : Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe
ID de l’application relative au package défaillant : App
Audio driver issue ?
@Sneaky74 : I have Xbox game bar and “Compagnon de la console Xbox”. No Xbox Store. I have the DVD version.