I just want to reply to let everyone trying to help me know that I am trying every suggestion made in this thread:

• Update graphics driver
• Windows 11 fully updated
• Community folder emptied
• Took out 'fast' setting in NVIDIA Control Panel
• Disabled G-Sync in NVIDIA Control Panel
• Removed all CPU and GPU overclocks
• Went into Device Manager and disabled all USB Root Hubs from being able to be powered down
• Hardware acceleration turned off.

The USB hub change is the last thing I did so I will test some more and report back.

5 hours ago, Rob G said:

I have read multitudes of things on the internet about resolving it but so far, nothing has worked.

Including the TDR Registry tweak?

7 minutes ago, Emerson67 said:

Including the TDR Registry tweak?

I don't know that one. Can you point me to info or explain? Thanks.

 

UPDATE: I looked it up and just did it. We will see LOL.

Edited October 26, 20214 yr by Rob G
Updated info

You MUST restart the computer after changing TDR delays!

 

44 minutes ago, Rob G said:

I don't know that one. Can you point me to info or explain? Thanks.

https://substance3d.adobe.com/documentation/spdoc/gpu-drivers-crash-with-long-computations-tdr-crash-128745489.html

https://www.softpedia.com/get/Tweak/Registry-Tweak/TDR-Manipulator.shtml

"TdrDelay

Specifies the number of seconds that the GPU can delay the preempt request from the GPU scheduler. This is effectively the timeout threshold.

The default value is 2 seconds.

TdrDdiDelay

Specifies the number of seconds that the OS allows threads to leave the driver. After a specified time, the OS bug-checks the computer with the code VIDEO_TDR_FAILURE (0x116).

The default value is 5 seconds."

https://docs.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys

My settings (hexadecimal values):

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers]
"TdrDelay"=dword:0000000a
"TdrDdiDelay"=dword:00000019

Decimal:

TdrDelay= 10 seconds

TdrDdiDelay= 25 seconds

Edited October 26, 20214 yr by Emerson67

6 hours ago, Rob G said:

I had not used it for several weeks, but yes it was working with Windows 10. However, I do not want to roll back as I am enjoying Windows 11. I just used DDU to completely remove all graphics software and then reinstalled the latest Nvidia software fresh. Have to test now to see if will make any difference.

 

6 hours ago, Rob G said:

Well, I used GeForce Experience to identify and install the latest driver. I would assume that app knows what I am supposed to have, wouldn't it?

Disregard ...

Edited October 26, 20214 yr by Maxis

Well now the list of things tried includes the TDR registry tweak. After I restarted the machine I restarted MSFS and just let it sit on the main menu screen without doing anything. It sat there for about 15-20 minutes and then crashed again the same way, exception code 5 in FlightSimulator.exe.

I don't have anything left to do unless someone has any suggestions.

Well I give up. It has become virtually impossible to use the app as it won't stay running long enough to do anything with it. I guess I will just bench it for a while and play Oculus VR games where at least I can have some fun instead of doing hours of diagnostic work every day with no success. Still hopeful either Asobo will fix something or one of you will have a winning idea.

Does (or did) this kind of nonsense go on with Xplane. I've never even seen xplane; I was just wondering. 

1 hour ago, Rob_Ainscough said:

From cmd prompt (run as admin):

sfc /scannow

If it reports any errors and fixes or doesn't fix, run it again until no errors.  If sfc errors persist then run DISM.  DISM options info here.

from cmd prompt (run as admin):

DISM /Online /Cleanup-Image /CheckHealth

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

Now download Prime95.  Run for 30 minutes and check to see if you have any errors and/or system instability.

I'm not saying this will fix your problem, as I've had CTDs in MSFS also even in a clean no DLC install (on 3 very different computers all tested out and stable).  But I CTD less often (maybe once every 2 weeks).

Cheers, Rob.

sfc /scannow did not find any errors.

11 hours ago, cianpars said:

