6.2 Causing Random Reboots?

[daviddavidw]

My HDVR2 with 6.2 and an upgraded 160MB HD records a show with major pixelation problems and sound drop outs about once a week. Luckily, it has not been rebooting, though. Everything else works fine.

Will doing a MFS partition check (pause 58) be of any help?

Is it a hardware/software problem, or a HD problem?

Thanks for any help. This has been a very informative thread.

-David

[BTUx9]

Does the pixellation, etc. recur in the same place, if you rewind and watch the same section over? Does it occur on the same channel, or same time of day? To determine if it's a bad spot on the HD, you may want to KEEP a recording that is exhibiting this behavior, that way other recordings won't be recorded over the same (possibly bad) sectors.

There are many possible causes for this, but since the tivo fixes itself, it's unlikely to be the same 6.2 issue (but not impossible)

[daviddavidw]

Yes, it's alway bad in the same place if I rewind. Does this mean it's bad sectors on the HD? Is there anyway to fix this without buying software? Is the only solution to keep the bad recordings?

Will the MFS partition check, or reseating the access card and restarting help?

Thanks for any info.

-David

[BTUx9]

It could be a bad sector, interference, marginal signal strength, or there may have been corruption when the stream was actually being written. If it's sectors on the HD, then keeping the recording may help (it may not, if the HD is in the process of dying. You may want to check what the weather was like during the problem recordings, to see if there's any pattern.

These problems are hard to diagnose 100%... running diagnostics on the drive could tell you whether it's disk errors or not, but make sure you use a DOS tool... XP will scribble on the drive, making it unbootable (can be fixed, usually, but is a PITA)

[Motterman]

Dan,

If it is a bug in the software, wouldn't it affect all Tivos? Why have only some 6.2 users been hit with this bug?

There is part of me that thinks that the upgrade from 3.1 to 6.2 didn't really upgrade very nicely. Some databases didn't upgrade well. Which is why those people who did a clear and delete everything post 6.2 aren't having issues for the most part.

I guess we will see I suppose.

Well, for me, the Clean and Deletes never completed. They just would hang on the "Please wait. This may take an hour" screen....

As for your theory, the replacement they sent me for my Hughes, a Samsung, started pausing/rebooting a day after it upgraded to 6.2. The Samsung was only hooked up for 2 days when 6.2 was installed and problems started soon after like I said...

[Mike_TV]

Well C&D did nothing for me. Here are my steps...

1) C&D
2) Redo guided set up and complete call via PPP over serial
3) Leave box alone for about three days to get complete guide data

Note: No reboots yet after about 3-4 days after C&D. Unit seems very stable without any Season Passes.

4) Start rebuilding Season Passes (about 40 of them)

After it starts recording a few of the Season Passes, unit reboots on its own. If I try to play anything it recorded via a Season Pass, I get an error saying it can't play the recording.

I'm guessing I can do a C&D again and just use it as a plain "receiver" without creating any Season Passes so the thing doesn't reboot on me. Kinda of waste for a Tivo, I know but not knowing why/when this thing is going to reboot is frustrating.

[BTUx9]

That sounds like another issue... after putting in the SPs, that is. Is the error you receive when trying to play a SP error 51? it sounds like a scrambling key issue.

[Mike_TV]

That sounds like another issue... after putting in the SPs, that is. Is the error you receive when trying to play a SP error 51? it sounds like a scrambling key issue.

I don't get a specific error number but get a message that says something like the program didn't record because of a signal problem. This isn't the exact text of the error, I'll have to take a picture of it and post it for the specific error. I know it's not a signal issue as I've seen this problem in another location in my house (I have three DirecTivos) and moved this one to another location with the same problem.

It does appear to be SP related with the 6.2 version as manual recordings appear to work without a problem. In fact, I may do a C&D again and set up a bunch of manual recordings as a test.

[BTUx9]

posting /var/log/tverr may help in the diagnosis

[Nightfall]

Welp, not a few days after the clear and delete everything, I am getting reboots once every day or two. Very fustrating. I have a spare Tivo I am going to swap out and see if that fixes the problem. The other Tivo has an upgraded drive, but only a 160gb one as opposed to the dual 160gb one that I have in the living room right now.

I suppose that it COULD be a hard drive problem causing it to reboot. However, I haven't seen any pixelation, stuttering programs, or other things that would show it has a bad drive.

*Sigh*

Looks like I am calling Directv tomorrow to get my box swapped.

[Nightfall]

I can attest to the fact that it is NOT a hard drive problem, since the SAME drive that caused freeze-ups in the HDVR2 is running fine in a DSR-704 - with no diagnotics or disk repair run at all...all I did was copy the Philips image onto the drive and install it.

This started as soon as 6.2 was spooled, so I don't think bad guide data is the issue, at least not directly.

We know that 6.2 rebuilds several of the TiVos databases. It may be that some pre-RID units (perhaps those that ran a particular software release, or got a guide download) have a particular database entry or value that causes the rebuild procedure a problem, which results in a bad system table or index value.

Dan,
When you say pre-RID units, what are those? Like any of the HDVR2 boxes or any Tivo that was made over 2-3 years ago? The R10 may not have this problem?

[Dan Collins]

I am utterly convinced that the random rebooting problems that are specific to 6.2 are due to driver glitches when the box becomes too busy. I've corresponded with some people that can't access TiVoWeb while a recording in progress without causing a reboot.

This is why a C&DE helps for a while - it wipes the thumb ratings clean and stops suggestions. Turning off Suggestions may help some of these boxes, by simplying reducing the number of things the TiVo needs to do.

Why this occurs on some, but not all, DirecTiVos is mystery to me.

[Dan Collins]

Dan,
When you say pre-RID units, what are those? Like any of the HDVR2 boxes or any Tivo that was made over 2-3 years ago? The R10 may not have this problem?
The non-RID Series 2s were, IIRC, the Hughes HDVR-2, the Philips DSR-7000 and the RCA-DVR40.

[BTUx9]

I think "too busy" may specifically apply to MFS access. Giving the box busywork without messing with MFS seems to have no ill effects.
Sounds like it could be the locking mechanism that prevents more than 1 thread modifying a piece of information at a time.
My question would be: is there a hardware component to this, or are all boxes susceptible and it's just a matter of time/use?

I agree with the idea that suggestions being on could make reboots more likely, and size of drive may be a contributing factor, too.

How many people with rebooting issues DON'T have suggestions turned on?

[Nightfall]

