EPG update crashing the program?

[sitush]

I have been finding holes in the EPG, with the guide showing no program information available. I've tried running a manual EPG update both with and without the NPVR service running but in both cases the update seems to cause NPVR to crash out to the Win 10 desktop at a point that does not appear to be consistent. Some of the holes in the EPG are filled by the update but others that previously held info are then "no information". Could this be another problem with the UK over-the-air EPG data, as with the recent unicode changes? NB: I've been experiencing a lot of issues using Kodi on a client PC, as documented in other threads.

[mvallevand]

It logs like you were doing a recording on a channel during the EPG update

2019-03-29 02:35:00.225 [DEBUG][8] About to start recording (11911 on 25): F:\recordings\The Good Fight\The Good Fight_20190329_02400340.ts...

so the EPG couldn't scan several channels.

Did it actually crash though? Do you have anything in your Windows Event viewer?

Martin

[sitush]

Hm. It was not recording when I did the manual scans this morning.

Loads of warnings in the event log and also errors around that time, eg:

Faulting application name: NextPVR.exe, version: 1.0.0.0, time stamp: 0x5c82e4bf
Faulting module name: ntdll.dll, version: 10.0.17763.292, time stamp: 0xf3450dbf
Exception code: 0xc0000374
Fault offset: 0x000e0e23
Faulting process id: 0x64c
Faulting application start time: 0x01d4e60bdd43009c
Faulting application path: C:\Program Files (x86)\NPVR\NextPVR.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 3135a123-f77d-4a87-a99e-8d76ee1e9292
Faulting package full name:
Faulting package-relative application ID:

[mvallevand]

Sorry my mistake I was thinking the problem with in the failed overnight update. That is going to be one for sub, I do remember posts when other user was having problems when they were getting thousands of EPG updates like you seem to be.

Martin

[sub]

Have you got a c:\temp directory? If so, does it have a c:\temp\crash.mdmp?

If not, create that directory, and let me know if you get a file next time.

[sitush]

There was no c:\temp so I created it. Checked the EPG and at that time it showed, for example, "no show details" for ITV from 0700-1030 31 March and for Channel 4 from roughly 1600 on the same day until 0700 on 1 April. ITV equates to channel 3 in NPVR speak, Channel 4 equates to, erm, 4.

Ran manual EPG update, starting at 1739, with no recordings taking place or being watched. On this occasion, it crashed within 10-15 seconds of beginning the scan (much sooner than on the last two occasions). The c:\temp directory is empty and a file search shows no crash.mdmp elsewhere. Event Viewer shows

Log Name: Application
Source: Application Error
Date: 30/03/2019 17:39:33
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: PVR
Description:
Faulting application name: NextPVR.exe, version: 1.0.0.0, time stamp: 0x5c82e4bf
Faulting module name: ntdll.dll, version: 10.0.17763.292, time stamp: 0xf3450dbf
Exception code: 0xc0000374
Fault offset: 0x000e0e23
Faulting process id: 0x2710
Faulting application start time: 0x01d4e71ed14d38e8
Faulting application path: C:\Program Files (x86)\NPVR\NextPVR.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 211580d6-f480-4dad-a54d-8422897a606e
Faulting package full name:
Faulting package-relative application ID:
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="2019-03-30T17:39:33.585809200Z" />
<EventRecordID>472</EventRecordID>
<Channel>Application</Channel>
<Computer>PVR</Computer>
<Security />
</System>
<EventData>
<Data>NextPVR.exe</Data>
<Data>1.0.0.0</Data>
<Data>5c82e4bf</Data>
<Data>ntdll.dll</Data>
<Data>10.0.17763.292</Data>
<Data>f3450dbf</Data>
<Data>c0000374</Data>
<Data>000e0e23</Data>
<Data>2710</Data>
<Data>01d4e71ed14d38e8</Data>
<Data>C:\Program Files (x86)\NPVR\NextPVR.exe</Data>
<Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data>211580d6-f480-4dad-a54d-8422897a606e</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

[sitush]

Update: a crash.mdmp was created at 0400 on 1 April, coinciding with a multitude of NPVR component failures logged in Event Viewer. The combination of NPVR backend + Kodi on a separate frontend has now been pretty much unusable for some time now due to all of the recent errors that have been reported here - it crashes or freezes or fails to complete a task in numerous ways, and I note that the first logged error on this occasion involved NDigitalHost rather than the NextPVR.exe mentioned above.

I've attached the .mdmp and the first of the logged failures says

Log Name: Application
Source: Application Error
Date: 01/04/2019 04:00:58
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: PVR
Description:
Faulting application name: NDigitalHost.exe, version: 1.0.0.0, time stamp: 0x5c82e4be
Faulting module name: combase.dll, version: 10.0.17763.253, time stamp: 0xa3f81b2d
Exception code: 0xc0000005
Fault offset: 0x000939a0
Faulting process id: 0x1764
Faulting application start time: 0x01d4e6109583d8d9
Faulting application path: C:\Program Files (x86)\NPVR\NDigitalHost.exe
Faulting module path: C:\WINDOWS\System32\combase.dll
Report Id: 152c2a1e-6533-4147-a3fd-59296373e9d7
Faulting package full name:
Faulting package-relative application ID:
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="2019-04-01T03:00:58.099130000Z" />
<EventRecordID>535</EventRecordID>
<Channel>Application</Channel>
<Computer>PVR</Computer>
<Security />
</System>
<EventData>
<Data>NDigitalHost.exe</Data>
<Data>1.0.0.0</Data>
<Data>5c82e4be</Data>
<Data>combase.dll</Data>
<Data>10.0.17763.253</Data>
<Data>a3f81b2d</Data>
<Data>c0000005</Data>
<Data>000939a0</Data>
<Data>1764</Data>
<Data>01d4e6109583d8d9</Data>
<Data>C:\Program Files (x86)\NPVR\NDigitalHost.exe</Data>
<Data>C:\WINDOWS\System32\combase.dll</Data>
<Data>152c2a1e-6533-4147-a3fd-59296373e9d7</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

[sitush]

I've just done an sfc /scannow and that found at least one corruption, so I will see what happens now that has been fixed. The error noted in the CBS log was "Repairing corrupted file \??\C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\\mscormmc.dll from store"

[mvallevand]

I think your problem is very similar to this on https://forums.nextpvr.com/showthread.ph...post532228 and appears to be unrelated to Kodi. Kodi won't be reliable if the server is in bad shape.

Martin

[sitush]

Yeah. This thread is in the NextPVR forum section, not the Kodi one, but certainly my issues posted in the Kodi section may well be down to NPVR not playing fair. I thought I was told in that other section that NPVR could not be the problem but perhaps I misremembered. In any event, NPVR certainly IS a problem and in combination with Kodi it is pretty much unusable at the moment and has been for several weeks. Even if the EPG populates properly for at least the next few hours, Kodi repeatedly crashes or freezes.

I'm trying to work out how to set up NPVR as a client instead of Kodi but not getting very far - says the database on the server cannot be found. The point would be to prove or disprove that the behaviour applies without Kodi being in the equation.

The corruption reported by the dism and subsequent sfc scan has made no obvious difference to performance - the thing is still falling over in pretty much any recorded programme.