1. Empty Community folder.

2. Ensure video driver up to date.

3. Download and install latest chipset drivers.

4. Check Device Manager to make sure all other drivers are up to date.

After doing all of this and assuming all windows updates have been done, consider downloading and flashing the latest BIOS for your MOBO.

Good luck because an uninstall of msfs and maybe a fresh Windows reinstall comes next.

CTD are rarely solved by uninstalling MSFS in my opinion, except when you leave it uninstalled. Fresh install of Windows can often help off course.

I've had CTD on literally every flight >30 minutes since lauch until a least May or June. My quest for a solution led to the number of connected USB devices being the cullprit; Without controllers I could mostly finish a flight, mostly flown by the AI pilot. Add a yoke and I could go quite a long way before a CTD would occur. The more USB devices were connected, the sooner the flight would end in a CTD.

It wasn't caused by a single USB devices nor by USB hubs. In fact, it was repeatable on four different computers with the only common factor these USB devices.

That led me to a possible cause: the controller profiles, since they are restored from the cloud even after reïnstalling MSFS and installing it on different computers.
Manually cleaning out the obsolete controller profiles from my MSFS profile folder did much to reduce the CTD's. The SU updates and driver updates from AMD did most of the rest.

I still have the occasional CTD. Some are clearly scenery related but once in a while I still exceed the resources on my PC
I have collected hundreds of CTD's for MSFS and nearly always the error code is xc0000005. Since so many have the same errorcode I think it doesn't point at a specific problem, unless that problem is MSFS itself.

Edited October 26, 20214 yr by orchestra_nl

I remember seeing a thread on msfs forums about msfs loading capture one files which causes ctd. I don't have capture one, but I do have Adobe creative cloud and a file called coresync_x64.dll from my Adobe folder was loaded with the FlightSimulator.exe process. Don't know why it's loaded but I renamed. 

So you guys might want to check the performance tab to see just what processes are being loaded with the sim, because those might be the cause 

When all else fails, go back to W10. 

5 hours ago, Bobsk8 said:

When all else fails, go back to W10. 

Can't go back easily. Rollback is only available for 10 days and I am past that. My backups are only saved for 14 days so I don't have a Windows 10 backup to restore.

6 hours ago, orchestra_nl said:

CTD are rarely solved by uninstalling MSFS in my opinion, except when you leave it uninstalled. Fresh install of Windows can often help off course.

I've had CTD on literally every flight >30 minutes since lauch until a least May or June. My quest for a solution led to the number of connected USB devices being the cullprit; Without controllers I could mostly finish a flight, mostly flown by the AI pilot. Add a yoke and I could go quite a long way before a CTD would occur. The more USB devices were connected, the sooner the flight would end in a CTD.

It wasn't caused by a single USB devices nor by USB hubs. In fact, it was repeatable on four different computers with the only common factor these USB devices.

That led me to a possible cause: the controller profiles, since they are restored from the cloud even after reïnstalling MSFS and installing it on different computers.
Manually cleaning out the obsolete controller profiles from my MSFS profile folder did much to reduce the CTD's. The SU updates and driver updates from AMD did most of the rest.

I still have the occasional CTD. Some are clearly scenery related but once in a while I still exceed the resources on my PC
I have collected hundreds of CTD's for MSFS and nearly always the error code is xc0000005. Since so many have the same errorcode I think it doesn't point at a specific problem, unless that problem is MSFS itself.

Where is the MSFS profile folder. Your suggestion is worth trying. Thanks.

5 hours ago, Mrmention said:

I remember seeing a thread on msfs forums about msfs loading capture one files which causes ctd. I don't have capture one, but I do have Adobe creative cloud and a file called coresync_x64.dll from my Adobe folder was loaded with the FlightSimulator.exe process. Don't know why it's loaded but I renamed. 

So you guys might want to check the performance tab to see just what processes are being loaded with the sim, because those might be the cause 

Thanks. I will look into that as well.