It happened to me twice. The first time was the OSU/UM football game. A couple of days in advance I went in to the guide, selected the show, and hit the "R" button. I then went to the ToDo list, found the entry, and told it to stop 60 (IIRC) minutes later than scheduled - padding the recording by an hour in case the game went long.
I sat down in front of the TV a couple of hours after the game started. I began watching it in my preferred "slip-30-between-plays" mode. Around 3:05, 5 minutes into the extra padding time, as I was FFing through the halftime show, the box spontaneously rebooted. By the time I was up and running, the game was over, and the box had not recorded the last few minutes of the game because it was rebooting.
A week later, it happened again during a Bears game. Same scenario - padded recording, recording in the added padding time while I watched it and worked to catch up when BAM! ((c) Emeril) it rebooted. Again, I missed the end of the game.
Those are the only two times the box has
ever spontaneously rebooted on me. I read other threads here where people found that padding was causing problems, so I stopped using it, and instead would record the next couple of shows following a game of interest. Not a perfect solution, since it seems like a minute or so of clock time gets lost when changing shows(*), but I never had another mystery reboot.
With 0x10B, I was able to pad today's Bears game and watch the playback, while it was recording in the pad time, with no problems.
(*) It turns out that the "missing time" may be an illusion. Apparently, when you start watching the second show, playback does not start right at the beginning of what is recorded, and you can rewind to see almost everything since the previous show ended.
