Hello everyone.

The Mixed Reality Forums here are no longer being used or maintained.

There are a few other places we would like to direct you to for support, both from Microsoft and from the community.

The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.

For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.

If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.

And always feel free to hit us up on Twitter @MxdRealityDev.

Error C00011-1 , acer headset on wos 16275

After I updated to windows 10 build 16275, i receive the error code 00011-1, in mixed reality portal when i connect the acer headset.

Answers

  • Hey @TonyLeone - Were you previously able to use your headset on earlier builds?

  • I had exactly the same issue.
    It was working previously with 16273 and older builds.
  • My error code is actually different: C00122-0.

    Emulation mode worked. But not with the real headset.

  • Seeing this error log in event viewer:
    Looks like I need to revert to previous version.


    Log Name: Application
    Source: Application Error
    Date: 8/28/2017 12:32:45 AM
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: kirin
    Description:
    Faulting application name: WUDFHost.exe, version: 10.0.16275.1000, time stamp: 0x44b2abb7
    Faulting module name: HeadTrackerMR.dll, version: 10.0.16268.1000, time stamp: 0x1eff1f9b
    Exception code: 0x00000675
    Fault offset: 0x00000000000d7822
    Faulting process id: 0x28d0
    Faulting application start time: 0x01d31fcfaf7296c1
    Faulting application path: C:\Windows\System32\WUDFHost.exe
    Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\hololenssensors.inf_amd64_cce8252c4ecde762\HeadTrackerMR.dll
    Report Id: c48eab73-d588-49c9-8ded-86a3cf5d5a2f
    Faulting package full name:
    Faulting package-relative application ID:
    Event Xml:



    1000
    2
    100
    0x80000000000000

    361
    Application
    white-road.kirin.local



    WUDFHost.exe
    10.0.16275.1000
    44b2abb7
    HeadTrackerMR.dll
    10.0.16268.1000
    1eff1f9b
    00000675
    00000000000d7822
    28d0
    01d31fcfaf7296c1
    C:\Windows\System32\WUDFHost.exe
    C:\WINDOWS\System32\DriverStore\FileRepository\hololenssensors.inf_amd64_cce8252c4ecde762\HeadTrackerMR.dll
    c48eab73-d588-49c9-8ded-86a3cf5d5a2f





  • I am also getting:

    We're not sure what's up, but this error code should help: C00122-0.

    Have tried uninstall, remove of devices manually, etc.

    Cannot get past the problem.

    All was working on previous Windows build.

    Peter

  • Have you guys all filed Feedback through the hub on this issue? It seems like a new breaking change, and that will help the engineering teams track it down.

    Thanks,
    Jesse

  • Ugh.. I have an acer. I haven't tried since the update. I'm going to be fuming if I can't dev this weekend again being that I already lost so much time before. What are the steps for downgrading a build?

  • @Jesse_McCulloch said:
    Have you guys all filed Feedback through the hub on this issue? It seems like a new breaking change, and that will help the engineering teams track it down.

    Thanks,
    Jesse

    Yes I did.

  • @mlfarrell said:
    Ugh.. I have an acer. I haven't tried since the update. I'm going to be fuming if I can't dev this weekend again being that I already lost so much time before. What are the steps for downgrading a build?

    I reverted to the previous version (which used to work), and guess what.... the same error persisted. I am stuck!

  • Yea.. I couldn't reproduce it when I tried real quick today before work. So its not as simple as it occurring on all acers. I hope you guys find a workaround soon though. You may need to reset all the internal app settings for the MR app.

  • MrB0yMrB0y
    edited August 2017

    Same problem with my Acer MRH. It started with C00011-1 and after uninstalling and updating the MRH drivers and my Nvidia display driver it now says C00013-0. I'm running 1675.r3_release.178022-1423 . It was working flawlessly prior to the update. Should I revert to previous build? Is there a list of error codes for the device?

  • I have this problem on my dell inspiron 15 7000 with build 16275, but on a dell e7540 with the same build i dont get the error. Another little tips, in the previous build i need to add in the registry a key to bypassing the graphics card driver check...in this osbuild and without the registry key i can proceed with the boundary setup. ah, i can do the boundary setup on the inspiron 7000, then the problem is only in the mixed reality portal software combined with this build. Remove the mhr and reinstall it dont resolve the bug.

  • Useful info. Guess I'm not even so much as touching my gfx drivers until the next insider build.

  • all the problem have been resolved with build 16278 rs3...

Sign In or Register to comment.