Greetings!

Similar. Because I was messing with the drives and player versions, I am not certain of the cause. The symptoms are very similar though. I would have expected an error to appear if it was a drive related issue (bad track, block, error, timeout, etc.). Still, I will investigate further this weekend.

The reboot issue is a known problem. Something is not being cleared or is not initialized when a reboot is done. Mark noticed it as part of the hijack reboot, and noted that some players showed this behavior while others did not. But this is an added data point - it is not just hijack - any reboot will cause the same symptoms.