Crash to desktop without error message

I don’t think that is entirely correct. I flew for an entire week with no issues. Then I installed KB5005033, and I had two flights after that, and both ended with a CTD. Before the patch was installed, I had flown a couple of test flights around San Francisco with no issues either, it only happened after the reboot.

Now I was flying in completely different areas in those three sessions, so the patch my likely have nothing to do with it. The flights with crashes were taking off from Courchevel, heading to Meribel. Curiously both crashes happened as I entered its vicinity. The first was taking a shortcut over the mountains, and I was about a mile out, and several thousand feet above it. The second time I took the usual route, turning left, then right down that long descending valley, then turning right to line up with runway 2. Just as I touched down, or within a second or two, it crashed.

Meribel doesn’t care that I have an EVGA 1600W Platinum PSU. It’s too much coincidence that I had the issue in the same location. This may be one of those cases where I have to clear out my scenery cache. Before I do that though, tonight I will try spawning there instead.

I had a similar issue to this a while back when WU5 came out. I couldn’t complete the landing challenge at the time as I my sim would crash just before I spawned in. Similarly, flying in from the East about 10 miles away, when I got near that airport the sim crashed. I then tried a different approach, over the sea from the West. For some reason that worked, and I was even able to land there. I could then load the landing challenge! That seemed like something had got updated or deleted, and that’s kind of what it seemed like last night.

So in conclusion, error 0xc0000005 is absolutely tied to MSFS as I don’t have a single other piece of software installed that does this.

You could make the argument that it something else, like Motherboard, Memory or Processor. Well over a week ago I swapped all those components out as part of an upgrade, and was flying fine until those two flights last night. Buying another pair of fault memory modules would be extremely unlucky. :slight_smile:

It’s not overheating either as I use a watercooler, for the CPU at least, and the highest I’ve seen it get to is about 57C. The GPU, a 3090 FE, usually peaks around 47-50 IIRC.

I get what you’re saying, it’s likely a data read error that can occur for both obscure and obvious reasons. Could be hardware or could be an actual bug.

Yeah. If you look at some of the posts by @N6722C , and others, they point out these “null pointer” roads to nowhere littered through the code, where the sim just cannot continue running, and falls over.

Ideally, what I’d like to see tonight is a crash when I spawn at Meribel. If not perhaps a quick take off out of the valley, then back in to land.

I’ll then repeat my flight NW up to KSFO, overflying the city, and landing at KOAK.

Rather than simply bad coding I can imagine this has something to do with the adaptions or limits made for Xbox (the culling for example), maybe they couldn’t just delete the code without a rewrite for which they had no time.

Some amount of absolute ■■■■ spouted in here. They should create a sub-forum for the apologists to play by themselves.

These problems have been going on since I can remember. But it only seems recently that PC users have been feeling the pinch, more acutely at least. It was always their intention to release on console, of course. But what I was surprised to read about is that XBox users have been getting crashes. It’s a closed system, so how they managed that I don’t know.

Info: All users which had trouble (CTD) because of Asus Sonic * stuff

Today I started my PC and these tool is back on my PC.

I can not see in which way it is re-installed, but it is again on my PC. RE-Installed one minute after starting the PC.

And much more worst: this install also re-activated the horrible Nahimic service.

image

so,.. please be carefully.

And I have to find now a way to block this bloodware for ever.

PS.: seems windows itself do that.. omg

FROM Asobo: Delete all these programs and tell us if our pile of (C)ode works!

  1. Seagate Toolkit
  2. Nahimic service
  3. Asus Sonic Studio 2
  4. Windows Audio Service
  5. Garmin Express
  6. WD Backup
  7. Logitech G Hub
  8. Project Lasso software
  9. MSI Afterburner / Riva Tuner Statistics Server
  10. EVGA Precision
  11. OBS
  12. Xsplit
  13. Discord
  14. MacType
  15. Warsaw Banking App
  16. Wallpaper Engine
  17. A-Volute Sound studio
  18. Malwarebytes
  19. Trend Micro Maximum Security
  20. Comodo Antivirus
  21. Sophos
  22. Emisoft Anti-Malware
  23. Avira
  24. Avast & Avast Cleanup
  25. Bullguard

