Rift loses randomly HDMI connection

[schrumpelrat]

first of english is not my native language and i'm not great with it, so please excuse bad grammar etc.

i have a problem with my rift. since it came to me i have trouble to play for more than a couple minutes or not even seconds before it loses the hdmi connection.
i tried several steps to fix this issue:

connect hdmi direct to the gpu port
connect hdmi through a front connection in my card reader
connect through a dvi to hdmi connector, a passive displayport to hdmi connector and an active displayport to hdmi connector

i also tried to refit the cable in the rift. i connected the rift to the usb 3 ports of my motherboard and on the port of my add on card. i also tried one usb 3 on the mb and one on the add on card and switch them vice versa.
i disabled the energy savings options on all usb ports, the rift sensor and the gpu.
i also tried different usb and gpu drivers (older ones as well as the current ones)

my specs:
intel i7 4790k
msi gd65 z87 gaming
palit gamerock 1080 (had the same issues on my palit 980ti, but my 1080 came short after my rift and i was thinking the 980ti had a incompatible hdmi port)
32gb ddr3 2133mhz
windows 10 pro 64bit
fresco logic fl1100 usb 3 pcie card

current installed gpu driver is 368.51, for usb 3 it is 10.0.10586.212 for the fresco card and the default windows driver for the intel usb 3 on the motherboard.

i also restart my pc after every fix attempt just to be sure everything is in the right place. 

i hope someone can help me to get in vr already ;_;

i added also the recommended logs. 

[SauSack]

Ok, looks like I have to correct myself - it IS NOT software related!!
Error seems to occur when I start to take that rift on or off, or when even if I knock gently at the cover next to the cable plug......
I plugged in the cable several times properly but the issue is not solved, it even becomes more and more - looks like something at the mainboard loses its connection further.

Fortunately the first responses came in really fast from the support.

Hopefully they will exchange my rift fast, too!

Must be a faulty series or something similar.......

Regards

[Laddi_de]

Hello SauSack,

are you from Germany, too? Because of your name...

I also tried knocking gently near the cable and it also looses the connection after that knocking. It seems we have both the same problem. 

I really regret to have bought an oculus rift. It's always the same when you are an early adopter...

Edit: I made a little video from my error:

https://youtu.be/TmZJlsGxr7I

[Durandal1707]

Also seeing the disconnect issue with HDMI during use. Does seem to be related to the duration of use or heat of the unit. I can confirm it also seems to be with the connection at the headset and not the USB or HDMI plugs on the computer side.

Now if support would respond to my ticket... it has been a week since they were "looking into it"... seems unlikely they don't know what the issue is at this point!

[SauSack]

Laddi_de said:

Hello SauSack,

are you from Germany, too? Because of your name...

I also tried knocking gently near the cable and it also looses the connection after that knocking. It seems we have both the same problem. 

I really regret to have bought an oculus rift. It's always the same when you are an early adopter...

Edit: I made a little video from my error:

https://youtu.be/TmZJlsGxr7I

Ja, komme aus dem schönen Rheinland 😉

Luckily you made this vid - it could be my rift as it is reacting exactly the same way ......
Must be a faulty charge - not everybody got this issue, so it is not the rift project in total I guess.

Hopefully we will get a fresh one in not to far future........ My vr-lens glasses are about to arrive today 😕

Regards und Grüße

[Fiege]

Hi Laddi de & SauSack, hi all.

I'm also from Germany and had exactly the same issues on my CV1 I received on Monday.
I opened a ticket with Oculus support and send in the first logs.

Maybe there is hope, since by now I'm not sure that the hdmi disconnects are really caused by faulty hardware.
But let's break it down a bit:

After installation:

- First I expected the cable to be faulty, because touching it caused the hdmi disconnect.
- Then I blamed the HMD, because holding the cable in place while moving the HMD caused the error too.
- Refitting the cable did not change anything...at first.

Second time I used the Rift (after reboot obviously) the problems were completely gone.

Not sure, what I did, but I did not have any hdmi issue now for 3 days. I can move my had as I like, I can put on and off the device as I like - nothing. HDMI is just fine.

