• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
The HP Community is where owners of HP products, like you, volunteer to help each other find solutions.
HP Recommended

It does sound like the same issue.

 

My bluetooth is 5.0 native to the motherboard, and the USB-C is also straight off the backplane and is VR ready (has more power-out to the port to support the power needs of a VR headset.) I am using seated now for testing so right next to computer (even added the bluetooth antenna.) I turned off all other bluetooth around and 2.4 GHz wireless just for good measure, to prevent any interference.  I can use an XBox elite controller with the XBox bluetooth dongle and that works fine in Steam VR and games; I just don't know how to use that to control the Steam interface or I wouldn't even mess with these controllers. I updated chipset drivers, Win 10, and reinstalled bluetooth drivers.  (Again, WMR and Steam VR work fine for *other* WMR controllers which puts it back to these and/or the code that is driving them.) Other folks are loading Steam VR and getting into games which makes me think some specific HP controller driver or conflict, or maybe an HP controller issue?  Bluetooth on PC turned off so only headset bluetooth makes no difference. It would be nice if there was a way to just use the pc bluetooth instead of the headset bluetooth if those drivers are the issue.  I do not know how to view the error logs for the crashed startups. Starting Steam VR from within the Cliffhouse also does not work. Viewing the error logs to see what is conflicting/failing makes the most sense; trying to figure out how to view those. Or maybe HP will release a firmware update?

HP Recommended

Hi @VanBurenPhilips,

 

Welcome to the HP Support Community.  

 

As this is a hardware issue, I'd suggest you Contact HP in your region regarding the service options for your computer. 

 

If you are having trouble navigating through the above options, it's most likely because the device is out of warranty. If yes? please send me a private message with the region you are contacting us from. Check next to your profile name, you should see a little blue envelope, please click on it.   

 

Have a great day!  

 

Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution. 

Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping! 

HP Recommended

I have the exact same problem. I assume there is no fix yet?

 

System:

Cpu: Ryzen 5 2600

Board: AsRock b450 Pro 4

Memory: 16 Gb

Gpu: Nvidia RTX 3070 FE

HP Recommended

I figured it out! It turned out I had an old instance of Steam VR installed on another drive, that I forgot about. I had an Odyssey Plus which i sold a while ago and thought, that I already deleted it :D.

 

I discovered it by following the instructions regarding "SteamVR is crashing after updating Windows" here: https://docs.microsoft.com/en-us/windows/mixed-reality/enthusiast-guide/steamvr-questions

 

I then just deleted the whole folder from the old drive and now it works (just tried the Lab).

HP Recommended

I love you and want to have your babies, but my doctor says it's impossible, so 'thanks' will have to do 😄

 

Worked for me too. Brilliant find, that's a needle in a haystack. I had a case open with HP and they stopped replying, so thanks a million. I'll mark this as the solution - I just want to give the others a chance to reply too, see if it works for them. It was exactly right for me - I had one extra steamvr path in that file; as soon as I removed it everything started working. I was waiting for the crash as steamvr launched, was so relieved when the home environment loaded and my hands were there! 

 

Thanks a lot, K. 👍

HP Recommended

I solved my problem but only by doing a full Win 10 clean install.  Uninstalling drivers, SteamVR and Steam, and WMR software and WMR portal didn't help, and i never found a duplicate SteamVR entry though I looked. Was painful but it works now.

HP Recommended

Darn, since I am a multiple-WinVR headset user too I thought for sure this would be the problem. Sadly not, I only have one instance of the external_drivers variable. Would one of you mind posting the innards of your %localappdata%\openvr\openvrpaths.vrpath config? I'd like to compare with another known working config just in case there might be another hidden gem in there.

HP Recommended

Here's mine: 

 

{
	"config" : 
	[
		"C:\\Program Files (x86)\\Steam\\config"
	],
	"external_drivers" : 
	[
		"C:\\Program Files (x86)\\Steam\\steamapps\\common\\MixedRealityVRDriver"
	],
	"jsonid" : "vrpathreg",
	"log" : 
	[
		"C:\\Program Files (x86)\\Steam\\logs"
	],
	"runtime" : 
	[
		"C:\\Program Files (x86)\\Steam\\steamapps\\common\\SteamVR",
		"H:\\Games\\Steam\\steamapps\\common\\SteamVR",
		"G:\\Games\\Steam\\steamapps\\common\\SteamVR\\",
		"G:\\Games\\Steam\\steamapps\\common\\SteamVR"
	],
	"version" : 1
}

 

It used to have one extra path under external_drivers, which I deleted.

 

I thought those extra paths under runtime might need some attention, but they don't seem to cause any issue. Sorry this has not worked for you so far. Do you have multiple library paths set up in Steam?

HP Recommended

To solve the problem of a crashing SteamVR with reverb G2 controllers, you only have to manually un-pair the G2 controllers in the WMR setup. After that, manually re-pair both controllers. After that, SteamVR works normally.

 

HP Recommended

@NaKlar wrote:

...manually un-pair ... re-pair both controllers. 

 



I tried that, it didn't make any difference for me.

 

Worth a try though, for anyone still getting the crash.

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.