Jump to content

[RESOLVED]Black Screen & HDMI Disconnects


twobells

Recommended Posts

Started having some real trouble only 3 weeks after my Rift arriving, essentially it started with 'hdmi disconnects' throwing me out of DCS but now I get a black screen AND an hdmi disconnect (probably the same thing) but this is whats weird, only in DCS, everything else works fine. So I tried repairing DCS but that didn't work so I assume my next step is a complete re-install...

 

May I ask, has anyone else experienced this issue and have they found a solution?

 

Thanks in advance

 

edit. okay, I have found another thread related to this issue, seems that many Rift owners are suffering these problems, what I don't understand is how my Rift which is only 3 weeks old, worked perfectly all that time in DCS with no problems suddenly have serious issues.

 

http://forums.eagle.ru/showthread.php?t=168053&highlight=disconnecting

 

resolved

Solution: Disabled Asmedia controller which has proven to be the #1 fault for hdmi disconnects and 'black screen'.


Edited by BIGNEWY
TITLE

[sIGPIC][/sIGPIC]

 

 

Rig: W10 PRO 64 bit, Intel 7700K, Asus Maximus IX Code, 32GB G-Skill Ripjaw DDR4, EVGA RTX 2080 TI, Samsung 1TB M.2 970PRO SSD Primary HDD, 4TB Storage, TH Warthog, Oculus Rift, 27" Samsung 4k Display. 2x Wheel Stand Pro v2 (Hotas & Stick) + Warthog Stick Adaptor

 

Link to comment
Share on other sites

