CTD after about 35 minutes - upgraded from 531.61 and used identical in game settings.
i9, 3060, 32gb etc
Only reason I upgraded was I heard things were fixed and MSFS showed me some message upon start that looked promising “driver out of date” or something like that.
I feel like I’m going to roll back and never upgrade my driver ever again.
I wasn’t even playing on VATSIM or anything - just a solo flight. Typically I play online and have tons of other a/c present… sigh
I rolled back to the last driver and it made no difference.
From silky smooth in VR a few weeks ago to now the menus in flat screen causing crashes and stuttering.
Well done to those who get a fix from the NVIDIA driver change. I got nothing at this stage.
The NVidia driver releases post 40 series cards are a continuing series of glitchy hot messes.
I’ve had to roll back to 528.24 to get stability not just in MSFS but also Windows 11.
If I use 528.24 it’s smooth, no CTD in MSFS or Windows 11. With anything beyond that I get varying degrees of MSFS CTD’s or Windows 11 Hypervisor BSOD’s (which are typically driver related).
Intensity varies, some it might cause one every couple of days, others up to 4 times a day.
The cause has most definitely been narrowed down to NVidia drivers, as rolling back to 528.24 resolves all the issues. Except now AAU 2 tells me:
I have downloaded 536.23 , will test it later but not holding high hopes given the signs in this thread are again variable.
Also, as I use my machine as an audio workstation too " * Increase in DPC latency observed in Latencymon [3952556] :" doesn’t give me confidence either.
They have really burned the quality barn down with this series of drivers.
I too saw this message after the aau2 update…never had any issues before and using 531.29 on a rtx3070…
do i upgrade to the latest or ignore…wonder if problems will arise if i stay on the older very stable driver…
either way…dont like how asobo/ms changing code to force messages like this to come out on what was deemed a very stable build.
I ignored it. I am quite happy staying on 531.29.
I was using 531.29 for a while, then it started giving me the MSFS CTD’s and WIndows 11 BSOD’s. 4 BSOD’s in one day once. I went back to 528.24 and it’s back to stable.
Edit: Testing 536.23 now, did some system checks beforehand.
I received the same warning and chose to disregard it. During the installation, a crash occurred, but I attempted the process again. The second attempt proved successful. Until NVIDIA or Microsoft resolves the issues that have arisen, I will continue to use the last stable driver, version 528.49.
Yes I have the same one and it is super stable
I took a different approach this time.
I did a “Deployment Image Servicing Scan” on on Win 11 first to ensure the system was 100% ok first.
DISM.exe /Online /Cleanup-image /Restorehealth
Now running on 536.23, ok so far will see. I hope I didn’t just jinx it by saying that!
The only other thing I’ve done is update to the latest DLSS dll via NVIDIA DLSS DLL 3.1.13 Download | TechPowerUp
Will see.
Personally I think audio issues need to be examined more. After installing MSFS almost 3 years ago (!) I was experiencing a lot of CTDs at random times many of them were the infamous TDR error that NVIDIA never seemed able to fix. Checked all of my drivers and discovered the default Windows audio driver was dated BEFORE Windows 10. I contacted the MOBO manufacturer for an update which they provided. It was an audio driver made by the audio hardware manufacturer, not the Windows default one.
CTDs decreased to almost zero and recently started increasing. A few months ago I upgraded my NVIDIA driver including the NVIDIA audio driver (Yes, I know. NVIDIA bloatware). Somehow, everything sounded differently. I checked my audio configuration and found the NVIDIA audio driver was connected to my monitor’s speakers (which are horrible) and these speakers were made my default audio device. The Windows driver connected to my external speakers was disabled.
I don’t remember making these changes but I’m not accusing NVIDIA. I was going to reconfigure my audio subsystem but noticed CTDs practically disappeared. Since leaving the audio subsystem in place, I’ve had maybe two CTDs. This is purely anecdotal and could simply be an anomaly. I don’t know but my MSFS life has been MUCH better! And I’m not recommending this as a workaround or a fix. YMMV
It is very easy to look at the MSFS graphics as the source of many if not most of our problems. However, MSFS sound is VERY important! Between the engine sounds ATC, and whatever other audio app we use, there is a LOT of “stuff” that has to be processed by the CPU and MSFS HAS to keep the audio and graphics synchronized. I speculate that some of the TDR crashes are because sometimes the synchronization gets out of sync.
Our PCs are like a symphony orchestra. All the instruments have to be present and play correctly with all the other instruments. Otherwise everything sounds awful. In addition, instruments have to know the music and play together correctly whenever there is a new Conductor (like MSFS).
Guys.
I noticed that after updating to 536.23, my graphics are WAY LESS SHARP (I play at 2560x1440p)
It happened some updates ago too, but was fixed some time later.
Now it happened again.
Anyone?
Just had my first CTD ever. The sim started loading, got through the ‘Launching’ count up, then crashed. Restarted and got the "Safe Mode or Normal Mode?’ question, with a message that it might be a problem with an incompatible driver. I’m going to uninstall 531.29 
and install 536.23
We’ll see what happens.
I’m still on 536.2
Uninstalled NVidia USB and Audio drivers, which seem to have stabilised the Windows CTD’s somewhat, but still getting occasional MSFS CTD’s now, especially when switching with alt-enter between windowed and windowed borderless. If you catch it at the wrong time it really doesn’t like it an instant CTD.
It also seem really twitchy with Google chrome open, seems they compete for Ram at times, and chrome can cause MSFS to CTD.
Turn off hardware acceleration in chrome, there is some kind off conflict there.
No kidding, should have done that sooner. Thansk for the reminder!
Hey,
Wondering if you might be able to help with this. I have been having constant ctd’s with the latest nvidia driver. The event viewer has shown that it is the same as you ( ucrtbase.dll ) I have the exact same system specs as you too.
I note you say you are able to run the latest driver with the CTD now, Could you possibly tell me what i am missing to avoid the crashes? I have even gone as far as reformatting my pc and a fresh install of the sim but there was still the CTD there.
Would really appreciate some help 
Sorry for the late response:
-When I uninstall older drivers, use Display Driver Uninstaller
-When I reinstall drivers, I DO NOT install Nvidia Experience. I also do a custom install to only install Physics and the driver
Below is part of my user.cfg settings:
-Adapter “NVIDIA GeForce RTX 4090”
Monitor 0
Windowed 1
FullscreenBorderless 1
WindowActive 0
Resolution 2560 1440
FullScreenResolution 2560 1440
PosX 0
PosY 23
AntiAliasing DLSS
DLSSMode DLAA
DLSSG 1
Reflex ON
FSRMode BALANCED
PrimaryScaling 1.000000
SecondaryScaling 1.000000
SharpenAmount 1.000000
ReprojectionMode 0
WorldScalePercentVR 100
AntiAliasingVR TAA
DLSSModeVR AUTO
DLSSGVR 0
ReflexVR ON
FSRModeVR PERFORMANCE
PrimaryScalingVR 0.800000
SecondaryScalingVR 1.000000
SharpenAmountVR 1.000000
VSync 0
HDR10 1
Raytracing 1
PreferD3D12 1
IntelMessageBoxDisplayed 0
CurrentGPUDriverVersion 536.40.0
DoNotShowGpuDriverRequirementPopup 0
Just so you know. I do not rub 4k, only 2k
Additionally, I run all cores at 5.7ghz and my 4090 is below:
I have since installed 536.40 which performs so much better.
Hope this helps
