OpenXR crashes WMR Headset after latest update

fagerbur 26

After the latest update to the WMR openxr runtime, running anything OpenXR (Unity and OpenXR developer tools for WMR) causes the headset to crash and restart. Using an Asus WMR headset on Windows 10 Build 19402.
Testing using Unity 2020.3 and OpenXR Developer Tools for WMR 108.2108.12003.0
OpenXR for Windows Mixed Reality 107.2108.5003.0

Error message from OpenXR Developer Tools for WMR
Unknown OpenXR Runtime
Exception XrResult failure [XR_ERROR_LIMIT_REACHED]
Origin: xrCreateInstance(&createInfo, instance.Put())

Is anyone else running into this issue? I'm not really sure how to troubleshoot it as I don't know where the error logs are, could someone help me find them or maybe there is a way to remove and reinstall the runtime and that will fix it? Using the headset through steamvr's openxr runtime still works fine.

tagged as hololens because I couldn't find an xr one.

Franklin Chen 1 Reputation point Microsoft Employee

2021-08-23T05:27:20.027+00:00

Using an Asus WMR headset on Windows 10 Build 19402. Testing using Unity 2020.3 and OpenXR Developer Tools for WMR 108.2108.12003.0. OpenXR for Windows Mixed Reality 107.2108.5003.0

May I ask if you have tried to launch the OpenXR demo scene in the OpenXR Developer Tools for Windows Mixed Reality app. Please let us know the behavior.

And if you have used the Unity to create a WMR app with OpenXr, could you please give us some details? It will be better to have a simple project to reproduce the Unknown OpenXR Runtime exception on our side. Thanks.
fagerbur 26 Reputation points

2021-08-23T14:18:58.65+00:00

@Franklin Chen Yes, you can reproduce the issue simply by launching the demo scene in the OpenXR Developer Tools for Windows Mixed Reality app. That causes the headset to go black and restart and the error i included in the message is shown under the status tab.
Franklin Chen 1 Reputation point Microsoft Employee

2021-08-26T03:42:13.157+00:00

We followed your steps, using Acer WMR headset and the same Win10 and OpenXR runtime version, everything worked well in the demo scene.

Since the hololens-development tag is for questions about programming HoloLens apps, not WMR immersive app development. Immersive app dev support is not currently available on Q&A. I will set the tag to Not Supported. Please create a free ticket via this link for your issue, so that we can collect some logs from you: https://aka.ms/mrsupport

2 answers

mbucchia-msft 1 Reputation point

2021-09-21T22:47:19.97+00:00
Hello @fagerbur ,

I'm Matt from the OpenXR team at Microsoft.

I apologize for not seeing your thread earlier.

The XR_ERROR_LIMIT_REACHED is likely not the cause of your issue, but rather a consequence. Once you click the "Launch OpenXR demo scene" button from the Home tab, this error may appear in the System Status tab because two pieces of code a competing for the device. So I will not focus on this error, but instead I will try to help you get more details.

Here is something you can do in order to view more detailed logs:

Enable the Device Portal: https://learn.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-desktop#set-up-windows-device-portal-on-a-desktop-device

Close the Mixed Reality Portal and the OpenXR Developer Tools. We want to start fresh before reproducing your issue with the logging enabled.

Open the Device Portal.

Navigate to the ETW logging page.

In the Custom providers section, enter the following GUID: 72E9B8D0-434D-4F50-9DCC-E6DFC9DF2B63. Select 5: Detailed trace.

Click Enable.

Reproduce the issue: start the OpenXR Developer Tools, make sure the Windows Mixed Reality runtime is active (click "Set as active runtime" under Installation status if needed), and click "Launch OpenXR demo scene".

After the crash is reproduced, go back to the Device Portal, and in Enabled providers, click Stop All.

In the Events section at the bottom, you can see the logged events. You may click Save to file to retrieve them as a CSV file.

Please share this file with me so I can try to identify your issue. Thanks!
Please sign in to rate this answer.
fagerbur 26 Reputation points

2021-10-15T17:21:02.797+00:00

