OTA Reboots - why oh why?!?!?!

[mors]

I've googled information on OTA reboots with the TIVO HD. I've had my TIVO HD for over a year and everything had been going fine til the fall season started. I would record local OTA channels and the box would either lock up completely (still show the program just fine, but I couldn't go to guide or anything) or it would just reboot itself. I finally called directv and they sent a replacement. This one worked fine for about a week. Now it's rebooting whenever it wants. I think I've narrowed the problem to local OTA channels. I don't have a clue as to what the problem is. I'm getting immensely pissed at the thing since I'm missing some shows due to these reboots. I'm positive the temperature is ok, and I'm sure it's not the box itself (I just replaced it). Could it be 6.3a - well the TIVO would lock up before I got that version, so maybe it fixed the lock-up problem, but it just reboots itself instead.

I've found people having problems with OTA audio dropping-I don't have that problem.
I've found people having problems with satellite channels (not OTA)-I don't think that's my problem.
I've also found a few people stating they've had similar problems as to what I'm going through, but no resolution.

I am so sick of TIVO, but I'm stuck with it for another 10 months. Their software sucks and why can't they do simple upgrades like color-code their menu? Come on.

Anyway, does anyone have any advice? or can someone at TIVO tell me what the problem is? Or is it specifically the signal my local towers are sending me or what???

thanks for any word.

[Cheezmo]

I have the problem with one or two local OTA HD channels. WFAA for sure, and I believe KXAS from time to time.

It is VERY sporatic. There are days that I can tune to the channel and see the slow down, degrading performance to a reboot process start immediately, other times it can record that same program (nightly news) for a week without issues.

So, yes it is related to the signal the local broadcaster is sending you, but it is also a new problem caused by the 6.3a update that didn't occur with 3.1.5. It is audio buffer overflow related, but less frequent and more serious than the Fox audio dropout issue.