This morning I got bold trying readjusting the side straps - no issues.
Even slightly touching and moving the cable at the device doesn't do any harm right now.

What I did was refitting the cable at the HMD a) properly and b) by building a basic strain relief by having a small "wave" in front of the connector.

Maybe it was a faulty cable/divice and the refitting did the trick for now, but I honestly doubt that, since the "wave" is gone by now due to heavy usage and no physical manipulation of the device (including slight!!! squeezing, shaking, tapping) or moving caused an hdmi disconnect for the last 3 days.

I do have a theory though.
It might have sth. to do with the USB connection! First I tried to reconnect to other USB ports, which did not change anything. After the first reeboot (when the error was gone), the oculus app told me, that the HMD was connected to an USB 2.0, which it was not (it was 3.0). Furthermore the app told me that the sensor was connected to an USB 3.0 but could use an update. After another reboot everything was OK and it got completely recognized as USB 3.0.

Therefore I think it might have sth to do with USB handling of the Rift.

Nevertheless I will do some more in depth testing on the weekend and in the meantime keep the ticket open at Oculus.

I'll keep you informed.

[Laddi_de]

Hi Guys from Germany and all the others,

BTW Ich bin aus Köln, also auch Rheinland 🙂 . 

@Fiege: I really tried a lot. And often I thought, that I got it. In my case for example I can not do lense spacing without reconnections. This was from the beginning. When I used the Rift for the first time and did the setup, I was wondering what the hell is wrong with the lense spacing, But after that it works fine for while better say it was acceptable. But then it was getting worse. Right now it is horrble. My Rift is now 2 months old. 

You got yours on monday. Be happy that we have two years warranty in Europe. I dont't wanna paint the devil on the wall (a German unterstand it 😉 ), but be carefull. 

I'm now in contact with the support. I had to made pictures from the pins of the cable. On a very high zoom level you can see, that all pins are ok. So I hope they don't send me a new cable. Like other guys in ths thread mentioned: it is never the cable when your pins are ok. But I'm afraid I get first a new cable and then I get a new rift.

My advice is: If you have problems in the beginning with loosing the hdmi connection, be sure, it is not getting better. Return the rift immedeatly, get your money back and buy later a new one. It is not like Amazon, something is broken and you send it back. You have to proof, that it is not your fault.

[PIXELATED]

My CV1 (RMA) arrived at the warehouse in the Netherlands yesterday (good ol' UPS tracking) and nice Oculus support lady said
 "I will do my best to expedite the process, but please keep in mind I have very little control over what happens at the warehouse"
I guess there's a whole lota CV1's piled up there waiting to be bar-coded and thrown in the skip before i get a brand new thoroughly tested and working one sent back..
I remain positive... as this has only been 9 days since I first raised a ticket about a hardware issue (-;

[Laddi_de]

But how many hours have you tried and tried to get it work  😛

[PIXELATED]

^ way too many hours ^ +16 would be an understatement  😛

[Fiege]

Small update:

In fact, the error occured again during taking off the HMD after playing Project Cars for about half an hour 😕
But again I wasn't able to reproduce it through physical manipulation including putting the device on and off a couple of times. So I still think Rift has problems with USB handling. Well either that or there really is a loose connection somewhere. But then again, shaking the device would produce the error, wouldn't it?

Although you've probably done all of that:

- Have you checked your USB drivers are up to date?
  I'm using windows 10 and it has a lot of problems with the drivers for USB (and LAN and bluetooth btw.).
  As I connected both, Rift and sensor, to the ASMedia ports on my Asus board, I had a couple of problems in the beginning. The driver wasn't really Rift ready. They've got a beta driver out now which is.

- Are the USB ports configured for XHCI in UEFI/BIOS?

- Are the USB ports configured for not going into power saving mode in Windows device manager?

- have you any other devices connected to the same controller, which might interfere, e.g. printer, webcam, game controllers?
  I have the Oculus (not the XBox Controller) devices connected to the ASMedia controller. Everything else is connected to the Intel controller.


I'll keep you updated.