I realize this post is almost a half decade old but I did come across it while searching for an answer to the very same problem and figure others might, as well.
The real problem is that the driver is broken, Microsoft has been able to duplicate the fault, admits it needs to be fixed, closed the CONNECT item promising to not let it slip through the cracks, and it's still broken almost 5 years later. Here's the link.
--Jeff Moden
Change is inevitable... Change for the better is not.