Question Valve Index headset display doesn't turn on, Valve support talking in circles - Help

Jul 17, 2024
4
0
10
So, after years of saving for it itself and a good enough computer, i bought my first VR system, the full Valve Index kit. Initially, everything seemed to work perfectly: I powered it on, explored VR, and enjoyed the headset for about a month without issue. Then, one day, the headset refused to leave standby mode—its LEDs remained lit, the cameras and motion tracking still reported data, but the displays stayed dark. SteamVR still “saw” the headset at a basic level, but there was no visual output, which pointed to something deeper than a simple software problem.


Following Valve Support’s advice, I swapped in a replacement cable to rule out a tether issue, but that made matters worse. After the swap, SteamVR no longer even detected the headset at all, reporting it as disconnected at the tether’s headset end despite everything appearing plugged in correctly. I began to worry that your own cable replacement had somehow introduced a new fault, but Valve’s support team—relying on the SteamVR system logs I provided them—decided that no further troubleshooting would fix the problem. They initiated an RMA for the headset itself, requesting that you send back the full HMD assembly, three-way connector, and accessories for a replacement unit.


Now, I've done that, right? And guess what? Still, nothing. If I recall correctly, it was the same thing. Yes, I have to "recall" because I had to give up after a while and put it back in its box like 4 months ago from now.

Yes I am putting it in the displayport, yes i have a compatible GPU (RX6600), yes I pass all the other compatibility checks, no there is no visible damage on anything, yes the whole setup isnt even a year old.

I belive this is some hyper specific compatibility issue so I doubt there is any helping this but if you think you have ANY idea as to how to fix this, PLEASE tell me, i would be insanely thankful. Feel free to ask any extra follow-up questions if you need something specified.
 
When did the problem begin?

Look in Reliability History/Monitor, Event Viewer, and Update History for any error codes, warnings, or informational events that started just before or at the time the headset problems began.

Use Day View in Reliability History to go back 4 months and start paging through.

Event Viewer is more complicated and takes time and effort to navigate and understand.

To help:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

Focus on just trying to find some entry or entries that relate to the described problems.

You need to and should connect the headset up again.

Just to refamilarize yourself with the connections and configuration settlings plus generate any new error code entries.

Look at the logs first- anything "new" may be more apparent to you.

Also update your post to include full system hardware specs and OS information.