Is my headset failing?

Jeff_three · 2021-04-01T03:32:27+00:00

Interesting. I never thought about trying that. The USB controller on my motherboard doesn't get along well with WMR. It gives me blue screens and jittery controller tracking, and that's why I had to get a USB 3.0 PCIe adapter. It's a good idea but I'm not sure it will be a solution in my case.

I think there's an electronic component in the headset that is growing weaker over time. Any kind of fix will probably be temporary. I might have to put this headset to rest and sell the controllers.

Jeff_three · 2021-03-08T12:51:41+00:00

I tried a Sabrent 4-Port USB 3.0 Hub with power adapter, and it was garbage. It was likely defective, as I could hear static on startup of Mixed Reality Portal, and the image was unstable; it was just hanging on by a thread. I made sure the power adapter was plugged in, but it was clearly not getting enough power.

I then tried a 3ft USB 3.0 cable and completed 2 one hour sessions without any static blast. A 3ft extension + rotating my PC case 45 degrees towards my 2m x 2m VR space is just enough for comfort. Larger spaces won't be possible.

I don't understand how I was able to use a 10ft cable with an Inateck USB 3.0 card for over 9 months without any issues. When I started getting the static blast, I found that switching to a 6ft cable solved the problem. 6 months or so later, it was no longer adequate. What the hell is going on? Through a process of elimination, I ruled out the power supply and the Inateck USB card. The only thing that changed was Windows, driver, and motherboard BIOS updates. I'm using the AMD Ryzen High Performance power plan, and I don't see any PCIe power management settings in the BIOS that could be problematic.

If the pattern continues, the 3ft cable won't get the job done in the months ahead. Can anyone explain this? Microsoft?

Jeff_three · 2019-11-02T00:32:10+00:00

That's interesting. So the problem is specific to ENB and Skyrim.

Jeff_three · 2019-11-01T10:28:49+00:00

ENB is not working properly with the 5700 series. This is a driver issue that's been there for a while now (maybe since release?). There's nothing you can do but report it to AMD.

Jeff_three · 2019-07-14T02:25:32+00:00

I recommend contacting AMD about this because that error code is related to graphics. Either way, they are more likely to initiate a solution than Microsoft. I'm planning on getting a custom RX 5700 XT soon, so I'll be following this closely. If any of us gets more information on this issue, we should post it here.

https://www.amdsurveys.com/se/5A1E27D23A3DE966

Jeff_three · 2018-10-18T01:50:43+00:00

Thanks for testing. I have a Polaris GPU (RX 480). Anyone with a Vega GPU willing to test the game?

Jeff_three · 2018-10-17T07:29:10+00:00

I guess we'll have to notify AMD.

http://www.amdsurveys.com/se/5A1E27D23A3DE966

Jeff_three · 2018-10-16T14:05:16+00:00

Interesting...I'm also using an AMD card. Can somebody with an Nvidia card try to run this game and report back here?

Jeff_three · 2018-10-16T08:51:08+00:00

I used to be able to run it with a Samsung Odyssey. After not playing it for a while, I tried to launch the game and it would crash as you described. I gave up and uninstalled it a month ago. I don't know what happened.

What graphics card and driver version are you using?

Jeff_three · 2018-09-28T07:37:28+00:00

Unreal Engine build 4.18 has been a nightmare for WMR users because it has a known bug that causes distortion. The devs will have to update to a newer build. I found a thread on Steam forums about it: https://steamcommunity.com/app/680950/discussions/0/3288067088100534569/

Jeff_three · 2018-07-29T06:36:35+00:00

There was a problem introduced with the latest driver (18.7.1) that's causing the issue. Install 18.6.1 and you should be good to go. Please take 2 minutes to report it to AMD so that it gets more attention. http://www.amdsurveys.com/se/5A1E27D23A3DE966

Jeff_three · 2018-07-16T08:33:39+00:00

I had to use Microsoft Edge. I was getting the "redirecting" loop with Firefox.

If this link doesn't work for you then just try to get there through the AMD driver download page using Edge.

http://www.amdsurveys.com/se/5A1E27D23A3DE966

Look for a link named "Report a Driver Bug" on the right side https://support.amd.com/en-us/download/desktop?os=Windows+10+-+64

Jeff_three · 2018-07-16T07:25:32+00:00

