I've searched through many solutions but unable to find a cure. Windows 10, Radeon RX 580 card (I also have an nVidia 980 GTX Ti I've tried). The oculus will install and detect (usb and display port green checks), sensors paired, but anytime I put on the headset for the first time after the "Continue in VR" screen, it will show the screen for a split second and then immediately crash as soon as I touch the sensors.
I've got an Allegro USB 3.0 card installed that it's plugged into and everything detects.
Once it crashes, the Oculus app just keeps rebooting over and over again.
I've tried different video cards, uninstalling/reinstalling from scratch, clearing my AppData Local, LocalLow, Roaming, deleting the c:\oculus.. cache on the root drive. I've disabled my antivirus protection and windows defender.
Occasionally I see these errors in the event viewer log for OVRserver_x64:
"..Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program OVRServer_x64.exe (CAPI: 1.79.0) b9d72dfc96bb-public SC:3863225380444964 because of this error..."
OK, quick update.. I mostly solved this. I was able to get my Oculus Rift S to launch and go through setup. I watched the really entertaining video of the robot handing me things to try. That was an amazing demo, really impressive.
Unfortunately, the only way I could get it to work was to downgrade Oculus to a previous client version (V25 I believe). Following the directions in this thread (on page 2 there is a pastebin that explains how to downgrade it). I don't necessarily recommend people follow it other than for informational purposes, for a few reasons I'll discuss below:
First, following this downgrade means SteamVR no longer works (it just complains that Oculus's drive is out of date). Someone mentions "OpenComposite" as a potential fix for this, but I haven't tried yet.
Second, downgrading means that some of the Oculus apps I tried (namely, Beat Saber) seem to have an issue. They load fine in the window on the PC, but in VR they just keep showing "Loading." I haven't gotten past that issue yet.
Third, downgrading means you have to redirect oculuscdn to loopback/localhost or it will auto-install a new update and it will stop working again. This means you can't buy things from the Oculus store (like Beat Saber) unless you momentarily unblock, purchase, and reblock (which is what I had to do).
But the good news is I was able to do the full robot demo, I can use virtual desktop, and the headset seems to work fine otherwise.
So after some research, my dual Xeon x5690 processors support SSE4.2 (or they wouldn't have installed Oculus) but they do not support AVX instructions. More than likely what's going on is Oculus injected some AVX instructions into the latest clients (past V25, starting around March of 2021?) and this might be the issue of the crashes I'm seeing.
So in summary, I don't know for sure, but it appears more than likely to be an AVX instruction problem. Unfortunately, my Mac Pro doesn't support processors past the Xeon x5690 on its motherboard, meaning it won't ever be able to work (perhaps the Quest 2 will? I might try that next).
Coincidentally, the Core i5-4590 that Oculus recommends in its recommend specs does actually support AVX, even though it's a slower processor than my x5690. So that would explain why their recommended setup works but mine doesn't.
Closing this out (hopefully this info is helpful to people who end up in my spot in the future). If I get the Oculus 2 to work, I'll let people know here, although the minimum specs for that say core i5-4590 also, so probably not.
Hello there, @joeknows2. We understand that you're having a hard time using your Rift S with your PC. No need to worry, we'd love to look further into this for you.
Please submit a support ticket with your PC logs, so that we can deep dive into your device. We look forward to hearing from you.
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
I have exactly the same issue. Ovrserver_x64.exe fails to launch constantly.
I tried all recommended solutions like you (uninstall, clean up, disable antivirus, restart, reinstall, restart, etc.)
Obviously something is preventing Ovrserver_x64 from launching. In the Oculus Service log file I can see an error finding packmanager.cpp
I did provide the logs to the support but I just received the standard copy/paste message stating to clean and reinstall with antivirus disabled or uninstalled.
Did you manage to find what is causing the issue? Is there a known conflict with other software ?
Oculus said my CPU score is too low. I have a 2010 Mac Pro 5,1 dual Xeon eight cores total. I have a pair of x5690’s in the mail which will raise the CPU score significantly so we’ll see if that’s the problem. The other thing I’ll try is flashing the ROM to 144.4 or whatever the latest is. Given that it’s crashing when I touch the sensors, it’s entirely possible that it’s a bandwidth issue. I have a really nice Allegro Pro USB 3 controller with dual controllers on board and 10gbps advertised bandwidth, so it should be enough. But my theory is the bus might be limiting the bandwidth without the ROM. Also my current processor supports SSE4.2 so I’m good in that department.
Otherwise I have no idea. Steam says my rig is VR ready in the high end so it should be more than enough to complete Oculus setup.
We are happy to know that you were able to get in contact with our support team about this issue, and found out what could be the cause of this. Please keep us posted on how this plays out. We want to get you back into VR, as soon as possible.
We look forward to hearing back from you @joeknows2.
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Thanks for responding. I have a very recent PC which passes all hardware tests. So I believe the issue must be different. I will submit a different Post for this.
So I've upgraded my CPU's today to Intel Xeon x5690 (dual CPU) with 6 cores each, 12 cores total, and 24 threads total. They score over 6200 on the benchmarks support gave me, but I'm still unable to use Oculus Rift S. It simply crashes in a loop when I get to the pairing controllers screen, or when I remove the device and I get to the point at which it asks me to enter VR mode and I touch the controllers. I'm not sure what to try next.
@joeknows2 I'd love to jump in here and give a bit of insight. Seeing as you're using a Mac PC, that could be one of the reasons you're having issues with our software since it requires Windows10+
Regarding your CPUs, I would highly recommend using some that fit with the Rift/S requirements listed here for the best performance.
Thanks AntiSociliazer. So I'm actually running natively on Windows 10 (not emulation or anything). The hardware itself is a Mac Pro though, but it's all intel (processor, chipset, etc). The processors I have are dual Xeon x5690's and they score over 6200 on the CPU benchmarks. One of the processors recommended in the link you gave is "Intel i5-4590" but that scores less (5343) than my current intel processor.
I agree with you though that probably something related to the hardware is giving it problems (since it started life as a Mac and now just runs Windows). Many people on YouTube have been able to make it work, but it's unclear why it may have some issues now.
It sounds like PCVR itself is a problem and something like the Quest 2 would probably work (there's a YT video where someone got a Quest 2 to work with identical hardware to mine down to the USB Pro card and processors I'm using). I'm not sure if I'm allowed so I won't post the link unless it's permitted. But the search terms are "Mac Pro 5,1 2010 vs The Oculus Quest 2: Setting up VR on a classic Mac Pro". But that's a much different hardware than Oculus Rift S.
I'll keep trying though but yeah ultimately it's looking like even though I meet the minimum specs, I'll likely have more success with different hardware. Thx
@joeknows2 Hmm, okay interesting. Regarding it coming from Mac to Windows, that could definitely be something there. Posting a link to a YouTube video isn't really harmless, especially if you're just educating so I won't hold you back.
As for the person getting it to work with the exact hardware as yours; there isn't really telling what will and won't happen when it comes to hardware that's not listed on our requirements although it would technically meet our specs. I've seen plenty a time where some hardware not listed has worked flawlessly, as well as not working at all.
As you stated, using the Quest 2 could work in this case seeing as it does differ a good bit in software and PCVR requirements but I digress.
I wish you luck on this journey and I hope it goes well. Let me know if there's any other questions or concerns!
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.
If you need an agent to help with your Meta device, please contact our store support team here.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
