![]() ![]() Sat 23:44:55.287 - ASMedia USB 3.0 eXtensible Host Controller - 0.96 (Microsoft) Sat 23:44:55.263 - USB Controller Details.Number of Controllers=6 At the start it looks like vrserver spins over the list of USB controllers: I used ProcMon to see what registry keys vrserver was accessing before it crashed. Since no amount of SteamVR re-installing was fixing the problem, I figured this must either be a problem with some driver on my machine or something in the registry. I figured out what was causing the crash (well what driver anyway). I'm happy to provide any additional info if they will help. (4be0.1ea8): Access violation - code c0000005 (first/second chance not available) The stored exception information can be accessed via. When opening the dumps inside windbg and running !analyze I got the following interesting snippets of output related to a null pointer exception: When I did this I noticed I was getting dmp files generated in my E:\Program Files (x86)\Steam\dumps folder named crash_vrserver.exe_.dmp. So it looks liked something bad was happening with vrserver after all. Thu 23:19:49.350 - Giving up server connection over pipe VR_Pipe after 50 attempts Thu 23:19:44.318 - Starting vrserver process: E:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\win64\vrserver.exe ![]() Thu 23:19:44.310 - vrclient startup with PID=7784, type=VRApplication_VRMonitor, config=E:\Program Files (x86)\Steam\config Then I checked vrclient_vrmonitor.txt and found this: I took a peek at vrserver log but it didn't seem to show any errors. No amount of rebooting, reinstalling SteamVR, reinstalling Steam, unplugging and moving around usb cables, deleting and reinstalling USB drivers seemed to fix the issue. I do SteamVR plugin development (PSMoveService) and I figured that it must be do to my plugin at first, but after uninstalling my plugin (and reverting my steamvr.vrsettings to not loading multiple drivers) the issue didn't go away. After the update SteamVR started failing at start-up with error 308. I started getting the error in the latest release of SteamVR (Content build ID 1375867).
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |