It seems that the current driver has been updated to 180.60. I presume that this version is newer than 180.53, so can it be assumed that this bug is either invalid or fix released?
It seems that the current driver has been updated to 180.60. I presume that this version is newer than 180.53, so can it be assumed that this bug is either invalid or fix released?