There is mass CTD’s on Xbox aswell (just a reminder the console is made by Microsoft, game made by Microsoft running on system made by Microsoft) they clearly haven’t figured out anything about the issue still after almost a year it’s just shocking.
1 Like
Sorry to say, but an 850W power supply should have been enough. If you didn’t do any overclocking that is. But a 1200W psu will give you way more headroom. Also be sure to plug all the sata power connectors on your GPU with their own individual cable and don’t use those second headers. Using all separate cables should provide a cleaner power delivery and stability 
Sshh, we can’t speak of that. How’s that PSU of yours though? Strong enough?
Thanks for these tips, duly noted!
1 Like
This makes no sense.
Contrary to the PC, the hardware is fixed and therefore, a crash is close to the simplest thing to fix as they can track it with the debugger and BAM!, there you have the culprit.
I bet it’s the Renoir library (<-- joke)
I meant that users with installing the VR drivers/software reporting suddenly issues in 2D too.
How can there mass CTD’s on xBox…the game hasn’t been released yet?
Getting so tired of these all the time, it makes it impossible to enjoy the simulation. I have a great rig and no addons, CTD pretty much every time I use the game now.
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60c0b1e3
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60c0b1e3
Exception code: 0xc0000005
Fault offset: 0x0000000003dfd210
Faulting process id: 0x14c
Faulting application start time: 0x01d782878b1cd6fd
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: a35b82ac-5d4a-4675-bd4f-430caa9944b3
Faulting package full name: Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
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?
2 Likes
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?
1 Like
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.
3 Likes
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.