InfiniTV PCI & WMC logs

[jaimeknapp]

Last night, in the middle of watching live TV, WMC just stopped and threw up the standard Windows screen to check online, or restart the application. No recordings or extenders were in use. This had occurred just once before at the PC and once on an extender. I chose to just restart, which it did without issue. Here are the log contents of that WMC event:

Log Name: Application
Source: Application Error
Date: 7/22/2013 9:42:30 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: kappa2
Description:
Faulting application name: EHShell.exe, version: 6.1.7600.16385, time stamp: 0x4a5bd053
Faulting module name: igdumd64.dll, version: 9.17.10.3062, time stamp: 0x513a99fd
Exception code: 0xc0000094
Fault offset: 0x000000000015c4b2
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-07-23T02:42:30.000000000Z" />
<EventRecordID>15197</EventRecordID>
<Channel>Application</Channel>
<Computer>kappa2</Computer>
<Security />
</System>
<EventData>
<Data>EHShell.exe</Data>
<Data>6.1.7600.16385</Data>
<Data>4a5bd053</Data>
<Data>igdumd64.dll</Data>
<Data>9.17.10.3062</Data>
<Data>513a99fd</Data>
<Data>c0000094</Data>
<Data>000000000015c4b2</Data>
</EventData>
</Event>

Note that I am running Firmware Version: (13.5.6.132). My WMC PC runs 24/7. This morning, without WMC or extenders running, I checked the log file. It had several thousand lines of:
Jan 4 17:23:58 ocur[21]: ocur: WARNING: [0] program 0 not found

Interspersed with :
Jan 4 17:24:00 ocur[21]: ocur: WARNING: [1] failed to get pat

I rebooted the PC and power cycled the Tuning Adapter and before launching WMC, checked the log file and found a few warning and error line items:

Jan 1 00:00:02 ocur[21]: libctn91xx: WARNING: slave busy read_addr: 00.54 write_addr: 00.00

Jan 1 00:00:02 ocur[21]: libctn91xx: WARNING: slave busy read_addr: 00.ffff write_addr: 00.ce
Jan 1 00:00:02 ocur[21]: libctn91xx: WARNING: slave busy read_addr: 00.ffff write_addr: 00.ce
Jan 1 00:00:02 ocur[21]: libctn91xx: WARNING: slave busy read_addr: 00.ffff write_addr: 00.ce
Jan 1 00:00:02 ocur[21]: libcetontune: WARNING: Could not find MxL241SF for instance 4 (00.CE)
Jan 1 00:00:02 ocur[21]: libctn91xx: WARNING: slave busy read_addr: 00.ffff write_addr: 00.ca
Jan 1 00:00:02 ocur[21]: libctn91xx: WARNING: slave busy read_addr: 00.ffff write_addr: 00.ca
Jan 1 00:00:02 ocur[21]: libctn91xx: WARNING: slave busy read_addr: 00.ffff write_addr: 00.ca

Jan 1 00:00:03 ocur[21]: ocur: ERROR: failed to init libusb -99

Jan 1 00:00:03 ocur[21]: upnp: WARNING: Removing instance 4 from announcement (pos 4).
Jan 1 00:00:03 ocur[21]: upnp: WARNING: Removing instance 5 from announcement (pos 4).
Jan 1 00:00:04 ocur[21]: upnp: WARNING: Removing instance 8 from announcement (pos 6).

Jan 1 00:00:12 ocur[21]: cyrano: [zccard/oobsi:INFO] Running oobsi filter nit, handle 80000001
Jan 1 00:00:12 ocur[21]: cyrano: [zccard/card:INFO] zapi/ccard/trunk/src/card/zccard_card_cchi.c:1021 Unable to create flow (pending one exists)
Jan 1 00:00:12 ocur[21]: cyrano: [zccard/oobsi:INFO] Running oobsi filter svct, handle 80000002
Jan 1 00:00:12 ocur[21]: cyrano: [zccard/card:INFO] zapi/ccard/trunk/src/card/zccard_card_cchi.c:1021 Unable to create flow (pending one exists)
Jan 1 00:00:12 ocur[21]: cyrano: [zccard/oobsi:INFO] Running oobsi filter stt, handle 80000003
Jan 1 00:00:12 ocur[21]: cyrano: [zccard/card:INFO] zapi/ccard/trunk/src/card/zccard_card_cchi.c:1021 Unable to create flow (pending one exists)
Jan 1 00:00:12 ocur[21]: cyrano: [zccard/oobsi:INFO] Running oobsi filter ntt, handle 80000004
Jan 1 00:00:12 ocur[21]: cyrano: [zccard/card:INFO] zapi/ccard/trunk/src/card/zccard_card_cchi.c:1021 Unable to create flow (pending one exists)
Jan 1 00:00:12 ocur[21]: cyrano: [zccard/oobsi:INFO] Running oobsi filter cea, handle 80000005
Jan 1 00:00:12 ocur[21]: cyrano: [zccard/card:INFO] zapi/ccard/trunk/src/card/zccard_card_cchi.c:1021 Unable to create flow (pending one exists)