On my rebooting Tivo, suggestions are turned off. I did the clear and delete everything. I have about 14 season passes set up and only 4-5 programs recorded!

On the Tivo that isn't rebooting, I pretty much made a clone. The one that isn't rebooting I set up with all the season passes of the rebooting Tivo and turned off suggestions. The only difference are the drives. The rebooting Tivo has 2 160gb hds. The non rebooting one has just a single 160gb drive.

I will keep this thread posted. I have a feeling the dual 160gb drive will reboot far sooner than the single drive one will. I am going to keep a watch out for it. I should know in a day or two.

[the new guy]

I have suggestions turned off on both of my units, and always have. I am going to avoid a C&DE on my DTiVo's, since everything is set up just the way I like it. I laugh in the face of the DTV CSR support scripts.

Surprisingly, I am reboot-free for 7 days on the Hughes, and 10 days on the RCA. Both units are getting busier with the upcoming fall season, though, so how much longer this streak will last is anyone's guess.

Tim

[Nightfall]

How did you get reboot free for 7 days? What did you do to get that far? Did you update something or turn something off? Did the reboots just magically stop? More info please. :)

After 1 day, both units haven't rebooted yet. :)

[the new guy]

Just lucky, I guess... :p

Tim

[Nightfall]

How did you get reboot free for 7 days? What did you do to get that far? Did you update something or turn something off? Did the reboots just magically stop? More info please. :)

After 1 day, both units haven't rebooted yet. :)

It took about 1 week before the unit rebooted. The other unit has yet to reboot. Season passes are set up the same on both units. No suggestions on both units. The only difference is the one that doesn't reboot only has 1 160GB hard drive. The rebooting Tivo has 2.

I have decided to download the 3.1 image, restore to a single drive, and the reinstall the Tivo from scratch this weekend. I think it may possibly be the larger hard drive causing the reboot.

Dan, is there any word on if Directv is going to be releasing a patch or something?

[the new guy]

As I mentioned in your other thread, I am now at 19 and 16 days reboot-free.

Still getting lots ofAug 27 21:56:56 (none) kernel: !!!!WARNING: Needed 2 tries to set video STC to 0x1e42e5fd
Aug 27 21:56:56 (none) kernel: Before = 0x1e42bb18, After = 0x1e42bb46 and occasionally one of Sep 1 18:20:46 (none) kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Sep 1 18:20:46 (none) kernel: hda: drive_cmd: error=0x04 { DriveStatusError } in the kernel log, but no reboots (maybe these are normal from time to time). The tverr log is not showing any strayed threads. I am still considering myself lucky, and will post if my streak is broken by a reboot on either machine.

Tim

I did see the term recorder canary in the tverr log, but it said it was a warning only, and was a week ago. Interesting term, at any rate.

[BTUx9]

Usually, the 2nd set of errors you're showing occurs when TWP tries to read the S.M.A.R.T. values when you use the "info" option. It's benign.

re: canary, yeah... I thought that was cute, too.

[the new guy]

Good to know the Drive Status Errors are not a problem... :cool:

I will keep an eye on the logs to see if the recorder canary is sent into the coal mine. :D

Tim

[BTUx9]

On a freeze, the canary filled my tverr with droppings, so it's definitely a good idea to keep your eye out for the little guy.

[Nightfall]

Welp, clear and delete everything didn't fix my problems. The HDVR2 with dual 160GB hard drive is rebooting once a week on average. Same goes for the HDVR2 with a single 160GB hard drive.

Now, it is decision time....

I can wait until the problem resolves itself with an update or something along those lines from Directv. I won't hold my breath....

I can call Directv and get both my Tivo's replaced.

What would you do?

[Wags]

Getting reboots here, also. Thought I was losing my unit. Maybe I'll exercise my extended warranty and get a new unit.

[kayson712]

I am utterly convinced that the random rebooting problems that are specific to 6.2 are due to driver glitches when the box becomes too busy. I've corresponded with some people that can't access TiVoWeb while a recording in progress without causing a reboot.

This is why a C&DE helps for a while - it wipes the thumb ratings clean and stops suggestions. Turning off Suggestions may help some of these boxes, by simplying reducing the number of things the TiVo needs to do.

Why this occurs on some, but not all, DirecTiVos is mystery to me.

Maybe it is just luck, but I have had no reboots since I did the C&D on 8/3 and I tend to agree with Dan's busy theory for a couple of reasons.

FWIW I talked to a CSR from retention before I did the C&D and he said even though D* didn't know how to fix the problem they acknowledge that it is a known issue and suspect that it occurs when the software gets overloaded with too many things to do. He suggested that after I do the C&D that I cut down my number of SP and ARWL.

Before the C&D I had over 100 items in my SP manager. After the C&D I put back about 30 and over the last few weeks with the fall season starting I am creeping back up to about 50 items. I like to record lots of movies and catch premiere shows, so many of my wishlists looked like this:
2005 & Movies
Season Premiere (category only)
200* & Moves & Premiere
199* & Movies
Home Improve/Home repair (category only)
with these all set to record 5 or 10 shows & set to "Space as needed".

After the C&D I kept most of these types of wishlists along with my SP network shows, but changed most of them to record 5 or fewer shows and set almost all of them to "Keep until I Delete"

I know most people will tell you not to use “Keep Until I delete”, but for me this seems to be working. My machine has gone from scheduling pages of shows per day in the “To Do list” to about 10 shows per day. This changed the record light from being on constantly to the machine actually sitting quietly for extended periods of time.:) And the good thing is that I still get all of the programs I am looking for. If the machine records a movie or other show I don’t want I just delete it and the machine starts recording another show within a short time. This works great with channels like HBO, HGTV, etc. that constantly repeat their shows. Also, I have kept my suggestions turned on so there are typically 30 to 40 shows recorded there. I like the suggestions because it gets me old shows like “Becker” & “This Old House” that I like to watch once in a while, but don’t necessarily want to make a SP for.

_________________________________________
SD-DVR40 upgraded with added 120GB (155 hours)

[kayson712]

One caveat of doing the C&DE is that you will loose all of your channel logos. I assumed these would come back over time, but they don't. Thanks to Earl, I now know these are stored as bitmaps on your drive and don't get re-downloaded until the next software update comes along, which maybe never for 6.2.

[aristoBrat]

FWIW I talked to a CSR from retention before I did the C&D and he said even though D* didn't know how to fix the problem they acknowledge that it is a known issue and suspect that it occurs when the software gets overloaded with too many things to do.
The only 6.2 reboot I've ever had (knock on wood) was the other night when I was using TivoTool to stream one of the life buffers while my roommate was reorganizing Season Passes. I think that'd probably fall into the "busy TiVo" category.

