HP reverb G2 blue screen in headset then crash.

[Dog 1-1]

Recently my dcs has started crashing.  First the display inside my reverb G2 goes blue and then dcs crashes.  Sometimes it recovers before DCS crashes and acts like it lost head tracking, sending my POV outside the aircraft or doing circles.  Sometimes only the VR portion crashes and the 2D image on the desktop is still controllable.  And sometimes DCS crashes completely and WMR restarts.  ALl occurrences start with the headset showing blue screens and crashing though.  I have seat shakers installed and I have noticed the audio from the shakers cutting in and out recently like there's a sound issue in the game, and I've seen other peoples issues where sound conflicts could be occurring.  The log file attached blue screened three times but recovered each time before DCS crashed completely. 

 

Any help is greatly appreciated.

 

Some of the things I have tried so far:

Fresh Install of DCS, removed all mods such as openXR, removed overclocks from my PC, Lowered settings in game, added a powered USB 3.0 HUB per HP's recommendations, removed unnecessary USB devices, disable hotplug devices in the UI settings (or enabled them, the problem happens either way).

dcs.log

[Dog 1-1]

Just made sure all BIOS settings were stock and no XMP or power profiles were applied.  Loaded into a MP server in an F14, got shot down, loaded into another Tomcat with an air battle taking place over the field with SAM launches.  Blue screens in headset and a loss of tracking on load in.  Exited the game and attached the log.

dcs.log

[Flappie]

Hi. I see no issue detected by DCS in your log. From the sim point of view, it's as if the VR screens were working until you exited the game.

Do you see VR-related events in your Windows Event viewer at the time of your issue?

[jurinko]

I had similar issues and the culprit was bad v1 cable. Now flying with v2.

[Dog 1-1]

6 hours ago, jurinko said:

I had similar issues and the culprit was bad v1 cable. Now flying with v2.

I saw that that was an issue in the past but my reverb came with the revision 2 cable out of the box.  I’ll look at windows event viewer tomorrow and see if there are any errors. 

Edited October 25, 2022 by Dog 1-1

[jurinko]

Try different USB port or use USB PCIE hub. V1 cable worked on hub only and v2 cable works on usb3.0 motherboard slot only.

[BIGNEWY]

My G2 cable recently failed, I had blue screen or vertical lines. Changed the cable and fixed it for me. 

[markcam4]

Had a recent HP reverb G2 error- where all of a sudden, the headset was complaining that the USB port was not version 3.0 !! A new V2 cable (free replacement if in warranty) fixed this issue.

[Mr_sukebe]

Apologies if this a little off topic, but are there aftermarket cables at sensible prices to replace the HP supplied ones?

Just conscious that the genuine HP ones appear to be "rather expensive".

[Doncho]

2 minutes ago, Mr_sukebe said:

Apologies if this a little off topic, but are there aftermarket cables at sensible prices to replace the HP supplied ones?

Just conscious that the genuine HP ones appear to be "rather expensive".

And rather faulty. 

[BIGNEWY]

6 minutes ago, Mr_sukebe said:

Apologies if this a little off topic, but are there aftermarket cables at sensible prices to replace the HP supplied ones?

Just conscious that the genuine HP ones appear to be "rather expensive".

I took a chance with a second hand one from ebay

[Dog 1-1]

I'll start looking at HP for cable replacement options.  In any case,

 

There is a windows event log error at the time of the blue screen:

Faulting application name: DCS.exe, version: 2.7.18.30765, time stamp: 0x63359821
Faulting module name: DCS.exe, version: 2.7.18.30765, time stamp: 0x63359821
Exception code: 0xc0000005
Fault offset: 0x00000000008fb939
Faulting process id: 0x4308
Faulting application start time: 0x01d8e816ec3e6cda
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\DCS.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\DCS.exe
Report Id: 4f433690-ea99-4fa0-8117-f7197f9aa12c
Faulting package full name:
Faulting package-relative application ID:

 

And the event details are:

- Provider       [ Name] Application Error

- EventID 1000       [ Qualifiers] 0

Version 0

Level 2

Task 100

Opcode 0

Keywords 0x80000000000000

- TimeCreated       [ SystemTime] 2022-10-25T02:26:47.4740634Z

EventRecordID 4366

Correlation

- Execution       [ ProcessID] 0       [ ThreadID] 0

Channel Application

Computer DESKTOP-FPSIKMS

Security

-

EventData

DCS.exe

2.7.18.30765

63359821

DCS.exe

2.7.18.30765

63359821

c0000005

00000000008fb939

4308

01d8e816ec3e6cda

C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\DCS.exe

C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\DCS.exe

4f433690-ea99-4fa0-8117-f7197f9aa12c

