MVP spontaneously reboots

[mniswonger]

For no rhyme or reason, my MVP has suddenly started rebooting itself during MPEG2 playback. I have made no changes to GBPVR or my system recently, other than an update that Acrobat Reader installed. I have a plenty powerful system, a P4 2.8Ghz HT w/ 1GB PC3200 and a Hauppauge PVR-250. The drive I use to store the recordings is a 120GB ATA, which I'm only using a tenth of that. That and my page file is on that drive.

I use comskip on my recordings, and I had GBPVR setup to automatically skip. I tried disabling autoskip with no help. When my MVP reboots I usually have to restart the GBPVR MediaMVP Server and power cycle the MVP. Sometimes it will connect back to the server and go to the main GBPVR screen on it's own.

I had a similar problem a while back with MP3 playback. The MVP would reboot after every 2 or 3 songs. I read on another post that installing the .NET 2.0 Beta Framework helped, so I installed it and it immediately helped. I'm now starting to wonder if that was simply a placebo, even though it was stable for 2 or 3 weeks.

I started looking through the log files, but I couldn't find anything obvious. I'm not exactly sure where to start to troubleshoot this. Any help would be appreciated.

Thanks.

[ram4x4nut]

See my post about MVP network tip.

[darisb]

What hardware version do you have? It says on the bottom. Mine is a D3. The D3 has an overheating issue, that causes it to crash. As far as I know, that's the only version that has a problem. Hauppauge will replace it if you call them.

[ram4x4nut]

Mine is a D1. Glad I didn't get a D3 ... sounds like they are trouble, sooner or later.

[mniswonger]

It seems that the fix was running a repair on the .Net 2.0 Framework.

I will check what hardware revision I have, in case it is overheating.

Thanks.

[funkybro_uk]

Is your connection wired or wireless?

[mniswonger]

It's wired.

It's also a D3, so I'm going to email Hauppauge and get replaced.

[wtg]

It's wired.

It's also a D3, so I'm going to email Hauppauge and get replaced.

If you're in the US, don't waste your time emailing them. If you ever get a response I'll be surprised. I had to send an email 3 times over a period of 6 weeks to get anymore than an automated response, and with the last one the only reason I think I got a reply was I copied the Hauppauge support group in Germany on it, asking them if they could help since the US support group never responded to me.

From what I understand, they're phone support is ok, but don't expect a reply from an email if my response from them is any indication.

[darisb]

If you're in the US, don't waste your time emailing them.

Amen wtg! Call them. They will want you to send it back first. If you live on the left coast (west), that's two weeks without it. The other option is to give them a credit card, they bill you for a replacement, and then credit your card when they get the old unit back. I went that way. The WAF was taking a hit, and I needed to get the numbers back up.

Customer Support isn't their strong suite. The guy I talked to didn't explain anything to me.

[mniswonger]

I did get a reply, although it was very generic. They wouldn't confirm that there is a known problem with the D3, they only said they would test my unit and repair or replace it.

I don't think my problem is related to an overheat issue. I ran the stock MVP software for a year with no problems at all. I started having trouble again tonight with it rebooting while watching an MPEG2 video. I had rebooted my computer a few hours before I was having problems, and that's all I could attribute the reboots to.

I power cycled the MVP, it didn't help. I decided to see if I could run a repair on the .Net 2.0 Framework and get the same results I did last time. Low and behold, it worked after I ran the repair and rebooted my system. I'm wondering if there's a shared library that the .Net Framework uses that maybe Windows is replacing w/ an older copy. Either that or a 3rd party app is to blame.

I'm not a programmer and I don't really know much about .Net. All I know for sure is at this that the .Net 2.0 Beta Framework helped keep my MVP stable compared to before it was installed. And when my MVP starts getting flaky, I can fix it by running a repair on the .Net 2.0 installation.

As for Hauppauge support. They never answered my follow up email to them. I wasn't really pleased with their response, and I've had limited success when emailing them in the past. I think I'll just keep my D3 and hopefully when .Net 2.0 goes final, the problem will be solved for good.