Sagetv service crashes

[rxnelson]

After many years of running great I am getting what seem to be random errors. It seems to typically occur when tuning a channel. I've removed all the physical cards and went to a HDHR and am still getting the same issue. Any ideas?

Faulting application name: SageTVService.exe, version: 6.0.13.1, time stamp: 0x4df93b47
Faulting module name: TSSplitter.ax, version: 3.0.0.85, time stamp: 0x4df93aab
Exception code: 0xc0000409
Fault offset: 0x0000d8de
Faulting process id: 0xbbc
Faulting application start time: 0x01d1309965590242
Faulting application path: C:\Program Files (x86)\SageTV\SageTV\SageTVService.exe
Faulting module path: C:\Program Files (x86)\SageTV\Common\TSSplitter.ax
Report Id: 2f23db9e-9e10-11e5-a2fd-d8cb8aa23f94

The last lines of the log do not seem to show any smoking guns to me.
Tue 12/8 20:00:05.348 [Seeker@1733b79] Enforcing keep at most limits for the files...
Tue 12/8 20:00:05.351 [Seeker@1733b79] Seeker clearing unwanted and partial files...
Tue 12/8 20:00:05.603 [Seeker@1733b79] needFreeSize = 2.025 GB currFreeSize=2544.58643968 GB
Tue 12/8 20:00:05.603 [Seeker@1733b79] needFreeSize = 2.025 GB currFreeSize=2547.180755968 GB
Tue 12/8 20:00:05.603 [Seeker@1733b79] Seeker waiting for 59 mins.

I've even pulled out a spare machine and used completely different hardware and am getting the same issue.

[maceie]

How odd.
I've got a very smiliar error from 10pm yesterday.
Faulting application name: SageTVService.exe, version: 6.0.13.1, time stamp: 0x4e0360eb
Faulting module name: TSSplitter.ax, version: 3.0.0.85, time stamp: 0x4df93aab
Exception code: 0xc0000005
Fault offset: 0x000067f0
Faulting process id: 0x630
Faulting application start time: 0x01d1312d28159f10
Faulting application path: C:\Program Files\SageTV\SageTV\SageTVService.exe
Faulting module path: C:\Program Files\SageTV\Common\TSSplitter.ax
Report Id: 9f6264f6-9d97-11e5-81dc-fb65d3ef2153

Also running a HDHR.
I'll do some digging into logs when I get a bit of time.
It's a new(ish) build and i've not activated Windows yet. Doubt thats the cause, but who knows.
It also seems to have crashed the Sagetvservice and not restarted it.

[rxnelson]

Yes, it definitely crashes the service and does not recover. Mine did it with 2250s and 1600s as well. It was kind of all of the sudden. I am starting to wonder if they have done something to the signal? Is that even possible? I have not noticed one of these crashes coincide with the HDPVR tuning a channel.

It is also seemingly random. Even during channel setup I've gotten crashes. Go back to the same exact channel and it tunes without crashing.

Do you have cable? What provider?

[maceie]

I run OTA with the HDHR.
I've just found another crash. same error, this time 10:37am instead of 10:08am (not PM as I thought before).

Just a thought, are you running a licenced Original V7 or V7 with replaced .exe files?
My licence was on the old server, so I replaced the .exe as described in other places for the licence free ones.
I think I'll swap them back and apply the licence and see if it makes a difference.

[rxnelson]

I've only had version 7.

[maceie]

The original exe made no difference (as I suspected), but I've got a lead.
The error and crash does tie into a tuner event as you found.
Specifically for me, a tuner conflict event.

My old setup had 4 tuners, and this is just the 2 in the HDHR but I have record padding set to 3min each end.
I wonder if thats causing it?
No tuners available AFTER a record event should have started?

Annoyingly I deleted the old message files so can't back track the other crashes.

I shall test.

[rxnelson]

For me it definitely wasn't just conflicts. It would occur even during setup while mapping channels on the first tuner. Good luck. I've been up 2 days and 20 hours......tick tock.

[KryptoNyte]

Are you able to tune one of these channels outside of Sage, with the HDHR software for example?

[maceie]

Since I resolved all the conflicts (manually) and removed the padding, no crashes (yet).
I do wonder if it's just Sage looking for the tuner and it's busy/not ready in time and it gives up?

8pm 13th Dec. - Had a crash
But it's always the same channel that it's trying to record when it crashes.
I *think* it might be a signal issue as a manual tune does show the signal can be 50% or lower.

Can you see what signal strength you're getting during tuning rxnelson?

[rxnelson]

They are all fine. High 90s or 100%

[rxnelson]

Up for about 7 days and then another crash of the same type? Again I don't see any smoking guns in the log file other than it crashed as soon as it tried to tune a favorite. The show comes on daily so it worked 6 times before this?

