07-30-2018 06:22 PM
I have error 208 on my VIVE headset with a solid red light on the side. I have exhasuted every single possible fix that I have found on the internet which includes updating graphic drivers, deleting and reinstalling SteamVR, power cycling the connection box, erasing the USB drivers for the connection box, reinstalling all VIVE drivers and software, pulling all cables and reseating them, re-enabling direct mode in SteamVR settings, plugging HDM into the computer directly,...everything. My headset won't connect over HDMI. I can't get the green light to show up on the side. Only hint is that in SteamVR when I refresh the USB interfaces in the Settings section, everything lights up except 'Audio Device'.
Before the red light showed up, I was in Steam yesterday playing with the VIVE and SteamVR showed my headset connected and ready but my display was black. I disconnected and reconnected all of the cables and rebooted the computer and then the red light came on and SteamVR can't find my headset at all with an error 208. My headset is over a year old and I am afraid that this thing just crapped out on me for good... Any help?
Solved! Go to Solution.
07-30-2018 06:24 PM
Also want to add that when I rerun the VIVE setup, it connects over USB but just hangs on HDMI and just sits there.
07-31-2018 10:09 AM
With that error, I'd highly recommend bypassing your linkbox and trying a different HDMI/USB cable instead of the 3-in-1 to see if it's the cable or linkbox (It usually is in that case)
08-02-2018 10:43 AM - edited 08-02-2018 11:02 AM
Nothing has worked. I have tried EVERYTHING including bypassing box, using different cables, deleting and reinstalling everything. This happened about a week ago, has there been some driver update on the Windows or Nvidia side that's bricking devices? When running the VIVE setup, it gets to the 'Connect the headset to link box' section and confirms on USB detected, but hangs on HDMI. In the SteamVR settings, it gives me an error that the camera can't be found over USB, try another and when I refresh the USB connections, it shows the camera connected but is missing Audio Device. I am worried the board is fried, I am worried that too much perspiration from playing Beat Saber (and I am in pretty great shape, so it's not abnormal amounts of perspiration) has caused hardware malfuction.
I am out of ideas.
08-02-2018 01:19 PM
Okay, new error from Steam:
VR - Error! SteamVR failed initialization with error code:
VRInitError_Driver_HmdDisplayNotFound "HMD detected over USB, but Monitor not found (208)"
08-02-2018 06:04 PM - edited 08-02-2018 06:05 PM
How are you connecting your monitor(s) to your PC?
VIVE is using HDMI.
How many monitors do you have connected to your PC?
What port is your monitor using?
08-02-2018 06:21 PM
Original setup DVI-D to HDMI to box and HDMI to monitor...now...HDMI to box/headest (if skipping box) and Display Port to monitor
08-02-2018 08:44 PM
Both cables are connected to the same graphics card right?
What did the DVI-D cable connector look like? Were there missing pins in the middle?
Are you using a desktop or notebook?
08-03-2018 08:18 AM
Both cables were same graphics card, setup has worked fine for over a year. No issues with DVI-D cable, no pins missing, I am on a desktop. Thanks
08-10-2018 09:57 AM - edited 08-10-2018 10:20 AMSolution
@Synthesis So, my headset was broken. I ordered a replacement HMD only off of eBay and it connected and turned on immediately.
WARNING TO OTHER USERS: Beat Saber may start killing headsets from the sweat. It appears HTC may have cut corners and never water proofed the electronics, so too much sweat in the unit seems to destroy it. It may be all coincidence and it has nothing to do with the sweat, but it seems like the likely culprit considering I have had zero problems with the unit until I started playing Beat Saber (I have never struck the headset with anything while playing, never dropped it, never ran into something with it on, I took really great care of it). I am in really great shape and don't sweat excessively, so it sucks that this happened. Be careful!
Of course it was out of warranty when this happened...but even if my warranty was still valid, pretty sure it wouldn't have been covered.