Crash to desktop without error message

Recently I have been using development versions to try some new features, so I am not surprised by those CTDs as this version is WIP.

In general, I have a rich history of CTDs within MSFS (including other machines such as CRJ or Cessnas), yet they disappeared in late November.

Speaking exclusively about development version of FBW, almost entire December has been free of those. They have returned around Christmas with large rate, one every second flight.

Flights with CRJ are stable, so naturally everything indicates that recent FBW builds are the cause. I wanted to try a newer build earlier today, but due to Live Weather being down, I am gonna check it out tomorrow.

Make sure you have the latest, older versions will cause issues.

Naturally, I always use the most recent build from FBW Installer :slight_smile:

W.T.F… Fly over 2h, short before landing on LSZH i got CTD.
FLB 0.7.3

Its so frustrated :frowning:

Unless this is occurring all the time, with today’s server issues I wouldn’t be too concerned

You can see this topic started in August 2020, right?

Anyway, same for me. On various drivers, with and without the community folder, with various amounts of hardware connected and even with different color slippers on each time. It randomly quits for no reason. Downloading the beta now, hoping they fixed it.

If you had noticed my 40 some posts in this thread, you could have avoided that answer.
I too hope they fix it.

At this point I approach every flight as if it’s a test and anything could happen so I don’t get so frustrated. However, the last three flights I’ve done have crashed all three times about 1 hour or so into each flight with the A32NX and Longitude. Very disappointing :weary_face:

I am having CTDs after latest update again.

New record: While preparing new flight on LSZH airport with FLB A320 (Dev 6f51411) => CTD :tired_face: :exploding_head: :face_vomiting:

Hi how are things.
I could try the stable.
I just got out of LSZH and no problem.
You could also delete your cache.

Moderator edit:
Hello, thank you very well.
Finally I was able to successfully (?) fly from LFSB to LSZH. After I had inserted a special loop on landing (there was a plane in front of me), I could not confirm the last command during the next landing approach, because the radio exchange was constant. Thus, I did not receive a landing permit until shortly before landing (which usually always comes too late anyway). I just made an illegal landing. “Who cares?!”
I suppose you mean cache in FS?

Hallo, danke ansich gut.
Habe endlich ein Flug erfolgreich (?) von LFSB nach LSZH durchführen können. Nachdem ich eine Sonderschleife bei der Landung (vor mir war ein Flugzeug) eingelegt hatte, konnte ich während der nächste Landeanflug den letzten Befehl nicht mehr bestätigen, da andauernd der Funkaustausch war. Somit erhielt ich bis kurz vor der Landung keine Landeerlaubnis mehr (was i.d.R. eh immer zu spät kommt). Machte ich halt eine illegale Landung. “Who cares?!”

Ich nehme an, du meinst, Cache im FS?

Yes
Cache FS.

It reads like there is something about your system that MSFS really doesn’t like, and it’s difficult to say what that might be. That error message is really unhelpful too.

When I was getting those errors messages regularly I just removed all ancillary things until I got my stability back, but I was always able to fly, I just didn’t know whether that flight was going to result in a CTD.

I use community mods as well, but only a handful. Some of my stability issues were caused by the PMS mods, or at least having them both installed at the same time. Back then I was flying the Arrow a lot, and had a lot of crashes. When I removed the 530 addon, and only used the 750 addon I found I was more stable.

I would still get the odd crash though. Thinking outside the sim itself, one other change I did was to stop using external flight tracking software, like LNM, and Volanta. I didn’t have a crash in months after that, and I continue to fly this way.

The last crash I had I had fired up LNM, and connected it to the sim for some reason. Obviously to get it to plot where I was but I forget why. I forgot to turn it off, and went back to flying. Towards the end of that flight, while doing some circuit practise, the sim crashed. It was then I noticed I left LNM connected. I haven’t done that since, and I have had zero crashes.

I also use Skypark, and that can also track your position, but I have not had a single crash since using that addon.

I don’t know if you have ever mentioned what you are using with the sim, but if you are crashing before you can even get to the main menu, it may not matter. You could try reviewing any overclocks you might have, and remove them for testing. Anecdotally I’ve observed that those with AMD processors seem to have move crash issues than Intel users. I just found your post where you mention you have an i7-10700, so that likely rules that theory out then.

I bought and installed new PC specially for MSFS. Its an Intel(R) Core™ i9-10900 CPU @ 2.80GHz with 32.0 GB.

I use SPAD.neXt, Navigraph Simlink and Littlenavconnect (for Little Navmap on other PC). Before I did not have this problem for long time.

I would consider chopping out the use of Simlink, and Littlenavconnect for a few flights in that case.

If you fly like that for long enough that you would expect to get a crash but don’t, then you may have found your culprit.

None of this is suggesting the sim is not at fault, only suggesting that processes external to the sim are triggering a bug.

Since upgrading to Win11, which is when my reliability history would have got wiped, I had a single crash on 10/12/21, which was when I had LNM connected to the sim. I had one unrelated host process crash, and one other was Razer Central. Neither of these had an observable effect, and I didn’t even know they had until I viewed it here:

Series of my CTD is not related to system virtual memory and any add-ons. MSFS have memory allocation errors in code related to online services (weather/ATC/traffic).
With the weather preset, I don’t have a CTD.

Bravo !!!
Yes sir that is correct.
With everything off (weather/ATC/traffic).
I can go around the world.

virt. mem setting was just a starting point because its often related to 0x80000003. But yes, the issue with the weather ( and or others services ) seems have wider range as expected:

I’m testing this morning with the following:

CVYR > KMCO - Citation Longitude

  • Nvidia 496.76
  • Turned off HAG in Windows settings, reboot
  • V-Sync forced on in Nvidia Control Panel for FlightSimulator.exe
  • Going to leave 1-1-1 flight settings (suspecting Live Weather could be related to the CTDs)
  • Going to use stock Longitude livery (usually use the freight company one)

The new things I’m trying today are from reading the latest replies, livery and HAG. Going to recreate the flight I last CTD’d on and see what happens.

edit: Progress report (2 hrs later) - Live weather is actually working, game is running very smooth. It’s either the livery or Hardware Accelerated Graphics. But it could still crash before I get to Orlando. Will update any changes.

edit2: Landed, went to lunch at my job - actually missed approach and used the time feature to get to approach. Had a separate joystick issue present, rudder was sticking to the left.

I am now going to reattempt the same flight with the freight livery. Based on new posts here, I bet it’s hardware accelerated graphics. However, I’m gonna test it.

edit3: so far so good with different livery. I might bank all my eggs on HAG. I’m also a W11 user.