For the moment the LFPG flight to FACT is at 1h30 and still no CTD with the GTX 1080 TI and the HP Reberv G2.
When you know that with the RX 6800 XT and the HP Reberv G2 on the same flight, I always had a CTD after a few minutes, you might start to think that 6800 XT and the HP Reberv G2, would not be the best combination …
EDITION: The HP Reberv G2 goes to sleep after a while despite the change in the registry, and to have prevent the sleep in the device manager. I switch it to VR and it starts again. We are now at 4 hours of flight. And 0 CTD
Just had my first CTD in months, AI is always off but this time something is different as I’ve never seen this before:
Faulting module name: CoherentUIGT.dll
I updated to the latest nVidia drivers yesterday so I’ll try rolling them back and see if that helps
What do you have as a PC configuration. GPU CPU Motherboard, and you play on screen of which definition, or vr of which models. If we had as much information as possible about our configurations, we would find everything there is in common with all these CTDs. On this subject, there is everything, from AMD to Nvidia, screen players and VR players. The only thing in common between us is MSFS.
I’m not even talking about Windows, because I myself have several Windows, some official ones, some more unofficial ones, some customs, but that doesn’t change anything at the CTD.
I rolled back to 461.92 and completed the flight with no CTD. Not pointing my finger directly at the new driver yet, I’ll try and do more flights and see what happens.
I will try to make some other flights to make sure it works all over the planet . (Sure hope so).
My specs are;
Radeon Rx 6900 xt 16 Gb
SSD 1 Tb
Ryzen 9 5950 X 16 core
32 gb vram
Reverb G2 (which I think causes a lot of problems alongside with AMD drivers)
None of any of this worked for me after the last GForce Game Ready Driver Update (465.89). Will not get past the loading screen, just after “Checking For Updates”.
One taxing out in Exeter. One taxing out in Lanvetter.
One when landing into Lydd (UK)
One whilst moving round the world map.
thanks
Mark
Not a pilot.
Returned to flight simulators since MSFS launch - dabbled in flight sim in the past but not to the level I am trying to attain now!
Love all types of flying - from the very functional process driven airliners (currently the A320FBW and the new CRJ (Aerosoft) to the fun, no rules GA flights in my Piper Arrow (Just Flight).
I get a CTD since last update to 1.14.6.0 every time around 10 to 20 minutes into a flight. I am trying to reinstall the sim, but get the same CTDs during download.
ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
I sincerely apologize for posting the link from a PM! Now that #AmbitiousPilots told me. Using the advice for getting the most out of a Nvidia was just part of how much the affinity mask helped me. But I have an i9 with 10 cores and 20 threads. Turning off cores 0 and 1 stopped all my stutters. I haven’t had a CTD since either. He does mention that this will only be good for those with a high core count CPU.
The last “performance improvements” did nothing for so many people. I didn’t notice any increase in performance but I was already using the Nvidia tweaks and affinity masking.
I seem to be con-curing with “nealspill” who posted earlier, I switched off the AI traffic (one of the 3 options just before you click Fly). I reduced most vehicle, boats, etc to 20. I also unplugged my new Xbox controller.
and I kid you not I have done 6 or 7 flights with Cat III landings with the new FBW A32NX, only 30min or 40min flights but the unexplainable crashes to desktop while performing minor tasks has halted! thats over 3 days simming now …and no CTD.
The flight were,Santa Barbara to L.A , Tampa to Orlando, Bristol to Heathrow, etc, I accelerated time, I checked web. paused the game etc …and still no CTD
I am as surprised as anyone that it is running OK… just frightened to plug in Xbox controller now.
The only problem I have now
I updated the Nvidea drivers today trying to stop the GPU from going into 100% mode in the menus of the game, which is ridiculous. and when I start the game I am lucky if the GPU goes above 70%?
I’ve had AI turned off for months now but it hasn’t helped me (not to mention it’s not ideal to have to turn off one of the major features of this sim in order to avoid performance hits or even CTDs).
I too have noticed the fact that GPU goes at almost 95-99% during the loading screens and also in the main menus. This makes absolutely no sense as the GPU doesn’t even have to render anything at that point.
Anyway, like I said I’ve had enough so I’ve begun researching Xplane11 and its absolutely must-have addons, all of which I’ll probably be buying today. For me stability, fidelity, study level aircrafts and accurate flight models are vastly superior to simply great graphics and lighting (because really this is all that MSFS does well and not always). Won’t waste any more time with Asobo.
Good news (well I’m not sure …) the plane went after 10 hours of flight time, but crashed on landing.
Thanks to everyone who shared their configuration, who can start to prove that it’s not just those who play VR with the HP Reberv G2 with an AMD 5000 or 6000 series GPU who are affected by these * ****** from CTD.
If we add to that, at least in my case that only MSFS causes me CTDs, where are we going to knock on the door so that they do something to resolve these CTDs ???
Why a GTX 1080 TI or GTX 1080 do not cause CTD, when more efficient configuration from AMD or Intel cause CTD ???
There is really something that the developers at Asobo have to explain to us, but ESPECIALLY they have to correct it.
Yes Zeppos, I was close to calling it a day also, it is the optimisation of the game that’s the real problem here, it’s as if Asobo / Microsoft had never heard of, or were aware of modern day Graphic cards or CPU’s made in the last 4 years?
We have multicore CPU’s with NOTHING to do, with such low utilisation of CPU cores to the point of embarrassment from the whole of the PC community.
My current readings in the game, GPU running at 70% and CPU at 17% usage that produces 35-39 FPS …both never go over 65°C in the Air?
I’ve been having CTD’s ever since the last patch to fix the stuttering issue. It can happen a half an hour to an hour in flight. I never had a CTD before this. My nvidia drivers were old so I updated to the latest version but it didn’t help. I have a 3080 rtx graphics card and a i9-10850 cpu. Any others in the same boat?
It’s sad, because it’s really gorgeous in VR, especially since I upgraded from the Oculus CV1, to the HP Reberv G2. But we are forced to note that it is unplayable for the moment.
We are all here to have fun flying, whatever our level, but by no means to become computer engineers.
Another victim here. Hardly ever had any CTDs since the beta. Now, I hit “Fly”, it loads to about 2/3 and poof, back to the desktop. This all seemed to start happening with the last major update. Haven’t changed any settings or hardware. Nothing overclocked. MSFS is the only thing doing this, so am not changing everything just for that. I did reinstall the sim and it seemed to cure it for about a week. i7-6700K, GTX 1060 6GB, 16GB RAM
I was telling myself that MSFS couldn’t stand being pushed into these limits by medium or large PC configurations.
I thought they wanted everyone to be able to play it, even with small setups.
But I see that everyone can be affected by these CTDs, whatever their PC configuration, small or large, whatever the Intel or AMD platform, whatever the Nvidia or AMD GPU, whether on a 2D screen. , or in virtual reality.
The fact that there are some that have no problem, the proof, I do not have with the GTX 1080 TI and the HP Reberv G2. I was able to do a 10 hour flight without CTD. Now a flight is not representative.
But the RX 6800 XT and the HP Reberv G2 are unplayable, because of the CTDs.
I never had one for 1 month with the RX 6800 XT and the Oculus CV1.
Even though some don’t have problems, that doesn’t mean there aren’t problems with MSFS.
And we must stop telling us that our Windows, or that our OCs, or our drivers are responsible.
We can play a whole collection of games with our PC configurations, without spending 95% of our time trying to find countermeasures.
Well, restoring my graphics settings, gets me through the loading screen, however, attempting to fly at 2-5 FPS, less than optimal. These latest updates/hot fixes, have made a virtual slide show on my Ryzen 7 5800, RTX 2070, 32g DDR 4 3200 RAM, well above minimum specs for this cough sim.
Curiously enough all of my recent problems began immediately after I upgraded from an ancient R9 290X to an 6800XT. With the older GPU I hadn’t had CTDs in several months (from November to March). I installed the 6800 literally a day before the early March patch came out, so can’t be 100% sure which of the two was the culprit (could be both). Even so I was able to fly for 2 weeks with absolutely no issues, just by setting Adrenalin Tuning to Manual with a max fan speed at 70-80% and a small increase in power limit (otherwise I’d get a CTD), but after some point the game began throwing CTD upon CTD no matter what I tried.
So I did more tests today and after 20+ consecutive CTDs immediately upon reaching the main menu, I decided to try and downgrade AMD chipset drivers to an earlier version (which I was using before the CTDs began). The chipset drivers package includes several components and most of their versions were the same, but one that was definitely different was AMD PCI (under System Devices of device manager) which with the older chipset package was 1.0.0.81 whereas the new one is 1.0.0.82.
Using the older package, I managed to start a C172 flight which was absolutely amazing given that I had dozens of main menu CTDs since yesterday. Again I had a huge stutter during takeoff (like a 3-4 second freeze where FPS must have dropped to less than 5 or so) and this is something that’s been happening since my issues began. After that the flight was very smooth at around 50-60fps.
Of course 10 minutes later I got the usual vcruntime crash without doing anything at all, I hadn’t even switched back to Windows in the meantime. Still better than crashing on main menu. I’m not implying that the older AMD PCI version is a potential solution for me, as I was already using the newest driver weeks before CTDs began (before I installed 6800). I may try with an even older version and see what happens.
At some point, when I’ll be super bored and with plenty of time, I may re-install my R9 290X to see how it’ll behave but in the meantime I’m doing research on Xplane (weather engine, mesh addons etc) and by reading through the various forums of that sim I’m amazed at the contemptuous comments of Xplane users towards MSFS. I hadn’t realized. At this point I tend to agree with them, MSFS is all about graphics and nothing else, it’s more of an MS World Simulator rather than Flight, and that’s if you don’t have CTDs. When stability and crashes come into play, then there’s no point to even argue.