OVRDisplayRT32.dll caused an Access Violation (0xc0000005)
A brief history... When I first received my DK2, Direct Mode would not work at all - not even in the desk demo scene. Eventually Dean from Oculus tried troubleshooting with me. After a lot of crashes, a lot of tests, and a lot of trying random things, we got Direct Mode to finally turn "blue" for something. We got the desk demo working and maybe another demo or two. I quickly noticed, however, that every Unity application gave a crash error in Direct mode. Extended mode becomes very fickle - wanting the Rift to be set as Primary, etc. My most recent attempt was on July 3rd with "StreetViewVR".
Unity Player [version: Unity 5.0.1f1_5a2e8fe35a68]
OVRDisplayRT32.dll caused an Access Violation (0xc0000005) in module OVRDisplayRT32.dll at 0023:5ad04e7f.
Error occurred at 2015-07-03_024736. C:\Rift\StreetViewVR.exe, run by . 31% memory in use. 0 MB physical memory [0 MB free]. 0 MB paging file [0 MB free]. 0 MB user address space [3844 MB free]. Read from location 00000000 caused an access violation.
The educated guesses I've heard is driver interference (specifically Razer or Logitech) or something to do with DX shims. I've tried uninstalling all Razer and Logitech software and uninstalling and reinstalling all Oculus software. It kinda becomes like searching for a needle in a haystack that may not even exist.
Anyway, I have plenty of error logs for you to have fun with if you'd like. I zipped a few up and attached them. I think I deleted the ones that were earlier than May, sorry!
The frames in your callstacks do not look valid. This is a symptom we have seen in cases where the direct mode driver was being used for non-VR rendering. Does your app do rendering to additional windows or swapchains beyond the main VR view? If you can afford to upgrade to the new Utilities package for Unity 5.1, that may be your best bet since it avoids injecting the direct mode driver shims into your app and only uses them with our new 0.6 compositor.
To clarify, this is an error that occurs after trying to run any downloaded demo built in Unity. It happens regardless of where the demo is coming from. It is not something I have compiled myself in Unity. So it sounds like another application on my system is hijacking the Direct Mode driver? If someone releases a demo with the new Unity build, I will test it and report back!