1 hour ago, Bobsk8 said:

BTW. whatg was the name of that Nav file that was corrupted after the "Fix" that Asobo did a couple of weeks ago. I forgot the exact name of it. ? 

BTW, this problem that I had at KATL this morning appears to be something wrong with that Airport. Just started a flight from KPDK which is 12 miles away with zero problem. KATL is now marked as a " No Fly Zone" on my monitor. 

I have considered scenery issues. Some of my crashes are indeed closely together, but some are far away from land. my previous testroute was between Sweden and the UK, and I often crashed somewere above the North Seam far away from airports. My current testroute is in the west of the USA . It might be scenery related still, but why then does it not crash there without USB controllers?

Without USB controllers, I sometimes make it all the way to destination (3-4 hours), or at least much further along the route. With USB controllers, I crash usually after 30-60 minutes. Without traffic I have more chance to get further enroute before a CTD occurs.

It's almost as if the chance of getting a CTD increases with time and is accelerated when using USB controllers. I might try the same flight but with a faster aircraft (sofar mostly trying GA), or use 2x-4x sim rate and see how far I can make it.

Stop troubleshooting in the dark. Windows generated an event in Event viewer when you CTD. Let's start with that. Please copy paste to us the error. 

4 minutes ago, Will Fly For Cheese said:

Okay - stop trying (word not allowed).

When you CTD - just before you do - do you get a slow down in Frames?

Or does it come out of the blue?

I haven't noticed a slow down in frames, but just before a CTD occurs there is a stutter in audio. I tried the ATC audio settings (from Azure to offline to off) but no difference.

3 minutes ago, orchestra_nl said:

I haven't noticed a slow down in frames, but just before a CTD occurs there is a stutter in audio. I tried the ATC audio settings (from Azure to offline to off) but no difference.

Are you running MSFS2020 on the same Drive as your Main Windows Install Drive?

2 minutes ago, fogboundturtle said:

Stop troubleshooting in the dark. Windows generated an event in Event viewer when you CTD. Let's start with that. Please copy paste to us the error.

You mean like this:

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6038d404
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6038d404
Exception code: 0xc0000005
Fault offset: 0x000000000012280a
Faulting process ID: 0x32ac
Faulting application start time: 0x01d714501b3f0204
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 53e6cb04-2123-44c8-aae2-d8dd1c1a1302
Faulting package full name: Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

All CTD's are like this, even on different hardware the event is the same.

2 minutes ago, orchestra_nl said:

You mean like this:

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6038d404
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6038d404
Exception code: 0xc0000005
Fault offset: 0x000000000012280a
Faulting process ID: 0x32ac
Faulting application start time: 0x01d714501b3f0204
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 53e6cb04-2123-44c8-aae2-d8dd1c1a1302
Faulting package full name: Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

All CTD's are like this, even on different hardware the event is the same.

ok this is a hard one. The only way to really get an answer is to open a ticket with Asobo. There is no indication where the crash occurred.  Normally, I see an DLL that points us in the right direction. Disconnecting USB devices would be the most obvious culprit.

Exception code: 0xc0000005

That's a Memory Access Permissions Error - dependant on the rig it's being run on.

I don't believe that you get that every time when you say you've tested across multiple rigs.

HOWEVER; If you get this as the main stay then I have a couple of suggestions; I see you've got 32 Gig of RAM but it might be that you need to push that up in VRAM if the speeds are low (or, just not playing right with the Caches on the AMD)

Are you O/C'ing?

 

Edited April 9, 20215 yr by Will Fly For Cheese

4 minutes ago, Will Fly For Cheese said:

Are you running MSFS2020 on the same Drive as your Main Windows Install Drive?

Not on my main rig. I am using a seperate NVMe drive there. On the same rig I have a 2nd windows installation on a SATA SSD. There, MSFS  is on the same SSD. There, MSFS CTD's during startup of MSFS unless I cancel loading syncing the settings from the cloud.

On the business laptop and the 2 other machines I used the same drive as Windows since I only have 1 SSD there.

