Recording service not running at recording time

[tallpilot]

This problem has occurred several times since I've upgraded to version 3.3.8 (once every week or so).

I had 2 shows set to record this past Sunday, Dec. 7. One at 10:00 a.m. and the other at 7:00 p.m. The first show recorded successfully, but the second show did not record due to the error specified in the title.

From looking at the NRecord logs, it looks like the recording service may have suddenly quit running at 2:20 p.m., right after the log message that reads "Cycling MVP servers". I'm not sure... I'm relatively new to MPVR (began with version 3.2.9).

When I looked at the Windows services, the NPVR Recording Service was not running. I was able to manually restart the service. There doesn't seem to be an issue with the service starting when the computer restarts. Each time I shutdown or restart, the service is running when the computer comes back up.

Help would be greatly appreciated. I love NPVR and its associated scripting capabilities, but it has been very unreliable lately.

[mvallevand]

I'd look in the event viewer logs to see if the recording service logged anything at 14:55

2014-12-07 14:55:22.945 [INFO][1] DigitalRecorder.StopHost()

Martin

[tallpilot]

I'd look in the event viewer logs to see if the recording service logged anything at 14:55

2014-12-07 14:55:22.945 [INFO][1] DigitalRecorder.StopHost()

Martin

Thank you very much for the prompt reply. I looked, and there are errors just before that time (but none of them are logged by NPVR). I copied the details of these events below. The Fuel.Service.exe crash seems to happen frequently. I'm looking in to that now. Any ideas?

Log Name: Application
Source: Windows Error Reporting
Date: 12/7/2014 2:55:23 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Mercury
Description:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Fuel.Service.exe
P2: 1.0.0.0
P3: 517f39a1
P4: Device.dll
P5: 4.1.0.0
P6: 4f55e10b
P7: c0000005
P8: 00000000000033c1
P9:
P10:

Attached files:
C:\Windows\Temp\WER798B.tmp.appcompat.txt
C:\Windows\Temp\WER79E9.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WER79EA.tmp.hdmp
C:\Windows\Temp\WER7C4C.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Fuel.Service.exe_8489f578b3ca4e9db96ea0412b9d921933f263_cab_22ef7c78

Analysis symbol:
Rechecking for solution: 0
Report Id: 5a3dd6ef-7e53-11e4-b63b-e0cb4e602d9f
Report Status: 0

Log Name: Application
Source: Windows Error Reporting
Date: 12/7/2014 2:55:20 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Mercury
Description:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Fuel.Service.exe
P2: 1.0.0.0
P3: 517f39a1
P4: Device.dll
P5: 4.1.0.0
P6: 4f55e10b
P7: c0000005
P8: 00000000000033c1
P9:
P10:

Attached files:
C:\Windows\Temp\WER798B.tmp.appcompat.txt
C:\Windows\Temp\WER79E9.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WER79EA.tmp.hdmp
C:\Windows\Temp\WER7C4C.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Fuel.Service.exe_8489f578b3ca4e9db96ea0412b9d921933f263_cab_22ef7c78

Analysis symbol:
Rechecking for solution: 0
Report Id: 5a3dd6ef-7e53-11e4-b63b-e0cb4e602d9f
Report Status: 4

Log Name: Application
Source: Application Error
Date: 12/7/2014 2:55:19 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Mercury
Description:
Faulting application name: Fuel.Service.exe, version: 1.0.0.0, time stamp: 0x517f39a1
Faulting module name: Device.dll, version: 4.1.0.0, time stamp: 0x4f55e10b
Exception code: 0xc0000005
Fault offset: 0x00000000000033c1
Faulting process id: 0x710
Faulting application start time: 0x01d01130789e4f5c
Faulting application path: C:\Program Files\ATI Technologies\ATI.ACE\Fuel\Fuel.Service.exe
Faulting module path: C:\Program Files\ATI Technologies\ATI.ACE\Fuel\Device.dll
Report Id: 5a3dd6ef-7e53-11e4-b63b-e0cb4e602d9f

Log Name: Application
Source: Microsoft-Windows-Winlogon
Date: 12/7/2014 2:55:15 PM
Event ID: 6000
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Mercury
Description:
The winlogon notification subscriber <SessionEnv> was unavailable to handle a notification event.

Log Name: Application
Source: Desktop Window Manager
Date: 12/7/2014 2:55:15 PM
Event ID: 9009
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Mercury
Description:
The Desktop Window Manager has exited with code (0x40010004)

[Lao Pan]

Thank you very much for the prompt reply. I looked, and there are errors just before that time (but none of them are logged by NPVR). I copied the details of these events below. The Fuel.Service.exe crash seems to happen frequently. I'm looking in to that now. Any ideas?

First off I would update the AMD Catalyst Drivers - if your graphics are fairly recent, a new version (14.12) which fixes several problems came out about 4 hours ago otherwise you will need the last legacy drivers Go here http://support.amd.com/en-us/downloadand put in your specs.

[tallpilot]

First off I would update the AMD Catalyst Drivers - if your graphics are fairly recent, a new version (14.12) which fixes several problems came out about 4 hours ago otherwise you will need the last legacy drivers Go here http://support.amd.com/en-us/downloadand put in your specs.

I installed the latest drivers for my HD 4200 last night. I'll let things run a few days and see if the AMD Fuel service errors go away. While the NPVR errors only occurred every week or so, the Fuel errors were occurring on a pretty regular basis.

Thanks again for the prompt replies!