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.