Crash / Shutdown

[fccgrant]

Hello All-



The computer that I use is mostly for HDTV recordings. Over the years I've had intermittent unexpected shutdowns. Running test recordings during the past month and checking or disabling various services or features has still resulted in at least one crash a week. Daily test recordings are from 9:00 PM to 9:30 PM with 5 minute paddings. The PC is set to sleep after 45 minutes.



The latest event message appeared this morning. "The previous system shutdown at 10:18:49 PM on ‎9/‎16/‎2021 was unexpected."



Digging into the NPVR logs I found 'device-FusionHDTV, BDA Tuner-1.log' with the same time stamp. Viewing the log files and making some comparisons to other log files of similar names showed some interesting results.



The end of the file ending in .2 log shows the following messages. The .1 log shows similar results but ends at line 6.  



2021-09-16 16:49:03.821 [DEBUG][7] Removing filter  BDA MPEG2 Transport Information Filter

2021-09-16 16:49:03.821 [DEBUG][7] Removing filter  MPEG-2 Demultiplexer

2021-09-16 16:49:03.821 [DEBUG][7] Removing filter  NPVR TS Mon

2021-09-16 16:49:03.821 [DEBUG][7] Removing filter  Capture

2021-09-16 16:49:03.821 [DEBUG][7] Removing filter  Tuner

2021-09-16 16:49:03.821 [DEBUG][7] Removing filter  Network Provider

2021-09-16 17:30:28.626 [INFO][6] Got GET request: /shutdown

2021-09-16 17:30:28.626 [DEBUG][6] /shutdown...

2021-09-16 17:30:29.076 [INFO][1] Flushing logs

2021-09-16 17:30:29.076 [DEBUG][1] stopping device

2021-09-16 17:30:29.076 [DEBUG][1] device stopped

2021-09-16 17:30:29.076 [INFO][1] Flushing logs



Some other logs appear to be truncated or 'cut off'.



Thanks and looking forward to hearing what the problem is and how it may be resolved.

[mvallevand]

It is not clear from the NextPVR logs not flushing, it looks like the it told the fusion device to shutdown earlier at 17:30 but didn't finish. You should enable verbose logging via config.xml so the disk caching is turned off for the next tests.

Martin

[fccgrant]

I have enabled for verbose logging so we'll see what happens.

I see 'shutdown' in the logs. What exactly is being shutdown? The card? If it is the card and for whatever reason the messge isn't being received or sent  is there some way I could put a script together to verify it is shutdown and if it is not send the messge again?

Thanks...Jerry

[mvallevand]

No I think NextPVR is shutting down and sent that message before the crash happened. The verbose logging turns off log caching.

Martin

[sub]

Maybe also look in the Windows Event Viewer for any crashes at that time.

[fccgrant]

The event viewer has always given the message that an Unexpected Shutdown at xx time. The time stamp in the event viewer matched the time stamp of one of the log files which I believe was 10:18 PM on 9/16.

[sub]

Does it give any more details about what happened?

[fccgrant]

I wish it did, sub! The system was idling for 45 minutes after the recording finished. The computer was not in use for any other purpose.

Thanks...Jerry

[mvallevand]

That log is odd, if you open it as hex there are lots of nulls at the bottom

001970 206b 7250 766f 6469 7265 0a0d 0000 0000
0001980 0000 0000 0000 0000 0000 0000 0000 0000
*
0001ab4

[sub]

The latest event message appeared this morning. "The previous system shutdown at 10:18:49 PM on ‎9/‎16/‎2021 was unexpected."
....
Digging into the NPVR logs I found 'device-FusionHDTV, BDA Tuner-1.log' with the same time stamp. Viewing the log files and making some comparisons to other log files of similar names showed some interesting results.

Could be flakey FusionHDTV drivers. Maybe make sure you're running the most recent version of them.

If the machine was going to sleep at that time, NextPVR would probably have asked the FusionHDTV device to stop. Maybe the drivers blue screened or something.