This problem seems to be coming with a driver update. I see it when 14.4 release candidate from 4/21/2014 is installed, is this a bug in driver? Because I realized it worked with an older driver (unfortunately I didnt check which driver I had before I upgraded the machine.)
↧