twobells, not sure why it happened to me either. It worked fine, then it just stopped. Going with a DVI or DP (can't remember) fixed it. I guess it's an Nvidia thing.

hsb

HW Spec in Spoiler

---

 

i7-10700K Direct-To-Die/OC'ed to 5.1GHz, MSI Z490 MB, 32GB DDR4 3200MHz, EVGA 2080 Ti FTW3, NVMe+SSD, Win 10 x64 Pro, MFG, Warthog, TM MFDs, Komodo Huey set, Rverbe G1

 

Link to comment
Share on other sites

my rift was running fine on usb 2.0. after the arrival of the usb 3.0 controller hdmi disconnects started. I switched the usb-cable of the glasses back to 2.0 and things were good again. no disconnects anymore. strange...

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

Happens when:

 

-HDMI Voltage Drops (as the OR is out of HDMI Spec)

-USB Voltage Drops (Having Sensor and HMD On the same cheap USB controller)

-Loose Cables (the Cable on the HMD can be Pulled / wiggled loose from use)

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Link to comment
Share on other sites

twobells, not sure why it happened to me either. It worked fine, then it just stopped. Going with a DVI or DP (can't remember) fixed it. I guess it's an Nvidia thing.

 

I have a DP connector let me try that.

 

resolved

Solution: Disabled Asmedia controller which has proven to be the #1 fault for hdmi disconnects and 'black screen'.


Edited by twobells

[sIGPIC][/sIGPIC]

 

 

Rig: W10 PRO 64 bit, Intel 7700K, Asus Maximus IX Code, 32GB G-Skill Ripjaw DDR4, EVGA RTX 2080 TI, Samsung 1TB M.2 970PRO SSD Primary HDD, 4TB Storage, TH Warthog, Oculus Rift, 27" Samsung 4k Display. 2x Wheel Stand Pro v2 (Hotas & Stick) + Warthog Stick Adaptor

 

Link to comment
Share on other sites

  • 3 weeks later...
my rift was running fine on usb 2.0. after the arrival of the usb 3.0 controller hdmi disconnects started. I switched the usb-cable of the glasses back to 2.0 and things were good again. no disconnects anymore. strange...

 

 

Did it affect your DCS framerate at all?

 

 

TIA

[sIGPIC][/sIGPIC]

 

 

Rig: W10 PRO 64 bit, Intel 7700K, Asus Maximus IX Code, 32GB G-Skill Ripjaw DDR4, EVGA RTX 2080 TI, Samsung 1TB M.2 970PRO SSD Primary HDD, 4TB Storage, TH Warthog, Oculus Rift, 27" Samsung 4k Display. 2x Wheel Stand Pro v2 (Hotas & Stick) + Warthog Stick Adaptor

 

Link to comment
Share on other sites

  • 1 year later...

If your Rift disconnect problem only occurs in DCS world, try moving power hungry USB devices (lighted HOTAS, RGB keyboards, etc.) to a powered USB hub rather than plugging them directly into front/back USB ports.

 

I noticed all of the llights on my HOTAS Warthog throttle go off at the same time my Rift disconnects. This revealed that ALL of my PC's USB ports were shutting off - apparently because too much current was required for all of my devices.

 

Since plugging my power hungry USB devices into a powered USB hub I have not had a single "Rift disconnect".

 

Hopefully this helps someone else. What a rellief!

Link to comment
Share on other sites

i had exactly the same problem as you are....

i solve it by changing Nvidia drivers ....problem solved

[sIGPIC][/sIGPIC]W10(64bit)Asus Rog Strix Z370-F - i7 8700K - Dark Rock Pro 4 - 16 giga ram Corsair vengeance 3000 - MSI RTX 2070 Super - Asus Rog Phobeus soundcard - Z906 Surround speaker - Track ir5 - HOTAS Warthog

Link to comment
Share on other sites

i had exactly the same problem as you are....

i solve it by changing Nvidia drivers ....problem solved

 

Which driver version are you using now?

System :-

i7-12700K 3.6 GHz 12 core, ASUS ROG Strix Z690-A Gaming, 64GB Corsair Vengeance RGB Pro 3200MHz, 24GB Asus ROG Strix Geforce RTX 3090, 1x 500GB Samsung 980 PRO M.2, 1x 2TB Samsung 980 PRO M.2, Corsair 1000W RMx Series Modular 80 Plus Gold PSU, Windows 10. VIRPIL VPC WarBRD Base with HOTAS Warthog Stick and Warthog Throttle, VIRPIL ACE Interceptor Pedals, VIRPIL VPC Rotor TCS Plus Base with a Hawk-60 Grip, HP Reverb G2.

 

 

Link to comment
Share on other sites

Well, after what, 2 years?, my Rift gave in today. No HDMI connection, period. I tried all the tricks, including NVidia drivers downgrade. I had no recent software changes, but I did get intermittent HDMI connection errors in the last few days (cured with restart or reboot). Does it sound like a bona-fide tired cable? Contacting Rift support, will see what they say.

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

Link to comment
Share on other sites

Well, after what, 2 years?, my Rift gave in today. No HDMI connection, period. I tried all the tricks, including NVidia drivers downgrade. I had no recent software changes, but I did get intermittent HDMI connection errors in the last few days (cured with restart or reboot). Does it sound like a bona-fide tired cable? Contacting Rift support, will see what they say.

 

Perhaps.

I assume you took the faceplate off and checked the HDMI connection into the Rift to make sure it had not come unseated a little? Any kinks in the HDMI cable where it comes out through the strap? It can develop twists there.

 

Also just for grins try a repair of Oculus Home?

 

If so I would probably try getting a new HDMI cable from Oculus.

I have been running mine hard , almost daily for the last year and a half, thinking about ordering another HDMI cable from Oculus just to have as a spare if needed.


Edited by dburne

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Link to comment
Share on other sites

Yep, tried unplugging/replugging and moving USB from Innotech back to motherboard. Oculus software just got updated itself, no change. I get video/sound in HMD for a few seconds after launching Oculus, but the picture is static (does not move when I turn my head). Then I get a warning about 'poor tracking', and then screen goes dark and I get an error 'HDMI not connected'. OculusVR process may freeze or crash at this point. It seems it lacks some type of feedback from Rift. Is this consistent with bad cable? Ironically, my 2-year EU warranty just ran out last week )))

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

Link to comment
Share on other sites

