3Dconnexion Forum

As a Microsoft employee I have to tell you this is a bug in your driver. Typically this class of bug is easily caught by enabling "driver verifier" which will cause an assertion and error during driver development. You must pay attention to whatever driver code that does not run at PASSIVE...

I have the same problem here. Exactly the same release as you do.