[kayson712]

The only 6.2 reboot I've ever had (knock on wood) was the other night when I was using TivoTool to stream one of the life buffers while my roommate was reorganizing Season Passes. I think that'd probably fall into the "busy TiVo" category.

What I failed to mention in my longer post above is that prior to doing the C&DE I was getting 4 to 5 reboots or more a day over a two week period. Sometimes as often as every 1/2 hour which made the machine unusable. I also tried to transfer some shows that I didn't want to loose to DVD before the C&DE, but after making a half a dozen more coasters with the machine constantly rebooting in the middle of the save to VCR, I finally gave up. Since I have the protection plan D* would have replaced this unit for me, but couldn't guarantee if I was going to get a standard 35 hour or larger capacity machine. They certainly weren't going to give me an equal trade to an upgraded unit of 155 hours, so that is why I took my chances with the C&D. I'm surprised they would even cover this unit since it was an upgraded unit purchased from Weeknees.

I know this is OT, but I’m not even sure why I keep the protection plan - its is beginning to seem like a waste of $8/month considering the HDVR2 is selling for around $50 and under on eBay & D* is basically giving this type unit out for free with the rebate. I took protection plan out in Oct. 2004 mainly on the advise of the two excellent D* installers who spent over 5 hours in my house last October installing the Samsung, putting up the phase III dish, wiring a new 4x8 multiswitch, and moving the two HDVR2 to other rooms. D* only charged me something like $30 above the cost of the Samsung which I believe was about $200 after D* discounts. The installers said the protection plan covered everything including dish realignment. We get some pretty nasty windstorms in the western PA, but I never had two realign my dish since I installed the first one myself back in 96.

---------------------------------
1 SD-DVR40 upgraded with added 120GB
2 HDVR2 standard
1 Samsung T160
1 RCA 403
D* customer since 1996

[Nightfall]

The big question is, are they going to fix the problem with a patch or something? I think I am going to call Directv to see what they can do for me. Hopefully, they will send me something different than the HDVR2.

*sigh*

[Dan Collins]

I'm still of the opinion that those cases where a C&DE helps are cases where the problem was excessive activity. When you do a C&DE you wipe all the season passes, clear the thumb ratings and stop any suggestions from recording. This vastly reduces the work a TiVo has to do.

As an experiment, I set up a cron job to run uptime every 15 minutes on my 4 DirecTivos and log the results. All 4 units reported activity levels (I'm referring to the 1 minute value) well below 1 (usually around 0.5) when not recording, and just slightly above 1 when recording on both tuners. While banging around in TWP, I could push them up over 2. If I re-sorted season passes, they would go up over 4 for as long as the sort took. When I tried to stop and reload TWP they would get up to at least 6 before a spontaneous reboot. So, somewhere above 6 is the "too busy" point at which the software glitches and dies. It would be interesting to have someone with a hacked unit that is rebooting try to monitor their activity level and report what it was around the time of the reboot.

Of course, the question then becomes what is making these units so busy...it could very well be disk problems, although any number of other causes are possible. Obviously, changes where made in 6.2 to improve performance, and these go beyond database changes. The code itself is running faster, so I have to assume that this is related to the higher incidence of fatal errors, and therefore, reboots.

[Nightfall]

Dan,

Are a vast majority of people having problems with the HDVR2 tivos OR is it with all older tivos like the RCA and Philips as well?

[Dan Collins]

I don't really have enough data points to say...my problem was with a HDVR2, but people have reported some problems with other models as well (such as the DSR-6000 and the DVR-39). If my theory is right, I'll bet it is not manufacturer or model specific.

[Nightfall]

I am on the phone with Directv now and I have a feeling they aren't going to be able to help me.

There is part of me that is willing to say screw it and get an R10. However, the problem I have with that is paying $100 for a Tivo that works when my HDVR2s are both rebooting, even after a clear and delete everything.

Dan, I wanted to say thanks for your input in this. I really appreciate it.

[BTUx9]

Just another data point, I think that it's got more to do with amount of MFS access, rather than general busywork by the tivo.

Older tivos had a bug in FP handling, so I wrote a program to test it... the newer (2.4.20) kernel no longer has the problem, and while it keeps the box very busy, it doesn't cause reboots.

My guess would be a bug in the mutex (or whatever they use) to regulate concurrent access to MFS.

[BTUx9]

And yet another data point... the reboots Dan is seeing from reloading TWP are most likely from running out of memory in the TCL pool.

I'm not sure what s/w versions this applies to, but I've done some testing, and trying to use more memory than is available under tivosh ALWAYS causes a reboot on my 6.2 machines.

These machines would consistently reboot on a TWP reload, but when I increased the memory pool, that no longer happened... I believe many of the other TWP reboots may also have this as a root cause.

[Dan Collins]

I'll throw one data point out here as well...one of my systems (the Hughes) apparently rebooted sometime yesterday afternoon (no one was home at the time). The logs show absolutely nothing - no errors, no suspicious warnings. The last line posted to any of the logs was at least 20 minutes before the reboot occurred. This unit is on a UPS, so I know it wasn't a power glitch. Odd....

[mathesius]

I had a two-year old Hughes HDVR2 that went bad due to the software bug. It started rebooting. The DirecTV rep had me try the Clear & Delete Everything and that got "stuck" so the unit had to be replaced. They sent me a refurb Philips with the 80 GB drive (70 hr capacity).

I haven't plugged it in yet though. I wanted TV back faster than the 5 days it took to get the refurb Philips so went to Best Buy and bought an R10.

The R10 rebooted two days after activating it. It rebooted again last night in the middle of a show. It's running 6.1 software.

Frankly I don't know what to do. We love TiVo and had no complaints with DirecTV.

It seems I have a few options:

1) Return the R10 to Best Buy (I've only had it for 10 days) & get my money back. Switch to Dish Network or Charter cable. Do something with the Philips, sell on eBay I guess?

2) Return the R10 and activate the Philips in its place. Hope the Philips doesn't have the reboot problem.

3) Try and find a different software image for the R10 and spend a few hours figuring out how to mount the drive in my PC to load the new software. Then worry that the problem will recurr when DirecTV sends new software down.

I wish I knew why some people don't have the problem and other people do.

[the new guy]

