I believe this issue has been addressed with driver updates 340.76 and 346.35. Therefore closing as fixed.