first of, pretty convoluted to get Oculus support for this. No direct contact, VR-fora well hidden and pushing 'Start Conversation' didn't give me any opportunity to create a post, it just send me to different pages everytime. So a bit of a wonder I'm able to type this message. Also, I have an Oculus CV1, not an S. But apparently that isn't an option in the labels.
I'm having a problem, that seems to happening to more than just me. So it's strange I can't seem to find a solution for it. Tried everything I've come accross, but nothing seems to work: disable Nvidia digital audio drivers, installing Process Lasso and changing affinity (disabling E-cores for Oculus, giving it High Priority, ...), doing a Windows System Check,... . When Oculus is active and the hardware is plugged in, I run the risk of freezing my computer and need to do a hard reset. Sometimes I can even get a BSOD of CLOCK_WATCHDOG_TIMEOUT. Yet I don't get a dump or minidump file of it. I did find some dmp files of specific executables in my users local appdata folder. SystemSettings (which the .exe of is somewhere in the Windows folder) and Home2-Win64-Shipping (from the Oculus software) are the highest count of dmp-files. I don't know how to read dmp-files, but I was able to open them with WinDBG.
Reading these dumpfiles with WinDBG, gives me following
SystemSettings :The stored exception information can be accessed via .ecxr. (5ad0.5714): Unknown exception - code c000041d (first/second chance not available). Only thing I can find about is something about the app exits because of an 'early thread created by app'
Home2-Win64-Shipping:The stored exception information can be accessed via .ecxr. (3370.16b0): Access violation - code c0000005 (first/second chance not available) Something about access violation, that the app tries to write or read to a memorypoint where it doesn't have permission for.
My computer exists of:
i7 13700k + Pure Dark 2 cooling
32Gb ddr4 3600Mhz
Asus TUF Gaming Z690-plus wifi d4
Asus Nvidia Geforce 3060 dual OC v2
Windows 10 and installed all the latest drivers of every component
latest BIOS and firmware version
With Oculus on, Chrome and Firefox open and other stuff, it doesn't even 'tickle' the CPU. Even with VR gaming, the CPU isn't hard at work. So it has enough headroom. The temperature stays cool, fluctuating between 35°C and 55°C, so it's no overheating problem either. But I do have a feeling it has to do with those new types of processors (the ones with P-cores and E-cores or AMD equivalent). Or is this a Windows problem? And if it was already happening with 12th Gen processors, why hasn't it been addressed yet?
I bought this new pc so I could start on development of my own (VR-)game, so I really need Oculus to not crash my whole system. And certainly not a few times a day.
So what's the solution? My hardware and OS-knowledge is limited and the solution I found on the internet, haven't helped up 'till now.
I got mine fixed indeed. I tried switching connectors to different USB3-ports on my motherboard. The USB3 cable for the headset itself is the most important one I guess. So if your system crashes, try switching the headset and sensors USB3-connectors around. As I don't know all the ins and outs, it's a bit of guessing which USB3-port your system likes.
I guess USB3-ports share their powersupply with the plug next to it, with one getting priority over the other. So you have to make sure the headset needs to be plugged in the right USB3-port. Mine atleast, hasn't crashed since then.
Hey there @eyeEmotion! Wow, definitely seem like it's been a handful for you. Not to worry, we can go ahead and take a deeper look into this issue. Below we have provided a few more steps that you can take to try and resolve the issue.
Disconnect the Link cable from the computer.
Disconnect your computer from the internet.
Backup any necessary content.
You can find steps on how to do so by clicking here.
Reboot into Safe Mode.
Uninstall Oculus PC app using the Control Panel.
Delete all Oculus folders from the following folder:
C:\Program Files
Remove any Oculus folders from the following locations:
C:\Users\YourUserProfile\AppData
C:\Users\YourUserProfile\AppData\Local
C:\Users\YourUserProfile\AppData\LocalLow
C:\Users\YourUserProfile\AppData\Roaming
C:\OculusSetup-DownloadCache
Restart your computer in normal mode.
Reconnect your computer to the internet.
Install Oculus PC app again using the setup tool from our website here.
Reconnect the Rift/Link cable and re-test the headset.
If the issue still persist, collect your logs and send them over to Meta Store Support. Doing so will protect your information from being compromised. If you have any questions or concerns, reach back out! We will be more than happy to help you find a solution.
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Yeah, as you would read my message, you would now I have done just about everything. I also did a full clean install of Windows and everything. It's how I figured out Oculus software was the culprit. I'm really not going to reinstall for the n-th time. It does not fix the problem.
What logs and where do I find them? I have the dmp-files that were stored in my users Appdata folder. Do they help?
I already went to that Meta Support page. None of the questions I get presented, portray the problem I'm facing. So I would I be able to get support when the questions already stop me from getting any further?
Hey @eyeEmotion! Thank you for that rapid response. No problem, since you have already done that, we can just skip to collecting your logs. Logs files have information about our device that you have connected to your PC, as well as info about your computer specifications. This can be helpful when identifying and diagnosing issues. Below we've provided the steps to gather your logs.
On your PC, press the Windows key + R on your keyboard to open the Run window.
In the Run window, type %LOCALAPPDATA%\Oculus\ and press Enter.
Locate the OculusSetup.log file and save it.
As for Meta Store Support, if you reach out via email or our live chat, we are able to assist you more in depth. Click on Meta Store support link to get redirected to the support page. Then follow through with what it asks. Keep us updated. If you have any questions or concerns, reach out we'll be here to help!
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Hey @eyeEmotion. Thanks for reaching out! We appreciate you letting us know you were able to find the log and that you have already sent it to our support page. Once we review them to get to the bottom of your issue, we will contact you by email. If you have any questions, please don't hesitate to contact us.
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
I got mine fixed indeed. I tried switching connectors to different USB3-ports on my motherboard. The USB3 cable for the headset itself is the most important one I guess. So if your system crashes, try switching the headset and sensors USB3-connectors around. As I don't know all the ins and outs, it's a bit of guessing which USB3-port your system likes.
I guess USB3-ports share their powersupply with the plug next to it, with one getting priority over the other. So you have to make sure the headset needs to be plugged in the right USB3-port. Mine atleast, hasn't crashed since then.
Still need help?
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.
