Hi, I've installed the software but can't use it because this crash occurs every time I plug in the DK2. The headset and sensor are plugged into USB 3.0 ports. All the latest drivers for the USB ports and video card are installed. The required Windows 7 SP1 updates are installed. My computer is very healthy. The DK2 worked fine with the 0.8 runtime. This is clearly a bug because it has an exception code and you can see the offset in the attached screenshot. That should lead you to the exact line of code.
Closing the crash message (with the Rift still pugged in) causes the Rift software to restart and the OVRServer then crashes again.
The sensor (camera) doesn't cause this crash. It only happens when the DK2 is plugged in. The Oculus software recognises the rift then within a second or so the OVRServer crashes with the attached message.
Additional Info: If I press the button on the DK2 so the light goes off, then the OVRServer stops crashing and this allows the Oculus software to run. As soon as I press the button on the Rift to switch it on this crash comes up again.
I've tried updating everything I can but the same crash comes up every time.
Thanks, but I get the same result with USB2 ports.
Cyber, I have found another user with the same bug. I looked around as I couldn't believe it would only be me. User dm18 reported he could plug in the USB - no crash at that point - the crash occurred only when the HDMI cable was plugged in. I tried this and I get exactly the same result! Other thread: https://forums.oculus.com/community/discussion/32532/oculus-crashes-when-plugging-in-hdmi
Sensor and Headset USB cables can be plugged in (to USB2 or USB3) and they are seen in the Oculus Software, with the correct warning that the HDMI cable is not connected. Connecting the HDMI causes the OVRServer to crash.
In my case it's a DK2. I think dm18 has a CV1 - In his log where it says "Oculus devices are enumerating:" it says "Rift" where mine says "Rift DK2".
EDIT: Added service log from today. Cyber already has a Log Gatherer zip I sent in a PM.
We now have the full explanation for this (link below).
Oculus specifies that you need a CPU that supports SSE4.1 instructions, but the OVRService uses an instruction called "popcnt" that was introduced at the same time as the SSE4.2 instructions. Our slightly older CPUs crash when they reach that line, although we still have plenty of CPU power.
Yes, we did just update the support page since this is not true at the moment. You do need a SSE 4.2 compatible CPU today. However, we already removed the problem instruction, so in the next update it's likely we can move back to supporting SSE 4.1. Though we aren't really testing on hardware below the recommendation, so it's hard to say if there are other issues similar to this.