As I have mentioned before, I wonder if the problem will eventually work itself out for most people. The instances of spontaneous reboots seems to have slowed drastically, or else not many are reporting them anymore. My RCA hasn't seen a reboot in 44 days now, and I keep TWP runing on it all the time (my Hughes did reboot, but only because I cut power to the room it is in so I could install a ceiling fan).

Has anyone else not seen a reboot, or am I the only one? I haven't really seen anything either way on this lately...

To answer your questions, I would probably return the R10 and keep the Phillips, especially if you will be looking to <cough, cough> enhance its functionality in the future. You will not be able to put any different version on the R10; 6.1 is the only one that will work on it. As for ditching the DTiVo entirely and switching providers, I haven't used any other DVR myself, but I have heard very few positive things about Dish's DVR's, and mixed reviews at best on cable's offerings. DTV is said to have Dish and cable beat on customer service, as well.

Tim

[BTUx9]

If you're going to hack the phillips or hughes anyway, you COULD put 4.x software on it, which doesn't have these issues. And the advantages to a hacked tivo are manifold. :D

[mathesius]

Sounds like a plan. I returned my rebooting R10 to Best Buy, got my $ back; installed my refurb Philips. We'll see how that goes and if/when I want to hack it.

Thanks!

[VideoVic]

I have a Hughes HDVR2 that started with the Reboot issue BEFORE it was upgraded to 6.2. My other Tivo has received the upgrade and with all the new season shows I really want the Folders. When i call Support they told me to reformat the drive. I replaced the drive with a larger one and all is working well (little noisy but I can live with it). It has been months now and I was pushing for the upgrade before I read this thread.

Is there a way I can force the upgrade and do I want to?

[chrishicks]

I was just in the middle of watching a program I had already recorded and my tivo(see sig) just went to "welcome...powering up". it happened at exactly 9:00. I swear I'm going to have major anxiety problems if these things keep doing this for fear of them dying.

[scottwood2]

My SD-DVR40 just started rebooting a few days ago. twice in an hour. then it was OK for about 3 days and tonight it started doing it again.

2 of the 3 times I was watching a show that was recorded and the screen just went blank and rebooted. 1 time the show paused a few times and then rebooted. I was thinking maybe a HD going but I am not sure now.

Is the reboot problem still an issue with many machines out there?

[Aquatic]

My HDVR2 has been good to go for the month or 5 weeks as well. I was rebooting often--at least once a day... I turned off suggestions, cleared Thumbs data, cleaned up my SP lists, and cleaned up my Now Playing list as well. once I did that, coincidence or no, Things have been working well! NO boots, working like a champ.

The other HDVR2 has been upgraded and was rebooting the same.. I don't think my wife cleaned up anything, or did anything special, rather just the opposite most likely. She hasn't rebooted in quite some time either.

[conspiracy theory] Think we got a "sneak" load of 6.2 that fixed the problem but didn't change the version number we see? [/conspiracy theory] :) :)

[the new guy]

[conspiracy theory] Think we got a "sneak" load of 6.2 that fixed the problem but didn't change the version number we see? [/conspiracy theory] :) :)

Certain that is not the case, as both of my machines are hacked to not take upgrades, and both stopped spontaneously rebooting on their own. I think the new software just takes some time to settle in once it is installed, but once it does, it is pretty solid.

Tim

[scottwood2]

I think the new software just takes some time to settle in once it is installed, but once it does, it is pretty solid.

Tim


Odd thing is that ours has worked great for months with no reboots. I think we upgraded to 6.2 back in June or July? All of a sudden it is rebooting on its own. Today it rebooted twice so far. This is after clearing out a lot of programs we had saved. We do have a second HD with about 130 hr cap.

Maybe it is time to clear everything out and try again. Too bad this is happening, the 6.2 upgrade almost made the Tivo a prefect recorder for us. The slow screen updates was really getting to us. Much much better with 6.2. Now if we can get around this issue.

Thanks for the replys

[the new guy]

If 6.2 was running without reboots before, maybe you have a bad sector or two on one of the drives. Try running MFS cleanup, and if that fails to correct the problem, pull the drive and scan for errors.

Instructions for MFS cleanup:
1. Reboot unit.
2. Watch for light on front panel to flash, then press Pause on remote. Yellow light should be on at front panel.
3. Press 5,8 on remote. You should see the 'Installing new software" screen.
4. Wait for unit to reboot again. Done.

Tim

[bengalfreak]

Does MFS cleanup erase your stored programs?

[scottwood2]

Thanks, will try that tonight.

I am assuming that it does not erase the drive?

[the new guy]

No, it does not erase anything.

Tim

[scottwood2]

Tryed to run MFS cleanup and it went OK. Too bad the Tivo rebooted again about 1/2 a hour after finishing MFS cleanup.

Not sure if we should pull the drives or try a complete restore of everything and start over?

Maybe I should buy a back up Tivo just in case.

Thx

Scott

[scottwood2]

Bit the bullet last night and completely started over.

I really don't think this will help in the long run but it was my last thing to try. Wondering if I should get another unit as a backup? If I do should I get another Tivo or the R-15? With Mpeg 4 coming, I am not sure if this is the thing to do?

Thx
Scott

[the new guy]

The only other thing I would suggest is to run manufacturer's diagnostics on the drive to check for bad sectors. If that doesn't help, I am fresh out of ideas, as I haven't had to go that far with my units. :)

At the worst, you will probably only need a new drive, not an entire new DTiVo.

Tim

[scottwood2]

Just thought I would give an update as to my machine.

I was pleasantly surprized that the hard restart worked. So far anyways (knock on wood). We have a lot of programing recorded now and everything is good :) :) :)

Thanks to everyone for the help.

Now I had to read the post on the HDTivo. Thinking about getting one (I need to talk to santa :p )

[scottwood2]

Guess I posted too soon. The original problem of random reboots is back. It must have rebooted at least 6 times yesterday. Thinking it is a HD now. Need to pull it and check it out.

[Nightfall]

I had to do warranty replacements on both of my HDVR2 units. I now have Phillips 708s and the reboot problem is gone.

[edadave]

Reminder - cover up any infrared extended emitters as an experiment. With the 6.2 upgrade, spurious IR noise will cause units to reboot. I saw this with two different units, getting reboots several times a day. Moved the emitter ten feet away and no reboots in two months.

[scottwood2]

The IR issue is interesting. Will try that. The HD's are OK. PUt a new HD in anyway. Still rebooting.

Weird that everything was OK for months though. Now it is acting up. I am thinking maybe a power supply?

