I've had this happen once so far in my 2-year ownership. A reboot resolved it and it hasn't returned (yet). Feels like it could be a display driver bug.