@mbucchia-msft

Thanks for the follow up, I tested this out with a Reverb G2 and had the same issue so at least I know for sure it's not an hmd problem. I followed your instructions and I don't see anything user identifiable in the log so here it is attached. I couldn't upload it as a csv so i swapped the format to txt. 140837-etwtrace.txt

mbucchia-msft 1 Reputation point

2021-10-15T17:40:45.737+00:00

Thanks @fagerbur !

I am not seeing any error, the session seems to start up OK, but then it exits immediately before the application can submit its first frame (this XR_SESSION_STATE_STOPPING event).

I am now going to look at the code inside our demo scene app, and try to find out what the app may be reacting too. Hopefully it will tell us where to look next!

I appreciate your patience here, and I will keep you updated!

mbucchia-msft 1 Reputation point

2021-10-18T18:54:01.41+00:00

Hi @fagerbur .

We're a little puzzled here by what we're seeing. The window used by the OpenXR application seems to disappear, causing the OpenXR runtime to tell the application to exit. This is why there is no visible error.

I have a few things that hopefully will give us a better idea why this is happening:

1) I wanted to confirm exactly what you are seeing:

"After the latest update to the WMR openxr runtime": OK so this used to work on this machine before you got the 107/108 update?

"the headset to crash and restart": Can you explain what you mean? Does the display go dark, and then you see the Windows logo again, and things "restart" in the cliff house (back to position when you first open it)? Or do you see the "cloud of triangles", then things immediately return to the cliff house but in the same position/state you were before starting the app?

Are you running the OpenXR developer tools app from your desktop or inside the cliff house?

2) What GPU do you have on this system? Can you try the following command (will need to run as administrator), then try the app again to see if it helped.

reg add HKCU\SOFTWARE\Microsoft\OpenXR /v "PreferD3D12" /d 0 /t REG_DWORD

3) We can gather even more tracing like you did earlier. When enabling providers, please also enable a second provider with GUID:765EDB1E-8414-4B94-AF14-1499F1A583ED.

I am sorry that you are having issues, but fortunately, your cooperation is helping us improve the product for every user. I hope to get to the bottom of this shortly.

Thank you!

fagerbur 26 Reputation points

2021-10-21T18:48:30.053+00:00

For

Yes, it used to work fine on this computer and then there was an update and it no longer worked. It may have coincided with a windows update as well around that time but i didn't make an changes to anything myself.

Yes, exactly that. The headset goes dark and the windows logo reappears as if I had just shut it down completely and restarted.

I've tried running it from both desktop and cliff house and its the same result.

I have an Nvidia Quadro P5200 and it also has integrated Intel UHD 630

I've tried disabling the Intel graphics and it still didn't work, I also tried adding the PreferD3D12 reg key but no change with that either. I can try pulling the latest graphics drivers for the P5200 and see if that helps.

I tried to pull logs with the latest GUID you provided but it quickly became way too big to upload and the data in those logs referenced all the programs on my computer. Anything specific you are looking for in there that I could filter out and provide?

fagerbur 26 Reputation points

2021-10-21T19:27:42.44+00:00

Actually I got it figured out. i must have done something wrong the first time. Here are the log files split out.142592-new-ac.txt 142593-new-aa.txt 142594-new-ab.txt 142595-new-ad.txt 142557-new-ae.txt

mbucchia-msft 1 Reputation point

2021-11-01T22:58:42.517+00:00

Hello @fagerbur ,

Thanks for your answers, they are providing a lot of information. The symptoms seem to point to something crashing in the graphics driver when OpenXR starts up. I would certainly encourage you to make sure your graphics drivers are up-to-date.

Unfortunately, the logs you have captured aren't quite right: I believe because the tracing I asked you to enable is so verbose, the buffer rolled over and I am only seeing a very small span of traces (14 seconds). I am not seeing any application startup in the logs.

The next step is to capture a clean trace so we can really look at it. The better approach is to use the Feedback Hub since the CSV approach did not work.

1) Be sure to update the Nvidia drivers.

