Hmm. And you're sure it's running the 1.03 player software? Your description sounds like a known bug in version 2.0b3 of the player software.

If it's 1.03, I'd say contact support. That shouldn't happen.