Crash / Shutdown

[fccgrant]

So there is a new 'The previous system shutdown at 5:24:57 AM on ‎9/‎19/‎2021 was unexpected.' Message.

Followed by 'The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.' Blah blah blah.

Hopefully the Verbose setting caputred something.

Set up was to power up at the top of the hour, record 10 minutes, the will sleep 15 minutes after that.

The drivers I have are the latest available from Dvico / Fusion. No further support from them is available.

Thanks...Jerry

[mvallevand]

Ok I should have checked you are running an old version of NextPVR so flushing is not available.

Martin

[fccgrant]

With the latest version on NPVR...

"The previous system shutdown at 3:55:46 PM on ‎9/‎19/‎2021 was unexpected."

Thanks...Jerry

[sub]

You're the only person reporting this, so it's sounding like something unique to your environment. You're the only person I remember seeing using the FusionHDTV device, so I'm guessing it's something to do with it's drivers.

Unfortunately I'm not really sure what to suggest to avoid the issue. (other than checking you're on the latest drivers etc)

[fccgrant]

The logs I just attached probably aren't helpful after all. There was a crash at 1:11 PM. I suspect the Verbose setting got disabled after that.

I do not see anything really unique to the drivers. They are all showing as Microsoft as the providers.

The Fusion card is using the XC5000. I was researching this chip out and read there was some issues with shutting down the card with a couple of other PVRs running in a Linux environment. Think there's any relation?

Thanks for all of the help that has been provided to this point.

Jerry

[sub]

Windows is pretty well protected against general user mode applications like NextPVR from doing anything that could cause a system to crash/reset/etc. Drivers are a different story, and run in protected mode, and absolutely can bring a system down, and we've definitely seen a few cases over the years of people having issues with drivers that could cause things like this.

[fccgrant]

Is there some way of having all of the logs completely flushed from the comand line prior to the computer going back to sleep?

I'm not quite ready to condemn the drivers just yet. Earlier in the week there was another crash.  Digging in into the crash log showed a memory corruption error.  The interesting thing was the nrecord log was interrupted / truncated on Wednesday. The recording for Wednesday was still made and the crash occurred on Thursday when it was doing the EPG update.

This got me thinking about the memory and the buffer that holds the results before nrecord is written.

The setup: NPVR has scheduled recordings manually added. At 4:45 PM every day the computer wakes up and updates the EPG. Then falls asleep 20 minutes later. The expectation is that all recordings will be made and no attention will be made to the computer until Saturday.

Other info:
There does seem to be a pattern where every Wednesday the computer may crash at the EPG update on Thursday or right before a recording on Wednesday.

Previously, crashes happened every Tuesday. However, on these events it was because there was a recording made on Sunday. The Wednesday crashes do not have any recordings made on Sunday.

Starting this week there will be Sunday recordings so it will be interesting to see if the crash shifts to Tuesdays.

Thanks.

[sub]

Is there some way of having all of the logs completely flushed from the comand line prior to the computer going back to sleep?

If you set a global environment variable NEXTPVR_VERBOSE=true, then restart, it'll create more detailed logs, and flush every log line as it's logged.