33 minutes ago, Alpine Scenery said:

True, but the errors seem to happen to me regardless, doesn't matter. They've even happened at my own airports, or when I'm testing a clean BLANK file build (as in running a blank package in Non-Dev mode), so even outside of development of a very remote airport in the middle of nowhere. So I know it's not really location specific for me, but it might be for some, but for me I kind of ruled that out.

Plus I have been flying the same places over and over the past 2 weeks, heck I don't even think I've left Colorado or Utah in 3 weeks except maybe twice.

There apparently was some kind of issue with corrupted streaming data coming from the MS servers around the weekend of 20 Aug that was causing CTDs for a large number of users.  If you were flying during that period, it might not be a bad idea to delete and re-create your cached scenery file in case some of that bad data got cached and is being re-loaded.

8 minutes ago, Bob Scott said:

There apparently was some kind of issue with corrupted streaming data coming from the MS servers around the weekend of 20 Aug that was causing CTDs for a large number of users.  If you were flying during that period, it might not be a bad idea to delete and re-create your cached scenery file in case some of that bad data got cached and is being re-loaded.

I haven't had bad issues in a few days, but I have reinstalled Windows twice and reinstalled MSFS three times, replaced my hardware twice, everything except the motherboard. Only reason I didn't replace the motherboard, was I didn't really feel like pulling everything out of the case. I'm just replacing the AMD next to reduce the TDR issues, it's known that Nvidia has better Timeout handling than AMD does, that's just a sad truth. Though the difference isn't huge, even that last 15% difference may help immensely.

