Don’t know what you mean. The WMR update was released on 24.03. via Windows Update.
You find it in „recently updated“.
No need to install it manually via the Microsoft development website.
1 Like
So that doesn’t solve the CTD problem, because since 03/23/2021 I’ve had a whole collection of them.
Exactly, I didn’t‘ know anything about the update before yesterday. I had it already installed since 24.03. and got the normal amount of CTD within the last days.
I have 64GB of DDR4 3600 Corsair Vengence installed and set my pagefile to 96000 - 196000 and I stillg et CTD’s so I think it’s not the RAM size. Or at least not in my case… Who knows.
So after my last post where I thought I’d have found a sollution I still get CTD’s pretty regulary.
I have no found one thing that works 100%. I use my Oculus Rift S and no CTD’s at all. I know that was mean to rite it like this 
So my opinion is there is a problem on the HP reverb G2 side and I don’t feel like troubleshooting any more. I will wait until next Updates (Sim, World, Driver, whatever) and try in a few weeks again. It’s a bit of a downgrade resollution wise but at least I get to close MSFS now (feels weird since I haven’t closed the Programm for quite some time).
I’ll keep reading this if you have any queations or want me to test something.
Same issue here my friend. Installed the patch. Before that, I tried doing most of the solutions suggested here by others. Tried doing a flight with the Just Flight Piper Arrow III from San Diego up to Monterey in VR. I got about 1 hour into the flight and, boom! CTD with the beautiful AMD driver timeout pop up. Feels so nice to spend 5 grand on a computer for FS and not be able to play it.
1 Like
Same for me. Bought new computer (AMD CPU, 6800XT GPU), invest more than 3k to get FSMS 2020 with VR and? Crashes, all the time. I am frustrated and don’t know when it will be solved. 
1 Like
Have you tried all these solutions ?
If that didn’t work for me, maybe someone else works.
For memory:
I got a decrease in CTDs by installing the English (US) language
And by increasing the virtual memory from 16GB to 48GB
I would add that you have to close all the applications that are running in the background, which can cause CTDs, because they can start for example to make an update.
On my last flight, I didn’t have a CTD during the flight, but RTSS.exe (RivaTuner) (Installed with MSI Afterburner) made me switch from VR to 2D. But it would cause a CTD.
I already had CTD because the Bluesoleil software (Bluetooth device management) which wanted to update.
For ÉnormeMercure163 it is GameBarFTServer.exe (Xbox Game Bar) which created a CTD for it.
You should only have what is absolutely necessary for the functioning of MSFS.
When you think you are on the right track to put an end to those CTD *******, another problem arises.
I had a CTD after 15 minutes of flight. MSFS crashed in Event Viewer, but just before that there were several warning messages, with “Audio Orchestrator microphone audio masking set to 0”
Same problem here with the exploding diamonds when I enable VR. I still have X-Plane 11 on my PC and VR works great with no issues when using the G2.
Same problem here with the exploding diamonds when I enable VR. I still have X-Plane 11 on my PC and VR works great with no issues when using the G2.
First thing to check is to make sure you have at least 64GB of total memory Physical + Virtual. seems like since 1.14.5.0 the game has started using way more memory.
64GB RAM + Virtual Memory, it is not enough, I had to increase the virtual memory to 48GB to have 80GB, with my 32GB of RAM, to have an improvement of the CTDs.
If I run the HB Rebrev G2 with an RX 6800 XT, I also have a GTX 1080 TI.
I tested it with the G2, with the default settings, no problem.
What do you have as settings in OpenXR and in MSFS?
I commonly had this warning before crashes as well, often multiple warnings switching between being set to 0 or 1.
@SirBloke The sound of the G2 works with you, because with me, it never worked.
It appeared in the sound manager, but disabled. And when I wanted to turn it on, it would turn off right away.
So, I don’t know if it comes from there, but I came to do a new installation of Windows 10 on a hard drive. Now the sound is working, but I haven’t done a long enough flight yet, to be able to tell if this “Audio Orchestrator microphone audio masking set to 0” issue is resolved.
EDTION: I forgot that I had read that CTDs could also be caused by a setting in the sounds of MSFS.
Voice syntesis parameter, You must switch Azur to Deactivate
Same, I did not fly long enough to validate.
This issue is 6 months old, I don’t know if an update has since fixed it.
I never found a solution with any changes I made to sound settings or language packs etc so maybe it’s part of the problem, but certainly doesn’t seem to be the sole reason for it. Wasn’t even the most common warning I saw, that would probably be DWM errors.
In Open XR - Developer Tab - Use latest preview Open XR runtime is set to on, Custom render scale checked at 80% render scaling and Motion Reprojection is disabled.
Try 70%ss in Open XR. I recall when I tried 80% the game would crash all the time. 100% 90% and 70% were all fine. I haven’t tested in a while but worth a go.
Will give it a shot and thanks for the follow-up!
I just did a 2 hour flight, after the new Windows installation.
On the first try I got a CTD Error Amdkmdap
I restarted the flight, but the same, I still had this Amdkmdap Error
While searching for the Amdkmdap Error on Google, I came across this topic.
Error Amdkmdap
As Windows is already up to date, and I didn’t want to reinstall the AMD drivers again, especially since I installed it yesterday, I applied method 3 in the registry.
I restarted the flight, and this time it went to the end.
- Press Windows+R keys on your keyboard, type Regedit, and press Enter.
- Inside the Registry Editor window → navigate to the location:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers - Right-click the right-side tab and click New.
- Select DWord (32 bit) Value. Name it TdrLevel and set it to 0.
Managed to fly about an hour in england without CTD, then changed to Berlin and after 5min CTD again.
After changing the registry value to 0 I fly around one hour in Berlin an didn’t got a single CTD.
It disables the graphic driver timeout monitoring.
Not the universal solution, but worth trying.
1 Like