Something to look out for after a system crash
Posted: Wed Jul 15, 2015 5:56 pmSo far I have only had one crash with this program, but after that crash I noticed an anomaly that was essentially hogging system resources on the down low. I had no active programs running in the foreground, but had the normal residual 3rd party applications running in the background, like the Oculus Server, Creative labs volume panel, Afterburner, etc. So with my system essentially idle, I was a little stumped to find that my CPU was not downclocking from its max speed. Looking further, I eventually found the culprit, and it was in fact the OVRServer_x64.exe that was consuming a quarter of my CPU processing power, while doing NOTHING. I took this screen to better explain the hang up. I simply rebooted and the problem was solved, but I wanted give a heads up that a crash with the Oculus SDK might leave your system functioning..just a little slower. It wouldn't be obvious that the program is hung up on dead threads, and one might believe that it was some random configuration issue causing poor performance. And one might waste 45 minutes trying to solve the phantom configuration issue, only to feel ashamed and vulnerable to more computer shenanigans in the future. Don't be that ONE