This is interesting. My (unmod'd) 5160 has recently started stuttering a little bit (second or so) now and then. I thought I'd see what was up internally, so I turned on some of the monitors. Saw only the CPU ever changes, so left that one running. Normal playback of a recording: about 50%. CA: jump to 75% for a second (as it searches ahead, I assume). On a stutter, also a jump, way up to 85-95.
So, I was watching an old NYPD Blue, and at about 57 minutes, it starts to stutter and then loop about two seconds of audio/video about 30 times, and then freezes (video there, no audio). CPU was about 85+ when the loop was running. Only time it ever looped. CPU meter also froze, if that means anything at that point.
Had to warm-boot to get it back, jumped to just before that part, and it did it again. QS/IR had no effect (thought I could 'power' over it, perhaps, but not so).
Background: broadband, drive about 30% full, no photo partition/screensaver. It does a lot of recording, but is never buffering unless we are actually watching that TV (2-4 hours/day); also does a lot of streaming to another unit, with never a hitch (max 2-4 hours/day also).
Live TV right now seems fine, even as it records it.
One more strange thing that happened tonight: I looked at the guide at about 8:00. The guide was totally empty. There was a message that said something along the lines of "Guide data is currently being updated, check later'. Never seen that before. However, 411 showed that the last connect had been at at 6:48. I checked about ten minutes later, all is fine. Guide there until 9/20.
Then, ran a NC for the heck of it, and got all the way through the end and got the generic "there was an error contacting the server... try later". [Note that this machine is not trying to get 5.1.]
Just ran another NC, got the same thing: blows at 'combining data 80%'.
Does all of this add up to anything concrete? (Now I know how some of the folks with strange issues feel!
)
So, I was watching an old NYPD Blue, and at about 57 minutes, it starts to stutter and then loop about two seconds of audio/video about 30 times, and then freezes (video there, no audio). CPU was about 85+ when the loop was running. Only time it ever looped. CPU meter also froze, if that means anything at that point.
Had to warm-boot to get it back, jumped to just before that part, and it did it again. QS/IR had no effect (thought I could 'power' over it, perhaps, but not so).
Background: broadband, drive about 30% full, no photo partition/screensaver. It does a lot of recording, but is never buffering unless we are actually watching that TV (2-4 hours/day); also does a lot of streaming to another unit, with never a hitch (max 2-4 hours/day also).
Live TV right now seems fine, even as it records it.
One more strange thing that happened tonight: I looked at the guide at about 8:00. The guide was totally empty. There was a message that said something along the lines of "Guide data is currently being updated, check later'. Never seen that before. However, 411 showed that the last connect had been at at 6:48. I checked about ten minutes later, all is fine. Guide there until 9/20.
Then, ran a NC for the heck of it, and got all the way through the end and got the generic "there was an error contacting the server... try later". [Note that this machine is not trying to get 5.1.]
Just ran another NC, got the same thing: blows at 'combining data 80%'.
Does all of this add up to anything concrete? (Now I know how some of the folks with strange issues feel!
)