2) Be sure to revert the PreferD3D12 regkey change we've done earlier.

At this point, please reboot, so we have a clean slate.

3) Open the Feedback Hub. In the Explain in more details box, be sure to reference this thread by URL and add your username fagerbur-1118, this way I will be able to look it up on my side.

4) In Category, select Mixed Reality, and subcategory MUST be Input.

5) On the Add more details screen, under Attachments, use the Recreate my problem feature. Click Start recording, then go in the Developer Tools and reproduce the crash. When done, hit Stop recording, and continue to submit the feedback.

When done, please let me know so I can go search for the report in our system.

I really appreciate your patience and feedback to improve our product!

fagerbur 26 Reputation points

2021-11-04T16:51:38.107+00:00

hello, @mbucchia-msft

Unfortunately this is an enterprise device so I can't provide feedback through the hub because it is disabled. Is there another way I can provide logs or to make sure that the csv data collected is from the initialization area you're looking at?

I updated the graphics drivers for both discrete and internal graphics but still no change.

mbucchia-msft 1 Reputation point

2021-11-08T23:34:07.07+00:00

Hi @fagerbur ,

We can try to capture the trace using the wpr tool, which will produce a binary ETL file. This will have all possible info, and should not be subject to time limitations (we have a limit but it's pretty high).

Please download 147541-winxrwprp.txt and rename it to WinXR.wprp

Open an administrator shell, then begin recording with the following command:

wpr -start WinXR.wprp -filemode

Reproduce the issue, then stop recording with the command:

wpr -stop WinXR.etl

A file called WinXR.etl is written. You can take a look at the content of this file, I recommend you use https://www.microsoft.com/en-us/p/tabnalysis/9nqlk2m4rp4j. We left off last time at the point we would see a spontaneous XR_SESSION_STATE_STOPPING as the reason why the OpenXR session is being terminated. You may search for this string to make sure the repro of your issue is being captured.

The file might be large. We need to coordinate on how you can share it with me. Can you suggest an acceptable method given your restrictions?

Thanks!

fagerbur 26 Reputation points

2021-11-30T21:34:39.9+00:00

@mbucchia-msft

Hello, took me a bit to get back to this but I ran the wpr commands and here are the rows from the etl file that have a level of Error. The whole file is 52mb so you were right about it being too big. Is there anything else i can filter down on besides Error that i could pass on to you within 3.1mb?

153816-winxretl.txt

Matthieu Bucchianeri 1 Reputation point

2021-12-02T18:27:54.843+00:00

Thanks @fagerbur ,

Given the circumstances, I will give you my personal address to send me the file. Do you have any social media account you can share with me so I send you the address privately?

If you use reddit, can you message me here? https://www.reddit.com/user/mbucchia-msft

Thanks!

fagerbur 26 Reputation points

2021-12-03T18:39:37.287+00:00

@mbucchia-msft

Apologies for the challenges on this, I don't have a reddit account. I don't see any PII in the file so I have placed the file in a repo temporarily - https://github.com/fagerbur/temp_xr_etl - once you have the file i'll delete the repo. Thank you for your persistence on this.

Matthieu Bucchianeri 1 Reputation point

2021-12-03T18:41:59.82+00:00

@fagerbur - Downloaded! You may delete it.

mbucchia-msft 1 Reputation point

2022-01-11T18:27:43.38+00:00

@fagerbur Happy new year, and thanks for your patience waiting throughout the holidays.

The findings from your trace are quite troubling unfortunately.

OpenXR seems to work fine and it is doing everything normally. However it looks like the compositor layer (the thing under OpenXR) is encountering two errors, making the Mixed Reality Portal crash.

This is the exact trace in your log pointing out to the error:

SomethingWentWrong StatusCode:14 SubstatusCode:1

Just before that, I also see a 15-5 error.

Per https://learn.microsoft.com/en-us/windows/mixed-reality/enthusiast-guide/error-codes, 15-5 is:

Mixed Reality Portal has lost synchronization with core Mixed Reality and Windows components it depends on.
This could be caused by a performance issue with your PC. Check "Task Manager" to make sure your CPU, GPU, and HDD are have enough capacity.
Temporarily disconnect all other USB devices from your PC.
Restart your PC.

and 14-1 is:

The Mixed Reality Portal is having trouble initializing the graphics and composition stack. To fix:
Desktop Window Manager (DWM, a key component of the Windows Graphics stack) may be crashing. Check the event log at Event Viewer > Windows Logs > Application to see if this is occurring.
Try a clean uninstall of your graphics driver, and then install the latest graphics driver from the graphics card manufacturer's website.

(cont'd on next message)

mbucchia-msft 1 Reputation point

2022-01-11T18:34:51.397+00:00

So of course these are the super generic suggestions that you've mostly tried already.

One thing I'm curious is to try using the "device simulation", so we can exclude anything induced by the headset driver itself. Can you follow the instructions here to try it out? https://learn.microsoft.com/en-us/windows/mixed-reality/develop/advanced-concepts/using-the-windows-mixed-reality-simulator

I'm curious to hear if the issue occurs even with the simulation driver.

Otherwise, my best suggestion at this time would be to uninstall the Mixed Reality Portal (from Add or remove programs) and attempt to reinstall it from the Windows Store. Maybe one of the internal components got corrupted somehow and it is causing this failure. So I'm hoping that reinstalling the portal (which contains a lot of components) can solve this "composition stack" error.

Finally, this is probably not something you want to hear, but you might want to try re-installing the entire OS. But before even getting there, let's try the 2 things I proposed above. Thanks!
Sign in to comment
Johnathon Brown 1 Reputation point

2021-10-24T08:50:31.41+00:00

I am not a regular poster here, but I wanted to confirm this issue is happening on Windows 11 Build 21H2 as well with OpenXR Developer Tools version 108.2109.21002.0

CPU: AMD 5900HX w/Vega iGPU
GPU: RTX 3060 (mobile)

I recently upgraded from Windows 10 to Windows 11. I have also uninstalled and reinstalled WMR.

OpenXR apps will open with SteamVR set as the OpenXR runtime with WMR for SteamVR installed.

With Windows Mixed Reality set as OpenXR runtime, I'm getting the same "XR_ERROR_LIMITED_REACHED" error in the OpenXR Developer Tools when attempting to run the demo scene.

I encountered this issue as I recently purchased MS Flight Simulator. VR works with SteamVR set as the OpenXR runtime. However, with Windows Mixed Reality as the runtime, it plays the app starting animation and goes to a black screen with no tracking being sent to MSFS. When the black screen is present, the WMR start overlay still works, etc. Turning VR mode off in MSFS returns the HMD to Cliffhouse.

I hope this helps describe the issue and show it isn't affecting only one user.

Edit 1: Added Developer Tool version

Edit 2: Added hardware details.
Please sign in to rate this answer.
mbucchia-msft 1 Reputation point

2021-11-01T23:07:05.083+00:00

Thanks for the report @Johnathon Brown .

Your issue sounds a bit different, since you are not seeing a crash of the Mixed Reality Portal, but instead lack of display (but overlay still worked).

I know you are seeing the same XR_ERROR_LIMITED_REACHED error code, but this is actually misleading in our tools (see my other reply).

I'd like to help you diagnose and resolve the issue, can you please follow the instructions to file a Feedback Hub issue, which will give me access to the trace logs?

Please reboot first to ensure we start from fresh!

1) Open the Feedback Hub. In the Explain in more details box, be sure to reference this thread by URL and add your username JohnathonBrown-3670. this way I will be able to look up the report on my side.

2) In Category, select Mixed Reality, and subcategory MUST be Input.

3) On the Add more details screen, under Attachments, use the Recreate my problem feature. Click Start recording, then start MSFS to reproduce the issue. When done, hit Stop recording, and continue to submit the feedback.

Once submitted, please let me know so I can go search for the report in our system.

I'm sorry you are having this issue when trying to use Flight Simulator, and thank you for your time filing the issue and collecting the traces!
Sign in to comment