Crash to desktop without error message

Bug Reporting Hub Resolved
, ,
2584

Hey! I experienced random CTDs after upgrading mein CPU from a Ryzen 7 3800x to a Ryzen 7 5800x. It was awfull. Ruined the Sim for me. Looked at this thread, tried everything. Reinstalling Windows and the Sim, older GPU Drivers, disabling cores and so on. Even disabled DOCP Profile. The Sim didn’t crash after 5 to 10 Minutes, but after 30 to 45 Minutes. Progress. My Hardware sits on a Asus ROG-Strix B550-F Gaming. Of course I installed the lates Version of the bios before Upgrading to the new CPU… And this was the mistake. After weeks of fiddling, countless restarts and after hours of hypnotizing the event-monitor I just had it and downgraded the Bios to the last stable Version. That did the Trick.

So to all of you experiencing CTDs working with an AMD CPU, try an older Bios. For me the AGESA V2 PI 1.1.0.0 Patch B is the last stable Version that works. No CTDs since downgrading the Bios. Sim runs like butter.

2585

Getting the CTD any time that I attempt to load in or fly into one of the “edited airports” that came with the previous update, as well as the airports edited upon release. The only thing that works is removing that airports information, and then starting in on non-edited scenery.

Info:
MacBook running Bootcamp for W10
32gb ram
1TB external SSD
Cache said to off / on / preloaded (tried them all)

running everything on essentially medium settings, though turning them up or down have not had any effect to fixing the issue.

what I’ve tried:

  • Deleted livery folder / re-installed / removed completed
  • Clear cache files
  • fresh MFS install, fresh add on install.

Attempting to use the “generic aircraft fix” now, and then going to try the manual scenery folder reset

fingers crossed

EDIT!!!

We’re fixed - ish! I can finally load an edited airport and not CTD (hoping this works for when im landing as well - going to try that in a bit).

What i did:

  • set generic plane models both to on, delete manual cache, deleted KDFW, re-install KDFW, redo manual cache.
2587

with 100 hours in the sim I am now getting a CTD when clicking on the world map…I can get into activities but not the world map

2588

I apologize if my question has been answered somewhere in the swarm of posts that have been added here since i last checked/voted back in November, but has there been any progress made on the “without error message” part of this thread? I accept that i have a problem with the rig i built brand new in August 2020 that keeps me from from flying more than ~45 minutes - but i just want to know what, if anything, i or Asobo can do to capture more information around what the heck is failing whenever i get the “screen/sound pause, oh ■■■■, yup crash” inevitability (i.e. not looking to “solve”/workaround the problem - looking to help reveal the actual source of the problem). tia

And for added emphasis - i’m not looking for help solving my CTDs. I’m looking to solve the problem where CTDs happen with no useful information (re-emphasizing the “without error message” part of this topic!).

1 Like
2589

My issues from yesterday seem to have fixed themselves.
Doing the same flight as yesterday YMEN to YKII with LittleNavMap and so far, fingers crossed, no issues.
Go figure

2590

My game keeps crashing and sometimes will crash my whole pc without even a bluescreen i don’t know why but all i know is that it only happens on msfs

2591

Hi! Did you update your bios? Try the latest stable Version, not the Beta-Versions. If that doesn’t work, try an older stable Bios. This was the fix for me, after trying everything else described here, including several redownloads of the sim and a clean Windows reinstall. I had to change to an older stable Bios, since then, no CTDs.

2592

Keep rolling the dice, and I suspect at some point LNM will bite you! I’ve had crashes with both LNM, and Volanta running in the background. I’ve also tried them independently, and had crashes. But I have also managed quite long flights with them too.

Right now, I’m flying without either tool running, and last night had two hour long flights without issue, and intend to keep flying without those tools as part of a trial. The only thing you can ever know really is it works until it doesn’t, then you’ve eliminated another theory.

Right now, I continue with the assumption that SimConnect is the issue, and the less you push through it the better, until Asobo fix it. And I think it may be the reason why so many people are chasing their tail, trying to find out what is wrong with their system, and failing to find anything conclusive, and may simply be looking in the wrong place.

Anyone remember the massive stuttering issues we had with it when you connected something like SPAD? It has had issues in the past, and they were resolved in a week or so. Hopefully this will be no different.

1 Like
2593

Before the latest update for MSFS, I rarely had any CTDs. Now they seem to happen constantly, often hours into a flight.
I’m using the SimToolkitPro, PACX, FSUIPC7 and the FlyByWire mod for the A320. If I find the time today I will start checking if not using one of those third party tools will actually help avoiding the CTDs.

2594

Just had a crash, while on approach to runway 25 at KDEN. No external tools open at all. I was just turning the CRS dial on my Logitech panel, and bang! This was about an hour, and a half in.

I had completed an hour long flight just before that without issue.

I’m thinking of just leaving Generic Plane models on permanently now. :slight_smile:

2595

Now i have a new problem. After trying to turn off the rolling cache, it worked for a while. well now i have new different problem.
Everytime i wanted to approach at any airport, my game crashed, sometime when decent and sometime at final. it happened in every flight in every region too.

2596

2500+ replys and only 700+ votes. Please, add in the first message something like “VOTE if you have the same problem”. I think we should highlight this problem to the dev team. Even if they cannot be relied upon :slight_smile:

1 Like
2597

This is very annoying problem.

I have installed Microsoft Flight Simulator (MFS) 2020 on my PC:

i7 6700 (stock cooler, stock clock), 1660 Super (stock clock, dual fan), 16 GB RAM, 512GB SSD Samsung 850 Pro (Windows 10 20H2 19042.746 + Store version MFS 2020 install location).

On MFS2020, I frequently experienced CTD without any error messages. I couldn’t even finishing short 20 mins+ distance flight (takeoff, cruising, landing). I have played this game since December 2020 (since the 1.12.13.0 version) using M+KB+Xbox One Controller.

The game is set on mix low-medium-high graphic options and I limit the game to 30fps via Nvidia Control Panel. I turned off AI and live traffic, and other online functionality except Photogrammetry.

I have tried some hints and guidance here to minimizing CTD but none of them works. At some point I think this is must be software issues.

CTD feels like the game has been accidentally being pressed Alt+F4, just close. Until now, I have not found consistent error (like what exact duration/time or what I am doing when CTD).

Sometimes, CTD happens while I’m just leaving MFS 2020 running idle at world map flight plan menu for couple minutes (I think it may not using so much resources at menu).

But yesterday I made observations and give me little clue at least for my CTD case.

I checked CPU and other resources usage and temperature while playing this game and fly in some same rural area with not crowded city.

Using Xbox game bar and HWinfo, I see usage:
CPU: 40%-74% (100% spike at some point)
GPU: 48%-58%
VRAM: 75%
RAM: 70%
FPS: 30

CPU temp max: 62C
GPU temp max: 72C

At some point, in the middle of the flight, I heard the fan getting louder and when I checked again via XGB, I saw the CPU usage going from 40% to 100% top and there was some of 90%-100% CPU spike for few seconds, every few seconds.

Like from CPU 40%-70%, then up to 100% for few seconds and down to 40%, for few seconds and up again to 100% and so on.

I think this is happened because the CPU is working hard processing something/drawing the area. So I press paused, but the 100% spike still happened.

IIRC, paused the game worked for some games to decrease CPU/GPU usage for a moment (because it just draw menu interface). But this isn’t work for MFS 2020.

At that time, I thought it might be CTD soon because my CPU was choking. And right, a moment later CTD happened, desktop shown, MFS 2020 icon disappear from taskbar but it can still play sound (engine sounds) for a moment, and then stop.

I think CTD in my case happened after my CPU experiencing multiple 90%-100% spikes in certain time.
I am curious what makes the ‘spike’.

I tried multiple flight in same rural area after CTD.
I tried takeoff - flight - cruising - exit to main menu - load flight plan again - take off again - flight -and so on.
Sometimes the spike (and CTD) happened even in the first flight, and sometimes happened in second or third flight.

Sorry for the wordy post. but that’s my observation.

2598

Yesterday evening, I took a flight from EDDM to EDDH using the A32NX mod as well as PACX. No problem there at all.
Today however, I wanted to fly from Hamburg to Frankfurt with the A32NX and PACX. No problem during the climbing phase but around five minutes after reaching cruising altitude, MSFS suddenly hangs for a couple of seconds and then CTDs.

This is getting increasingly frustrating especially since I feel MSFS was a lot more stable before this latest version.
This could of course still be an issue with the A32NX mod or FSUIPC so in the next test, I will deactivate all mods and take a slightly longer flight.

2599

i checked the event viewer and found this
0x2000000000000001
0x2000000000000008
0x2000000000000001 (again)
three of them happened in less than 30 second in the last second of the game life
i dont know if this caused the CTD or not
maybe someone know what is this

2600

The same problem :frowning:

2601

Every long flight i had crashes to deskop- No major mods either..

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5fda32ba
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5fda32ba
Exception code: 0xc0000005
Fault offset: 0x000000000043ca7a
Faulting process id: 0x1ee4
Faulting application start time: 0x01d6fbb9232b5af8
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: f5a867c7-104e-4055-875f-94593c30259b
Faulting package full name: Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

2602

Well, for the last month it’s been great. Now it’s CTD every day. There haven’t been any changes to my system or the game since my last post. My last post stated that it started running great for no reason (amost like it fixed itself). I made no changes then, and I’ve made no changes now. I really hope they get this fixed. :sob:

1 Like
2603

I have an idea … perhaps the MSFS team should be counting posts AS votes … Or allowing us to vote each time we have a CTD ? I’d have more than 700 votes myself by now.
I see little point in making a World (you can’t successfully complete a flight in) look better when it’s part of a program that simply doesn’t work !
Ryzen 7 3700x x570 32GB 980Pro & 970 1TB SSD’s RX5700 xt + G2 all bought new for THIS GAME. And now it just sits there as it’s almost of no use.
Random CTD’s all the time - I had a 1 hour flight in VR the other day as a test , with the headset siting on my desk without any issue. Next day I started the same flight and got CTD within 5 minutes. Only difference was the I was wearing the headset.

2604

GOOD NEWS.
Last time i have these error message:
0x2000000000000001
0x2000000000000008
i found a solution, you need to set your PC power plan to ultimate, by typing these to cmd:
powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61
After that, you need to reboot.
After reboot, open power setting > additional power setting > show additional plan > select the “Ultimate”
And after opening MSFS, open Task Manager > Detail and set Flightsimulator.exe priority to Low and if you using CPU with 4 core or more, you can set your affinity by deselecting core 0 and 1 for Flightsimulator.exe

Another problem that i can solve is 0x80000000000000.
If that appear in event viewer, you need to reinstall all Visual c++ (from 2005-2015) both x86 and x64

Credit goes to @AmbitiousPilots and some random guy in Reddit

2 Likes