I've already eliminated everything, it's MSFS, it's not peoples hardware, but it's specific malloc issues that the MSFS error handling code cannot take care of. Some hardware configs will never trigger those TDR issues, and will never experience it, for varying reasons. It's the same reason that some PC's have issues in Quixel and Substance Painter and nothing else (especially when using AMD's), it is interop. Interop issues are rare, but they still exist unfortunately, and MSFS just happens to not have coded around them correctly.

The reason some people think it's peoples hardware is because they got lucky in the chance game of interop, and because sometimes it is peoples hardware config, but there are too many variables in interop, and a leaky pointer is a leaky pointer is a leaky pointer. We all know MSFS has a history of leaky pointers.
 

Edited September 1, 20223 yr by Alpine Scenery

I wasn't addressing your specific issue w/r/t my overclocking comments, but rather the more-and-more commonly thrown-out internet folklore that MSFS is somehow and quite mysteriously more stressful on a PC than any other 3D game, so much so that hardware optimizations that work with everything else must be abandoned to appease the performance demons dwelling within the MSFS folder.

 

3 minutes ago, Bob Scott said:

I wasn't addressing your specific issue, but rather the more-and-more commonly thrown-out internet folklore that MSFS is somehow and quite mysteriously more stressful on a PC than any other 3D game, so much so that hardware optimizations that work with everything else must be abandoned to appease the performance demons inhabiting your MSFS installation.

Right, but I am just saying for others, that I wasn't sure, but now I am that MSFS has some pretty weird bugs that only certain configs will trigger. MSFS can be very stressing with certain settings, but there are quite a few other games now that can match it or get close. The thing is I have an FPS limiter, so I don't really stress it out that much at all.

My PC is fine for now, but like I said it could be as simple as removing drives or reducing USB devices, but it's annoying that I'd have to do that. That's why I'll try the NVIDIA first.
 

Edited September 1, 20223 yr by Alpine Scenery

So new day, new issues with MSFS 🙂

On repeated tries the sim would get stuck on flight loading. If I just waited, eventually it would CTD without a message. I found this in the event log: 

Faulting application name: FlightSimulator.exe, version: 1.27.17.0, time stamp: 0x00000000
Faulting module name: VCRUNTIME140.dll, version: 14.30.30704.0, time stamp: 0x615a9215
Exception code: 0xc0000005
Fault offset: 0x00000000000015f0
Faulting process ID: 0x0x15CC
Faulting application start time: 0x0x1D8BEC7DD9072ED
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.30704.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll
Report ID: cac538a6-d677-40c2-85f3-e963a23e6307
Faulting package full name: Microsoft.FlightSimulator_1.27.17.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

I've had these before, and I can usually resolve the "stuck on flight loading" issue by:

1. Log out of MS store
2. Log out of Xbox
3. Repair then reset MSFS
4. Reboot

But not today. So I emptied my community folder and turned off all online services. Got the flight to load. Then I was able to load with online services on. Then I put the Kodiak in the community folder - and flight still loaded. 

I'm in the SU10 beta. Couldn't see any recent posts in the official beta forum on this type of problem. And I didn't change anything from the last flight yesterday to the first flight today. So I have no idea how to explain this. 

42 minutes ago, Cpt_Piett said:

So new day, new issues with MSFS 🙂

On repeated tries the sim would get stuck on flight loading. If I just waited, eventually it would CTD without a message. I found this in the event log: 

Faulting application name: FlightSimulator.exe, version: 1.27.17.0, time stamp: 0x00000000
Faulting module name: VCRUNTIME140.dll, version: 14.30.30704.0, time stamp: 0x615a9215
Exception code: 0xc0000005
Fault offset: 0x00000000000015f0
Faulting process ID: 0x0x15CC
Faulting application start time: 0x0x1D8BEC7DD9072ED
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.30704.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll
Report ID: cac538a6-d677-40c2-85f3-e963a23e6307
Faulting package full name: Microsoft.FlightSimulator_1.27.17.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

I've had these before, and I can usually resolve the "stuck on flight loading" issue by:

1. Log out of MS store
2. Log out of Xbox
3. Repair then reset MSFS
4. Reboot

But not today. So I emptied my community folder and turned off all online services. Got the flight to load. Then I was able to load with online services on. Then I put the Kodiak in the community folder - and flight still loaded. 

I'm in the SU10 beta. Couldn't see any recent posts in the official beta forum on this type of problem. And I didn't change anything from the last flight yesterday to the first flight today. So I have no idea how to explain this. 

Pay attention to the faulting module Faulting module name: VCRUNTIME140.dll, This the Visual C++ redistribution crashing. So my first advice to you would be to reinstall it. 

12 minutes ago, fogboundturtle said:

Pay attention to the faulting module Faulting module name: VCRUNTIME140.dll, This the Visual C++ redistribution crashing. So my first advice to you would be to reinstall it. 

Thanks, I'll give this a try. 

EDIT: I've got a lot of C++ packages installed. Not sure if I'll go ahead and reinstall all of them. And 14.30.30704.0 doesn't even show up in my installed apps...

Edited September 2, 20223 yr by Cpt_Piett

Not by any stretch of the imaginations suggesting abandoning MSFS for any of the previous sims, it's still WAY too good to contemplate that.

But . . . lots of witchcraft and OTT tips being banded about on this thread amongst others, and constant mention of the fact that there are so many variables on an MSFS system with all its addons etc. But the truth is that I used to have just as many addons and variables on both P3D and XP (still do, even though I don't fly them much now) and yet I certainly never had the sort of random and annoying issues that I've been getting the last couple of months with MSFS.

Yes, you could argue that sims have moved on since those other beasts, and that it's all more complex now. But that's both true and false. Definitely feels like a lot of new stuff in MSFS, no doubt, and I'm sure that is a major headache to get right. Also feels though like there's a lot of old stuff still embedded in FSX, going way back to who knows when, and that can't be helping matters either.

All I can say with certainty is that my MSFS system was running fine until SU9 landed. There had been irritations like the gradual reduction in draw distance over the past year, and the plain ugly Italy WU with all its issues, but it was essentially stable. Since then though it has apparently random bursts of running like a three legged dog, plus giving me several CTDs and lots of "insufficient bandwidth" messages.

But some of the steps being suggested as definite cures and the like in here strike me as a teensy bit bizarre. I'm certainly not going to be faffing around with my (previously working fine, thank you) system, as I remain convinced that this is either a core bug in MSFS or a server issue. The fact that SU10 keeps getting delayed suggests to me that they know something is up and are working on it but not necessarily getting it done successfully.

So I'll wait, and just use the sim without any great expectations of a trouble free session. If they do manage to deliver all the stuff thats being suggested, it will have been worth the wait.

Here's hoping.

What visual installer do I need? Me, I stayed on the 2015 2017 2019 and 2022
https://docs.microsoft.com/fr-fr/cpp/windows/latest-supported-vc-redist?view=msvc-170

I got it installed. And I believe that Altitude (IVAO) also installs another one.

Well I decided not to reinstall all my C++ redistributions. I managed to load into (and finish) a couple of flights today. The random nature of all these bugs and glitches though… super frustrating.

My problems got solved after i removed the RX6800XT and installed a 3080Ti. I have been flying non-stop for hours and hours and it just goes.

Something was wrong with that video card / drivers / whatever. Those random black screens always left me thinking and that was definitely it. As a bonus, the 3080Ti offers noticeably more performance for less noise (and more power usage, ugh!).

Happy camper now.

3 minutes ago, Nuno Pinto said:

My problems got solved after i removed the RX6800XT and installed a 3080Ti. I have been flying non-stop for hours and hours and it just goes.

Something was wrong with that video card / drivers / whatever. Those random black screens always left me thinking and that was definitely it. As a bonus, the 3080Ti offers noticeably more performance for less noise (and more power usage, ugh!).

Happy camper now.

I bet it's the AMD drivers. There is a long history of AMD GPU and Flight sim issue. I am glad your new GPU it working to your liking

1 hour ago, Cpt_Piett said:

Well I decided not to reinstall all my C++ redistributions. I managed to load into (and finish) a couple of flights today. The random nature of all these bugs and glitches though… super frustrating.

Hi Cpt_Piett,

I have been following your CTD odyssey with interest for the past few days (avsim & fs forums), because I had the same problems with SU9. Most recently also 0xc0000005 in conjunction with (a) VCRUNTIME140.dll or (b) nvlddmkm. Completely random.

After the big fuss of last weekend, flying was possible again, but I continued to have big problems editing airports with the SDK. It was enough to select an object after opening a project, this led to immediate CTD, sometimes in combination with a short sound-quirk, which other users also described.

So I followed some hints from other users:

Updated all VCRuntimes, emphasis on all. With success, finally the VCRUNTIME error was gone but I still had instant CTD while working with the editor.

Previously I had experimented with slightly older NVD Game Ready drivers, without success.
Yesterday I read - in this thread I think - that someone had success with a Studio driver from June, which he thought was more stable.

So yesterday I installed 516.59-desktop-win10-win11-64bit-international-nsd-dch-whql.exe (Studio) from June 2022 and voilà all is well, no more CTD, no sound quirks, even editing large airports works wonderfully again.

It's possible that it's a coincidence, because the CTD occur so randomly, but I thought I'd share it here, maybe it helps.

(Hardware, brand new - Intel Core i7-11700F, mainboard MSI MPG B560I GAMING EDGE WIFI (MS-7D19), 32 GB DDR4 SDRAM, RTX3070, no OC for CPU, RAM or GPU, XMP off. Store version, default installation path on a 1 TB NVMe 4x 8 GT/s.)

3 hours ago, andy1252 said:

[...] But the truth is that I used to have just as many addons and variables on both P3D and XP (still do, even though I don't fly them much now) and yet I certainly never had the sort of random and annoying issues that I've been getting the last couple of months with MSFS.

Interestingly, MSFS (up until the recent CTD shenanigans) has been rock solid with not a single crash for me. That's despite me having an ever-growing list of add-ons running simultaneously.

CTDs really do appear to be hit and miss for people depending on: what combination of PC hardware is being run, what add-ons arwused, what peripherals used, Internet speed, which MS server used, time of day, the selection of certain in-sim settings, which version of GPU driver in use, if there's a letter  'r' in the month...

@EDDB2020 thanks for your suggestions, I’ll look into it.