Developer? Click here to go to the Developer Forums.
Breakthrough For Many Issues: 'UserModePowerService'
If users check Windows Event Viewer and select 'Windows Logs/System' they will discover numerous messages referring to 'Process C:\Program Files\Oculus\Support\oculus-runtime\OVRServer_x64.exe (process ID:3556) reset policy scheme from {*****************************} to {******************************}
This is a deliberate decision by the developers in how OR configures the power for the headset, essentially, a combination of Windows and the hmd are constantly resetting the power policy to protect the life of the lens and save energy, unfortunately for us this causes many of the 'driving me crazy' disconnection issues. Now, Windows should not constantly be resetting power policy in reference to any device but (under instruction from the OR software) the OS does esp in Windows 7, 8 and 10, when that happens you can guarantee HDMI or Sensor disconnects.
So, with this in mind what we are going to do is force Windows to set one power policy and keep it, thereby preventing the vast majority of 'HDMI and usb sensor disconnects'
Go into your Windows power option settings and select 'High Performance', then 'advanced' and look for the USB settings, change 'Sleep mode' from enabled to Never.
2: In the Run Box bar type 'cmd', a window will appear, in that window type: POWERCFG -LIST
If you look you will see the different power plans listed and the one you just set called 'high performance' with an asterisk next to it (indicating that this power plan is active) right click and copy the GUID (that series of numbers associated with the high performance setting) ) line, open notepad and paste, then save it somewhere on your desktop.
3: In the run box type: gpedit.msc, this opens the Local Group Policy Editor which will force windows to keep the performance plan that the Rift MUST have i order to work correctly.
In the left pane, navigate here:
Computer Configuration -> Administrative Templates -> System -> Power Management
4. In the right pane of the window shown above, double click Specify a custom active power plansetting which is Not Configured by default to get this:
5. In the above shown window, firstly click Enabled and then in the Options section, input the Custom Active Power Plan (GUID) as we copied from step 1. Click Apply followed by OK. You may close the Local Group Policy Editor now.
6: When you go back into Power Options you should see this:
Finally, if you go back into Event Viewer and select 'Windows Logs/System' you should see:
See the top one?
(Also, note underneath the top one you can see OR Home is resetting the power policy every three seconds, no wonder people are getting hdmi and sensor disconnects!)
After this, you should never see a single error associated with 'UserModePowerService'
Source:
http://www.thewindowsclub.com/specify-custom-active-power-plan-windows
edit. Asmedia have released a new usb driver in the lsat couple of weeks, I installed them and the problem remains if you allow Windows OS and Oculus software to constantly reset the power policy. I recommend the above policy to force Oculus Home to stop resetting and causing disconnects.
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Comments
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
https://forums.oculus.com/community/discussion/33792/how-to-get-logs-for-bug-reports-for-consumer-rift-1-3
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
I see in my event viewer, I am having the same errors as noted in the above screenshots.
https://www.itechtics.com/enable-gpedit-windows-10-home/
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
Oculus_Logs_20160830_082132 is after I removed the power plan which produced numerous hdmi and sensor disconnects.
Oculus_Logs_20160828_112632 is with the customized power plan in place
notice at: 28/08 00:32:42.312 when I turned off customised power plan: {!ERROR!} [Kernel:Default] [DisplayManager] Failed to set power mode on NVidia adapter. -175
If I had left off my customized power plan a very long list of hardware and other errors start creeping in.
Without a doubt, the constant power resetting of the hmd is the root cause of many support issues.
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
I covered the occupancy sensor and after noting the following:
31/08 15:49:40.330 {INFO} [Kernel:Default] [DisplayManager] Completed enabling high performance power scheme successfully.
Changed power setting to "power savings" which includes USB selective suspend, LSPM and CPU throttling.
No disconnects or any noticeable effect of any kind. I toggled back and forth between various plans many times while HMD was active and nothing.
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
Gainward 1080 Founders Ed
32gb Ripjaw DDR4 memory
OS: Windows 8.1
I've appended my entire system specs and you can grab them at the bottom of the post.
Btw, Cyber, I contacted Asmedia about their USB controller in relation to the rift and a chap called Alex Chen from their HO is going to respond in the next few days.
For now, I've disabled my Asmedia USB controller and that resolves many of the issues but not the disconnections when removing the HMD, for that I carried out the above solution.
Now this is really, really interesting, would you please post your hardware details here inc OS and what your USB solution is ?
if we can find what the difference is we may be able to pin down and resolve this once and for all.
------------------—-------------------------
Excellent news!
Is there any chance you could also post your system specs as well?
No, not at all, max performance seems to be the most reliable power policy
the power management folder doesn't exist and therefor could not set the policy.
Are you referring to Event Viewer/windows logs/system 'folder' ??
OS: Windows 10 Pro (64bit)
CPU: Intel Core i5 4670K (3.4Ghz)
RAM: DDR8GB
MB: MSI Z87-G45 (Bios v1.9)
HD: SSD Samsung 840 500GB
Video: Nvidia 372.54 - (Bios 86.04.1e.00.01)
USB: MB Integrated 3.0 (eXtensible Host Controller v. 10.0.10586.212)
About to give up...
@Xmerc
Guys, can you both go into event viewer, see 'summary of administrative events'? In that box you'l see 'errors', click the '+' symbol and it will will open up, double click 'OculusVR'.
Now, please highlight each entry and report the first half a dozen here.
thanks.
02/09 17:04:16.534 {!ERROR!} [SimpleHttpRequest]
Request LibraryManager Update Request FAILED: 6: Could not resolve host: graph.oculus.com
02/09 17:04:16.534 {!ERROR!} [SimpleHttpRequest]
Request GateKeeperCheck FAILED: 6: Could not resolve host: graph.oculus.com
02/09 17:04:16.534 {!ERROR!} [NetworkRequest]
Download failed: 6: Could not resolve host: graph.oculus.com
02/09 17:04:09.742 {!ERROR!} [Kernel:Error]
Failed to get string descriptor from hub. Error: 31
01/09 17:43:33.169 {!ERROR!} [LifeCycle]
Transitions Timeout
01/09 17:43:32.471 {!ERROR!} [Kernel:Default]
[DisplayManager] Failed to set power mode on NVidia adapter. -175
01/09 17:42:01.523 {!ERROR!} [Kernel:Error]
Camera frame truncated
01/09 17:41:49.070 {!ERROR!} [DML:CameraImpl]
WMTD302K400PAK: Breaking out of capture loop due to catastrophic error. OVR Error:
Code: -8020 -- ovrError_HALNordicSyncNoFrames
Description: Sync pulses sent but no frames received
OVRTime: 1504.894111
Time: 2016-09-01 17:41:49 [69:117:800]
01/09 17:41:49.068 {!ERROR!} [Kernel:Error]
Sync pulses sent but no frames received
01/09 17:31:32.334 {!ERROR!} [OAF ERROR]
..\..\..\AppTracker\AppTracker.cpp(134) : Unexpected exit (1971039)
A Kernal-PnP error (event ID 255, task catagory 223)
The application \Device\HarddiskVolume1\Oculus\Support\oculus-runtime\OVRServer_x64.exe with process id 6148 stopped the removal or ejection for the device USB\ASMEDIAROOT_Hub\5&1b46e37c&0&0.
and
The application \Device\HarddiskVolume1\Oculus\Support\oculus-runtime\OVRServer_x64.exe with process id 6148 stopped the removal or ejection for the device PCI\VEN_1B21&DEV_1242&SUBSYS_86751043&REV_00\4&27259a83&0&00E0.