If you Installed Oculus Home, please check your Event Viewer

[ThreeDeeVision]

Hey all,

I have had the Rift installed for a few weeks and noticed a few random PC crashes, so I went to the event viewer and the OVRServiceLauncher is throwing an error every 30 seconds.

I have tried a fresh install of Windows 10 and the issue persists.  It doesn't seem to effect my Rift performance, but doesn't instill any trust in the product.  It can't be good to be spamming the Event Viewer with all these errors.  I verified I have all the latest drivers for my hardware, so I have no idea what could be causing this.

Anybody else with a Rift seeing this?

[Dfenestrator]

This is brutal, causing some serious issues on my PC.

[Numbskull]

Confirming I'm experiencing these incessant errors as well, 980ti, Win10.

[lairyboy]

Getting this error as well. Please fix Oculus

[Zenbane]

Yep, it's been happening since last night at the very least on my PC. Although it isn't impacting my Rift performance. I say that because I beat Crystal Rift last night followed by 45 minutes of Eve: Valkyrie. I also downloaded and watched "ABE VR" and "Discovery VR."

But yeah, this should probably be fixed asap since it will certainly create negative publicity on da internets.

[ThreeDeeVision]

Looks like the latest Oculus Home update fixed this issue.  Very happy to not have errors spamming that event viewer any longer :).  Thanks devs!

[RenaudS]

W10 Pro 64.

Errors still here.....thousands....

[ColinB]

I believe that the latest update 1.5 has fixed this ?
No errors reported after some hours of use.
And about time too. This was unacceptable for a (so called) consumer ready product.
But at least now Oculus can begin fixing other problems...Waiting for 1.6 now.

[ThreeDeeVision]

@RenaudS yes, I still see all the errors from before in my error log as well.  I still have over 4000 in the history of the logs.  But as soon as I got Oculus Home 1.5, the errors stopped.  Verify your Oculus Home is the latest version and also make sure the errors aren't happening every 30 seconds.

[RenaudS]

I clean my log at every reboot.
Error are logged when i launch home

25/06 04:03:35.631 {!ERROR!} [Overlays] 

[overlays_failed] { message: Failed to initialize libOVR,  }

25/06 04:03:36.336 {!ERROR!} [OAF ERROR] 

AppTracker\AppTracker.cpp(100) : Unexpected exit (1971039)

25/06 04:06:20.781 {!ERROR!} [Overlays] 

[overlays_failed] { message: Failed to initialize libOVR,  }

25/06 04:06:20.784 {!ERROR!} [OAF ERROR] 

AppTracker\AppTracker.cpp(100) : Unexpected exit (1971039)

25/06 04:06:29.068 {!ERROR!} [Overlays] 

[overlays_failed] { message: Failed to initialize libOVR,  }

25/06 04:06:29.070 {!ERROR!} [OAF ERROR] 

AppTracker\AppTracker.cpp(100) : Unexpected exit (1971039)

(...)

25/06 04:16:11.544 {!ERROR!} [Kernel:Default] 

[DisplayManager] Failed to set power mode on NVidia adapter. -175

(...)

For me 1.5 runtime isn't stable/fix for win10 PRO

Have you Pro or family win10 ?

[RenaudS]

/offtopic/
@ColinB
(...)But at least now Oculus can begin fixing other problems...Waiting for 1.6 now(...)

You right... My real problem is not error in log... it's error when i launch any game
None of them are working... "No Oculus detected"... But Home work in oculus...

1.3 runtime OK
1.4 runtime broken (of course for me)
1.5 runtime broken (of course for me)
1.6 runtime ????

/end offtopic/

I wait for dev they fix the runtime to begin to play with my oculus... For now, it s just a piece of plastic...
 😞