Appcrash during OTA EPG update

[Croftie]

EPG has loads of gaps in it today so thought I'd run it manually again and again and note down the muxes it goes through to see if it's crashing on a certain one or after a certain number of muxes.

Noted the first ones down and the one it crashed on. Rebooted and started the manual update, this time it completes and doesn't crash. So maybe it only crashes when there are lots of updates or it needs a reboot just before it's run. IDK.

[Croftie]

Don't know it if helps but here are the crash details. clr.dll seems to be related to .NET, could it be a .NET bug causing this?

Problem signature:
Problem Event Name: APPCRASH
Application Name: NextPVR.exe
Application Version: 1.0.0.0
Application Timestamp: 5571cf04
Fault Module Name: clr.dll
Fault Module Version: 4.0.30319.34209
Fault Module Timestamp: 5348961e
Exception Code: c0000005
Exception Offset: 0000e31e
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: f0e6
Additional Information 2: f0e61824a2ec8850d1f7b2e1f59acb48
Additional Information 3: 9f78
Additional Information 4: 9f78bc5db6d1db0253de5c2d5ec762f6

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=1...cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

[sub]

Can you reproduce and post your npvr.log?

[Croftie]

Yep no problem, it will probably be the same as the one I posted in the OP though.

[Croftie]

Here you go, last line of log is different so maybe it tells you something.

Also don't know if it's relevent but I had to install .NET 4.6 for another program and the Fault Module Version of clr.dll has changed in the crash report

Problem signature:
Problem Event Name: APPCRASH
Application Name: NextPVR.exe
Application Version: 1.0.0.0
Application Timestamp: 5571cf04
Fault Module Name: clr.dll
Fault Module Version: 4.6.100.0
Fault Module Timestamp: 55bc08a1
Exception Code: c0000005
Exception Offset: 0000ffe3
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: 6af4
Additional Information 2: 6af4039ba13b172969c4c3e4d1ae56aa
Additional Information 3: 432d
Additional Information 4: 432d2b815430ff47460c1dfe6326f63f

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=1...cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

[Croftie]

Now sometimes the EPG won't even run, after clicking update epg this pops up for a few seconds and then closes.



After a reboot the update will run but then it crashes.

Logs attatched from before the reboot (NPVR1.zip) and also after the reboot, epg run and crash (NPVR2.zip).

[sub]

Croftie, there is a new release coming out this weekend. If you still have the issue with this release, I'll try to help you work through it. ie, patches with additional logging etc.

At the moment, it looks like the drivers for the device are getting into a broken state, and refuse to start. I take it there are no updated drivers available for the device?

2015-08-28 17:19:02.408 [DEBUG][4] Failed to start device: 0x8007001f

[Croftie]

Ok, thanks.

It's on the latest drivers, used them on an older version of NPVR aswell without this issue. Maybe they only have a problem on a fresh install of windows, IDK.

I just so happen to have a previous version of my card drivers so if it still happens with the new NPVR release I'll roll back the drivers.

[Croftie]

Hi Sub, long story short I think my card is faulty. Got a new one installed last night and the EPG now updates with no issues. Left the PC on overnight aswell and scheduled some recordings which were all successsful. Before I had to reboot shortly before they were due to start or some would fail.

I suppose it could be bad drivers but I'm pretty sure things started going wonky on the same set of drivers before I tried updating them.

I'm amazed it hasn't given up the ghost and died completely yet, it's been giving me these issues for months. It would of been better had it just died completely, that's easy to diagnose

Anyway problem solved hopefully, thanks for all your help.