I only fly in VR with the Reverb G2, but that didn’t always go well. For unclear reasons, the headset sometimes failed, causing the VR session to crash and then not recover. Only solution then was a complete reboot of my system and hope it didn’t happen again. Very frustrating because sometimes I could fly for two hours without problems and at other times less than 5 minutes.
This problem regularly made the sim a disappointment. I then committed myself to solving this problem, which took a lot of time. I have tried the following:
- Hundreds of different combinations of settings (Windows Mixed Reality, OpenXR Tools, Nvidia Driver, Game Mode, Hardware-accelerated GPU scheduling, graphics settings in MSFS, UserCfg.opt, OpenXR Toolkit
- Complet new installation of MSFS2020 several times
- A complete clean install of Windows 11
- Update drivers
- Several USB ports
- An externally powered USB hub
- Extra lighting for improved tracking of the headset
Nothing helped or improved and I even considered building a new system with different VR headset (Varjo Aero).
Because I suspected that it was a hardware and/or driver problem, I started looking in the Windows Event monitor. There I encountered a number of critical error messages, including: “The device HP Reverb Virtual Reality Headset G2 is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this issue.”
With this error message I went to work and found a number of users who had similar problems with the Reverb G2 and an X570 motherboard (as I also have). One of the users on Reddit reported: “My problem was solved by in the BIOS setting, putting / setting PCIE to Gen 3. (Is default set to auto /4) Game doesn’t crash anymore. All USB ports work”
Then I set the PCIE setting from Auto to Gen3 in the BIOS and the problem was solved. It was quite a search, but finally the Reverb G2 now works perfectly stable. So for people experiencing the same problem, try this setting in your BIOS!