Reverb G2 Blue Screens?

[Zimpow]

My issue is that upon second single player mission loading or re-spawning in multiplayer, once the mission loads my g2 goes Blue yet steam VR on desktop is still running DCS and is ready to fly.

[BIGNEWY]

Hi

 

can you attach your dcs log after it happens, and let us know your system spec. 

 

Also make sure steamvr and windows mixed reality are up to date. Go to the Microsoft store and check for updates also.

 

thanks 

[Zimpow]

Where do I find the DCS log?

I'm a bit of a noob.

[Zimpow]

now it happens at the rearming screen.

 

i7-9700KF  3.60GHz

16GB Ram

2080Ti

G2

[Zimpow]

dcs.log maybe this?

[Baldrick33]

Are you running the beta version of WMR for SteamVR? Opting out of the beta seems to have helped with some SteamVR crashes (blue screen and DCS still running)

[Zimpow]

I am not in Steam Beta

 

Now its when I open the Rearm window

dcs.20210515-222346.crash dcs.20210515-223359.crash dcs.log

[Baldrick33]

I have been chasing down blue screen issues with my Reverb G1 for several weeks now. What makes it especially hard is that I am convinced I have had three distinct issues:

 

1/ I have the original G1 cable (with a replacement newer headset). I could make the headset blue screen by wiggling the cable connector near the headset. I taped this up and that seemed to have solved it.

 

2/ I had SteamVR crashes which caused the Reverb to restart (initially blue screen). This seems to be an issue with the WMR for SteamVR beta. Rolling back seems to have stopped that

 

3/ I have had emf issues with my sim racing rig in the past with previous headsets (Pimax & Index) which would grey out when I touched certain parts of the headset. I tried ferrite cores but the only resolution was gloves. This seems to have become an occasional issue with the Reverb. I touch the headset and it would blue screen with no pull on the cable. So maybe I need to wear gloves like a real pilot!

 

The 4th issue would appear to be DCS causing a SteamVR crash if it repeatable at the same point, possibly a combination of versions of WMR Portal, WMR for SteamVR, SteamVR, graphics drivers, Windows updates etc.

[Zimpow]

I'm beginning to suspect my cable.

 

If I try to respawn or restart a mission or select role again I go blue screen headset.  Steam VR and DCS still running?

 

Deleting my saved games folder solved the rearm window issue.

[despinoza]

i had a similar issue time ago, someone told me that i should disable the selective USB suspend. It worked for me

[Zimpow]

I am not familiar with selective USB suspend?

Oh, that sounds promising.

[Zimpow]

I forgot to also post I'm running DCS from an SSD.

Edited May 17, 2021 by Zimpow

[Zimpow]

Wow that selective USB change may have fixed my problem!

 

No blue screens since the change!

 

Thank you so much!

[despinoza]

Glad to read 

[fylzz]

@despinoza Got WMR "blue screens" all of a sudden  also CTDs. Everything worked for months before that.  No 2D issues. Just changed the USB selective standby setting : works like a charm now. Never had so much hardware trouble than trying to make VR to run smoothly. Thanks would never have found this alone.

[Flash001]

Got the same problem, when high loads are happening like Rearming, sometimes at the end of server load
Rig:- Z390 Aorus Master- i9 9900K 5Ghz- RTX3080 TUF Gaming- 64GB RAM G-Skill 3200Mhz- M2 NVME Intel & Samsung- HP Reverb G2- Water Cooling Corsair H150i- Joy X56 from Saitek- Propedals for rudder control

[Nova1395]

I've come from an Odyssey G1 to a Reverb G2 - these symptoms are similar. It happens whenever I make a drastic view change - ie, F2 view to another aircraft that is 150nm away, so it has to render the aircraft and the map and scenery around it, or - the F10 map. It doesn't happen every time, but roughly about 10% of the time. On the Odyssey it would so something similar, but the headset would instead just crash out. My Reverb does that too, sometimes it bluescreens and then just goes to a black screen while the sim continues running, and continues tracking. 

I can't say I'd blame ED for this one entirely, but perhaps there's better ways to go about rendering.. It feels like the GPU just gets overloaded with a new request for a new environment out of the blue, and takes up such a toll on the GPU that essentially WMR crashes out because there's nothing to even really render at this point, the GPU is maxed out. Staggered rendering in a way would be a better way to go about it I guess is the best way to put it, at least when switching external views - initial render is low res, then populate with higher renders. As for the F10 map, this has been an issue for me for over a year now because it's the same damn problem. It's ditching the cockpit and environment we were just in, and now rendering a totally new environment with an aircraft in the hangar bay. Tolls out the GPU, and if you're unlucky, you bluescreen out. I wish they'd just move onto a live F10 overlay map like the kneeboard.