cancel
Showing results for 
Search instead for 
Did you mean: 

I'm almost giving up... hours, days, weeks of troubleshooting :@

Insr33
Explorer


Hi
All



I
must say I have never ever encountered the amount of misery I'm having since I
bought an Oculus Rift.  Don't get me wrong the device itself (if working)
is great to play on but boy did I get my share of misery.  Lockups, black
screens, usb going berserk you name it.  I hope someone here can help me
get out of this hole because I'm sick and tired of
troubleshooting.  20% of the time my rift is connected I'm
troubleshooting.  Ok, rant ended.  Let me describe my problems.



As
many of you have experienced I have the sensor disconnect problem.  I'm
reading that the devs are on it so I'll leave that hoping there will come a
solution. 



The
main problems I have for the moment are:



After
20 mins of playtime (iRacing) my Rift starts to show black screens.  The longer I wait the more black screens I
get resulting in a complete black screen. 
If I look into my eventvwr I see the error:  



“The Oculus VR Library Service service terminated with the following
service-specific error:



There are no more
files.”



A lot of other
errors as well but don’t know which one really causes all the problems.  I’m on the latest video drivers + oculus
update.  Here is the rest of my rig:



Asus sabertooth x99

Core I7 -5820K

32 gigs of ddr3

M2 ssd drive



Also using hdmi + usb extension cables (3m) 
I ordered the ones that were recommended here on amazon.  Having the problems as well when connected
directly on pc.



Let me know what I
can do to end this please.



 



 



29 REPLIES 29

cybereality
Grand Champion
Can you revert to the Nvidia 368.x driver until we figure this out? Thanks.
AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV

Scawen
Heroic Explorer
Recently I tried drivers 368.81 and 372.70 but found they were both unstable.  There were quite a few driver "crash and restart" events each day, even while simply using Firefox to look at a website.  It was too frustrating and they didn't help with the Rift black screens either so I reverted to 364.72 which doesn't crash.
Live for Speed - www.lfs.net

Insr33
Explorer
Have new issues since yesterday.. I installed Virtual Desktop via the Oculus store and start it prior to start Iracing.  As you return to desktop between each session it's handy to remain seated in my simulator.  However since yesterday my Virtual Desktop seems to pop up for no reason and blocks my screen during gaming.  If I then rerturn to game I can continue my session but it's very annoying.  Any fix for that guys.  Really think I should put my headset away for some months until all this misery is (hopefully) over... 

UnFknBLievable
Expert Protege
Haven to had any issues. Everything has been rock solid.

Latest ASmedia USB drivers, uninstalled intel USB controller drivers and let windows reinstall it, I got asus AI suite installed and sensor plugged in to my monitors powered USB 3 hub.

Keep sensor cables away from PC

Techy111
MVP
MVP
That ai suite may cause micro stutters, did for me so I uninstalled it. Something to keep an eye on ?
A PC with lots of gadgets inside and a thing to see in 3D that you put on your head.

Scawen
Heroic Explorer
I can confirm more results along the same lines, this time using Dreamdeck and Invasion.

Typically, after starting OVRServer then starting a program, one person can watch the experience, with possibly a few one second blackouts.  The second person puts on the headset and watches the experience.  The black screens will start and at some time near the end of the experience, there will be a permanent black screen.  In the longest case I've seen, we got to the third person before the black screen.

When the permanent black screen event occurs, on the OVRServer console window the red message "Device dependent timestamp too far from sample timestamp by -2707.87 msec" is displayed, as reported above with a screenshot.
https://forums.oculus.com/community/discussion/comment/438966/#Comment_438966

We enjoyed Dreamdeck.  It's a nice demo.  The kids liked Invasion but I haven't seen it now, just shut down OVRServer after the permanent black screen event (the second person watching, as described above).  Restarting OVRServer cures the black screen until the next time, some minutes later.

I should add that the programs are running perfectly on my computer, smoothly and so on, until the one second black screens and eventually the permanent black screens and the timestamp error message.

I have also re-routed the sensor cable, tried to keep them away from other cables as much as possible.  It doesn't make a difference in my case.  It does look like a software error as it is cured by restarting OVRServer.
Live for Speed - www.lfs.net

Insr33
Explorer

Insr33 said:

Have new issues since yesterday.. I installed Virtual Desktop via the Oculus store and start it prior to start Iracing.  As you return to desktop between each session it's handy to remain seated in my simulator.  However since yesterday my Virtual Desktop seems to pop up for no reason and blocks my screen during gaming.  If I then rerturn to game I can continue my session but it's very annoying.  Any fix for that guys.  Really think I should put my headset away for some months until all this misery is (hopefully) over... 


Solved this issue thank to someone on the iracing forum.  It was the voice activation setting that caused this. 

Scawen
Heroic Explorer

Insr33 said:



Solved this issue thank to someone on the iracing forum.  It was the voice activation setting that caused this. 


But do you still have the black screens issue?  It's still happening here.

Definitely a software issue, as it can be solved by restarting the OVRServer (Oculus runtime).

As said before, it's a series of one-second black screens and eventually a permanent black screen with the message "Device dependent timestamp too far from sample timestamp by -2707.87 msec" (though the number of msec may vary).
Live for Speed - www.lfs.net

jeffnebraska
Honored Guest
I have had the same issue since I first installed my Rift, but I solved it last night.  I added a mini displayport to HDMI adapter and the problem went away.  Notably, I had tried that before with a different mini displayport to HDMI adapter and got no image, so I figured it wouldn't work.  But the adapter I tried last night, which is bulkier than my original one, and is an expensive adapter I got from the Mac store solved it.  I was able to play the Climb with no black screen flashes for as long as I wanted.

Note that I also think its an NVIDIA issue, and I have a laptop with a 980GTX card. 
Still need help?

Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.

If you need an agent to help with your Meta device, please contact our store support team here.

Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.

Check out some popular posts here:

Getting Help from the Meta Quest Community

Tips and Tricks: Charging your Meta Quest Headset

Tips and Tricks: Help with Pairing your Meta Quest

Trouble With Facebook/Instagram Accounts?