NPVR Recording Service crashing at least daily

[turndave]

Since around the time I updated my NextPVR software to v4.0.4 (170820), I have experienced program crashes each day. I haven't noticed any pattern to it beyond that. Usually I find the NPVR Recording Service is no longer running, though on rare occasion Services indicates it is still running, but I none-the-less have to restart it to restore proper functionality.

Let me back up a bit to describe my installation. I have NextPVR installed on a Win7 pro desktop which is primarily used for this purpose. I have an HDHomeRun tuner (two tuner model) configured on NextPVR. In another room, where my TV resides, i have a Raspberry Pi with OSMC installed and the NextPVR PVR Client. The remote works fine for selecting recordings for playback, but is lacking in other areas such as being able to delete recordings. So... I'm using a laptop to access NextPVR's web interface for that purpose... I also find it convenient for scheduling recordings.

The symptoms I get that indicate the NPVR Recording Service has shut down include the web interface failing, an inability to play back a recording, or missed records. Strangely (to me anyway), sometimes the recordings are missed altogether, and sometimes they just don't show up in the list, but do after I start the NPVR Recording Service.

There is an error in the computer's Application event log... event ID 1000, source "Application Error". I have attached a text file including a few variations on that error, though most of the time it involves "Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll". It also seems to be NRecord.exe that is reported as the faulting application.

I attached a zipped log file from when I most recently found the NPVR Recording Service not running, as well as another zipped file after i started it. There does NOT seem to be a crash.mdmp file in the temp folder.

Hopefully I have provided enough info to assist in trouble shooting.

Dave

[sub]

There does NOT seem to be a crash.mdmp file in the temp folder.

Do you have a c:\temp directory? You need to create it manually, and it's got to be on the C:\ drive.

[sub]

Your nrecord.log files seem to end with the overnight EPG update.

If you hit the Update EPG button in NextPVR, does it complete without an error?

[turndave]

Yes I have a c:\temp folder. Just nothing in it. there was a crash.mdmp file in it 10 days ago, but as there was a number of crashes since then, I didn't know the circumstances of what created it and figured it wasn't likely relevant. So... I moved it elsewhere to see if another one would take its place when the next crash occured... and none did. In any event, it was an empty 0 byte file.

Pressing the Update EPG button doesn't trigger any errors on the screen nor cause the NPVR Recording Service to crash. Nor do I see anything appear in the Windows Event log.

Dave

[sub]

Stop the NPVR Recording Service, then manually run it in a command prompt with 'nrecord.exe RUN', that way we should see any error messages on the screen when it crashes.

[turndave]

See the attached text file captured shortly after the last crash. Hopefully there was enough in the Command windows's buffer to get what you need.

Dave

[sub]

Hmm, it didn't seem to end with any error. There was no popup Windows message on the screen tell you it crashed?

Was there a Windows Event Viewer message?

[turndave]

No, there wasn't any pop-up Windows message. The NRecord.exe program just terminated. I happened to be watching a recording at the time and it suddenly froze, which is why I knew there was a problem.

Windows Event viewer message:
Faulting application name: NRecord.exe, version: 1.0.0.0, time stamp: 0x59991470
Faulting module name: ntdll.dll, version: 10.0.15063.608, time stamp: 0x802f667e
Exception code: 0xc0000005
Fault offset: 0x0005da74
Faulting process id: 0x22b0
Faulting application start time: 0x01d36b2d6791cc12
Faulting application path: C:\Program Files (x86)\NPVR\NRecord.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 12d3bd23-aa92-4d86-9391-2524d30a7ea8
Faulting package full name:
Faulting package-relative application ID:

[sub]

Still no c:\temp\crash.mdmp when manually started nrecord? At the moment I've got nothing to go on, lots don't show any sign of anything happening at the time, and ntdll.dll as the faulting module is just a Windows DLL.

[turndave]

No, there still isn't a c:\temp\crash.mdmp.