As an update on the subject - it seems that the latest Catalyst drivers (10.3) fixed it. To validate this, I re-installed 10.2 and tried again and indeed there is something (which isn't directly mentioned in the release notes of the 10.3 fixes) that causes the same problem to occur, so 10.3 it is.

Thanks again for your time!