Headset Crashes and Only Shows White Dot (Between Crash Cycles)

[ind_trng_intl]

Hey all. I've been using my Oculus for a while now but I'm coming across a problem that I haven't been able to fix yet so I'm trying to come here. Does anyone see a flaw in my troubleshooting log, or have a recommendation of what to try next?

Here is a summary.

*
ALL I can see inside the Oculus Rift is a short squiggly white
line/dot, and occasionally the hourglass. When the headset crashes
Oculus Home installer (and previously the full application) crashes as
well and restarts itself....and then crashes again. Doesn't matter if
I'm holding down the light sensor or not.

* Light sensor in Headset switches between white light and orange light

* Swapped out Sensor with same results (I have several Rifts at my disposal)

* Swapped out Headset with same results

Initial State:

Turned on Oculus
Home this morning and got notification that I had new Oculus hardware connected
(not the case). Upon prompt I "set up new hardware" with "full
set up" then launched sim.

Rebooted desktop
later and lost headset tracking and got Windows USB Malfunction Error, and
Oculus Home showed the sensor as being not properly connected. I plugged it
into a new USB port and it showed as being connected properly.

Uninstalled Oculus
Home

Deleted File Path

Reinstalled Oculus
Home

Upon reinstallation
Oculus hardware and Oculus account were already connected - looks like I didn't
delete things thoroughly enough?

Navigated to
Settings and went through "Full Setup" again

 

Got to the sensor
set up screen then crashes.

Headset Cycle - reproduced multiple
times

 

Cover light sensor
and it lights up again and loads Oculus Home

Holding my phone up
to the headset I captured this. The red circle indicates the white light that
is displayed in the headset.

When the light
disappears Oculus Home crashes as well.

I then detached
cable from headset and plugged back in.

 

That broke the cycle
and now the light stays orange, except for when the light sensor is covered and
it disappears.

Upon trying to
reboot Oculus Home I got the above error.

 

Rebooted computer
and got USB malfunction error again

 Restarted computer
again with Sensor USB unplugged and did not receive error.

Restarted computer
with Headset unplugged but Sensor plugged in. Same malfunction again.

 

Moved Sensor to a
new USB port and opened Oculus Home to confirm that USB port is functional and
received the following error. (Note: Headset is unplugged) Selected "Skip
Setup"

Restarted computer
with Sensor plugged into a different USB port and Malfunction error opened.
Seems like sensor is bad.

Swapped out Sensor
for new sensor

 

Set Up Rift

Got past moving the
headset for the sensor to identify (which it did). Error suggests 2.0 USB port
is the problem. Switching Sensor back to original USB 3.0 port.

Crashed again after
the green circle loaded and "Sensor Tracking Confirmed."

When setup reloaded kicked me back to beginning of Sensor Setup. White light on headset. Tried five more times with identical results. Got to green loading
circle and crashed and reloaded again.

Swapped out for new Oculus Headset
with same results. Crashed and reloaded. Suspecting computer now. Fear now
being stuck in setup loop.

Oculus Forums: https://forums.oculus.com/community/discussion/32811/stuck-in-sensor-setup-loop

Performed the above
steps, uninstalled drivers from Device Manager, deleted all the above file paths, reinstalled and tried to complete Oculus Home setup with new Headset. Same results. Now rather confused.

Any suggestions guys? Here is a summary again. [repeated at top]

* ALL I can see inside the Oculus Rift is a short squiggly white line/dot, and occasionally the hourglass. When the headset crashes Oculus Home installer (and previously the full application) crashes as well and restarts itself....and then crashes again. Doesn't matter if I'm holding down the light sensor or not.

* Light sensor in Headset switches between white light and orange light

* Swapped out Sensor with same results (I have several Rifts at my disposal)

* Swapped out Headset with same results

New Oculus update might be to blame?

Thanks in advance guys!

[ind_trng_intl]

How do I post this under "Unanswered Questions?"

[Nexious]

I am in the same boat.  

[ind_trng_intl]

Nexious said:

I am in the same boat.  

In one sense I'm glad to hear that you are having the same problem. When did your headset begin having this problem?

[cybereality]

Sorry about this. We have received the reports of crashing and should have a fix soon.

[Nexious]

ind_trng_intl said:

Nexious said:

I am in the same boat.  

In one sense I'm glad to hear that you are having the same problem. When did your headset begin having this problem?

Started happening last monday.

[firebane]

I think it's 1.10.  I had no problems until that version came out.

[colinbgood]

Thank GOD its not just me... My rift at home has been working for a long time now, then a few days ago I got my touch controllers. Now I have EXACTLY the same issue as above. BUT when I uninstalled everything, downloaded the new OculusSetup.exe and ran it I got Sorry your CPU does not have SSE 4.2 -> QUIT
Not deterred by that I hacked the OculusSetup.exe to bypass the CPU architecture check and everything installed fine. The setup works all the way up to the part where it says to continue in the rift.

At this point I pulled the HDMI and it gave me the option to skip. Then oculus app opened. I press on the first contact demo, I get to see the first frame, or hour glass then white dot on a fuzzy grey background then crashes. After a few attempts like this the oculus service will lock up and I get


I then run services and goto oculus runtime service, stop it and start it again. This allows oculus app to run again. Start an app and same as above. Rinse and repeat of the same error.

My machine at home is an older machine, but more than good enough. I have a AMD thuban x6 1090t, overclocked to 4 gigahertz per core, a bunch of USB 3.0 ports, and a Titan X Pascal.

The only thing I can add beyond this is my rift at work works fine. That machine is a newer intel xeon with a 1070.



UPDATE: I frickin figured it out...

Run the oculus client app as usual.. GET THIS!
press CTRL-ALT-Numpad1  this disables that horse crap and it runs again. Thank god.

[mm0zct]

Is there any resolution to this yet? Everything works perfectly on Windows 7, but I installed a clean windows 10 system because Virtual Desktop no longer supports 7 😞

I'm also running a Phenom II (1055t), with an Nvidia 1060 (6BG). As I say, it works perfectly on the same machine with windows 7, but not in Windows 10.

I'm meant to be demoing this for a group of friends and I thought "I'll install a clean new system, on a hard disk with enough space for all the oculus applications"., and now, after leaving it overnight to download and install everything, it doesn't work at all!