Wed 12/16 17:00:00.903 [Seeker@1763ff7] Saving properties file to C:\Program Files (x86)\SageTV\SageTV\Sage.properties
Wed 12/16 17:00:00.911 [Seeker@1763ff7] Checking video directories for new files
Wed 12/16 17:00:00.912 [Seeker@1763ff7] Diskspace checking is running
Wed 12/16 17:00:00.912 [Seeker@1763ff7] Verifying existence of all TV media files in database fixDurs=false avoidArchive=true
Wed 12/16 17:00:01.382 [Seeker@1763ff7] Enforcing keep at most limits for the files...
Wed 12/16 17:00:01.386 [Seeker@1763ff7] Seeker clearing unwanted and partial files...

Edit: Interesting? Sage reports that there was a conflict with the tuners at the time of the crash. However there was no conflicts to resolve prior to this. Bogus error message?
Edit 2: It crashed at 5pm but I have about 17 minutes of the show that it crashed on starting at 5:43pm-6pm. I'm not even sure how that is possible.

[KryptoNyte]

Have you folks run full scans on your hard drives, and possibly even your system memory?

[rxnelson]

I've definitely done the memory. I could run scans on the disks but I think they are good or I'd have more frequent failures? I'll check it out though. Appreciate you chiming in. It crashed again today oddly enough on the same 5pm show.

[KryptoNyte]

Not necessarily. If there is a block on the hard drive that is corrupt, but not tagged as corrupt (as it would be if a scan were done), then it's possible that intermittent problems can occur when the operating system attempts to access that block.

I would try a scan, if for no other reason, to rule it out of the equation. Scan all disks involved, including your operating system disk, even if your OS disk doesn't hold recordings.

[rxnelson]

Quick update....did a scan on one of the recording drives and it is clean according to the WD tool. I'll scan the others today/tonight. In the mean time I changed that one show from recording over QAM to the HD-PVR and it the service hasn't crashed in 10 days.....no whammies, no whammies, no whammies.

[rxnelson]

Had another crash a few days ago. I assume this one is from the HDPVR as it is saying it encoded as H264? I wasn't watching but it was reported that they were watching live TV and a movie preview came on. They thought they recognized the actor and rewound it and the it crashed. Kind of strange it played it once?
Any ideas? This kills the service and the extenders.

I captured this from the Native log which seems to have a little different logging than the Sage logs.

03/27/2017 21:48:57 *********** PARSER STATUS: STREAM START ***********

03/27/2017 21:48:57 *********** PARSER STATUS: PARSING STREAM ***********

03/27/2017 21:48:57 PMT-MAP Table is updated

03/27/2017 21:48:57 PAT-0:Program (total channel:2, tsid:0 )

03/27/2017 21:48:57 	PMT pid:0x001f program:0000

03/27/2017 21:48:57 	PMT pid:0x0100 program:0001

03/27/2017 21:48:57 	Channel:1 (tsid:0) PMT pid:0x0100 Program:0001 PCR pid:0x1001 .

03/27/2017 21:48:57 		Type:0x1b Pid:0x1011

03/27/2017 21:48:57 		Type:0x81 Pid:0x1100

03/27/2017 21:48:57 		Pid:0x1011 descriptor(10) REG(HDMVÿW?) 

03/27/2017 21:48:57 		Pid:0x1100 descriptor(14) REG(AC-3) ATSC_AC3(6) 

03/27/2017 21:48:57 	 TS:0 type:0x1b pid:0x1011 video      H264

03/27/2017 21:48:57 	 TS:1 type:0x81 pid:0x1100 audio      AC3 

03/27/2017 21:48:57 	 PCR:	pid:0x1001

03/27/2017 21:48:57 	*Select REMUX_FILE channel  (slot:0, media:0) channel:1 tsid:0 sid:1 (1) stream:2

03/27/2017 21:48:57 	 ES:0:1 strmid:0xfd-0x0 esid:0x0000 private   MPEG2    

03/27/2017 21:48:57 	 ES:0:0 strmid:0xe0-0x0 esid:0x0000 video     MPEG2   "open" 

03/27/2017 21:48:57 	 AV:0:0 video    H264		 (pos:3760)

03/27/2017 21:48:57 	 AV:0:1 audio    AC3 		 (pos:0)

03/27/2017 21:48:57 stream clock (GMT):UTC:12/31/1969 19:00:00

03/27/2017 21:48:57 *********** PARSER STATUS: STREAM READY (slot:0) elapsed time:0. ***********

03/27/2017 21:48:57 INPUT|MPEG2-TS;br=2948000;[bf=vid;f=H.264;fps=59.940060;fpsn=60000;fpsd=1001;ar=1.777778;arn=16;ard=9;w=1280;h=720;lace=0;main=yes;tag=1011;pid=4113;index=0;];[bf=aud;f=AC3;sr=48000;ch=6;br=448000;main=yes;tag=1100;pid=4352;index=1;];

03/27/2017 21:48:57 **** Find AVINF(pos:91556) ****

03/27/2017 21:48:57 Parsing is Done!

03/27/2017 21:48:57 ERROR: TS SYNC header is lost!

03/27/2017 21:48:57 ERROR: TS SYNC header is lost!

03/27/2017 21:48:57 ERROR: TS SYNC header is lost!

03/27/2017 21:48:57 ERROR: TS SYNC header is lost!