After recent MSFS update, every of my VR flights ended up in CTD (crash to desktop) after around 30 minutes. I have confirmed that I can fly the same flight in 2D 4K with similar or even higher settings for hours no problem. So this is specific to VR.

I have rolled back NIVIDIA drivers to what MSFS recommended, cleared cache, uninstall/reinstall WMR, and testing flights in safe mode. Nothing solves the CTD, although after all these measures it appears I could fly a bit longer in VR until CTD. MSFS actually runs beautifully in VR at 35-40 fps, then all of sudden my HP G2 gets blank out, the PC freezes up for few seconds followed by a complete CTD of MSFS. 

My PC is 7950X3D/32GB/RTX4090, Win11 and MSFS were all fresh installed when I built this PC six months ago. Although occasionally I got CTDs, but never had such guaranteed CTD in VR before, sth mush have happened in recent MSFS updates I'd guess. 

Does anyone have similar CTD problems recently? It's really frustrating to figure out why and how.

 

last msfs flight for me was two days ago, but everything went well. Ive had similar in the past usually solved by doing below.

Are you using opencomposite or openxr toolkit? If so, you could try removing them temporarily.

installing the very latest amd chipset driver from amd's website? (not microsofts suggested equivalent)

a sudden drop in power via the usb port causing g2 to crash. Changed windows power settings.

is the headset cable fully pushed into the headset

if you get it sorted, and havent yet tried using HAGS, turning it on might now give you even better smoothness than before. Something about it has been fixed for amd users 

Edited August 29, 20232 yr by dogmanbird

17 hours ago, FlyIce said:

After recent MSFS update, every of my VR flights ended up in CTD

Look in the Event Viewer and see what module is crashing. It may provide some insight into the cause. I sometimes get NTDLL.dll crashes after updates which can be cause by a file corruption. There's a fix for that. 

Edited August 29, 20232 yr by odourboy

thank you for all your suggestions, really appreciated! So far nothing I tried worked. Any, by making 2D flight longer I found it also ended in CTD ("..memory could not be read..") after 70 minutes. I kind of run out of options. I hope MSFS2020 future updates will eventually fix the problem. Or, at the worst, MSFS2024 is on the horizon... 

Edited August 30, 20232 yr by FlyIce

There's some info of similar issues in this thread if you haven't yet seen it

https://forums.flightsimulator.com/t/msfs-application-error-memory-could-not-be-read/510977/44

Clearing or increasing the windows paging file size might be a fix

might be caused by an unlucky combination of flight location, aircraft and the gps module?

 

Edited August 30, 20232 yr by dogmanbird

thanks! I found that page a few days ago too. It has 1600 posts and took a lot of time to read.. 💀

Many potential fixes suggested but I haven't seen a sure "fix". This is really frustrating and I'm afraid that only Asobo can eventually fix it, if ever.

 

 

Just want to add that my overall experiences over last few days strongly suggest that the recent CTD is mostly sensitive to graphics settings. For instance, last night I flew NYC helicopter tour in VR with all the ultra/high settings I had before, and the sim crashed in 7 minutes. I then did one change that is reducing TLOD from 400 to 200, I was able to flew 30 minutes, landed and exit flight no problem. 

It's like the sim has a limit in terms of how much data/scenery/content it can process in total. The higher the settings, the sooner it will reach that limit and CTD. The interesting thing is that I only had CTD occasionally before recent update with same ultra/high settings, while now CTD is guaranteed after certain amount of time in flight, regardless 2D or VR.

So either the new update lower the "limit", or at the same settings more stuff get processed in the updated sim during the flight so the limit reached much quicker. Luckily I do mostly short GA flights, rarely more than an hour, so I might be able to live with such CTD if TLOD=200 is the only sacrifice to make. 

just for testing purposes, could you try setting you bios to its defaults (not xmp or any performance modes) and see how it goes?

https://forums.flightsimulator.com/t/vr-ctd-without-event-log-when-pressing-buttons/408435

 

Ok, I have tried both, keep 2D window maximized and reset my ASUS motherboard BIOS to default. I still get CTD.

Since I now can fly a bit more than than 1 hour before CTD, I'll just live with it, while hoping the next update will get better. 

Just to update, no good news though. I noticed that I had mistakenly installed notebook version of Nvidia driver, so I used DDU to do clean uninstall, reinstalled the latest desktop driver but overall not much difference. After anywhere between 20 minutes to littler over one hour of flight the sim will just sudden CTD. If SU13 still doesn't solve the issue, I may reinstall the MSFS as the last try. 

Edited September 15, 20232 yr by FlyIce

6 hours ago, FlyIce said:

Just to update, no good news though. I noticed that I had mistakenly installed notebook version of Nvidia driver, so I used DDU to do clean uninstall, reinstalled the latest desktop driver but overall not much difference. After anywhere between 20 minutes to littler over one hour of flight the sim will just sudden CTD. If SU13 still doesn't solve the issue, I may reinstall the MSFS as the last try. 

Since you're desperate, try this procedure. Not likely, but possible and there's no downside. It's helped me with CTDs!

Open a Command Prompt - Run As Administrator

Run the following commands…

Go through each of the following steps one at a time. Copy each line, one at a time , paste it into the Dos window (crtl + V) and press return and it will then run. Wait until each runs and finishes before you move on to the next one.

When you are completely finished, Restart your computer and then try to see in MS2020 will start and run properly

• Dism.exe /online /Cleanup-Image /checkhealth
• Dism.exe /online /Cleanup-Image /scanhealth
• Dism.exe /online /Cleanup-Image /Restorehealth
• sfc /scannow
• Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
• Dism.exe /Online /Cleanup-Image /StartComponentCleanup

RESTART your computer as the last step. Then go for a test flight.
 

Edited September 15, 20232 yr by odourboy

On 9/15/2023 at 5:34 PM, odourboy said:

• Dism.exe /online /Cleanup-Image /checkhealth
• Dism.exe /online /Cleanup-Image /scanhealth
• Dism.exe /online /Cleanup-Image /Restorehealth
• sfc /scannow
• Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
• Dism.exe /Online /Cleanup-Image /StartComponentCleanup

RESTART your computer as the last step. Then go for a test flight.

Thanks! I read about these commands before but this is really convenient that you list them all here step by step. I ran each of these commands in order and none gave any error messages. I restarted computer, ran the exact KLGA - KDCA flight in VR and it crashed just shy of 2 hours. While this is much longer than my previous record of 1.2 hours, it could just be a fluctuation in this random CTD business. 

But by all means, thanks for the help!

13 hours ago, FlyIce said:

While this is much longer than my previous record of 1.2 hours, it could just be a fluctuation in this random CTD business

Oh well.. at least you tried. I share your frustration and hope you manage to sort this out.

Thanks. I'm curious if anyone else here also has this CTD problem in VR, or I'm the only one suffering?