My MSFS crashes all the time with this driver version 536.99…
i am using 3080Ti 32gb ram windows 11
have no clue what to do to fix this issue…
p.s. i managed to get into the game normally only one or two times…
Game has server problems at the moment
Glad it sorted out for you…
1 Like
I have no crashes but lags every 1/2 minutes for 20/30 sec :-/ It’s disgusting
1 Like
I installed it an hour ago and the sim didn’t like it at all. Couldn’t even start a flight as the map just froze. Rolled back to 535.98 and everything’s fine again.
The servers are down, see message. That could have been your problem
I’m using the previous version and it seems stable, may the server have been fixed. I am waiting for the stable version of the latest driver.
My simulator has started working without crashes with this new version, (touch-wood) of the driver. A lot of us get different results which makes fault finding harder.
Charles.
536.40 is still the absolutely best version for me (3060 Ti)
1 Like
MSFS beta SU13 - dx12 TAA Ultra settings - all good.
Increase virtual memory (pagefile).
1 Like
That I’m not sure of, haven’t used Reshade.
@sttovo - previous Nvidia driver versions would cause CTDs in MSFS if you were using Frame Generation and filters. For sure with Nvidia Filters, but not sure with Reshade as I haven’t used Reshade in MSFS before.
So can we confirm we are GOOD to go with FG/DX12 and Nvidia filters with this driver update? I’ve been using an ancient driver because I kept crashing with my filters…would love to update if this is confirmed fixed!
Thanks!! I did some testing tonight and found that at least for me, Reshade does cause Frame Gen to not work while flying. Once I uninstalled Reshade I got my 2x FPS back. Too bad. 
After updating the driver and installing the SU13beta I tried Freestyle filters for the first time.
When loading in the game (with the fenix A320) with the filter active I get a CTD as soon as i get to the cockpit.
If i start the game with filters off and wait till loaded into the cockpit and then activate the filter, it works.
But with the new driver i have white flickers regardless if filters are applied or not.
I have not seen these flickers before bit cant tell if it is the driver or the SU13beta…
Reshade should certainly not effect FrameGen. The problem in the past was Reshade could conflict with MSI Afterburner. Not sure if that is still the cause of crashes.
Don’t know if you know that you can use Reshade shaders in nVidias Freestyle. That’s what I do.
Not had any crashes since the new driver (admittedly I need to do a lot more testing to say for sure it’s fixed)
1 Like
Have you tried turning Bloom off?
1 Like
Thank you for the advice.
I turned off bloom and could start a flight with filters on.
So it looks like that helped.
Hi TenPatrol, I have set my swap file set to allow Windows to handle it. I have managed to get out of the the cycle of CTD’s with the simulator. It appeared to be Canada that was inflicted with CTD’s! I made no changes to my default Nvidia driver profile after installing 536.99 and I can fly again. I could fly from EIDW but not CYYC or CYVR. I have an inkling that, if I change a setting in the NVCP, I will get crashes within the sim. I will test my theory later. Unfortunately I have a problem with the computer, it shuts down abruptly without warning. The first time it happened, I thought it was a power cut.
BRGDS
Charles.
1 Like
So just to be transparent, when I posted above that the latest Nvidia driver works with Filters and Frame Gen = ON, that was before SU13 beta. I haven’t tried it yet.
1 Like
Anyone else using Oculus Quest Link (AIR)?
The only thing on my system that has changed is the driver, and now every time I connect over the Air Link immediately MSFS starts hitching every second or two like a heartbeat. I don’t even need to put MSFS into VR mode. I can just sit at the main menu in normal 2d mode. Soon as I connect AirLink bam problem starts, and soon as I quit it MSFS goes back to smooth.
EDIT: Rolled back to previous drivers and same issue now. I have NO idea what is going on.
Switch over to SteamVR and use Virtual Desktop and it works perfectly