OVRServer_x64.exe 202883-public TCID:964894 has stopped working

[Scawen]

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.

Exception Code: c000001d
Exception Offset: ...00f5e1d

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.

[cybereality]

I know this is a little extreme, but have you considered upgrading to Windows 10? That has helped some people get their setup working.

[elboffor]

Holy double-triple post in one thread batman!

I have to echo what cyber says here though, Win10 is the latest (and in my eyes) greatest OS out and will work best for most VR

[Royspain]

cybereality said:

I know this is a little extreme, but have you considered upgrading to Windows 10? That has helped some people get their setup working.

To be even more slave of microsoft? no, no the day i need other OS i back to Linux to be owner of my own pc...

[elboffor]

and play no games...

[Royspain]

I will try installing win10 as second SO then i start in win 10 just to play oculus (if I can exe the games/aplications, it seems there are probs with w10 and some programs) and win 7 to all but oculus since i have an SSD hd for SO and takes 12 scs starting win7 (I know I have to install win10 in a different hd but hope it will take no more of 30 scs starting win 10) anyway oculus support are studying all the information of my pc and seems are going to reply soon, though I am sure it won´t be before monday or...)

[Royspain]

Evening, installed win10 as second OS cause there is no way to finish
setup with win 7 and in win10, oculus setup dont even start downloading
soft, it crashes with ""Cant Connect It looks like we cant reach the
oculus server.
Please check your connection."

No antivirus, no
firewall but disabled win10 firewall, clean installation, all win10
updates and last driversm I just can not believe it, and after 15 days
and oculus support did NOTHING, im getting angry WHAT KIND OF JOKE IS
THIS?

[Royspain]

Well, the "problem" was that the hd where installed win 10 was in dynamic,
when oculus soft needs it in basic (mbr) format... as nerd as that...
who told me to convert to basic? no one... no one who had too, of
course... I found it looking in forums by my self and if I have visited
near 100, I see it twice, one of them in this forums from someone who
wanted to help, no more, no less.... great support team, great...

[3duserjax]

I have the same issue. After the latest update, (that I did not want!), it kept telling me that drivers needed to be updated. After 5 times of saying yes, update, it would come up and work for a few minutes then crash.
Same error as original in this thread---
ovrserver_x64.exe 730459-public SC:2514551092 has stopped working

 After a reboot, or restart of ovrserver, it went through the driver updates again 5 times.

 I would just like to go back to the old version which took me 6 months to get working reliably. Then the forced update broke it! Just let me have the old version ,,,,PLEASE!

[3duserjax]

cybereality said:

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.

 
So why can't we just have the older version that works with our CPU's? I don't get it, if it works for us, leave it alone! What part of this is not understood?