![]() So last night i uninstalled whole oculus software and unplugged Rift from my computer and problems are gone, so it´s definately an oculus software error, hope it gets resolved soon. After couple days of fighting i went check event viewer what the heck is going on, and there is USB ETW Tracing errors all the time and the OVRserviceLauncher seems to be the problem here, not sure what it does but it basically messes up every single USB device on my computer (keyboard, the DIY usb handbrake, mouse.). My computer also would sometimes hang on booting and all that kind of annoying stuff, i suspected my USB drivers are somehow borked, so i even updated my X99 FTW mobo bios, did fresh install of windows 10 etc. ![]() I installed oculus couple days ago to test out some driving simulators with my new DIY Arduino controlled Handbrake, while gaming it was constantly disconnecting and was driving me mad, since i was sure everything was soldered correctly etc. Code: Application: Handbrake.exe Framework Version: v9 Description: The process was terminated due to an unhandled exception. I did uninstall Handbrake and then reinstall it. Ive tried looking around online but havent found anything to help. I have not yet tried uninstalling and reinstalling the Oculus software and was hesitant to do this until I received some direction or feedback from support, or someone who has had some success fixing this.īump, this is very big issue for me aswell. It instantly crashes and the Event Viewer points to some issue with d3d9.dll. The other oculus sensor has the exact same problem. I have an extra Oculus sensor that I wasn't using so I swapped the other sensor in, wondering if I had a bad sensor. I went through my entire windows event log and the first time these error messages appeared in my Windows Event log was. Whatever the Oculus is doing, its messing around with the USB 2.0 on my system and it looks like its causing crashes and all kinds of problems on other people's systems. My USB keyboard may stop working, or my Thrustmaster HOTAS Warthog may have its lights blink on and off. Often, at this point, the Oculus begins to cause problems with OTHER USB 2.0 devices I have plugged into my system. In the Windows notification area a popup message will appear saying that Windows can no longer identify the device and that something has gone "wrong" with the device driver. In the windows event log, that "ETW USB tracing" error and the warnings as those above have described will appear. In Windows Device Manager that sensor will no longer show up. Then, the rear sensor on the USB 2.0 will disappear from the "Settings" pane of Oculus home. However, suddenly there will be a "twitch" in the VR view and things will get a bit choppy. It will start off with all of my sensors showing up as fine in Oculus Home and when I load into a game it starts out fine. ![]() This setup has worked well up until the end of February. 2 in USB 3.0 via a powered hub and 1 (the rear sensor) in USB 2.0. All of my event log entries are identical to those who posted above. I'm getting this error as well, exactly as the folks above have described it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |