2020-04-12, 11:53 AM
lately I have been getting 'Failed" recordings. last night it happened again.
NPVR Logs shows that the Service stopped running.
NPVR Logs shows that the Service stopped running.
NextPVR Forums
Public
NextPVR Support
Windows
logs show Service Recording stopped
logs show Service Recording stopped
|
2020-04-12, 01:26 PM
It looks like your server went down (likely crash) last night so you had fails for all recordings until your restarted. Check the Event viewer around 8:30 last night.
You also a bad rule for Broke you don't need the * for wild card searches. Martin
Here are the NPVR Event Viewer crashes:
Error 4/12/2020 7:29:00 AM Application Hang 1002 (101) The program NextPVR.exe version 1.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 4c38 Start Time: 01d60f3557886e77 Termination Time: 10 Application Path: C:\Program Files\NextPVR\client\NextPVR.exe Report Id: d7604c03-76c5-40d2-8b79-20e794861505 Faulting package full name: Faulting package-relative application ID: Hang type: Cross-thread Error 4/11/2020 8:26:49 PM Application Error 1000 (100) Faulting application name: Explorer.EXE, version: 10.0.18362.693, time stamp: 0x587c1978 Faulting module name: dcomp.dll, version: 10.0.18362.752, time stamp: 0x726649f8 Exception code: 0xc0000602 Fault offset: 0x000000000009c2fa Faulting process id: 0x1a48 Faulting application start time: 0x01d60f504f26dd7c Faulting application path: C:\WINDOWS\Explorer.EXE Faulting module path: C:\WINDOWS\SYSTEM32\dcomp.dll Report Id: 7a7b5ea0-9399-4eaf-bf48-ab190e9d4d68 Faulting package full name: Faulting package-relative application ID: Error 4/10/2020 9:19:27 AM Application Hang 1002 (101) The program explorer.exe version 10.0.18362.693 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 2cd0 Start Time: 01d60f39748117b3 Termination Time: 0 Application Path: C:\Windows\explorer.exe Report Id: 5ca84719-c91f-4b15-830b-d49f54544b9b Faulting package full name: Faulting package-relative application ID: Hang type: Unknown Error 4/10/2020 8:42:11 AM Application Hang 1002 (101)The program NextPVR.exe version 1.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 461c Start Time: 01d610bd3a69955f Termination Time: 7 Application Path: C:\Program Files\NextPVR\client\NextPVR.exe Report Id: 37b43378-d17c-4a0d-b0ff-3ec633bea941 Faulting package full name: Faulting package-relative application ID: Hang type: Cross-thread This one happened this morning and found NextPvr service not running. I added the Explorer.exe in since it happened near the same time as NPVR crashed. Below from Reliability Monitor: NPVR CRASH: Description A problem caused this program to stop interacting with Windows. Faulting Application Path: C:\Program Files\NextPVR\client\NextPVR.exe Problem signature Problem Event Name: AppHangB1 Application Name: NextPVR.exe Application Version: 1.0.0.0 Application Timestamp: 5e72e65c Hang Signature: b6f9 Hang Type: 262144 OS Version: 10.0.18363.2.0.0.256.48 Locale ID: 1033 Additional Hang Signature 1: b6f90ddb74be284df792b6c039f1819a Additional Hang Signature 2: af05 Additional Hang Signature 3: af05260ef0423a32ce3a0322841e0731 Additional Hang Signature 4: b6f9 Additional Hang Signature 5: b6f90ddb74be284df792b6c039f1819a Additional Hang Signature 6: af05 Additional Hang Signature 7: af05260ef0423a32ce3a0322841e0731 Extra information about the problem Bucket ID: 472877c27c662f50daad7c39f8b2da13 (1922329204384520723) Problem signature Problem Event Name: AppHangB1 Application Name: NextPVR.exe Application Version: 1.0.0.0 Application Timestamp: 5e72e65c Hang Signature: b6f9 Hang Type: 262144 OS Version: 10.0.18363.2.0.0.256.48 Locale ID: 1033 Additional Hang Signature 1: b6f90ddb74be284df792b6c039f1819a Additional Hang Signature 2: af05 Additional Hang Signature 3: af05260ef0423a32ce3a0322841e0731 Additional Hang Signature 4: b6f9 Additional Hang Signature 5: b6f90ddb74be284df792b6c039f1819a Additional Hang Signature 6: af05 Additional Hang Signature 7: af05260ef0423a32ce3a0322841e0731 NPVR CRASH: Description A problem caused this program to stop interacting with Windows. Faulting Application Path: C:\Program Files\NextPVR\client\NextPVR.exe Problem signature Problem Event Name: AppHangB1 Application Name: NextPVR.exe Application Version: 1.0.0.0 Application Timestamp: 5e72e65c Hang Signature: c9ab Hang Type: 134479872 OS Version: 10.0.18363.2.0.0.256.48 Locale ID: 1033 Additional Hang Signature 1: c9ab031e1c61309760b79e34d79493bd Additional Hang Signature 2: 2ec3 Additional Hang Signature 3: 2ec3aac49f60e55c291bf24f5c85821e Additional Hang Signature 4: c9ab Additional Hang Signature 5: c9ab031e1c61309760b79e34d79493bd Additional Hang Signature 6: 2ec3Description A problem caused this program to stop interacting with Windows. Faulting Application Path: C:\Program Files\NextPVR\client\NextPVR.exe EXPLORER.EXE CRASH: Description A problem caused this program to stop interacting with Windows. Faulting Application Path: C:\Windows\explorer.exe Problem signature Problem Event Name: AppHangB1 Application Name: explorer.exe Application Version: 10.0.18362.693 Application Timestamp: 587c1978 Hang Signature: 5b34 Hang Type: 134217728 OS Version: 10.0.18363.2.0.0.256.48 Locale ID: 1033 Additional Hang Signature 1: 5b34c00675128c93af7fadfe6cf191ca Additional Hang Signature 2: 5c40 Additional Hang Signature 3: 5c40ffdf8dbad0f6e957645162d78ed9 Additional Hang Signature 4: 5b34 Additional Hang Signature 5: 5b34c00675128c93af7fadfe6cf191ca Additional Hang Signature 6: 5c40 Additional Hang Signature 7: 5c40ffdf8dbad0f6e957645162d78ed9 Extra information about the problem Bucket ID: fbf1cd4c039c7c0f54b12659bf24a5a1 (1491015118537139617) Second of all I have no idea what you are talking about doing searches with "*" for wild card searches when I haven't used search using that symbol in years. Plus I haven't used search anywhere using NPVR or KODI at any time, as far as I am aware. I have used search in my Start menu but never use the "*" symbol just the name of the file I am looking for.
2020-04-12, 02:12 PM
Explorer crashed around the time of the problem which is the most likely indication there was a windows or driver issue. NextPVR crashes could simply result from the server not responding.
Apparently you used the * recently so the rule is wrong. <EPGTitle>Broke *</EPGTitle> Martin
2020-04-12, 02:18 PM
(2020-04-12, 02:12 PM)mvallevand Wrote: Explorer crashed around the time of the problem which is the most likely indication there was a windows or driver issue. NextPVR crashes could simply result from the server not responding. Broke is a TV Show that failed to record. I did schedule it to be recorded in the future was the only thing I did with that show. I never used "BROKE *" in any form or way. If that is showing then it must of been NPVR putting it there when I clicked to have it scheduled. Possibly I did check to see when future shows of BROKE will be showing. But I used the program's own menu to do that. Not sure if it was in NPVR or KODI.
2020-04-12, 02:30 PM
Ok thanks that is one for sub then.
Martin
2020-04-12, 02:50 PM
(This post was last modified: 2020-04-12, 02:50 PM by mvallevand.)
Since you use zap2xml I wonder if you use their option to append * to new shows?
Martin (2020-04-12, 02:50 PM)mvallevand Wrote: Since you use zap2xml I wonder if you use their option to append * to new shows?I will check my EPG Batch file to see if it shows that in the commands. Went to Zap2XML website and one of the original commands does use that "*" for new shows such as BROKE: -A "new live" append " *" to program titles that are "new" and/or "live" I have been using the -A "new live" command switch since the beginning using NPVR versions 3-5.
2020-04-12, 03:16 PM
As it turns out I misinterpreted the logs Broke * is ok (not sure you need that rule if zap2xml supports the new flag) the problem seems to be with "The Honeymooners" or maybe you have a rule in between the two in your recurring list that is causing the issue?
Martin |
|
|