Do you think changing the location of MSFS to other than default might make it run unstable?

Did you do all of your windows update ? Open the MS Store and check if there is any store update pending

6 minutes ago, orchestra_nl said:

Not on my main rig. I am using a seperate NVMe drive there. On the same rig I have a 2nd windows installation on a SATA SSD. There, MSFS  is on the same SSD. There, MSFS CTD's during startup of MSFS unless I cancel loading syncing the settings from the cloud.

On the business laptop and the 2 other machines I used the same drive as Windows since I only have 1 SSD there.

Do you think changing the location of MSFS to other than default might make it run unstable?

Are you Overclocking?

27 minutes ago, Will Fly For Cheese said:

Exception code: 0xc0000005

That's a Memory Access Permissions Error - dependant on the rig it's being run on.

I don't believe that you get that every time when you say you've tested across multiple rigs.

You are right, it is not exactly the same. The exception is the same, but the timestamps are different:
This is what I get on my business laptop (it has only 16GB of ram)

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60420f33
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60420f33
Exception code: 0xc0000005
Fault offset: 0x00000000005a0fdc
Faulting process ID: 0x43b0
Faulting application start time: 0x01d72bbf49e97151
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.6.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.6.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 8508d42e-f9c1-4254-8003-aa01effc2d32
Faulting package full name: Microsoft.FlightSimulator_1.14.6.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Quote

HOWEVER; If you get this as the main stay then I have a couple of suggestions; I see you've got 32 Gig of RAM but it might be that you need to push that up a bit if the speeds are low (or, just not playing right with the Caches on the AMD)

What do you mean by 'push that up'? do you advice adding more ram, or increase the speed?
I was thinking of upgrading my RAM to 64GB (HWinfo shows 0.4% virtual memory use) which could help mimimise stutters, but at the moment stutters isn't my main issue, unless you think the CTD's also could be caused by having only 32GB of RAM.

I did do a Windows memory check, which found no errors. There are more thorough ways to check the RAM modules, but if it was a case of bad RAM, I would expect MSFS to run without CTD's on my other machines, or at least lead to different error messages.

About overclocking: I was using the default PBO settings but even with this completely turned off, as it is now, I get these CTD's. RAM is using the XMP settings, but also tried 2133 Mhz which didn't make a difference. I also disabled PCIe 4.0 which supposedly solves USB issues on AMD until their patch is available.
I haven't overclocked my GPU either. I did try to undervolt it and even lowered the clockspeed to see whether that would lead to less CTD's but to no avail.

Edited April 9, 20215 yr by orchestra_nl

Umm, we'll come back to what I mean when I say "Push That up" I'm talking about VRAM not physical. Leave that alone for now.

Could you do a simple experiment for me?; I want you to disconnect all USB Interfaces except Keyboard/ Mouse and the Fulcrum - you should still be able to fly.

Try a flight and report back.

38 minutes ago, fogboundturtle said:

ok this is a hard one. The only way to really get an answer is to open a ticket with Asobo. There is no indication where the crash occurred.  Normally, I see an DLL that points us in the right direction. Disconnecting USB devices would be the most obvious culprit.

I have already filed two tickets sofar, one in September and one in February. I received their standard troubleshooting guide. Tried all their suggestions. At first, completely removing the sim and reinstalling seemd to help: the first three longer flights(France to Sweden) went fine. Then I flew from Sweden to the UK and the CTD's were back.
Come to think of it, Most CTD's occur in area's that have received the 'World Update' treatment. Off course I am not the only one with issues in these area's, but 95-100% of CTD's seems excessive.

7 minutes ago, Will Fly For Cheese said:

Umm, we'll come back to what I mean when I say "Push That up" I'm talking about VRAM not physical. Leave that alone for now.

Could you do a simple experiment for me?; I want you to disconnect all USB Interfaces except Keyboard/ Mouse and the Fulcrum - you should still be able to fly.

Try a flight and report back.

Good suggestion. Will do that tomorrow though, need some sleep now.

Me too.

Check it out in the morning and report back here.