2 hours ago, Chock said:

I'm not saying the machines are faulty,

It's the humans operating the machines that are faulty. 

The mention that it only seems to happen on flights beyond a certain distance (aka time) immediately made me think of an issue with USB devices going to sleep or something, causing the crashes.  It's a problem they've already had to patch once, so it's entirely possible the issue isn't completely cleared up across all PC hardware configurations.

I've had two crashes since August, and both were pretty random circumstances.

7 hours ago, Glenn Fitzpatrick said:

 

Your not running in developer mode to get the FPS meter or aircraft selector are you ?

The logbook and crash detection are both disabled in developer mode for obvious reasons.

Yes developer mode  was on , and I turned it off last night before my two successful flights.

.

 

Edited January 31, 20215 yr by Bobsk8

4 hours ago, sal9000 said:

I can do that often that I want without CTD when I tick ESC (Pause-Menu) on. And after the plug I tick ESC again and everything is fine.

I had several CTD´s in the past, but they all got to do with bad Freeware (modelLIB-Error).

After I repair all these files I had only one CTD this month causing by metadata (Live Weather)

Stephan,

Thanks for the suggestion, I'll have to try ESC to pause next time my keyboard goes dark!

Kind Regards

52 minutes ago, Bobsk8 said:

Yes developer mode  was on , and I turned it off last night before my two successful flights.

.

 

I hope you have found the probelm Bob. Nothing is more frustrating than CTD.

GL and keep us informed please.

11 minutes ago, Nyxx said:

I hope you have found the probelm Bob. Nothing is more frustrating than CTD.

GL and keep us informed please.

I think it was either the USB power save or Developer mode. Now it seems very stable. On a flight now into Anchorage. 

Edited January 31, 20215 yr by Bobsk8

5 minutes ago, Bobsk8 said:

I think it was either the USB power save or Developer mode. Now it seems very stable. On a flight now into Anchorage. 

Thats great to hear Bob, as I was really looking forward to you enjoying MSFS as imo its a VFR dream. I do now hope you can just relax and now start to enjoy the sim, IMO the best two aircraft are the carenado M20 and RY from Realair Bonanza mod.

10 hours ago, Bobsk8 said:

there must be quite a few faulty PC's out there

Seeing that you seem to have narrowed down your problem - and hoping you will have a stable running sim from now on - I can say that everyone reading this and having obscure CTD's ever so often should ALWAYS consider hardware (or the respective BIOS settings) first, especially when it comes to MSFS which seems to be running pretty stable inside its sandbox. I have built most of my rigs myself and the current one is the first - knock on wood here - without any issues so far, apart from once refusing to update Windows10 (solved with installing the next version on top of the existing one). However, every build had its minor issues, and the current one is very sensitive when it comes to the USB ports. It took some time to figure out which USB plug should go where in order for the system to run stable. Just plugging one USB device to another port results in the OS not recognizing some peripherals. So if you are having problems with MSFS - maybe a deeper look into your hardware could be beneficial.

Edited January 31, 20215 yr by Tom_L

11 hours ago, Bobsk8 said:

You would think it is a machine problem, but if you read the numerous posts on the MSFS forum on the Microsoft site , about CTDs, there must be quite a few faulty PC's out there, many of them top of the line rigs. A few people even went out and purchased brand new machines, and wound up with the same problems with the new rig. . 

LOL, of course there are... do you know how many ppl are computer iliterate and expect it to be like a tv, just turn on and watch? Smh,,.

Hi

understand how frustrating it must be. 

I have an overclocked PC from 2015  (i5 4690) and fly 1-2 hrs a day in MSFS mostly Ultra settings at 2k res.

I have a number of modded planes (TBM, CJ4..) and add on airports, and on a daily basis I have zero CTDs anywhere in the world. I typically fly up to 600 miles on a leg with no issues. So you can have a stable sim.
 

I recently reinstalled Windows (20H2) and MSFS from scratch. and installed a fast SSD, having had severe issues prior to that. I have a GTX 1080Ti which was the best purchase I’ve bought recently.

Whenever I have had CTDs in the past it’s usually been a result of a dodgy mod or something in my set up.

Provided you’re careful, and don’t expect too much, everything else being equal, you can have an amazing, immersive and CTD free experience in MSFS.

Is your new installation of Windows stable? What error messages were generated in the Windows Event Viewer? 
 

good luck 

Ray

17 minutes ago, rayharris108 said:

Hi

understand how frustrating it must be. 

I have an overclocked PC from 2015  (i5 4690) and fly 1-2 hrs a day in MSFS mostly Ultra settings at 2k res.

I have a number of modded planes (TBM, CJ4..) and add on airports, and on a daily basis I have zero CTDs anywhere in the world. I typically fly up to 600 miles on a leg with no issues. So you can have a stable sim.
 

I recently reinstalled Windows (20H2) and MSFS from scratch. and installed a fast SSD, having had severe issues prior to that. I have a GTX 1080Ti which was the best purchase I’ve bought recently.

Whenever I have had CTDs in the past it’s usually been a result of a dodgy mod or something in my set up.

Provided you’re careful, and don’t expect too much, everything else being equal, you can have an amazing, immersive and CTD free experience in MSFS.

Is your new installation of Windows stable? What error messages were generated in the Windows Event Viewer? 
 

good luck 

Ray

Looks like problem is solved. I think it was developer mode. I am even running Avliasoft EFB now, and now issues at all. 

Good to read Bob!

About those knobs and not touching them as I read in this topic: I just completed a first flight with the Boeing 747 and touched about any knob during flight to learn the AP. 🙂
I'm not going to say anything about the landing though... 😎

The number of CTD's can be counted on the fingers of one hand here. The last CTD was because of a rogue livery.

I've had a number of CTD's over the past few months, but I have also had some really nice flights. When it seems like things are stabilized, another CTD seems to pop up. To address those issues, I removed all CPU and GPU overclocks, The only overclock that remains is XMP1. This seemed to help quite a bit, and the loss in performance isn't too bad. I think this should be the first thing people should look at. 

In the past couple weeks I have completed a number of great flights in the FBW A320 with Navigraph data, but I had another CTD just before ToD when flying to SAEZ using the scenery that was recently uploaded Flightsim.to. Is it my system? Is it the new scenery? IS it something else? IDK Still, to address the CTD I had last night, I changed the USB power settings as suggested in this thread. I also went through my addons and renamed the duplicate file paths. I know this isn't necessarily a CTD fix, but it sounds like something that needs to be done anyway. 

I'll have to see if those steps make a difference, but I don't think there is a single answer. Like most sims, I think MSFS is just resource hungry, and it will exploit any weakness you have in your setup. It doesn't help that a ton of people have created scenery, but they didn't realize that you had to have unique files names (can't remember the details, but it has been mentioned everywhere). Had developers known this when the sim was released, we probably wouldn't have as many issues. In addition, I bet there are other issues like this that no one has discovered yet.

Edited January 31, 20215 yr by duckbilled

22 hours ago, MegaRiceBall said:

Turn your CPU, RAM & GPU frequency down by 500MHZ and see if it still crashes. If not, then you know why.

This made me laugh very loud.

Thank you so much.

 

17 hours ago, marsman2020 said:

or reduce the RAM from XMP to non-XMP settings, things start working for them

Memory has been the main cause for me in every build it seems.

Cheers

bs