[Dog 1-1]

I have a replacement cable on the way from HP.  However I kept trouble shooting and I was able to reproduce the bug and push it all the way to a crash.  When the audio file of a jet in afterburner is played it triggers the blue screen and eventual crash if the sound file is played long enough.  I was able to reproduce the bug on the blue flag server sitting on the taxi way while jets did low passes and took off overhead.  Log attached. 

dcs.20221026-184320.crash dcs.log

[Dog 1-1]

BUMP.

 

Received the replacement cable from HP earlier.  I've been playing most of the day without incident. However on Blue Tempest server the issue continued to happen.  It really seems to be audio related. 

dcs.log

[Flappie]

Your log ends with a lot of both video and audio devices plugging/unplugging. It's not only audio. It still looks like a VR cable issue.

[Dog 1-1]

32 minutes ago, Flappie said:

Your log ends with a lot of both video and audio devices plugging/unplugging. It's not only audio. It still looks like a VR cable issue.

It happened on a factory new cable that I received earlier.  

Edited October 28, 2022 by Dog 1-1

[Flappie]

Maybe it's the connector then?

[Dog 1-1]

I haven't heard of that being an issue with this headset.  I've seen the cable being an issue.  I just flew for a little bit on tempest and respawned into a M2000C and it crashed on me again.  Before the device unplugged warnings I see that there is always an audio warning.  And this seems to coincide with the headset crashing.  I always get a loss of sound to my seat shakers, then the screen goes blue, then WMR crashes. 

 

I can have the headset sent back to HP for repair but its just strange that DCS is the only game this happens with. 

dcs.log-20221029-031824.zip

[Dog 1-1]

Georgia at war, load onto carrier, F2 view on different jets in the server, get to hornet supercruising, instant crash. 

 

I had the headset sitting on the desk so no movement through the cable or connector.

dcs.20221029-145421.dmp dcs.20221029-145421.log dcs.20221029-145421.crash dxdiag.txt hash

[Dog 1-1]

Further testing in the task manager and resource monitor shows that as I view different units on the map RAM is committed and not released.  I started out on the deck of the carrier using 20 GB of my ram and it goes up rapidly if you F2 different units around the map.  When my ram hits 34GB of usage, which is insane by the way, my game crashes.  This crash is repeatable. 

Also since I've been doing this test with my headset on the desk I can see a new error message that has been appearing on the screen

Opencomposite Error

xrWaitSwapchainimage timeout

 

dcs.20221029-150601.dmp dcs.20221029-150601.crash dcs.20221029-150601.log dxdiag.txt hash

[Flappie]

I see you have a HDD in your PC. Can you please make sure your Windows pagefile is not stored on it?

Run the following command in a cmd window and paste the result here:

wmic pagefile list /format:list

 

[Dog 1-1]

C:\Users\>wmic pagefile list /format:list

AllocatedBaseSize=16384
CurrentUsage=414
Description=C:\pagefile.sys
InstallDate=20220828211649.117791-300
Name=C:\pagefile.sys
PeakUsage=879
Status=
TempPageFile=FALSE

So I set a pagefile according to the forums when this problem began.  I've tried a few more times inside the game and it would appear that there is a massive memory leak taking place.  When I join a server I can see my Ram steadily being used and as soon as I hit 34 GB of usage the game crashes. 

[Flappie]

Yet you have 64 GB of RAM, which means DCS should be quite comfortable. This is weird.

I saw your crash log error label is 'Breakpoint', which is quite unusual in DCS. I wonder what it means in this case.

Have you tried repairing DCS? If not, choose the "slow" mode.

https://www.digitalcombatsimulator.com/en/support/faq/repair/#2463807

[Dog 1-1]

So I just removed the page file that I had set and it removed the memory leak.  Now no matter how much I F2 around the map the RAM usage tops at 21Gb and the source of that crash is solved.  However I just got the blue screen error again and the headset failed.  It listed an audio problem right before the device failure again.  I'll contact HP about getting the headset repaired but I'm not sure either way. 

dcs.log

[Dog 1-1]

I was able to finally solve this issue by getting a USB 3.0 PCI extension card for my PC.  To anyone that finds this thread the powered external USB hub that HP recommends did NOT solve my problem.   You need to buy a separate PCI usb expansion card to put into your machine. 
 

Since I added the expansion card I haven’t had any crashes, and as a bonus the tracking of the headset has improved greatly.  Whenever I would look down at the panels in the cockpit the headset would drift causing me to be too low in my seat when I looked back up.  Now it tracks very good and there is no drift.  I figured that was just the way the headset performs but I can see it’s been broken for a while and now it’s fixed. 

Edited October 31, 2022 by Dog 1-1