MSFS 2020 Crash in VR - HP Reverb G2

@SaiienII This is what I did, as I said, I applied point 3 by modifying the register.

I just did a 9 hour flight. I had a CTD on the approach, but there was no airport, although the aircraft was less than 2000 ft. I did not understand, why, there was no airport displayed on the VFR map.
I alternated between interior and exterior views several times, trying to spot an airport, and ended up getting a CTD with the VCRUNTIME140.dll error which as usual crashes FlightSimulator.exe.
BUT no crash message from AMD driver.

EDITION: I had chosen the VECC airport as arrived, and it exists because I just took off there with the 747.

Has anybody tried out the new AMD 21.3.2 drivers? Anything to report? I don’t have MSFS installed and it won’t be going near my system again until there is some form of proper fix that doesn’t involve workarounds and tinkering with settings and crossing of fingers.

Yes I have it, but so far I’ve only done a 9 hour flight.

Still resulted in a crash eventually from your previous post so I’m still going to leave it for while. 150GB is too much to download even with a gigabit connection when it almost certainly isn’t fixed.

No AMD driver crash

@SirBloke I have listed upper
everything I had tried to fix these CTD problems.
On your side, have you tried something, or are you waiting for either Asobo, or AMD, or HP, or Microsoft to find solutions?

I have tried plenty, including 2 full system wipes and Windows re-installation.

Why have you made it sound like I should be making an effort to fix my problem anyway? I have paid money for a working product, it is their responsibility to make it work, not mine.

Yes exact, wait until they search.
If you think that because you have paid, that you are a place to have a game that works, you put your finger in the eye.
Besides, how do you know if it works without installing the game 

Anyway, it’s you who sees.

So, I was able to do a complete flight with CRJ without CTD.
The changed registry key really seems to do its job
 test it out.
I didn’t had any CTD since then.

1 Like

I just realized that I had made the registry change on another Windows installation, but not on this one.
If I could fly 9 hours without CTD, except at the end, because I couldn’t see the airport. Is there a bug with this airport, I don’t know.
As I did not stay 9 hours at 43,000 ft with the helmet on, I put it on a table, with the screen hidden from the light. After a while the G2 went into standby, and the display went to screen, in 2D. A Ctrl + TAB and the VR flight was off again.

I have just made the modification of the register, I am going to launch a rather long flight with the 747, we will see if the G2 goes to sleep.
But hey in the end, if he goes to sleep without CTD, I wouldn’t care.

What are the steps to change your “Virtual Memory? Thanks

Video searches on Youtube to increase virtual memory on Windows 10

Once you have found what to do:
I read that it was necessary to multiply its physical RAM by 1024.
Example with 32GB of RAM
32x1024 = 32768MB
Then multiply by 1.5
32768x1.5 = 49152 Value to enter as virtual memory

Thanks for the prompt response!

After completing some flights, (some at the airport, some at the desktop
) I think TdrLevel = 0 helps a little to extend the flights, but it gets much more annoying when the CTD happens. Because you have to restart your computer.
I change it back to = 3, but increase the delay to 12s.
Still crashes of cause, but I don’t have to reset.

I talked to @Jummivana to get any information from the devs if they are aware of this problem. The answer was yes, but the only thing we can do is gather CAB GUIs from the windows eventviewer.

HOW TO: https://flightsimulator.zendesk.com/hc/en-us/articles/360015913659-How-to-report-a-bug-

Unfortunately in my case the CAB GUI is always 0 at crash events. Maybe some of you can provide better data?

Would it be necessary to do this if I already have 64gb of ram?

I don’t know where I was talking about it anymore, but to put it simply, Windows cannot have multiple applications on RAM that would use the same files. Virtual memory is partly used for that.
There are indigestible videos that explain it if you ever want to know a little more.

Someone on the forum mentioned that they also experienced connection issues, crashes, exploding diamonds, etc. They discovered that it was due to MSFS software opening up the ATC and Camera displays on a second monitor if you have a multiple monitor setup.

  1. I setup my flight first without enabling WMR
  2. The ATC & Camera pops up on my second monitor and closed them both.
  3. If they also show up on your primary monitor close them both.
  4. Hit “Ready to Fly”
  5. Hit Fly
  6. Enable WMR
  7. Wait until WMR fully loads.
  8. Hit Control Tab to enable VR
  9. You should be in VR in the cockpit of your favorite aircraft!

The above are the steps for loading WMR without using Steam since I purchased MSFS from the MS Store.

The above fix is for the HP Reverb G2 that worked for me!

Personally, I only have one screen, but when the installation of the AMD driver is finished, there is a notification that says it has detected multiple DPI screens with high resolution, and to do some adjustment that I no longer remember.
Does he see the 2 screens a G2 as PC screens.

But hey at the same time, I don’t have explosive diamond crashes. I only have CTDs.

1 Like

For the moment the LFPG flight to FACT is at 1h30 and still no CTD with the GTX 1080 TI and the HP Reberv G2.

I had no problems whatsoever with VR in MSFS Store, but crashes “VR Headset not worn” in SteamVR Dirt Rally 2.0,

MSFS GPU use 50-80%, Dirt Rally 2.0 98%

had to underpower my GTX 1080 from 120% power to 90%, fixed it.