Did notice this morning that the video had a quick pause, then it rebooted within 5 minutes. I guess it could be memory also.

Thx for the replys

[patwoods]

Ok, here to add one more tidbit to the mix:

I've been reading these posts trying to associate my problems with these symptoms. I have done the thumbs clear and the C&D, and my reboots have generally slowed. However, I have found one interesting thing. My machine reboots DAILY at about 9AM. How do I know this? Easy, I have two toddlers who watch Disney Channel while eating breakfast (I know, great... but you should see them if the tube is off :( )

To add insult to injury, I have just upgraded my drive to a brand new Samsung 160gb, not once, but twice mind you, because the same issue happened with my original Maxtor 120. I got the same 'drive is corrupted' spiel from folks swearing it was a bad drive. Well, I plugged my tivo in (unplugged for over a year from the landline) to let it upgrade the original 40gb to 6.2 first, then put the 160gb 6.2 upgraded drives (clean instantcake images) into it, and voila, reboots and freezes galore. This was working fine under the previous 3.0.c software, so I know it is the 6.2 as this thread attests.

However, I find it interesting about the 9am reboot. Definitely at 9am each morning. My wife has of course decided this is my fault since the 6.2 download and the larger drive upgrade happened around the same time.

Does anyone else see a reoccuring time that their machine reboots under .6.2 (as well as some oddball reboots), but the 9am daily one is a constant it seems. I have nothing else installed except for telnet at this point, even TWP is commented out for the time being.

[Jumi]

Put off the 6.2 upgrade until last week when the random slo-mo problem caused me to do a C&DE and upgrade from 3.1.1e. Was in heaven for a few days (fast unit!) but last night it rebooted about 11:50pm while recording on both tuners. Hughes SD-DVR80. Oh well.....

[niccitv]

I have 2 dvr's from direct tv. The new Samsung unit is fine, it's the old
HNS Model SD-DVR40 that over the weekend started freaking out. I have tv shows saved that I need to record to vcr or dvd( my little girl is on them). Is there any way I can transfer programming if I have to get a new DVR unit?

[fsck_101]

Just to add that I think my random reboots were caused by IR noise as well. Had a laptop in the room with my SD-DVR80. When the laptop (with IR port) was positioned just so, the DTivo would reboot every 10-45 minutes. Turned off the laptop, no reboots...

[john-duncan-yoyo]

Just to add that I think my random reboots were caused by IR noise as well. Had a laptop in the room with my SD-DVR80. When the laptop (with IR port) was positioned just so, the DTivo would reboot every 10-45 minutes. Turned off the laptop, no reboots...

Sounds like you need to rig a removable cover over the IR port.

[fsck_101]

Sounds like you need to rig a removable cover over the IR port.

I'll probably just disable the IR port, as I don't actually use it for anything...

[Phantom Gremlin]

I've read thru most of this thread and it seems that mostly older units have been rebooting, once they are upgraded to 6.2 software. Sounds like a software bug to me. Especially with the log messages about assertions failing.

But there is also at least one report of an R10 with this problem.

Does the R10 generally have the random reboot problem, or was that an anomoly? I'm looking to upgrade from a SAT-T60 that's dying.

[the_scotsman]

Well , after a while of almost(?) no reboots, one of my DSR7000 is rebotting several times a day. It's rebooting while recording programs I want to see :(

I've tried (almost) everything to fix the problem but alas nothing has worked.

So, I've decided to purchase newer S2 Dtivos in the hope that the RID versions will be more stable. The four DSR7000s (all 250GB) will be setup as mrv/archive machines - great for movies, series and kids stuff. If it wern't for the MRV and folders i'd just put them all back to 3.x - oh well.

I managed to pick up 2 DVR80's from Value Electronics (shipping next week) and already purchased a DSR708 from Weaknees. I can't beilieve how many TIVOs I will have :

