sivart2000

With the later driver releases I was encountering more and more issues similar ro yours. Sometimes device hung, sometimes just a screen freeze that I had to use task manager to kill MSFS. I have a 3090ti. I have gone back to driver 566.36, stopped using the nvidia overlay and filters and most importantly I slightly underclocked and undervolted my GPU with MSI afterburner. 1)I think the newer drivers changed how memory was handled and MSFS didn't like it at the clock speeds I was running. 2)The overlay and filters seemed to hit my FPS and I would get increasing VRAM usage until about 2 hours into a flight when it would hit 100% and start getting stutters even though my FPS was still decent. 3)Underclocking was key. Only underclocked -150 but it worked wonders. No CTD or device hung messages since. 4)The undervolting was because I went from a RTX2080 to 3090ti without upgrading my PSU. I think this also contributed to the instability. Smooth sailing now with with mostly ultra settings, Beyond ATC traffic settings at 6. I can fly for hours with no degradation in performance, solid 50fps locked with frame gen at even busy airports. I HIGHLY recommend that you try underlock and undervolt at the very least. If you still have issues, go back to driver 566.36.

Had this issue since day one with MSFS and thought with one of the updates it would clear up, but it persists. If I end a flight and try to fly a new one using the same aircraft the loading freezes at about one third. It even happens if I restart the sim and try using the same plane as the one that was loaded when I shut it down. I've gotten in the habit of loading a different aircraft and different airport, without pressing fly, and then loading my actual departure airport and aircraft before I press fly. I also load a new airport and different aircraft, without pressing fly, each time I shut down. This keeps the freeze from happening 99% of the time. Its really getting quite tedious and was wondering if any of you have encountered the same issue and if you have found a solution? If you have never had this happen, no need to respond, please.

It looks like to me, because I did have the same issue, that it is a combination of MSFS, Nvidia drivers and the user end. I had all the latest drivers installed and ran DCS flawlessly. I kept running into more and more CTDs however in MSFS. Like I said, rolling back to an older driver eliminated about 80 percent of my crashes and they completely disappeared when I added an under volt. I did try the newest drivers with an under volt but I was getting a CTDs still. I know for sure that my VRAM usage went up with the newer drivers. My usage is pretty high anyway because I run 2.25xDL on my 3090ti with 24GB VRAM. But, with the 566.36 I'm at about 70% VRAM usage and the new drivers have me at 98-100% VRAM usage. I think this combined with the way MSFS handles memory plus my PSU being the minimum wattage (went from RTX2080 to RTX3090ti, 850w PSU) necessary to run my rig set me up for CTDs. All things you may want to look at.

Ok. You guys have a point, which is why I asked the question.

I get your reasoning. I think a more constructive response might be "I'm running ***.** driver and its working for myself and others" and then give some specifics on your system and settings. I think without context, the "mine runs fine" blanket statement seems a bit unhelpful when you are in the frustrating situation of troubleshooting an issue.

See, another one. In what way does this point the OP towards a possible solution?

I'm sure you mean no ill intent with your reply and are a well-meaning person. But, in general, a response like this to someone who is trying to solve a problem is not super helpful. Especially since no insight is provided on what exactly your setup and settings are. This type of response is very prevalent on discussion forums and I'm genuinely curious as to what exactly the point is. I'm seriously not trying to be a jerk.

Same here. My BATC was stuttering, screen would dim a little bit every once in a while, and constant CTD usually on descent or final and it got worse as newer drivers came out. It got to the point that I'd get a GPU out of memory and CTD when I changed a MSFS setting and then applied it. So, I underclocked and undervolted my GPU with MSI Afterburner just a tad (1.075 to .975mv, and -100mhz), went back to driver 566.36 and problem solved. I can now run 2.25xDL resolution (5160x2160), TAA, frame gen and locked at 50fps, BATC with traffic, no CTD. Butter. Still occasional CTDs after exiting a flight and clicking fly on a new one but at least I'm not in the middle of a flight. Its something you may want look into even if you've figure your issue out. You will see no performance degradation and in the very least your card will run cooler. I'm running a 3090ti btw.

