Crash to desktop without error message

My latest CTD was about 45 minutes into flying the LFBD-KSEA (Asobo to Microsoft) achievement.

I was happily at 38000ft in the stock A320Neo with autopilot engaged. I opened the VFR map to see where I was. As soon as I tried to resize the map window, it immediately froze and then crashed.

My CPU and GPU were not under heavy load. I was monitoring that on the side. CPU was under 25% and GPU was maybe 50-60% and both had been steady for some time.

1 Like

Reloaded the fight plan, used time acceleration for much of the flight, and landed 3hrs later. Never opened the VFR map this time. Achievement unlocked!
:+1:

1 Like

Just a few of my observations here-

  1. CTD (or freeze) normally happens after around 30+ mins of flight
  2. Crash happens randomly (ie not linked to an event or anything I do)
  3. I can force the game to crash by doing one of the following things- a) if I forget to plug in my Thrustmaster T-Flight Hotas X, then plug it in after MSFS has started. And b) simply pressing ESC to open the options screen often causes a crash.
  4. Sometimes it’s not a CTD, but a ‘freeze’ that I must reset my PC to recover from.
  5. Crash often kills my NVIDIA hi-definition audio device (needs a full reboot to recover from that). It’s like the device simply vanishes.
  6. I can often hear a ‘juddering’ sound from the speakers moments before the crash.
1 Like

I’m sure it’s covered somewhere in this 5500 post mega-thread, but are crash reports automatically uploaded to Asobo or Microsoft?

I haven’t had any CTDs during three flights what makes me optimistic. However today, sim started freeze while entering the Options menu during flight. There appear to be some kind of memory leak.

And again, CTD

related to your reported sympthoms you should check the former hints about sound-drivers ( may be also de-install the nvidias hd-audio driver stuff, or disable the device ) and have a look at your system in point of over-heat.

and PS: just dont forget to plugin your joystick :wink:

“This topic has been solved” Lol, what? Solved how if people are still getting CTDs, random or not?

Just had one in the middle of a 2-hour flight, completely out of the blue and for no obvious reason or error at all (just the usual 0x0…05 stuff). Previous 20+ flights went smooth, most were over 3 hours long and had no issue. Suddenly boom.

Good old MSFS. 5500 posts later and CTDs are still a thing, nice. Another 2 hours wasted (1 for prep, 1 for the half-flight)

4 Likes

such kind of post and you get, as you sayd in 20 x 3h = 60h ( and you mentioned 20+) one single ctd for which you not not know that this was causes from the game or your system itself :thinking:

And not sure why the time of the “half flight” was wasted.. you enjoyed a 2h flight..

No matter how good or bad the scenery is looking, weather, aircraft, and so on, it’s just impossible to play.
CTD in the middle of the flight.
They should fix the bugs, before any other WU release.

3 Likes

The best part about any flight is a good landing. Yes every other aspect from engine start up to descent is also very special…but the iceing on the cake is the landing and a non incident flight till the parking.

If this is interrupted, especially after competeing most of the flight…it really sucks! You do not feel that you have completed a flight…unaccomplished maybe?? After all, the aim of flying is to get up and land right?

If that ain’t happening folks, what are we doing? Might as well get on the Train Simulator or a bus simulator, where you can start off where you stopped!

MS and Asobo need to think back and get the basics of the sim working again, in which you can experience a full flight. Yes, it might put us back to Update 4 level, but at least you complete a blummin flight! After that they can take all the time to test and get things right, and we would support them…but things aren’t going that way. For many, it aint even getting past the launch stage!

4 Likes

I’ve been suffering from massive CTD after SU5 and WU6.
CTD during loading, during flight, during landing, even during taxiing after landing.
I’m really tired now.
Before that, I only had CTD about once a month.
I’m really angry.
Asobo should stop everything else and start stabilizing the sim.

6 Likes

Gained about 10 hours of gameplay on Steam today. Why?

Upgraded my two Ryzen gaming rigs with GTX 1080 and RTX 3080 to Windows 11 today and re-installed FS on a blank system. Still having the same CTD issues I had before on Windows 10.

I do now finally give up on this stupid game!!! It’s simply broken and a waste of lifetime. How can it still CTD on a fresh Windows 11 install and vanilla FS installation.

4 Likes

A very sad end…which leaves a bad taste. It’s more agonizing when you know this could have developed into the ultimate Flight Simulator.

So you consider that development has ceased, and it won’t get better?

