Hi Allen,
It seems that the issue has been fixed with the latest driver (15.33.8.64.3345) for HD 4000.
However, it still exists while using HD 3000 even with the latest driver (15.28.20.64.3347).
Here is a print screen:
Since the issue has been half-fixed, to make it fixed completely is not so difficult I think.
Thanks!