Recording Service crashes at 1700 daily

[bicbasher]

Can you please supply it?

It's zero bites, so nothing to actually upload.

[sub]

Check Windows Event Viewer for a crash messages for either NRecord.exe or NDigitalHost.exe. Hopefully this will give more info, including maybe a path to a windows dump file stored in a windows directory.

[bicbasher]

Does any of this make sense?

- System

- Provider

[ Name] Service Control Manager
[ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4}
[ EventSourceName] Service Control Manager

- EventID 7000

[ Qualifiers] 49152

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x8080000000000000

- TimeCreated

[ SystemTime] 2018-02-12T03:04:31.467270200Z

EventRecordID 905730

Correlation

- Execution

[ ProcessID] 328
[ ThreadID] 332

Channel System

Computer Martin-Zoo

Security


- EventData

param1 TVService
param2 %%2

The TVService service failed to start due to the following error:
The system cannot find the file specified.

[bicbasher]

Also found this.

Application: NRecord.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.Remoting.RemotingException

Server stack trace:
at System.Runtime.Remoting.Channels.Ipc.IpcPort.Read(Byte[] data, Int32 offset, Int32 length)
at System.Runtime.Remoting.Channels.Ipc.PipeStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Runtime.Remoting.Channels.SocketHandler.ReadFromSocket(Byte[] buffer, Int32 offset, Int32 count)
at System.Runtime.Remoting.Channels.SocketHandler.Read(Byte[] buffer, Int32 offset, Int32 count)
at System.Runtime.Remoting.Channels.SocketHandler.ReadAndMatchFourBytes(Byte[] buffer)
at System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadAndMatchPreamble()
at System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadVersionAndOperation(UInt16& operation)
at System.Runtime.Remoting.Channels.Ipc.IpcClientHandler.ReadHeaders()
at System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessage)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(System.Runtime.Remoting.Proxies.MessageData ByRef, Int32)
at NUtility.IRecorder.IsActiveHandle(Int32)
at NShared.DigitalRecorder.IsActiveHandle(Int32)
at NShared.RecordingService.WorkerThread()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

[bicbasher]

And this may be part of the issue.

Faulting application name: NDigitalHost.exe, version: 1.0.0.0, time stamp: 0x5a298c2e
Faulting module name: KERNELBASE.dll, version: 6.1.7601.23915, time stamp: 0x59b94abb
Exception code: 0xe0434352
Fault offset: 0x0000c54f
Faulting process id: 0x1118
Faulting application start time: 0x01d3a2adca7b2065
Faulting application path: C:\Program Files (x86)\NPVR\NDigitalHost.exe
Faulting module path: C:\windows\syswow64\KERNELBASE.dll
Report Id: b078bf67-0f1e-11e8-a9ad-c860006bd67e

[sub]

It looks like NDigitalHost.exe dies for some reason yet unknown. NRecord.exe dies soon after when checking the status of NDigitalHost.exe. I have made a change for the next build, so that this problem will not cause NRecord.exe to die when checking the status of the dead NDigitalHost.

We still don't know the reason your NDigitalHost.exe is dying though, and unfortunately that crash message didn't provide a dump file.

[bicbasher]

This came up after rebooting the PC.

Application 'C:\Program Files (x86)\NPVR\NDigitalHost.exe' (pid 3664) cannot be restarted - Application SID does not match Conductor SID..

I've also now updated Windows 7 to see if any of the issues are due to me not updating recently.

[sub]

That error doesn't really mean anything to me, and I don't think I've ever seen it reported. Does it do that each reboot, or was it a one-off?

[bicbasher]

Appears to be a one-off.

Once again, recorded the same channel at 0900 and 1100. The 0900 recording finished at 1102, but the 1100 didn't start.

[Graham]

Once again, recorded the same channel at 0900 and 1100. The 0900 recording finished at 1102, but the 1100 didn't start.

The ndigitalhost-20 log has this ...

2018-02-14 10:59:02.747 [ERROR][93] StartStream Exception: System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.

What tuner are you using? Are the drivers up to date? What happens if you move the tuner to another slot/port?

Thought for the day ... it may be that your tuner does not support the magic that NextPVR uses to record two shows simultaneously on a single tuner when both shows are on the same frequency (including shows on the same channel).