Here's the Event Viewer log for two crashes:

Faulting application name: FlightSimulator.exe, version: 1.22.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.22.2.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001b22bba
Faulting process id: 0x1894
Faulting application start time: 0x01d81e60af50f875
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: a5a44757-89a2-42e8-9360-276d1ab5e340
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: FlightSimulator.exe, version: 1.22.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.22.2.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000213a886
Faulting process id: 0x37c4
Faulting application start time: 0x01d81ecb351640af
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: 4866e238-27ae-4ed2-a41c-658ff3ef1110
Faulting package full name:
Faulting package-relative application ID:

I tried the process given here: https://forums.flightsimulator.com/t/ctd-fix-info/471880. That fixed 3 files but CTDs continue.

I have also tried older and newer nVidia drivers but again, CTDs continue.

Cheers,

Noel.

Have you create an exclude folder / process for msfs in your antivirus ?

Since i did that l have less ctd.

Crashes in MFS were never a big problem for me, but there were a few episodes when I was still in Win 10.

After migrating to Win 11 and DX12, and now DX11, I only had one crash associated with a button assignement to "move camera back / forth" that caused a CTD on almost all single engine aircraft. It turned out to be an assignement to a pair of my T16000 buttons I had previously assigned to "right throttle increase / decrease".

Without wanting to sell the idea that going Win 11 is a better option for anyone, all I can say is that since I migrated to Win 11 I really don't look back. It's probably my preferred Windows release so far since Win XP...

I bought a new PC from Jetline. I spent a ton of money on it and I kept getting crashes. I reached out to them over and over again and they kept blaming it on the fact that MSFS isn't "stable". It turned out that there was a ram setting in the BIOS that was turned on that shouldn't have been. Once I turned that off, I never got another CTD. I wish I remembered what that setting was because it was a while ago, but from what I can remember, it was one of those BIOS settings that was trying too much, when in reality, its better just to turn it off. 

I know this isn't much help. But maybe do a search about ram settings in the BIOS and that might help. It helped me. I cant say I was too impressed with Jetline, considering the money. 

10 hours ago, Bdub22 said:

I bought a new PC from Jetline. I spent a ton of money on it and I kept getting crashes. I reached out to them over and over again and they kept blaming it on the fact that MSFS isn't "stable". It turned out that there was a ram setting in the BIOS that was turned on that shouldn't have been. Once I turned that off, I never got another CTD. I wish I remembered what that setting was because it was a while ago, but from what I can remember, it was one of those BIOS settings that was trying too much, when in reality, its better just to turn it off. 

I know this isn't much help. But maybe do a search about ram settings in the BIOS and that might help. It helped me. I cant say I was too impressed with Jetline, considering the money. 

Likely XMP

Funny thing is it is hit & miss whether or not it works. I have (2) XMP profiles in my BIOS and neither causes any issues.

22 hours ago, Virtualwombat said:

Here's the Event Viewer log for two crashes:

Faulting application name: FlightSimulator.exe, version: 1.22.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.22.2.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001b22bba
Faulting process id: 0x1894
Faulting application start time: 0x01d81e60af50f875
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: a5a44757-89a2-42e8-9360-276d1ab5e340
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: FlightSimulator.exe, version: 1.22.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.22.2.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000213a886
Faulting process id: 0x37c4
Faulting application start time: 0x01d81ecb351640af
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: 4866e238-27ae-4ed2-a41c-658ff3ef1110
Faulting package full name:
Faulting package-relative application ID:

I tried the process given here: https://forums.flightsimulator.com/t/ctd-fix-info/471880. That fixed 3 files but CTDs continue.

I have also tried older and newer nVidia drivers but again, CTDs continue.

Cheers,

Noel.

Be sure the MS store app/s are up to date.Even though you're on Steam the sim still requires certain apps to be current. Apps could include MS Game Services, XBox app etc...

Do an integrity check of the sim within Steam last. And be sure and do 'ALL' the steps I linked to.