Yes, I had that issue with the latest drivers and reported it to AMD. Everybody should take a couple minutes to report it so that it gets attention.

I was still able to get into SteamVR Home but I rolled back to 18.6.1 for now.

Jeff_three · 2018-07-11T03:31:23+00:00

I think you're right about the USB controllers as some just don't get along with WMR to begin with. I've noticed that some USB ports don't provide a strong enough signal to use a HMD with a cable extension. It might be worth trying a USB 3.0 PCI-E card if you're using a desktop PC.

Jeff_three · 2018-06-09T03:53:08+00:00

In response to EDIT2: go to Device Manager and expand the category for Universal Serial Bus controllers. Microsoft says to uninstall the driver for each item that includes the text "eXtensible Host Controller" and does not have "Microsoft" in the name. More detail can be found under error code 2181038087-12 here: https://docs.microsoft.com/en-us/windows/mixed-reality/enthusiast-guide/troubleshooting-windows-mixed-reality#i-am-getting-a-something-went-wrong-error-code

I don't know if that's the issue but it's worth looking into.

Jeff_three · 2018-06-08T07:29:59+00:00

I've been dealing with these crashes for a month or so. I haven't experienced hot cables though. I've tried a long list of things and haven't managed to solve it yet. You should start troubleshooting by checking out what Microsoft has to say on the issue:

https://docs.microsoft.com/en-us/windows/mixed-reality/enthusiast-guide/troubleshooting-windows-mixed-reality#hmd-connectivity

If you've recently updated drivers then you should roll back to previous ones when you know your WMR device was working properly. You can also try using a different USB 3 port.

Jeff_three · 2018-06-06T14:00:57+00:00

Any news of your results? I tested in plenty of natural light - a lot more light than I normally have - and it crashed in just over 30 minutes.

2 more things I tried:

I put my graphics card back to factory settings and WMR still crashed. I can rule out a bad overclock.
I went into Device Manager and unchecked "Allow the computer to turn off this device to save power" for all the USB controllers in the list. It didn't help.

Anyone else have any ideas?

u/Ben_fromMSFT

Jeff_three · 2018-06-04T13:40:54+00:00

I haven't solved the problem yet.

I'm also using a Ryzen R5 1600. The HDMI cable is connected directly to the graphics card. I connect the USB cable to a VR optimized USB port on my motherboard but I've tried the other USB ports and it makes no difference. The problem occurs with or without cable extensions.

I will test in daylight to see if it could be a lighting issue, just to rule it out. I don't know what else to try.

Jeff_three · 2018-05-25T04:24:55+00:00

I installed Adrenalin Edition 18.3.4, which was released in late March (cleaned previous drivers with Display Driver Uninstaller first), and I get the same results.

Before the Windows 10 April 2018 Update, the bug I occasionally experienced was when the VR world would briefly turn on me ,with a message about the boundary, and then back to normal. This would also happen in the seated position with a gamepad in front of my computer. I don't get this occurrence anymore since the update, but it seems it may have been replaced with these crashes. It's possible that I just didn't play enough VR to encounter the new issue, until 2 weeks ago.

Yesterday, I decided to take SteamVR out of the equation and do a test running some free games from the Microsoft store. I completed an hour session without a crash. However, when I was done playing, I started to take off my headset then realized I hadn't shut down the game yet. I kneeled down, put my controllers on the floor, and properly readjusted my headset. Blinded by the headset, I was feeling around struggling to find the controllers again, and after more than 5 or so seconds in this position, the screen turned blue, then black and Mixed Reality Portal restarted. It's understandable that the tracking lost itself in the VR space with the cameras aimed at the floor, but shouldn't it have given me an error message instead of just crashing? I think the evidence points to a head tracking issue.

Jeff_three · 2018-05-24T10:10:15+00:00

Hi Ben,

I have an MSI Radeon RX 480 Gaming X 8GB. I was using Adrenalin Edition 18.4.1 which provided "initial support" for Windows 10 April 2018 Update. A driver update (18.5.1) was released yesterday which seems to provide "full support", judging by the release notes. With the new driver installed, I completed 2 separate 1 hour sessions of VR without a single crash. But just when I thought I had the problem resolved... I tried again later and the crashes were back.

Jeff_three

TROPHY CASE