Oculus, USB 3.1 and blue screen of death loop (thread exception not handled)

In these days I’ve completely formatted my VR PC. The reason? A damn blue screen of death loop.

My friend Max was playing with Robo Recall and having a lot of fun. Then suddenly he started having some audio issues, so after a while I decided to restart my PC. Well, blue screen of death. F*ck.

Oculus BSOD system thread exception not handled
Oh, f*ck (Image from Oculus forums)

Ok, I can handle it. Just restart again and… oh, no.

Oculus BSOD system thread exception not handled
That damn sad face and that damn QR code… I hate you (Image from Oculus forums)

Ok, let’s go to safe mode and…

Oculus BSOD system thread exception not handled
Not even in safe mode??? What has happened? Is my CPU melting? (Image from Oculus forums)

Well, no. I was entered the Bill Gates’s hell: a continuous loop of blue screens of death, from which I could not escape. Error was “thread exception not handled” but there was no associated file. Current BSOD have a super useful QR code that if you take a picture of it, it will guide you to a Microsoft page telling something like “This is a BSOD. If you’re seeing this, then you’re f*cked.” Thanks Microsoft, very useful.

In the end I had to use a Kubuntu pendrive to move all my data to an external hard disk and then reinstall completely Windows and all my software. I haven’t be that happy.

Oculus BSOD Thread exception not handled USB
As always, Linux in the end saves me 🙂

Why has this happened? I have no idea… but some online info gave me some suspects. I stumbled on some articles like this one and on some Oculus forums threads talking about issues with new Oculus Runtimes and USB 3.1. And I always attach my Rift to my USB 3.1 port. In particular, the damn day I’ve also switched by chance the port to which I usually attach my Rift hmd with the one to which I usually attach one of my Rift sensors. I thought: “who cares? They’re just simply USB ports…”, well, not.

The provided links of the above paragraph contain the solution to this issue and if you’re lucky enough, you won’t need to restore completely your PC (I was not lucky, of course). In short, if you have an ASUS motherboard and an Asmedia USB controller, you may have issues with Rift. So, if your system has gone crazy, you can deactivate the Asmedia controller in the BIOS and then update the drivers when windows restart (because if you deactivate the USB 3.1 ports, the system restarts again… USUALLY (again, not for me)). After the update, you can restore the controller in the BIOS… and after that everything should work like a charm. I invite to look the above links for more detailed instructions.

If you never had this issue, but you have an ASUS motherboard, please do that for you: update the damn Asmedia USB controller drivers and all USB related drivers. It is the first thing I’ve done after the PC restore.

So, hope this won’t happen to you. But in case you’ve stumbled here because of the “thread exception message”, I wish you luck.

(Header image by Oculus Forums)


AR/VR developer, startupper, zombie killer. Sometimes I pretend I can blog, but actually I've no idea what I'm doing. I tried to change the world with my startup Immotionar, offering super-awesome full body virtual reality, but now the dream is over. But I've still not waken up...