Is it just my imagination? I used to fly a route, do a turnround then another, over and over without a restart in P3D. In fact, I did a solid 24hrs once with no issues. Seems that MSFS becomes more and more unstable with each turnaround. Functions or features of the aircraft, sim, or utility program will randomly stop working properly and performance diminishes for MSFS. I found the only thing to do so I don't waste time is to restart the sim after every flight which in itself is time wasting but at least I haven't invested 2 hours into another flight when it goes bad on me. Related but unrelated; does anyone know if its possible to fly a second route without completely restarting BATC? In other words, can a new simbrief route be loaded to BATC without restarting BATC?

I think you hit the nail on the head. I underclocked and undervolted and CTDs went away. Before that, it seemed CTDs got worse with every new driver.

Use MSI afterburner to underclock and undervolt your GPU a touch. I had same exact symptoms. There are a couple good tutorials on youtube. Worked wonders for me with no loss of performance and cooler GPU temps.

I have been battling this since around driver 565 ish. Constant freezes and CTD's, MSFS was unusable. After many months of trying and failing, I finally found a solution to make it playable. It seems for me, the new drivers kept using more and more VRAM and I was getting a slight momentary dimming of my monitor every few seconds, imperceivable during the day but could just make it out at night. Oh, and I never had any thermal issues. I theorized that the new drivers were demanding more of my 3090ti and since I hadn't upgraded my PSU when I went to the 3090ti, the power demand caused by the newer drivers was making the voltage unstable. I was also running x1.78DL upscaling. I found I got less CTD with native resolution and locked at 58fps. So, I went back to an older driver, 560.81, I used MSI Afterburner to underclock my GPU by 100mhz, undervolted from 1075mv to 975mv and dialed up the memory clock by 800mhz. I was running x2.00 resolution, TAA and running consistently with no more issues. As I started using the newer drivers to take advantage of the newer DLSS, I started encountering the memory issues again with high VRAM usage and CTD when applying changes to the graphics setting menu in MSFS. I would start a flight with 65% VRAM usage and then as I got close to my TOD, it would creep up to almost 100%, that's 24GB on the RTX 3090ti. My FPS would stay good but panning became stuttery. With the newest driver, to get this under control, I had to in addition to the undervolting, use x1.78DL upscaling and run it with TAA and downscaled to 70% and lock my frames at 40fps. Seems to work ok but a few months ago my sim was killing it. I would fly leg after leg with no issues. My ultimate solution will be: Underclock and undervolt Go back to 560-ish driver since I don't use DLSS. Looks bad and really buys me no extra FPS Run x2.00DL resolution and TAA downscaled 70% FPS locked at 40 Like I said, the newer drivers are allocating VRAM differently. I would check your usages, dial back FPS, and resolution if possible. if you aren't using DLSS, go back to the last driver that worked well and look at maybe undervolting and underclocking the GPU a bit if you still have issues.

Sensitive. You are actually probably right. However, your reply to my OP would have come across a little better if it said, " This is why I..." instead of "This is why you..." Sounds more like advice that way instead of scolding or bossy. Bonus, while my method was a bit more of a headache, I solved my problem in less time than a new install would have taken AND I learned a lot of new things about my computer system and software, So, glass half full. Yes, your way is more fool proof. Cheers

You're right. Installing a fresh windows and terabytes of P3D, MSFS, DCS and whatever else sounds a lot less time consuming.

So I've been putting off installing the windows 10 to 11 update but after a lot of reading and watching YouTube vids, it appeared pretty simple and trouble free. I finally did it this morning and as I feared, it f****** up a bunch of stuff. I first noticed my MSFS wouldn't start which led me down a rabbit hole culminating in Microsoft Store apps not updating or installing, firewall not starting and I'm sure to encounter other issues. Most everything else seems ok, it's the xbox app, which I uninstalled and now can't reinstall, Microsoft store, and gaming services. Losing my mind. Follow up many hours later: All my issues were caused by the firewall. In the services it was stuck "stopping". Found this: Windows Firewall 0x800706d9 - Microsoft Community Did this: Create a Restore Point. In the C:\ drive, create a folder named “Registry” — i.e., C:\Registry. Do not use any other folder name. Download firewall_fix_windows_11.zip (for Windows 11) firewall_fix_windows_10.zip (for Windows 10.) Save the .zip file to the desktop. Extract the four files from the Zip file to C:\Registry. From the C:\Registry folder, right-click “Run.bat” and choose “Run as administrator.” And rebooted. Firewall fixed, reinstalled gaming services and xbox app, up and running. What a nightmare.