Yesterday my 5000 series ReplayTV suddenly showed a blue screen and the "no video signal" message even though the cords were plugged in correctly and the Directv box it's connected to was on as always. I rebooted the Replaytv unit, and got a brief message about a problem with the fan, then the blue screen and "no video signal" message" again. No problem going through all of the normal reboot screens until it tries to detect the video signal.
After reading lots of posts on this forum, I unplugged everything from the unit and unplugged the power, let it sit for about an hour, opened it up and used compressed air to blow out all of the dust from the inside of the unit and the fan. The fan had no problem spinning.
I closed it back up and let it sit for another 12 hours. I plugged it back in but ONLY plugged in the RCA OUT cables (and NOT the IN video, ethernet cable, IR blaster, etc.). Unit booted up fine, and when I got to the blue screen and the "no video signal" message, I plugged in the RCA IN cables from my Directv box to the Replaytv. I waited a few minutes and the ReplayTV magically found the video signal again.
Not sure what caused it, but it's now working like a champ again. I realize the threads that I was reading are quite old, but I wanted to post this in case it helps someone else having the same problem in the future.
After reading lots of posts on this forum, I unplugged everything from the unit and unplugged the power, let it sit for about an hour, opened it up and used compressed air to blow out all of the dust from the inside of the unit and the fan. The fan had no problem spinning.
I closed it back up and let it sit for another 12 hours. I plugged it back in but ONLY plugged in the RCA OUT cables (and NOT the IN video, ethernet cable, IR blaster, etc.). Unit booted up fine, and when I got to the blue screen and the "no video signal" message, I plugged in the RCA IN cables from my Directv box to the Replaytv. I waited a few minutes and the ReplayTV magically found the video signal again.
Not sure what caused it, but it's now working like a champ again. I realize the threads that I was reading are quite old, but I wanted to post this in case it helps someone else having the same problem in the future.