New to the forums? Click here to read the "How To" Guide.

Developer? Click here to go to the Developer Forums.

OVRServiceLauncher Spamming the event log when HMD is unplugged/plugged

LhunLhun Posts: 189
Hiro Protagonist
So far, since the 9th, there's 2313 error entries in the event log. It's also possible that this is causing a bug with windows 10 sleep mode. I've set OVRService to manual for now, but this isn't a fix... The log is flooded, constantly, and this is a really bad thing for people with SSDS. 

Any reason why this is occurring? 

http://imgur.com/pgTHbnd


Tagged:

Comments

  • ThreeDeeVisionThreeDeeVision Posts: 2,087
    Wintermute
    edited April 2016
    I have this issue as well.  OVRServiceLauncher errors every 30 seconds.  My PC just rebooted out of nowhere so I decided to take a look at the Event Log.  I wasn't even using the Rift, yet this service keeps throwing errors.  Plugged in the Rift and started Oculus Home and it is still throwing errors and warnings.

    I just uninstalled and reinstalled Oculus Home and installed on a different drive.  The OVRServiceLauncher error is still happening every 30 seconds completely spamming my Event Logs (Going on 40000 of them now).  The strange thing is the Rift works perfectly, so these errors don't seem to effect the performance.  I will see if I can find a fix, but I will probably have to uninstall Oculus Home if these errors keep happening.

    This is the error:
    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: 
    [SetProcessGPUPriorityClass] Target process did not respond in time
    the message resource is present but the message is not found in the string/message table
    i7 5960X @ 3.8 GHz | Corsair Vengeance LPX 16GB DDR4 PC2800 | GTX Titan X Pascal | Win 10 64 bit | Asus ROG PG348Q | EVGA X99 Classified
  • ThreeDeeVisionThreeDeeVision Posts: 2,087
    Wintermute
    edited April 2016
    Going to try a fresh win 10 install because I am running an upgrade from win 7 and have had some other strange issues.  I will let you know how it goes.  Looks like there is an upgraded bios for my board too :).

    Got all the Win10 drivers installed for my various hardware and first thing I did was install Oculus Home.  Same errors every 30 seconds :(
    i7 5960X @ 3.8 GHz | Corsair Vengeance LPX 16GB DDR4 PC2800 | GTX Titan X Pascal | Win 10 64 bit | Asus ROG PG348Q | EVGA X99 Classified
  • CMonsterCMonster Posts: 2
    NerveGear
    Same here - do you have any updates on this?
  • rossross Posts: 3
    I'm having the same problem.
  • BEARDEDFIGNUTZBEARDEDFIGNUTZ Posts: 51
    Hiro Protagonist
    I am also having the same issue. Anyone have any updates?
  • BEARDEDFIGNUTZBEARDEDFIGNUTZ Posts: 51
    Hiro Protagonist
    I have this issue as well.  OVRServiceLauncher errors every 30 seconds.  My PC just rebooted out of nowhere so I decided to take a look at the Event Log.  I wasn't even using the Rift, yet this service keeps throwing errors.  Plugged in the Rift and started Oculus Home and it is still throwing errors and warnings.

    I just uninstalled and reinstalled Oculus Home and installed on a different drive.  The OVRServiceLauncher error is still happening every 30 seconds completely spamming my Event Logs (Going on 40000 of them now).  The strange thing is the Rift works perfectly, so these errors don't seem to effect the performance.  I will see if I can find a fix, but I will probably have to uninstall Oculus Home if these errors keep happening.

    This is the error:
    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: 
    [SetProcessGPUPriorityClass] Target process did not respond in time
    the message resource is present but the message is not found in the string/message table

    Did you ever resolve this issue?
  • RedRizlaRedRizla Posts: 6,989 Valuable Player
    No, it's still an ongoing problem.
  • DeaconnfrostDeaconnfrost Posts: 47
    Brain Burst
    Noticed the same issue myself last night in event log. Windows 10. It's constant
  • eisenb11eisenb11 Posts: 30
    Brain Burst
    Yeah, same issue.
  • ThreeDeeVisionThreeDeeVision Posts: 2,087
    Wintermute
    I submitted a support ticket and sent them my error logs and got the standard "thanks for showing us, we will fix it soon..." message and nothing more.  There was an Oculus Home update but it didn't fix this issue.  I will keep an eye out though.  Oculus processes shouldn't be running when the HMD isn't in use, period, much less spamming errors to the error log every 30 seconds.
    i7 5960X @ 3.8 GHz | Corsair Vengeance LPX 16GB DDR4 PC2800 | GTX Titan X Pascal | Win 10 64 bit | Asus ROG PG348Q | EVGA X99 Classified
  • marc0marc0 Posts: 4
    NerveGear
    Same issue here, including PC freeze when starting Oculus client
  • TwoHedWlfTwoHedWlf Posts: 2,234 Valuable Player
    Oculus processes shouldn't be running when the HMD isn't in use, period, much less spamming errors to the error log every 30 seconds.
    How is the oculus process supposed to know if the HMD is in use if it doesn't poll for the HMD to see if it's in use?

    Not really worth putting an error into the event log,. But not really much more than an annoyance Unless you're wanting to go back months through the event it doesn't matter much if it's adding a lot of events and pushing older ones off the end of the log sooner.
  • ThreeDeeVisionThreeDeeVision Posts: 2,087
    Wintermute
    TwoHedWlf said:
    Oculus processes shouldn't be running when the HMD isn't in use, period, much less spamming errors to the error log every 30 seconds.
    How is the oculus process supposed to know if the HMD is in use if it doesn't poll for the HMD to see if it's in use?

    Not really worth putting an error into the event log,. But not really much more than an annoyance Unless you're wanting to go back months through the event it doesn't matter much if it's adding a lot of events and pushing older ones off the end of the log sooner.

    Easy, make it a push event from the HMD instead of a pull event that fires every thirty seconds.  There is absolutely no reason any OVR processes should be running if the HMD isn't in use.  My PC is used for many other things besides the Rift, such as the Vive and regular PC gaming.
    i7 5960X @ 3.8 GHz | Corsair Vengeance LPX 16GB DDR4 PC2800 | GTX Titan X Pascal | Win 10 64 bit | Asus ROG PG348Q | EVGA X99 Classified
  • DeaconnfrostDeaconnfrost Posts: 47
    Brain Burst
    EASYJABBA said:

    Ok where is the data being sent too? The data is being sent to Facebook servers? Ok what the hell is being sent to Facebook? My Data!!!

    This is like being angry that testflight has to call apple servers to return your data. People have beat up the information being transferred at length and there is no personal identification information being transmitted. Hardware logging and software logging is commonplace.
  • rankinsectrankinsect Posts: 61
    Hiro Protagonist
    edited June 2016
    I have no difficulty at all in stopping the Oculus runtime, either by terminating the process or through the Services panel.  I have waited several minutes and refreshed, and it doesn't come back for me.

    And is this "account" you are referring to called "NT Service\OVRService" or "NT Service\OVRLibraryService"?  That's a "virtual account" created by Windows - in fact every version of Windows since Vista always has one behind the scenes for every service, even services that never run or services that are configured to run as other users.  These aren't real accounts, they are security principals; Microsoft creates them to allow simple use of service accounts.

    It's actually much better for admins if a service runs as a service account rather than as the generic "system" or "local service" accounts, since if the service runs as its own service account, you can control its access much more granularly.  You can actually set this up for any service on your machine, even those that typically install themselves as "system".  For example, if I didn't want the iTunes service to have access to a directory, I could change it to use its virtual service account - NT Service\iPod Service - and then forbid directory access to that service account.

    I definitely don't see any new actual accounts on my machine.
  • DeaconnfrostDeaconnfrost Posts: 47
    Brain Burst
    EASYJABBA said:

    Hello,

    With all due respect I'm not buying it, the Oculus server processes refuse to end even if you manually end the process it starts back up immediately, there isn't any I repeat any process which acts like this I can literally end any process I wish. The reason why you ask? Is because oculus driver places an account with Admin rights to your unit.

    Disgusting tactics Oculus you lost another customer.  

    I think you're frustration is getting the better of you in this case, you can stop the process with no issue. 

    The previous comment by rankinsect is spot on. I'm starting and stopping the process right now with no issue.

    Check out this link for more detailed research: https://www.reddit.com/r/oculus/comments/4da3r5/oculus_home_network_traffic_detailed_analysis/

    Hope this helps in some way.
  • ThreeDeeVisionThreeDeeVision Posts: 2,087
    Wintermute
    This looks to be fixed in the latest Oculus Home update.
    i7 5960X @ 3.8 GHz | Corsair Vengeance LPX 16GB DDR4 PC2800 | GTX Titan X Pascal | Win 10 64 bit | Asus ROG PG348Q | EVGA X99 Classified
  • Huambo81aHuambo81a Posts: 57
    Brain Burst
    Not fixed for me . . i have 11,500 errors since Tuesday
  • rankinsectrankinsect Posts: 61
    Hiro Protagonist
    The nearly constant OVRServiceLauncher errors are fixed - I haven't logged any since 6/23.

    There are still errors the Oculus can log - most notably when the HMD is disconnected - but those are not the same issue as originally reported.
  • FistnGypsyFistnGypsy Posts: 18
    NerveGear
    I have a similar issue, but it more than just annoying, the computer immediately shuts off. No shut down process, or info of any kind, just dead. It boots up and the only info showcasing this issue is a massive amount of errors in the event log.

    I have noticed the 2 updates the Oculus set up files claims Im missing, {KBXXX}. I can uninstall and reinstall the first update, but update KB3033929 doesn't show up on my system, MS says its installed... I use the CMD command to bypass the hotfix but if I really dont have KB3033929, and MS says I do, this may be why I get the crash. It seems that everyone else that gets the errors in their logs are still able to operate.

    **Below is the Error Log Entry I get after the crash occurs:

    "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: 

    21/02 00:18:08.088 {!ERROR!} [Input] 
    X360Emulation: Unable to initialize gamepad emulation - Driver may not be installed. Error=1"
  • BNS.Random.PrecisionBNS.Random.Precision Posts: 3
    NerveGear
    edited August 2017
    I'm getting those errors now - a year and more since it was first posted about on here. Please tell me Oculus have a fix by now?
  • MindsEye69MindsEye69 Posts: 2
    NerveGear
    I'm still getting them in 2020 so my guess is this was never fixed.
Sign In or Register to comment.