Jan 1 00:00:13 ocur[21]: cyrano: WARNING: No callback for dri event 00400000

Jan 1 00:00:13 ocur[21]: ocur: WARNING: Stubbed callback
Jan 1 00:00:13 ocur[21]: cyrano: [zccard/card:ERROR] zapi/ccard/trunk/src/card/zccard_card_cchi.c:858 Found 7 filters for pid 0x1ffc

WMC, the Ceton and extenders are operational, although I continue to have issues with TWC San Antonio over what they are attributing to a lack of "robust" error correction in the Ceton tuner. They were just out, confirming my installation and monitored the incoming line finding stream errors they considered above normal, but I do not know their details. The claim the issue resides on their SDV Servers, effecting all CableCARD devices to some degree other than their own supplied Cisco, Motorola and SA units and they have been and continue to be "working on it." The Tuning Adapter network status log prior this morning's reboot:

CURRENT FDC
Freq: 75.000 MHz
DAVIC: Connected
Status: Locked
Level: 3 dBmV
Seconds: 537800
Corr Bytes: 190
Uncor Blks: 536
Errs Avg/Inst: 0 / 0
Total Bytes: 524178828
S/N: 32 dB
CURRENT QAM
Freq: 639.000 MHz
Tuning Mode: QAM-256
Status: Locked
Level: 3 dBmV
NextPage Previous Refresh Home
---
S/N: 39 dB
Seconds: 35151
Corr Bytes: 28144
Uncor Blks: 4545
Errs Avg/Inst: 1 / 0
EQ Gain: 1.0
CURRENT RDC
Freq: 16.750 MHz
Power: 30 dBmV
Delay: 690 uSec
Retrans: 0

I have no way of knowing whether there is any association between any of these events, but would be interested in knowing anything more that I can about these log entries as possible. Thanks for your time.

[erkotz]

Without a full set of InfiniTV logs, I can't say what the cause of your signal issues are, however the InfiniTV logs and TA logs look normal. The WMC crash is likely due to an add-in or codec pack - I would recommend you start by removing any of those you have installed

[jaimeknapp]

Thanks regarding the logs. You can never really tell whether errors and/or warnings are really significant. Is there a quick way to generate a file, or files containing "a full set of logs" without creating a ticket through the application?

No add-ins have ever been installed, or codec changes made since before the turner was installed in January. The crashes had not occurred prior to installing the ...13_06_03_1088 installation package, but I doubt that is relevant.

[JohnW248]

Go to the Ceton Diagnostic Utility and run the Scan (with or without a channel number) and save the resulting file to your HD. It is a zip file and you can easily look inside it to find all the things they collect which is far more extensive than the logs you have looked at.

There is a possibility that there are SDV errors from the server and it would not be out of line for "corporate" to report these as working with their own equipment even if it isn't. Most users that see a SDV error or see their box reboot wouldn't think twice about it. Of course the problem could be closer to home and be in your node, Keep an eye on the Retrans number after the system has been up for a few days and see if you have any numbers showing up there.

Ceton could pinpoint your cableCARD errors from their collection of logs and you will always have a copy of what you send them (until you delete them). Some times a MC crash can just be restarted without a machine restart, sometimes it can't if services can't be restarted for some reason. If you had other 3rd party codecs installed prior to installing the tuner, you might consider removing them. Sometimes these things don't happen instantly or only happen under a certain collection of events and drivers operating.