09-25-2018 09:24 AM
So myself and several people on the r/Vive subreddit with Ryzen series cpus are encountering a Blue Screen of Death and total lockups of our computers when attempting to use the vive wireless adapter. This issue eneds to be fixed and is persisting accross several types of Ryzen CPUs and mobos.
It also only seems to occur when steamvr is active. before that nothing will happen the vive Wireless app pairs to the ehadset just fine but when steam vr is used itll BSOD in about 2-10 minutes.
09-25-2018 10:11 AM - edited 09-25-2018 10:12 AM
We're assessing your report and the few others you mentioned on/Vive - We're aware of your situation and we'll be sure to keep in communication as we work to understand the behavior you're seeing.
If you are reading this thread and are currently experiencing a similar behavior, you can post here to receive a ping when we have additional updates. If possible, please share your CPU/Mobo model #'s and any "stop codes" that may be displayed if a BSOD occurs.
09-25-2018 03:00 PM
I am having same issue with computer freezing after opening steam vr (everything else connects fine) specs:
AMD Threadripper 1950x
Gigabyte Aurous x399 Gaming 7
No bsod codes, computer just completely freezes and have to do a hard reset to recover.
09-25-2018 03:55 PM
I'm also getting hard locks with no blue screen, error code, or event log when running SteamVR
Threadripper 1950X in a ASUS ROG ZENITH EXTREME
EVGA NV 1080 Ti @ 411.63
09-25-2018 08:46 PM - edited 09-25-2018 08:48 PM
I'm having the nearly the same issue. Sometimes it will BOSD to a "DPC Watchdog Violation"
AMD Ryzen 7 1800X Eight-Core Processor
Crosshair VI Hero
NVIDIA GeForce GTX 1080 Ti (184.108.40.20624)
09-25-2018 09:30 PM
09-26-2018 01:53 AM
We are experiencing the same issues with Ryzen CPU. But most of the time only when we are trying to activate the Camera for SRWorks experience. I'm happy for a quick update, because we need to showcase our app on a fair this week...
09-26-2018 03:39 PM
09-26-2018 06:01 PM
Ryzen R5 1600X
ASUS Crosshair VI Hero
Parameter 1: 00000000`00000000
Parameter 2: 00000000`00000501
Parameter 3: 00000000`00000500
Parameter 4: fffff803`f4e5e378
Caused By Driver: ntoskrnl.exe
Cause By Address: ntoskrnl.exe+1a9380
09-27-2018 07:15 AM
I am also havign BSOD
DCP Watchdog Violation and I also got Page Fault in nonpaged area once.
Ryzen 7 1800x
I have removed and re-installed SteamVR and wireless adapter. Also got a large SteamVR update today. Still have the issue.
09-27-2018 03:16 PM
Just was able to get my first real blue screen instead of just a hardlock and it was a DPC_Watchdog_Violation. Decided to check the Steam VR logs to see the log that was updated just before the crash and found this:
Thu Sep 27 2018 17:55:34.172 - Unable to load driver displaylink from C:\Program Files\DisplayLink XR\displaylink\bin\win32\driver_displaylink.dll.
Thu Sep 27 2018 17:55:34.172 - Unable to init watchdog mode for driver displaylink: VRInitError_Init_FileNotFound
Thu Sep 27 2018 17:55:34.173 - Could not create interface in driver gamepad from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\gamepad\bin\win32\driver_gamepad.dll.
Thu Sep 27 2018 17:55:34.173 - Unable to init watchdog mode for driver gamepad: VRInitError_Init_InterfaceNotFound
Thu Sep 27 2018 17:55:34.180 - error VRInitError_Init_LowPowerWatchdogNotSupported when initing driver lighthouse from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\lighthouse\bin\win32\driver_lighthouse.dll.
Thu Sep 27 2018 17:55:34.180 - Unable to init watchdog mode for driver lighthouse: VRInitError_Init_LowPowerWatchdogNotSupported
Thu Sep 27 2018 17:55:34.180 - Unable to load driver manx from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\manx\bin\win32\driver_manx.dll.
Thu Sep 27 2018 17:55:34.180 - Unable to init watchdog mode for driver manx: VRInitError_Init_FileNotFound
Thu Sep 27 2018 17:55:34.181 - Could not create interface in driver oculus from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\oculus\bin\win32\driver_oculus.dll.
Thu Sep 27 2018 17:55:34.181 - Unable to init watchdog mode for driver oculus: VRInitError_Init_InterfaceNotFound
Thu Sep 27 2018 17:55:34.181 - Could not create interface in driver oculus_legacy from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\oculus_legacy\bin\win32\driver_oculus_legacy.dll.
Thu Sep 27 2018 17:55:34.181 - Unable to init watchdog mode for driver oculus_legacy: VRInitError_Init_InterfaceNotFound
Thu Sep 27 2018 17:55:34.181 - No drivers were capable of being watchdogs. Failing init.
09-27-2018 04:13 PM
Wow, so it looks like it's looking for 32 bit driver files to initialize watchdog mode and failing because the files didn't get installed or wern't bundled with the package. Good job HTC!
09-27-2018 07:56 PM
It works sometimes for me, but will usually crash when loading into games. The Vive Pro and PC worked well before using the Wireless Adapter.
Dpc Watchdog Error
09-28-2018 01:53 PM