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

[Insr33]

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.

[Flausn]

i get disconnects every few minutes now...your rift is not connected your we couldnt find your sensor ...its annoiing...what is so difficult to fix this bug ? in devices it shows usb 2.0 then 3.0 then 2.0 and this dissconect connect sound are really annoiing. greez

[Anonymous]

Flausn said:

i get disconnects every few minutes now...your rift is not connected your we couldnt find your sensor ...its annoiing...what is so difficult to fix this bug ? in devices it shows usb 2.0 then 3.0 then 2.0 and this dissconect connect sound are really annoiing. greez

If you know the answer to the fix - please let us know as well 🙂 There are a lot going from Windows chaning how USB work to some background changes that went on with the USB drives to some new changes to the Oculus driver as well. Hell even the motherboard has some say in the way USB work adding another layer of problems. To pin down what is causing the problem - that's harder to find then a rock on a ground.

For proof - I don't have this problem yet I have asus board as well - so you shouldn't be having this problem either if we're both on the same updates and software. If that's true, then that only leaves your software/hardware environment that will be the only difference. If so, then the problem would be kind of on your side of things. See where this is going?

It could very well be a hardware issue with the cameras. I haven't roll that out as a possible, but it does seem weird that it's a small number of users instead of everyone having this issue.

[Insr33]

Had another 10 min session today.  Had changed my power settings
policy to forced "high performance".  Unfortunately my session
was (again) unplayable due to black screen interrupts. I must say in the past I
was able to play without black screen interrupts so it must definately be a
combination of windows update with usb drivers / Oculus drivers / firmware.
 The Sensor disconnect was always there though.. 

Please Oculus grab your team together and fix
this.  I can completely understand that the first gen headsets can have
some bugs but this is just completely unplayable.  If I think about the
amount of time and money I invested into this VR project (Headset , new pc,
troubleshooting) it just makes me sick.  I hope Oculus will give first gen
users a big discount on their next set.  We are just beta testers for your product it
seems

PS: OculusSetup.log attached

These logs appeared in my eventvwr:

The description for Event ID 0 from source OVRServiceLauncher cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

[LauncherService] Unable to launch: There is no active interactive user session.

---------------------------------------------------------------------------------------------------------

Detected unrecognized USB driver (\Driver\asmtxhci).

---------------------------------------------------------------------------------------------------------

Detected unrecognized USB driver (\Driver\ACPI).

---------------------------------------------------------------------------------------------------------

The description for Event ID 0 from source OculusVR cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

22/09 19:46:12.789 {!ERROR!} [OVRServer] 

Could not download compatibility data

-----------------------------------------------------------------------------------------------------

The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

------------------------------------------------------------------------------------------------------

The description for Event ID 0 from source OculusVR cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

22/09 19:48:14.754 {!ERROR!} [Home] 

[home_error] { description: [Build] Not yet implemented: LogQEExposure, stack:    at System.Environment.get_StackTrace()\r\n   at Assets.Scripts.SnapUI.Lumberjack.Lumberjack.MakeLine(Level level, System.String tag, System.String message, System.String[] append)\r\n   at Assets.Scripts.SnapUI.Lumberjack.Lumberjack.Log(Level level, System.String tag, System.String message, System.String[] append)\r\n   at Assets.Scripts.SnapUI.Lumberjack.Lumberjack.E(System.String tag, System.String message, System.String[] append)\r\n   at Assets.Scripts.Config.Platform.OnNotImplemented(System.String feature)\r\n   at Assets.Scripts.PlatformSpecific.Rift.HomeApplicationRift.LogQEExposure(System.String universeName, System.String groupName, System.String userId)\r\n   at Assets.Scripts.DataStores.QuickExperimentDataStore.LogTestExposure()\r\n   at Assets.Scripts.DataStores.QuickExperimentDataStore.HandleDispatch(Assets.Scripts.SnapUI.Routing.SnapDispatchEventArgs eventArgs)\r\n   at Assets.Scripts.SnapUI.Routing.SnapStore+<SnapStore>c__AnonStorey3E.<>m__F(Assets.Scripts.SnapUI.Routing.SnapDispatchEventArgs args)\r\n   at Assets.Scripts.SnapUI.Routing.SnapDispatch.Dispatch(ISnapDispatchable dispatchable)\r\n   at Assets.Scripts.SnapUI.SnapUISystem.HandleEnqueuedDispatchables()\r\n   at Assets.Scripts.SnapUI.SnapUISystem.FrameUpdate()\r\n   at Assets.Scripts.SnapUI.SnapUISystem.DispatchSystemThreadActions()\r\n   at Assets.Scripts.SnapUI.SnapUISystem.SystemDispatchThreadFunc(),  }

[Scawen]

I realise that Oculus don't "fix" those non-existent "bugs" any more, but maybe this could be a clue, in case you would like to do a "Rift Visual Experience Improvement Update".

I got a few "black screen experiences" without any visible errors at all, but when it gave me a permanent "black screen experience" (necessitating removal of the headset) this error message was displayed.

Device dependent timestamp too far from sample timestamp by -2707.87 msec

I realise it's all part of the fun but I feel it would be a lot more fun in a racing simulator if I could stay on the track.  I find the black screen experiences a little unwelcome.

[Scawen]

To be clear, there aren't any log messages at all displayed (in OVRServer_x64.exe console) when the normal black screen events occur.  No red errors and no white messages either.  It seems the software is unaware that anything is wrong.

[viengthieugia]

black screen, please check

[cybereality]

From what I have gathered in the forum, the black screen issue is unique to the Nvidia driver. We still need to investigate further, so any more log files would be helpful. Thanks.

[Scawen]

I might do some log files at some point, though I'm trying to sort other things out at the moment.

Some more info, I have tried various Nvidia drivers and always had the same issue with the CV1, also with all runtimes 1.3 to 1.8.  Today I tried the DK2 and managed several laps without a black screen.  So possibly it's specific to the CV1.  But my test was not long enough to be conclusive.

I'll report back if I try the CV1 and the DK2 again to see if the black screens really don't appear on the DK2.  By the way, the black screens do not seem related to anything physical like head movements.  They do seem random.  Sometimes there is also a repetitive sound crackle that can start some time before the black screens start.  The sound crackle can get worse, with additional repetitive crackles as if a looping sound buffer has become corrupted.  The sound crackle is not audible if I select a different audio device.

It these are related then it may be some kind of memory trasher.  If there is a memory trasher then of course it could be the cause of countless unexplainable issues.

[cybereality]

I've heard of audio issues happening on Asus motherboards due to conflicts with software like AI Suite. If you have an Asus mobo, you may want to uninstall the Asus software.

[Scawen]

Not ASUS - It's a Gigabyte one and there's no ASUS software that I can see.  My PC has the minimum installation that I can get away with really as it's for development and I just want a quick booting clean computer.  All runs perfectly until the black screens start happening after a few minutes...