Increased reboots since firmware upgrade on 8/28/12

[haydongreenbutton]

Anyone experiencing an increased number of blue screen and reboots since installing the new beta firmware and drivers?

[JohnW248]

It would help to know what type of tuner (usb/PCIe) and what the FW and HW versions are on the device. From looking around there seems to be some variation among users so its hard to tell. Personally I haven't experienced that in a long time, and about the only thing was occassionally the USB tuner might stop communicating with the PC but several MS USB Hot Fixes seem to have resolved that issue.

[adam1991]

Anyone experiencing an increased number of blue screen and reboots since installing the new beta firmware and drivers?

[mod edit - NSFW] http://www.alcimedes.com/techflowchart.gif

[SilverRubicon]

Not more reboots, but every so often I get a flash of a blue screen while watching a show or recording. This started after upgrading the firmware. Doesn't happen often enough to be annoying and otherwise things have been rock solid.

[TeddyR]

I have had a major issue with the Cisco VPN client and incompatiblilty with the latest beta Ceton drivers. In my case it was the USB version on Windows 7 x64. (thanks ceton support for going through several memory dumps to trace the issue). Disabling the service or unchecking the "Deterministic Network Enchancer" component from the Ceton card had no effect; only a complete uninstall of the Cisco VPN client worked. (Though I am still chasing an issue with the TA losing connectivity, but thats a different item)....

[richard1980]

Anyone experiencing an increased number of blue screen and reboots since installing the new beta firmware and drivers?

[mod edit - NSFW] http://www.alcimedes.com/techflowchart.gif

Stop trying to take all the fun out of things!

[STC]

Anyone experiencing an increased number of blue screen and reboots since installing the new beta firmware and drivers?

[mod edit - NSFW] http://www.alcimedes.com/techflowchart.gif

Stop trying to take all the fun out of things!

Ironically, all those paths are ones I've been down many times

[newfiend]

Right there with you STC...lol

[haydongreenbutton]

It would help to know what type of tuner (usb/PCIe) and what the FW and HW versions are on the device. From looking around there seems to be some variation among users so its hard to tell. Personally I haven't experienced that in a long time, and about the only thing was occassionally the USB tuner might stop communicating with the PC but several MS USB Hot Fixes seem to have resolved that issue.

It's the Ceton public beta drivers and firmware dated 8/28/12. The versions are:
Driver package version: 12.08.28.0019
InfiniTV firmware version: 1.1.8.2
InfiniTV hardware version: 6289

It's the PCIe model. Thought there would be more discussion of this software here. Guess too many people haven't installed it or aren't experiencing more issues.

[STC]

^^ Your symptoms probably deserve creating a ticket with Ceton.-
http://www.cetoncorp.com/support/index. ... ets/Submit

They have excellent support.

[lithium630]

Anyone experiencing an increased number of blue screen and reboots since installing the new beta firmware and drivers?

[mod edit - NSFW] http://www.alcimedes.com/techflowchart.gif

I might have to steal that.

[STC]

^^ Too late I already whooped it

[JohnW248]

It would help to know what type of tuner (usb/PCIe) and what the FW and HW versions are on the device. From looking around there seems to be some variation among users so its hard to tell. Personally I haven't experienced that in a long time, and about the only thing was occassionally the USB tuner might stop communicating with the PC but several MS USB Hot Fixes seem to have resolved that issue.

It's the Ceton public beta drivers and firmware dated 8/28/12. The versions are:
Driver package version: 12.08.28.0019
InfiniTV firmware version: 1.1.8.2
InfiniTV hardware version: 6289

It's the PCIe model. Thought there would be more discussion of this software here. Guess too many people haven't installed it or aren't experiencing more issues.

I've had 1.1.8.2 on a PCIe4 since 5/17/12 without issue. I don't have that HW version since I've been unable to install the beta driver package due to an issue that Ceton is working on.

But that FW has been very stable for me, if you're having trouble you should certainly start a ticket and a scan to see what's going on. There might be some cnflicting issue or some hot fix that might be recommended. I've install a total of 3 USB Hot Fixes (although I think the last on is the only necessary one new) and a PCI bus hot fix. Ceton can look at your diagnostics and advise accordingly. There can be other issues such as VPN networks (somehow those get installed on the Ceton adapter where they shouldn't be as well as on your NIC. Those can just be removed by unchecking them (go to network and sharing, change adapter settings, click on the Ceton adapter and properties and look for any VPN that installed by MS, mine got there by installing XP on a Win7 Pro 64 upgrade.)

If you haven't done the hot fixes, Ceton will give you the KB numbers and these are the type you have to request and get an email back from MS with a link to download, they aren't available with a direct URL reference.

[evilOlive]

I was instructed to update to this beta firmware during a troubleshooting process on my own ticket with Ceton. Though they have been unable to identify the problem, the error log has always shown a problem with communicating over UPnP and Ceton has claimed it is something else installed on my machine, telling me the best they can do is stab at shadows and guess at what the problem might be. I didn't think that was very useful "support" so today I've used TCPView to sniff the connections and found literally THOUSANDS of unconnected TCP endpoints on my machine. No joke. Over 3000 at one point. They all are created by "System Process" and are all headed for 192.168.200.1 on a wide range of ports. It appears there are several hundred new requests per minute. 192.168.200.1 is your friendly Ceton hardware address.

The unconnected endpoints look like this and there's literally thousands:

[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 32769 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 32853 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 32855 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 32860 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 32862 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 33008 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 33019 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 33113 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 59673 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 59716 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 59727 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 59838 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 59875 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 59880 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 60860 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 60957 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 60959 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 33055 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 33090 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 33097 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 59813 TIME_WAIT
[System Process] 0 TCP evilolive-pc.local icslap 192.168.200.1 59822 TIME_WAIT