I found a solution that worked for me:

  • disabled “game mode” in the windows settings
  • disabled “hardware-accelerated GPU scheduling” in the windows settings
  • updated all windows drivers
  • updated (MSI-)BIOS

I now use the flight simulator the same way as before the SU5:

  • a few AddOns/Mods in the community folder
  • “MSI Afterburner” for overclocking my GPU
  • “Riva Tuner Statistics Server” to show various parameters.
  • “Discord” runs in the background

Anyway .. I’m pretty sure the crashes were either due to “Game Mode” or “Hardware Accelerated GPU Scheduling”.

Try this and give me a feedback.

interessting… not that again HAGS made trouble. I have this Off.. it was just to random that with an update of windows or nivida the whole PC run into reboot issues ( not game related ).

But if I read this here:

… I can only recommend: dont do that.. the 1fps more is it not worth :wink:

I took part in the livestream earlier, and decided to turn off the scenery cache for once. Flew for nearly 2 hours in the vicinity of many other players in all sorts of aircraft. No stutters, or crashes.

Afterwards I repeated my flight, in reverse, that gave me two CTD’s last night, from Meribel ro Courchevel. No crashes, and I spent about a half hour or so doing landing practise.

I think I may continue with no scenery caching for a bit.

Just before the infamous SU4 came out NVIDIA messaged me of an update and I accepted it. Now CDT after CDT, after futilely trying every fix recommended on Youtube, I decided to try to roll back my graphics card driver to that which I was using with SU4. This CDT problem is totally new to me. Never had them with MSFS since its inception. Unable to find a way to do it within NVIDIA , I contacted support and they helped me find the version of my old driver and install it. So far I have not had a CDT and prior to my rollback I couldn’t even start most flights let alone complete them.
Could this be an added glitch to those of us with NVIDIA graphics cards? I had already changed from gaming to studio setting as recommended but that alone did nothing. More testing necessary but so far seems to be the light at the end of the tunnel on this issue for me.

My event viewer info is identical to yours.

Which driver version did you go back to?

My hardware accelerated GPU scheduling was off and no overclocking.

Are you certain?

Once again, I carefully checked a number of your recommendations on myself, with minor clarifications:

“hardware-accelerated GPU scheduling” is always turned off for me.
"Bios (Asus) I have not updated now (updated half a year ago)

Well, the community folder is clean.

what do we see? I see the desktop 30 seconds after takeoff …

(But I can more confidently confirm that the crashes right in the menu seem to have disappeared since 1.18.15).

Everything seems to indicate that these crashes are not Asobo’s problem. Exactly at 6:30 am on June 6th, on July 27th, my computer broke down.

But what is mysticism?

It is worth literally for a second to take a look and run, for example, the X-Plane 11.55 occupying 370 gigabytes and installed on the same one terabyte new ssd disk, specially purchased for these two simulators. With a huge bunch of orthophoto scenery, plugins, airplanes and external programs - all sorts of Active Sky, LittleNav or Pilot2Ats. And this ■■■■■■■ (bad) computer is instantly repaired, the X-Planeworks like a reinforced concrete, it is simply impossible to crash it … Moreover, the load on the processor in it will be even more, it takes up the same amount of memory as a video card. Moreover, the PC does this on old drivers, and on new ones, with or without patches, with any sound or usb devices.

I’m trying to bring the PC to clean water and run a 16 gigabyte virtual machine with a production environment and working with a 3D environment - also, the infection does not fall into any.

And it is worth for a moment to stretch the mouse to the MSFS icon and the PC breaks down at the same second …

Looks like I need to think about changing the computer. (Not really)

to be sure.. You let run MSFS and in parallel a VM and do some work ? And only in this case you get CTD ?