I have seen this before on both my S3's. A channel change usually clears the issue and it has been around as long as I can remember on my boxes. I have no idea what could cause it, but as I said if I change the channel and then go back it's magically cleared.
Jim
Jim