2 x 120GB Sony SAT-T60 - fully functional but retired.
4 x 250GB Philips DSR7000 - all with MRV - 3 rebooting :(
2 x Hughes DVR80 (arriving soon)
1 x Philips DSR708 (stock for now)
1 x 800GB HR10-250
1 x Toshiba RS-TX20 (stock)

Yes... I like my Tivos!

Paul M

[dixoncider]

Same problem as others, started rebooting like 5 times a day. Did the thumbs and cleaned up season passes forced call in. It is much better now has not rebooted in a day. So the outcome of this thread is that there is no real FIX :confused: ...????? Thanks

[gen.greivous]

I've read thru most of this thread and it seems that mostly older units have been rebooting, once they are upgraded to 6.2 software. Sounds like a software bug to me. Especially with the log messages about assertions failing.

But there is also at least one report of an R10 with this problem.

Does the R10 generally have the random reboot problem, or was that an anomoly? I'm looking to upgrade from a SAT-T60 that's dying.
my R10 +160 reboots all the time. More so when watching off the NPL then live T.V.

[tinkererguy]

Sighh, sure would be great news if a true resolution to this matter surfaces soon.

I have been lurking for a while, as I have 3 HDVRs with 3 120GB Samsungs with 6.2 software, owned these for nearly 3 years. Guess what, 2 of 3 have been rebooting these past 2-3 months, sometimes as often as every hour or two.

I have already tested one of the drives with SpinRite (no issues). And the prospect of resetting all settings and loosing all programs not terribly appealing. Yeah, I could restore my original 40GB, but that's even less appealing.

I do happen to have an IR blaster nearby, will cover it to test if related, we'll see.

I am thankful to know I'm not alone, this forum is very helpful in so many ways.

[Windstar]

Covering the IR port on my laptop that is in the same room with the DTivo solved my problems.

Thanks! I would have been replacing hard-drives if it wasn't for this thread!

[gen.greivous]

My R10 is still running on 6.1 somthing. The original software maybe? In any case if 6.1 is not the same as 6.2 then either both programs have bugs or it's not the software. I contract for DTV but have no clue what the problem is. Seems to crash less after hard reset but it's still a problem. Any other failed attempts at a fix would be great.

[BTUx9]

R10s have a different architecture, so it will never get 6.2... 6.1 is basically 6.2 for R10s (same layout and signalling setup AFAIK)

[gen.greivous]

Thank you for info. Does that mean it's not the software causing reboots? If all versions of DTV tivo's are crashing it"s got to be somthing else, you think?

[Windstar]

Yes, it is a software issue. No, you're DTivo is not "crashing", it is "restarting". I have without a doubt discovered the source of this problem. It is due to exceptionally high sensitivity to IR signals in the same vicinity as your DTivo.

I was having the same problem, numerous restarts per week (day). I solved the problem by covering the IR port on my laptop (which was in the same room as the DTivo) with black electricians tape.

If you have ANY component in the same room as your DTivo with the ability to emit IR signals it is surely the cause of your problem (provided your problem is regular and radom re-booting).

I almost replaced my hard-drive in an effort to solve this problem. I am very glad I found this thread first. Unless you are stuck on "Powering Up" or something similar, your hard-drive is not the problem. The random re-booting with software version 6.xxx is definately, undoubtably, no further questions or answers needed, caused by errant IR signals (laptops, remotes, blah, blah, blah).

This is the answer to this problem. There is no need to turn this thread into a mini-novel. Find the source of errant IR signals, kill it, and your problem will disapprear.

If your issue is something like stuck on "Welcome, Powering up", you are reading the wrong thread and you possibly have a bad hard drive. Go somewhere else and do not post here....

[tbeckner]

Yes, it is a software issue. No, you're DTivo is not "crashing", it is "restarting". I have without a doubt discovered the source of this problem. It is due to exceptionally high sensitivity to IR signals in the same vicinity as your DTivo.Although, I would not rule out hard drive problems. I actually believe that more reboots and reboot failures have been caused by hard drive failures than extra IR chatter.

[Windstar]

In my experience, hard-drive failure re-boots are almost always accompanied by hang-ups at "Welcome, Powering Up". If your unit is re-booting on a regular basis and then working fine (with software version 6.xxx) you have an errant IR signal that is screwing with you. If your re-boot hangs up regularly, then you have a different issue, probably a bad hard-drive...

[tbeckner]

In my experience, hard-drive failure re-boots are almost always accompanied by hang-ups at "Welcome, Powering Up". If your unit is re-booting on a regular basis and then working fine (with software version 6.xxx) you have an errant IR signal that is screwing with you. If your re-boot hangs up regularly, then you have a different issue, probably a bad hard-drive...I would say it depends upon your actual experience. My experience of temporary hard drive errors is that they cause reboots but not reboot failures and might go away after the hard drive notes the failures, but then again "YOUR MILEAGE MIGHT VARY". As an example, right after the 6.2 upgrade, I had a few reboots and bad recordings, but after a week or so, they went away and they haven't been back. There were no errant IR problems at that time.

But I have to agree with you, that checking for IR problems is less expensive and less invasive, than replacing a hard drive.

So, I would advise checking for possible IR problems first and then maybe checking the hard drive.

[Windstar]

Your problems may disappear if you are regularly receiving software updates. However, my problems began when I replaced a hard-drive through WeaKnees which came with software 6.xxx. I do not have a land-line and therefore could not obtain further updates.

I simply did not have this problem with software version 3.xxx and only began to experience it with 6.xxx. I was very close to returning the hard-drive to Weaknees as defective when I discovered this thread. Once I covered the IR port on my laptop with black tape, all problems disappeared.

Pretty convincing, don't you think???

I realize that some cannot see the forest for the trees and will run this topic into the ground with bogus and un-founded claims.

[Windstar]

I have provided the solution to this problem. Spew forth as you will and confuse those who need an answer.

[BTUx9]

I have provided the solution to this problem. Spew forth as you will and confuse those who need an answer.
Blind faith is a good thing in church, but on a tech. forum? -- not so much.

Yes, errant IR is triggering problems for some people with the newer software.
No, it isn't the only issue, and I would expect it's more of a symptom of an underlying problem in the IPC messaging (just an educated guess).

Reasons for my position:
1) a C&DE has improved the situation for MANY people (though not necessarily permanently)

2) disconnecting the satellite inputs has temporarily fixed the problem for some (though that isn't a workable permanent solution, it does allow time to work on other things... for instance, salvaging recordings)

3) There are some who have 2 or more boxes in the same room, and only 1 of the boxes exhibits this behavior

These observations give more credence to IR NOT being the only/main culprit

[the_scotsman]

All my DTivos are on one closet and are controlled by wireless remote control adapters (the RF transmitter battery type) except one which uses a IR repeater.

All of these DTivos are hooked up to a very large UPS.

My 2 original DSR7000s both started rebooting after the 6.2 upgrade on the original HDD. prior to that I hand zero issues.

Both my original DSR7000s were given C&D etc etc - did not help.

Both My original DSR7000s were given new 250GB HDDs - did not help

