08-25-2017 05:43 PM
I thought I would post this here as there are still a few users
encountering this pretty horrific issue which is easily fixed. This
issue is NOT widespread but when it happens it can leave you thinking
your computer is completely screwed and you have to reinstall. You don't
need to reinstall you just need to follow some simple steps.
Hopefully there are enough key words in this post and title so that
anyone encountering this issue can find it before they freak out too
much.
The Issue
This seems to affect people with motherboards with an AsMedia USB
controller using drivers older than Jan 2017 ( < 1.16.36.1). I
believe this only occurs when you plug Rift components into these
AsMedia USB 3.1 ports.
It doesn't happen to everyone but when it happens it sucks. It starts
off with a Blue Screen of Death (BSOD) stating that "SYSTEM THREAD
EXCEPTION NOT HANDLED". If you are one of the unlucky few Windows will
try to boot and you will get the same BSOD.
Sometime unplugging the Rift doesn't help and you still are stuck in the reboot loop.
Trying to get into Safe mode doesn't work. I can't remember the error but you are still stuck in a reboot loop.
I reinstalled Windows 5 times before I found this solution which is super simple.
Could you be affected by this?
This appears to ONLY affect users with motherboards with AsMedia USB
controllers. It also appears to only happen very very rarely so don't be
too freaked out. This post is mainly to help people who encounter the
issue when the stars align in just the right way.
It is pretty easy to tell. Just check the support page for your
motherboard it will usually list the USB controllers somewhere on that
page. Like this for my motherboard.
http://imgur.com/gallery/Nb43J
I also included an example of a motherboard that does not have these
controllers as well as the support page showing the latest drivers from
2015 that Asus is providing its customers. These drivers still contain
the issue that can put you in a BSOD loop. Update to the latest Windows
ones linked below.
Preventing this from happening to you
If your motherboard has an AsMedia USB controller update your AsMedia
drivers to anything greater than 1.16.36.1 (2017-01-03) which is when
the specific fix for this problem was made.
If your motherboard manufacturer is too lazy to give you updated
drivers then use the latest Windows version here from April 2017
https://www.catalog.update.microsoft.com/Search.aspx?q=asmedia%201.16.47.2
The fix for those stuck in a BSOD loop
Don't PANIC! The problem is super easy to resolve. The very basic steps are.
Detailed instructions at these two links
https://forums.oculus.com/community/discussion/comment/501927/#Comment_501927
or
https://www.vrheads.com/why-youre-seeing-system-thread-exception-not-handled-after-oculus-update
Why is it still happening?
Because some manufacturers (I'm looking at you ASUS) are still
listing as the latest version the old AsMedia drivers which are prone to
this dangerous bug for Rift users.
Some newer model Asus motherboards like mine "Asus Z170 PRO Gaming" are saying the latest drivers are the ones from August 2015, over 2 years older
than the ones available from Microsoft. The updates which stop this
dangerous BSOD loop happening have been out for a very very long time.
What is your deal Asus?
Most other manufacturers like MSI have the more recent versions of
this driver with the patch applied. Not sure why Asus is dragging their
feet on this.
More reading
The original source of the fix and discussion on this issue can be found here
https://forums.oculus.com/community/discussion/comment/552145
02-06-2018 11:34 AM
11-17-2018 02:09 AM
11-17-2018 03:21 AM
“Dreams feel real while we are in them, it's only when we wake up that we realize something was strange.” - Dom Cobb
"Be careful, if you are killed in real life you die in VR too." - TD_4242
I7 10700K, RTX 3070, 32GB DDR4 3200Mhz, Oculus Rift CV1
09-23-2019 09:35 PM