Originally Posted by netllama
If you're looking for good news, I can report today that this issue will be worked around in the next driver release.
Glad to hear it. I hope the next release is worth the wait. I guess this also means that it's been a software problem all along?
Keep us posted. Thanks for your support with this problem.