Windows 11 is not yet officially supported. Plus we don’t know that you didn’t reinstall the things that made your sim unstable when you were running Windows 10.

When you try to run before you can walk, problems happen. We were getting there with the walking bit and we knew that eventually we would run. It’s pure logic…build a good foundation and you have a Rock solid construction.

I say, stop the development and get the basics fixed. Then you can go to the next step of development.

I don’t think any Flight Simmer would go against that!

1 Like

How can we fix the basics if we stop development? Do you perhaps mean stop adding features, and instead fix what we already have? Reading between the lines I think they have said as much, but I’d have to go back to the last Q&A to be sure.

That’s exactly what I think yes.

And I knew a sentence like Windows 11 is not yet supported would immediately appear here :rofl: simply ridiculous. Let me elaborate one last time in this forum before I stop wasting time on this game …

I have two gaming PCs with more than potent enough hardware for this game:
RTX 3080, Ryzen 5800X, Crosshair VIII Hero, 32 GB Ram
GTX 1080, Ryzen 3700X, Crosshair VII Hero, 16 GB Ram

Disclaimer: There is nothing overclocked in the PCs and the GPUs (especially the RTX 3080) are even downclocked not for stability but for lower temperatures and less noise. A ton of other resource hungry games (despite no game being completely bug free) run without CTD issues and also general PC stability is fine with not a single crash of Windows since I have these PCs.

I was running Windows 10 21H1 and Windows 21H2 in the period when I had the CTDs.
I am now running Windows 11 21H2 (production release no preview version!) and still have the same CTDs.

I am owning the premium deluxe version of the game on Steam. I have tried to stop the crashes by just installing the standard content. Didn’t help. I have no custom modifications installed.

I have tried with and without the “world updates” installed in both variants the vanilla standard install and the premium deluxe content install.

I have tried all planes from the standard version and the 787.

I was even installing a clean copy of Windows 10 21H2 and Windows 11 onto a separate SSD and only installed Steam and FS (and of course system drivers).

I have no accessories connected to my PC for testing except for a mouse and keyboard, oh and a display if you call that accessory :smiley:

Did I miss anything? Probably but I am sick of trying to find a solution to this broken game if it can’t even run on a clean install.

The CTD issues are reproducable with any plane in any of the above configurations and never happened while starting the game or in the menu, they ALWAYS happen 1-5 minutes after take off no matter if I fly with auto-pilot or manually (which admittedly is difficult on some planes with just mouse and keyboard). There is no error message except an access violation logged in the Windows logs (0x00…5).

Btw … when the game was out new everything was working fine in terms of no crashes happening (auto-pilot and planes were bugged but there were workarounds for that). The CTD issues started with world update V iirc but they are not related to the content since they happen when world update V isn’t installed as well (but standard content was “patched” to death at that time too).

Probably the last 100 hours of my Steam gameplay statistics were (re)downloading at 100 MBit and loading times of the game …

3 Likes

Gaming rigs huh? Try down clocking, start with xmp

I’ve actually managed to avoid CTD’s almost completely the last year until this week, where it’s crashed three times, straight to desktop about an hour and half in to flight with no warning. The computer itself didn’t crash and I haven’t had to reboot.

Now I have a fxxk ton of add-ons, both free and payware, in fact I purchased around 10 airports/airfields and a couple other add ons in the past week alone, including Seafront’s South East England ship pack tonight.

Now, I don’t actually care about occasional crashes, as long as I know its a bug with the sim and not a fault of my system, GPU getting too hot for example.

I know I can’t troubleshoot easily, and I certainly don’t want to remove any of the 50 or so add ons I’m running, but I was wondering if there’s a way to tell easily if a crash is on Asobo’s end, or a problem with my PC? As long as computer is ok I largely don’t sweat the odd crash, But if I’m overheating my PC that would be worry.

I have a high-end 3090 setup and only play in VR, using a Reverb G2. Loading into GPUZ immediately after the crash my GPU was around 60 degrees and myhot spot (VRAM) 78 degrees. It took me about a minute probably to get off my chair, take my headset off and run that so they were presumably much hotter a few seconds before.

Is there a way I can test it wasn’t my GPU or CPU?

Hey Chris…that was a good one…
hhhh

See…thats the problem…you had your monitor connected! Now, if you had disconnected your Display monitor, it would have solved the issue completely :rofl:

But on a serious note…too many hours have been spent trying to rectify the issue without success..

1 Like