Hi. I'm on the Beta channel and since the update to Core 2.0 I'm getting hard freezes most of the times I open Oculus Home, requiring a restart (keyboard leds stop responding). Also, something weird is that when it doesn't freeze, it does stall for several seconds and the "new hardware" sound is played, which it didn't do before. Am I the only one?
Same thing here. The second I start loading the program, I get a hard freeze for 10-20 seconds. Then it will intermittently unfreeze/refreeze until I'm forced to restart. Killing all processes related to Oculus does not solve the issue, only a restart.
I have tried reinstalling video drivers (Nvidia), uninstalling/reinstalling numerous times on different drives (an SSD and HDD). Also tried manually uninstalling the drivers for the sensors.
Only thing I could find in the Event Viewer about it was -
Warning,12/20/2017 7:08:09 PM,Microsoft-Windows-Kernel-PnP,225,(223),The application \Device\HarddiskVolume6\Program Files\Oculus\Support\oculus-runtime\OVRServer_x64.exe with process id 4696 stopped the removal or ejection for the device USB\VID_2833&PID_0211&MI_00\9&24a304b7&0&0000.
Also been having freezing issues with the public beta build, mostly when going between headset to monitor or using the desktop viewer, I was starting to think that it might have something to do with my monitor being at 144 hertz. But I've also had my system freeze just by launching the app.
Also to note - my issues aren't stemmed from the beta build. When I reinstall, my beta opt-in is off so this seems to be on any (maybe recent?) version.
Juin_Roet mentioned he has a 144 htz monitor, I have recently installed one since last running the software. Unfortunately, unplugging that didn't resolve any other issues.
Only other thing I changed was moving from an i7 to a Ryzen 5. I had to reinstall Windows at this time, obviously, so I don't really have any old logs/experiences to share on that.
Another strange thing to note - after the system hangs itself for about 20 seconds, my mouse goes bonkers. Invisible on 2nd and 3rd monitors, not changing back to a pointer, just stays as what it last was. I doubt it means anything, but figured I'd report as much as I could in hopes of finding an answer, as I'm at the bottom of the barrel.
It just occured to me to check the event log after one of these crashes, and in System events, I found the following:
First, a Service Control Manager error that says (exact text may vary, as my Windows is in Spanish) The OctBroker service shut down with the following error: Incompatible request.
Then there's a couple of information events, and then come two identical DistributedCOM errors that say (again, I'm translating this myself so it may not be the exact text in English): The application-specific permission configuration doesn't grant the Local Activation permission for the COM server application with CLSID
to the user NT AUTHORITY\LOCAL SERVICE with SID (S-1-5-19) at the address LocalHost (with LRPC) running in the application container with SID Not available (Not available). This security permission may be modified via the Component Services administrative application.
I checked Google and the OctBroker service is called "Microsoft Octagon Broker Service". No clue what this is. Had never heard of any Microsoft Octagon until this day.
@cybereality any chance you can have someone look into this? My PC is otherwise perfectly stable (no overclock), and I've already reinstalled the OS and the issue still occurs. Also, there's other people having the same issue.
I'm guessing the PC dies the moment Oculus Home initializes the Rift as a display. The "new hardware" sound plays, my monitor loses signal, and shortly after (the time varies) the PC reboots.