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.

DPC Watchdog Violation Error Hololens Emulator

I'm trying to run the Hololens emulator, but after trying to load for quite some time it blue screens and gives me the error "dpc watchdog violation" and restarts the computer. The only thing I can find that may be causing the problem is that I'm running on DirectX 10.1 and WDDM 1.1 instead of DirectX 11.0 and WDDM 1.2. I've tried finding a way to update those, but have been unsuccessful. That may not even be the problem though. Any suggestions?



  • From what I found on other forums, a 'dpc watchdog violation' seems to occur when running with outdated/un-supported drivers. Open 'Device Manager' and check that your drivers are up-to-date. I would suggest starting with your Display and Network adapters.

    HoloLens development requires a graphics card capable of running DirectX 11 and WDDM 1.2, so without a hardware update, you will likely encounter issues. You can check on the manufacturer's website of your current graphics card to see if it is capable of running DirectX 11. If so, they should have a driver update available on their site that you can install.

  • DPC Watchdog Violation errors were extremely regular when Windows 10 was first discharged. To such an extent that Microsoft needed to discharge a refresh to handle it. Initially it was caused by a SSD driver that was observed to be incongruent with Windows 10. It is really a rehash of an issue that happened in Windows 8 when that was discharged as well. On the off chance that you discover you have to settle the Windows 10 blunder DPC Watchdog Violation, this instructional exercise is for you.

Sign In or Register to comment.