bought 2 refurbished DSR7000s from Weaknees and upgraded to 250GB HDD as soon as the 6.2 upgrade was downloaded - No recordings were done prior to the upgrade. One suffers from the reboot, one seems to be OK (at least I haven't seen a reboot or had a partial recording). The other is used as a archive for kids programs thanks to no view card (I use a viewing card from my Sony T-60 to get rid of the nag).

Installed a new DSR708 (different location for now) ... so far so good... however it's not used/viewed that much yet.

2 New DVR80's on the way - so we'll see how they get on.

I'll try disabling the IR repeater to see if that helps any.

One other option id to transfer a copy of the "working" DSR7000 image to the other DSR7000s to see if that cures the problem. This won't happen quickly as I have a ton of stuff i want to watch before wiping the HDDs. More likely I'll just use the DSR7000s as archive/MRV viewers as mentioned in my earlier post.

[tbeckner]

Your problems may disappear if you are regularly receiving software updates. However, my problems began when I replaced a hard-drive through WeaKnees which came with software 6.xxx. I do not have a land-line and therefore could not obtain further updates.

I simply did not have this problem with software version 3.xxx and only began to experience it with 6.xxx. I was very close to returning the hard-drive to Weaknees as defective when I discovered this thread. Once I covered the IR port on my laptop with black tape, all problems disappeared.

Pretty convincing, don't you think???

I realize that some cannot see the forest for the trees and will run this topic into the ground with bogus and un-founded claims.The only real test would be to uncover the IR port on your laptop to see if it recreates the problem. I do know that you can shutdown the IR port on most laptops through configuration without taping them over. Having been in IT for almost 33 years, the fact that problem disappeared when you covered over the IR port does NOT convince me 100% that covering it over actually solved the problem. I have seen that effect many times, it kind of the last thing I tried fixed the problem, when the problem fixed was fixed by something else. At this point, if you didn't uncover the IR port to see if the problem returned, then you did not prove that the solution corrected the problem, and I would call the IR port covering to be UNFOUNDED solution.

[tivoupgrade]

The only real test would be to uncover the IR port on your laptop to see if it recreates the problem. I do know that you can shutdown the IR port on most laptops through configuration without taping them over. Having been in IT for almost 33 years, the fact that problem disappeared when you covered over the IR port does NOT convince me 100% that covering it over actually solved the problem. I have seen that effect many times, it kind of the last thing I tried fixed the problem, when the problem fixed was fixed by something else. At this point, if you didn't uncover the IR port to see if the problem returned, then you did not prove that the solution corrected the problem, and I would call the IR port covering to be UNFOUNDED solution.

Try running diagnostics on the hard drive.

Not only is it possible that you have more than one problem, it is also possible that the hard drive is defective. Regardless of what actually triggers the random reboot, the underlying problem should be diagnosed before it can be declared 'solved'

As for the original subject of this thread, and I'm sure its been stated several times in its many pages, it is not uncommon for random reboots / drive failures to occur and get reported on these forums after a major software upgrade.

Why? Because every time there is an update to the software you begin using partitions on the drive that were previously not in use (or at least not in use since the previous upgrade occurred). That means, if bad sectors exist on the previously unused partitions, they will now start to emerge.

The incorrect assumption to make would be "the upgrade caused the drive failure" whereas the more correct assumption would be "the upgrade revealed it..." Only testing/diagnosing the problem can actually prove or disprove that....

[tbeckner]

Try running diagnostics on the hard drive...Actually, any problem that my hard drive had were fixed automatically and disappeared completely within two weeks of the original 6.2 upgrade. What I was attempting to point out, was that just because something they might have done at the same time that the problem disappeared, might not actually have been the solution to the orginal problem. In the 33+ years that I have worked in IT, I have seen this same effect many times, and sometimes only through complete and time consuming systematic testing can you actually find the problem. In the case of hard drives that diagnose their own problems and can change their own internal redirection tables, it sometimes becomes just a timing issue.

I wouldn't rule out an IR problem creating an overload situation, but I do believe that they would see other problems with an IR overload problem that would extend beyond a simple reboot problem.

[scottwood2]

I have had this reboot problem as well. I thought it was the HD's (2). Pulled them and tested, they checked out OK. I still replaced the HD. This time I put only one 200G drive in. Still had the reboot problem, upto 6 times a day. I covered the IR port and it has worked well for about 3 weeks now.

I did not try to uncover the IR port but all is well on my end.

BTW I have a IR transmitter under the cover and use my home automation system to send IR to the DTivo.

[tinkererguy]

Sighh, sure would be great news if a true resolution to this matter surfaces soon.

I have been lurking for a while, as I have 3 HDVRs with 3 120GB Samsungs with 6.2 software, owned these for nearly 3 years. Guess what, 2 of 3 have been rebooting these past 2-3 months, sometimes as often as every hour or two.

I have already tested one of the drives with SpinRite (no issues). And the prospect of resetting all settings and loosing all programs not terribly appealing. Yeah, I could restore my original 40GB, but that's even less appealing.

I do happen to have an IR blaster nearby, will cover it to test if related, we'll see.

I am thankful to know I'm not alone, this forum is very helpful in so many ways.

Well, guess what, 2 of my HDVR2s TiVos have been up for >50 hours straight. The 3rd one, well, I don't use it much and don't have it plugged in to the network at the moment.

This is the longest I've had the 2 stay up for the last 2-3 months of reboot woes, despite getting 6.2 this past summer. It was particularly bad when watching shows, it'd reboot when you were using it, and not reboot as often when not using it (meaning, no IR signals sent).

This restored stability is certainly good news to the family. All I did was unplug my IR device, a 2 year old "Remote 'Long Ranger' Xtender" like the one in the right-hand picture at this site
http://www.nghp.net/products.htm
but mine uses N type batteries.

Seems mighty suspicous. First, I'll take the aftermarket emitter extension cable out of the picture, then power the base back up. This time, I'll keep the base itself in line of site with the TiVo's IR receiver windows.

Then, if that fails, I gotta figure out if I'm going to go back to 4 year old Powermids in my upstairs bedrooms:
http://www.radioshack.com/product/index.jsp?productId=2104477&cp
but they had spurious IR emissions as well, with a blinking activity indicator LED when nobody was pressing any remote buttons. And they're annoyingly position sensitive, sigh, the search continues....but it's nice to have TiVo back, without wiping out all shows and starting over, and without trying to run wiring for a far more pricey IR repeater system.

[tbeckner]

I gave up on extra IR Transmitter/Receivers a long time ago. Most of them are just too flaky to use with all equipment, and never where sensitive enough to do the job. I finally put all of my equipment where it could be reached by it's remote and all of the problems disappeared, although I never had a reboot problem cause by extra IR chatter/signals.

[BTUx9]

Just a FYI... some IR extenders are sensitive to flourescent bulbs, ESPECIALLY the long-life replacement bulbs that go in incandescent sockets.

[dixoncider]

Call dtv they sent me a "new" tivo for free with 2 year contract, it was a refurbed samsung sent it back and ordered and R-10 from weaknees.

[gen.greivous]

HOPE YOUR R-10 doesnt crash as much as mine.

[MustHaveTivo]

FWIW, we suddenly started getting plentiful random reboots after many months of normal operation with 6.2. Hard drives checked out good. Cleared thumbs data, after which we have had a week of reboot-free living. Details here (http://www.tivocommunity.com/tivo-vb/showthread.php?t=279032).

[cronimi]

All I did was unplug my IR device, a 2 year old "Remote 'Long Ranger' Xtender" like the one in the right-hand picture at this site but mine uses N type batteries.

Seems mighty suspicous. First, I'll take the aftermarket emitter extension cable out of the picture, then power the base back up. This time, I'll keep the base itself in line of site with the TiVo's IR receiver windows.

Great post! I'd been suffering through random reboots for months. I don't have the "Long Ranger" -- I have the "Around the House" Extender featured on the same webpage. I moved the base of the extender a few feet from the D*Tivo, and not a reboot since (3 weeks and counting).

[tinkererguy]

Great post! I'd been suffering through random reboots for months. I don't have the "Long Ranger" -- I have the "Around the House" Extender featured on the same webpage. I moved the base of the extender a few feet from the D*Tivo, and not a reboot since (3 weeks and counting).

Glad to hear of another success story. I have been using my old Powermids for >1 month now, and TiVos haven't rebooted even once with 6.2.

[scottwood2]

Just wanted to post an update to our issue. We had the DVR-40 work for quite a while then started rebooting (see previous posts for details). We then tried covering up the IR Receiver and the reboots went away for months.

We then purchased a new DVR-80 and have not had any issues running 6.2 with the IR receive uncovered. It has been running about a month now.

[jlmwrite]

My stock RCA DVR40 started randomly rebooting shortly after getting the 6.2 upgrade. I tried clearing the thumbs data, unhooking cables, and everything suggested EXCEPT unhooking my IR extender.

Finally, in a desperate rage after 3 reboots in less than 1/2 hr, I unhooked the IR extender. No reboots for the entire week! The following weekend I plugged the IR extender back in, and presto -- the reboots started within a few hours.

It rebooted all weekend. So... Unplugged the IR extender, and now three weeks later I hadn't seen a single reboot. Just for grins, I plugged the extender in again and got a reboot within a few minutes. The extender is now living in the junk drawer and my DVR is happy.

I'd truly discounted the IR chatter as a cause of the d**n reboots when I first read it here, but now I'm a believer! If only I didn't have to leave the cabinet door open to watch TV...

[JaserLet]

What brand/model is your IR extender? I want to buy one for my DVR40, but I certainly want to avoid that problem!!

[rmassey]

re: IR - this sux for those of use that need an IR repeater solution. I use my HT DTivo to feed my MB and need a way to control the unit remotely.

I had this problem (reboots) last year with my HDVR2 after the 6.2 update. I tried everything and finally upgraded to an HDTivo, which of course doesn't have 6.2 and the problem stopped. If it is IR w/ 6.2 causing the problem, I hope they never upgrade the HDTivos to 6.2.

So is there an IR solution that does not cause reboots? BTW the one I use is the x10 Powermid.

[scottjf8]

I'm suddenly getting reboots now with my S2 (not sure the exact model number, i'm not home)

It's got the latest code with folders and everything... it's worked fine for 6 months now, but suddenly the last few days it's rebooted a few times...

I have no IR repeater... any other suggestoins? We moved it to over our TV and DVD player - any chance it's a heat related issue?

[Jumi]

Me too. I got 6.2 and had one reboot. OK for weeks then another reboot about midnight the other night during recording. Not a power issue - on a UPS. Hughes DVR80.

[kgaren]

About a week ago, random reboots started happening 1-2 times night between 9-11 pm. This is about the time our TV in our bedroom is on, which happens to have an IR remote extender right next to it. I noticed (last night) that when I turn on the TV the red (IR receive) light on the IR extender would come on. I moved the remote to be further away from the TV. That solved the problem with the red (IR recieve) light on the reciever. I also have not had a problem with the TIVO rebooting since then. Not sure why it started only a week ago, but I looked at the software version - with is 6.2 (not sure how long it has been at this version). I have Samsung TIVo w/directv that I bought about 2-3 years ago. I was close to buying hard disk, but this seems to have solved the problem.

[MikeF]

About a week ago, random reboots started happening 1-2 times night between 9-11 pm. This is about the time our TV in our bedroom is on, which happens to have an IR remote extender right next to it. I noticed (last night) that when I turn on the TV the red (IR receive) light on the IR extender would come on. I moved the remote to be further away from the TV. That solved the problem with the red (IR recieve) light on the reciever. I also have not had a problem with the TIVO rebooting since then. Not sure why it started only a week ago, but I looked at the software version - with is 6.2 (not sure how long it has been at this version). I have Samsung TIVo w/directv that I bought about 2-3 years ago. I was close to buying hard disk, but this seems to have solved the problem.
This is exactly what I experienced. I've had my Series 2's now for almost a month and no problems then last week random reboots around 1 to 2 a day. I saw my IR Extender light on (flickering) almost constantly so moved it so its not on anymore. I'm now 30+ hours without a reboot on all 3 of my boxes. Crossing my fingers that this is all that was wrong.

[BTUx9]

when my extender flickered all the time, it turned out to be a flourescent replacement bulb (one of those long-lasting low-power jobbies)... block the receiver and see if it stops flashing, to make sure it's external

[MikeF]

when my extender flickered all the time, it turned out to be a flourescent replacement bulb (one of those long-lasting low-power jobbies)... block the receiver and see if it stops flashing, to make sure it's external
My IR Receiver was right on top of a 20 year old 27" TV. By just moving the receiver about 1 foot to the side of the TV all of the flickering stopped. We do have some florescent blubs in that room, so if I have more problems I may look at replacing those to see if that helps further but so far it seems just the location to the TV was creating extra interference.

[nova tivo]

One example that may be of help to others.

I had a series of random reboots with a central DTivo runnnig 6.2 with two IR inputs to a Xantech amplified distrbution device (the 791-44 model). The LED light was constantly flickering, especially in the daytime since most of the IR receivers out there generate noise in a sunlit room. At times on sunny days, the remote signal could barely penetrate the IR noise.

With only one DTivo I never changed the remote address on the single DTivo so it was device #0 (it would recognize all remote codes). In preparation for my DVR4ME DTivo box, I changed the remote code on my first box to #1. Immediately, the remote became more resistant to IR noise (since a remote code of #0 responds to all signals probably). When I got the second DTivo, I set it up with remote code #2. For whatever reason, remote code #2 was better at reducing reboots and IR interference than #1 so I then changed the codes for the two boxes to #2 and #3.

That solved half of the reboot and noise problem. The other half was to install and inline resistor from Radio Shack on the Xantech connecting block per the instructions on the Xantech website for the 791-44 model. It cost 99 cents for a five pack of resistors (you only need one). The LED light practically stopped flickering at all from random noise, but the Tivo remote signal made it through with no problems.

In short, change the remote code away from #0 if you have one DTivo and use an inline resistor if the manufacturer of your connecting block suggests it. Just make sure you buy the right resistor.

Reboot and IR noise problems solved for me. :) Hope this helps.

[alan]

Well, my Samsung SIR-S4120R with version 6.2-01-2-381 started randomly rebooting again.

Looks like the C&DE only works for a while. I'll have to try the IR extender moving stuff. I have the old Powermid models.

Here's a conspiracy theory for you. Maybe DirecTV just wants everyone to get rid of their TiVos. :D

[dkdevin]

Just to add my solution to this thread. I recently experienced random reboots. My laptop is in my family room and I had just turned on the IR port which happens to be facing the DTivo (Philips DSR7000). I didn't realize that was the problem until reading through this thread, so I decided to try disabling the IR port. I disabled it 5 days ago and it hasn't rebooted since. I also use an IR Extender and have for over a year without having unexpected reboots. It was definitely the laptop.