Jeremy_SC2

Ah **bleep**, too bad. It is completely seamless for me now. Hope they figure out what it is soon that is causing it.

as I know you also have a threadripper, try setting it to "Game Mode" in Ryzen Master as this solved all my issues and a few other threadripper folks issues. https://community.amd.com/community/gaming/blog/2017/08/10/amd-ryzen-threadripper-for-gaming

For you other Threadripper folks, thanks to this thread on reddit I was able to get my wireless adapter working flawlessly. I just had to set it to Gaming Mode in Ryzen Master. If you havent been following my other posts on here, to get the crashing to stop I had to do a few things in my bios to get the wigig card recognized. The gaming mode fixed the performance issues I was having though. https://www.reddit.com/r/Vive/comments/9mkla2/vive_wireless_pro_on_an_amd_system/

I have the same motherboard and build, this was what I had to do to get it working pretty well...still think it can be tweeked on HTC's end though, but framerates are fine. https://old.reddit.com/r/Vive/comments/9k6qvh/possible_ryzen_wireless_adapter_workaround/

Mine only blue screened once, the rest were just hard locks. Also looking at a few other peoples motherboards, it can be pretty confusing which PCIe Slots support GEN 3.0 standard. Just do yourself a favour and make sure a) The slot physical conforms with GEN 3.0 b)The BIOS is set to make sure it is utilizing GEN 3.0

Just posted this on Reddit, Im having some luck with this, give it a try see what it does for you guys: https://old.reddit.com/r/Vive/comments/9k6qvh/possible_ryzen_wireless_adapter_workaround/

Everything crashes for me lol. SteamVR Home, SteamVR loading zone (non home), Eleven Table Tennis, Beat Saber. Might get 5 mins of laggy use that is nauseating and then bam hard lock,

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.

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.