Yep, tried unplugging/replugging and moving USB from Innotech back to motherboard. Oculus software just got updated itself, no change. I get video/sound in HMD for a few seconds after launching Oculus, but the picture is static (does not move when I turn my head). Then I get a warning about 'poor tracking', and then screen goes dark and I get an error 'HDMI not connected'. OculusVR process may freeze or crash at this point. It seems it lacks some type of feedback from Rift. Is this consistent with bad cable? Ironically, my 2-year EU warranty just ran out last week )))

 

Hard to say for sure, but it is sounded like it. Any noticeable twists in the cable coming out of the headset?

If what you describe was happening to me, I would probably order another cable from Oculus to give it a try and see if it clears it up.

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Link to comment
Share on other sites

I have a clip that I attaches to my shoulder. I never felt like the cable on the HMD would stand up to the strain. Just one of those badge holders with plastic band and a clip.

 

 

But if you have a HDMI-DP adapter, you might give that a shot as well.

hsb

HW Spec in Spoiler

---

 

i7-10700K Direct-To-Die/OC'ed to 5.1GHz, MSI Z490 MB, 32GB DDR4 3200MHz, EVGA 2080 Ti FTW3, NVMe+SSD, Win 10 x64 Pro, MFG, Warthog, TM MFDs, Komodo Huey set, Rverbe G1

 

Link to comment
Share on other sites

Well, after what, 2 years?, my Rift gave in today. No HDMI connection, period. I tried all the tricks, including NVidia drivers downgrade. I had no recent software changes, but I did get intermittent HDMI connection errors in the last few days (cured with restart or reboot). Does it sound like a bona-fide tired cable? Contacting Rift support, will see what they say.

 

I wouldn’t expect much in the way of help from Oculus support from my experience with them for the same issue. You can check the HDMI connector pins for any obvious signs of damage. In my case it looked like the recessed +5V pin was bent. I had the black screen issues before Oculus were selling replacement cables and they refused to entertain the notion that the damaged pin was causing the problems.

 

After almost a year of it not working I decided to try again back in March. Magically it started working again. No idea what the issue was.

Link to comment
Share on other sites

  • 2 weeks later...

UPDATE. Today, after 2 weeks of DCS withdrawal, Oculus shipped me a replacement HMD + cable under warranty. But this DID NOT solve my problem! I am still getting freezes while loading Oculus Home and/or black screen, then 'HDMI not connected' error.

 

Moreover, after clean reinstall of Oculus I am now getting crashes a few seconds after PC reboot and Oculus launch. I noticed in the Event Viewer that OculusVR.exe crashed the same second as OVRServiceLauncher process was saying that OVRRedir.exe 'died with 4'.

 

I had another ticket before trying to resolve this bug (it was spamming my Windows logs) but after numerous tests and reinstalls I was told by Oculus support that 'it was normal'!! Now this bug does not seem so innocent - I hope they can investigate better.

 

Another of my theories is that one of the Oculus automatic updates broke compatibility with my Windows 7 and/or .net 4.6.2. All my non-VR games and programs work fine so I am not willing to try complete Windows reinstall or upgrade to 10 in order to fix their bugs.

 

BOTTOMLINE: Oculus developers and support stuff are complete and utter rubbish!

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

Link to comment
Share on other sites

I gave up years ago, with intermittent HDMI and went with a DP adapter. haven't had issues since then. SkateZilla and others have posted about HDMI specs not being quite to spec that can cause issues.

hsb

HW Spec in Spoiler

---

 

i7-10700K Direct-To-Die/OC'ed to 5.1GHz, MSI Z490 MB, 32GB DDR4 3200MHz, EVGA 2080 Ti FTW3, NVMe+SSD, Win 10 x64 Pro, MFG, Warthog, TM MFDs, Komodo Huey set, Rverbe G1

 

Link to comment
Share on other sites

I actually found a spare HDD and installed clean Windows 7 with all the same drivers etc, and the problem is gone! So it is NOT a hardware problem, just my old Windows got clogged somewhere.

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...