BSOD while using Steam VR

Hagbard · 11 May 2016

Hi there!

I own a HTC Vive for a few days now and everytime I use it, playing Steam VR, i get an BSOD (System_Service_Exception) after approximately one hour. I already cleaned the registry using CCleaner, ran sfc /scannow as admin, mad ea clean install of the newest version of my graphics card driver and upgraded my BIOS to the newest version, but still the same issue.

WhoCrashed tells me the following:

On Wed 11.05.2016 17:08:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051116-10421-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR

On Wed 11.05.2016 17:07:27 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80028C4DFE2, 0xFFFFD000A6D7EDB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

My System:

Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., M5A97 LE R2.0
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 8484155392 bytes total

My graphics card is a AMD Radeon R9 390 from XFX

I don't know what to do anymore :-\

axe0 · 12 May 2016

Seeing the minidump is corrupted we'll need to try driver verifier

Diagnostic Test

DRIVER VERIFIER

Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.