New to the forums? Click here to read the "How To" Guide.

Developer? Click here to go to the Developer Forums.

Preventative measure and fix for BSOD or "SYSTEM THREAD EXCEPTION NOT HANDLED" reboot loop

phoenixdigitalphoenixdigital Posts: 167
I just posted this over on reddit and thought I would post it here as well. Hopefully if someone encounters the problem this might show up in a search and help.

Preventative measure and fix for BSOD or "SYSTEM THREAD EXCEPTION NOT HANDLED" reboot loop on in Windows due to older AsMedia USB drivers and Oculus Rift.

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 ( < 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.

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 (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

The fix for those stuck in a BSOD loop

Don't PANIC! The problem is super easy to resolve. The very basic steps are.

  1. Unplug your Rift and all sensors from your motherboard.
  2. Ensure your mouse and keyboard are connected to USB 2.0 ports if possible. We are about to disable the AsMedia USB ports and if you are connected via these your keyboard will stop working until you move it to a enabled port on your motherboard.
  3. Reboot into BIOS
  4. Disable the AsMedia USB controller
  5. Restart Windows
  6. Delete the AsMedia drivers via "Programs and Features"
  7. Reboot into BIOS
  8. Enable AsMedia USB controller
  9. Restart Windows
  10. The Asmedia card will likely be auto detected and installed.
  11. Install the latest version from Microsoft here -
  12. Plug back in all your Rift devices and run through setup because you likely moved your sensors and possibly USB port locations.

Detailed instructions at these two links


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

CPU: i5 6600K (conservative overclock), GPU: Asus GTX1080Ti (not overclocked), motherboard: Asus Z170 Pro Gaming, USB Card 1: Inatek 4 Port, USB Card 2: Startek 2 Port


  • masoodabasmasoodabas Posts: 4
    A lot of windows users get this error “System thread exception not handled" is an error after windows starts and some users get this error after 10 to 15 minutes. This error came out on a Blue Screen of Death. This error occur due to driver malfunction. Mostly display driver is the common reason behind this error. So, need to uninstall the display driver and then reinstall to get rid of this error. May it will helpful
  • vertewvertew Posts: 1
    @phoenixdigital - thanks so much for posting!  I've got a vive, but the same issue seems to happen very occasionally.  in the past, I've fixed by restoring from a system back-up image, but have wasted ++++hours trying find the root cause.
    cheers   :):) 
  • YoLolo69YoLolo69 Posts: 1,158
    Ok, here an Old Asus MB P8Z77-V and AsMedia from 2016 Version I don't have any problem but anyway big thanks to you, I downloaded the latest version.

    “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,  GTX1080 OC 10%, 32GB DDR4 3200Mhz, Oculus Rift CV1

  • larabrianlarabrian Posts: 1
    edited September 2019
    The SYSTEM THREAD EXCEPTION NOT error usually occurs when a serious problem causes the computer to shut down or restart unexpectedly. Usually, this error occurs because the graphics card driver is outdated. Upgrading the driver to the latest version is one way to fix the issue. However, there could be other factors that may cause this error, such as damaged hard drives, corrupted drivers, BIOS corruptions, corrupted Windows system files or missing Windows registry entries.
    In order to fix Blue Screen of Death error, the computer must be restarted in safe mode. Once after booting the computer in Safe Mode, you have to uninstall the incompatible device driver from the Device Manager, and then download and install the latest drivers from the manufacturer’s website.

Sign In or Register to comment.