hi all
I recently set up an htpc with an infinitv 4 as my tuner. I ordered a ceton echo at the same time and set up 2 xboxes as extenders. My first echo was a brick and I got the replacement this morning. Went thru the setup and for some reason my echo when it attempts pretty much anything other than loading wmc causes the htpc to reboot. This does not happen with my other two extenders (xboxes). I have upgraded to the latest firmware on the echo, uninstalled and reinstalled the echo plugin, etc. I had it working for about an hour and then after playing with my son we came back to watch tv and it froze and then I heard the htpc reboot. Any idea why this is happening? I have a ticket out to ceton. Honestly, this is the second echo and I am getting a little frustrated. Hoping to get this figured out. My RMA took a week to get back to newegg since even shoprunner RMAs are slow, I would hate to have to wait another 9-10 business days for a replacement.
any help would be great. I can add more specs, etc if needed.
oh this is on windows 7
Echo causes HTPC to reboot - solved
Forum rules
Ceton no longer participate in this forum. Official support may still be handled via the Ceton Ticket system.
Ceton no longer participate in this forum. Official support may still be handled via the Ceton Ticket system.
-
johny3
- Posts: 17
- Joined: Thu May 09, 2013 8:41 pm
- Location:
-
HTPC Specs:
Echo causes HTPC to reboot - solved
Last edited by johny3 on Sat May 11, 2013 12:30 pm, edited 1 time in total.
-
foxwood
- Posts: 1761
- Joined: Fri Sep 07, 2012 3:43 pm
- Location:
-
HTPC Specs:
Updating the NIC drivers is frequently suggested for dealing with Echo problems.
Not through Windows Update - check the network chipset in Device Manager, and check the chipset manufacturers website for current drivers.
(I'm not excusing the Echo in this - I don't know what it's doing that nothing else on your network seems to do. But if it's possible for an external device to cause the machine to crash, then the driver needs to be fixed, even if there's a way to stop the Echo from triggering this behaviour in the first place).
Not through Windows Update - check the network chipset in Device Manager, and check the chipset manufacturers website for current drivers.
(I'm not excusing the Echo in this - I don't know what it's doing that nothing else on your network seems to do. But if it's possible for an external device to cause the machine to crash, then the driver needs to be fixed, even if there's a way to stop the Echo from triggering this behaviour in the first place).
-
johny3
- Posts: 17
- Joined: Thu May 09, 2013 8:41 pm
- Location:
-
HTPC Specs:
thanks guys I will do that shortly 
-
mikefromnj
- Posts: 7
- Joined: Sat Jan 05, 2013 11:28 pm
- Location:
-
HTPC Specs:
I had the same problem. NIC driver fixed it.
-
johny3
- Posts: 17
- Joined: Thu May 09, 2013 8:41 pm
- Location:
-
HTPC Specs:
hi guys
It ended up being comodo it seems. I did update the NIC driver and it happened again. Uninstalled comodo and now it works.
It ended up being comodo it seems. I did update the NIC driver and it happened again. Uninstalled comodo and now it works.
-
Sammy2
- Posts: 1708
- Joined: Fri Aug 24, 2012 7:35 pm
- Location:
-
HTPC Specs:
Only use Microsoft Security Essentials and Windows Firewall. They work perfectly well.
-
johny3
- Posts: 17
- Joined: Thu May 09, 2013 8:41 pm
- Location:
-
HTPC Specs:
yup I made that change. thank you for suggesting it!Sammy2 wrote:Only use Microsoft Security Essentials and Windows Firewall. They work perfectly well.