Mediaportal 1.3.0 stopped unexpectedly (1 Viewer)

[mm1352000]

I agree it is possible but if the program had crashed at 2:55 how did it restart and crash again later?

I'm a bit confused.
You said:

The timestamp on both those error messages is the same time almost as when debug mode created the log zip (MediaPortalLogs_31_05_13__06_55), I am guessing they aren't related to the crash earlier in the morning?

I'm confused about how you knew there was a crash earlier in the morning and how you're grabbing these logs. So let's straighten this out.

Have you enabled the watchdog in MP config?
http://wiki.team-mediaportal.com/1_...aPortal_Configuration/11_General#General_page
...and then you're leaving TV playing overnight and finding zip files on your desktop in the morning?

OR... are you using the debug mode link in the MediaPortal folder in the Windows start menu to run the watchdog tool and collect all available logs after you observe a crash?

If the watchdog is enabled in MP config (ie. first option) then that explains how MP was restarted - the watchdog is configured to do that. It also explains why the previously noted times are so close. The system event log entry was created by Windows when the OS detected the crash; the watchdog created the zip file after the crash, and then restarted MP.

MP disappears showing the desktop and a windows error message saying Mediaportal has stopped working.

Okay.
And you're not interacting with MP or the PC at the time right? TV is playing nicely one minute... then BAM...crash?

It is like your system is not stable. Like something in the playback chain - ie. TsReader, codecs or renderer - gets upset decoding and displaying the content of the DVB-T streams.

If any one of those things were causing this surely the logs would point that out?

Not at all.
For a start, some of the components involved like codecs are 3rd party. In other words they don't log into the MP log files (if they log at all).
Also, crashes are usually caused by exceptional/unexpected conditions that are not handled. When a crash happens during some particular interaction with MP then we have some context to help us reproduce and find the cause. When a crash just happens and you weren't actively interacting with MP... as appears to be the case here... then it can be quite a bit more difficult to find the source of the problem, let alone fix it.

 

[adrian5800]

I'm confused about how you knew there was a crash earlier in the morning and how you're grabbing these logs. So let's straighten this out.

MP left running all night, in the morning turn on monitor (tv) and windows reported MP has stopped (at some stage). The log zip I posted which is named
MediaPortalLogs_31_05_13__06_55 was the time in the morning when I closed the windows error message and the zip was created.

Have you enabled the watchdog in MP config?
http://wiki.team-mediaportal.com/1_...aPortal_Configuration/11_General#General_page
...and then you're leaving TV playing overnight and finding zip files on your desktop in the morning?

No

OR... are you using the debug mode link in the MediaPortal folder in the Windows start menu to run the watchdog tool and collect all available logs after you observe a crash?

Yes - the first option - Report a bug to team Mediaportal

If the watchdog is enabled in MP config (ie. first option) then that explains how MP was restarted - the watchdog is configured to do that. It also explains why the previously noted times are so close. The system event log entry was created by Windows when the OS detected the crash; the watchdog created the zip file after the crash, and then restarted MP.

See above

And you're not interacting with MP or the PC at the time right? TV is playing nicely one minute... then BAM...crash?

Yes

For a start, some of the components involved like codecs are 3rd party. In other words they don't log into the MP log files (if they log at all).
Also, crashes are usually caused by exceptional/unexpected conditions that are not handled. When a crash happens during some particular interaction with MP then we have some context to help us reproduce and find the cause. When a crash just happens and you weren't actively interacting with MP... as appears to be the case here... then it can be quite a bit more difficult to find the source of the problem, let alone fix it.

I appreciate the time you have given me so far to nut this out.

 

[adrian5800]

Anyone else have any input to this?

 

[jehe]

Hi Adrian,

What I would do is the following:

Check your energy savings settings
reinstall your drivers (TV card)
remove all unnecessary codecs, just use LAV codec's
clean up your registry
run a scandisk on your external hard drive.
test your tvcard with other software -> ProgDVB

if that does not help remove and reinstall mediaportal

if that does not help reinstall mediaportal on a clean windows

 

[adrian5800]

Hi Adrian,

What I would do is the following:

Check your energy savings settings
reinstall your drivers (TV card)
remove all unnecessary codecs, just use LAV codec's
clean up your registry
run a scandisk on your external hard drive.
test your tvcard with other software -> ProgDVB

if that does not help remove and reinstall mediaportal

if that does not help reinstall mediaportal on a clean windows

Will do. Thanks for the advice.
Not looking forward to reinstalling MP or Windows if your first solutions don't fix it..

Cheers

Adrian

 

[adrian5800]

Check your energy savings settings Done
reinstall your drivers (TV card) Done
remove all unnecessary codecs, just use LAV codec's Done
clean up your registry Done
run a scandisk on your external hard drive. Done. No errors found
test your tvcard with other software -> ProgDVB Done.
And with all the above MP still crashes as before.

if that does not help remove and reinstall mediaportal Done. Clean re install to MP 1.4.0, currently testing now - fingers crossed

if that does not help reinstall mediaportal on a clean windows

Cheers
Adrian

 

[mm1352000]

I'd say the first thing I'd do would be the drivers, and I'd focus more on platform - GPU in particular.
I doubt there is any problem with the TV tuner as the TV service is not crashing.

The second thing I'd be doing is trying other codecs - both video and audio.

The third thing I'd do is check your heat levels and monitor GPU and CPU utilisation when watching TV.

 

[adrian5800]

I'd say the first thing I'd do would be the drivers, and I'd focus more on platform - GPU in particular.
I doubt there is any problem with the TV tuner as the TV service is not crashing.

The second thing I'd be doing is trying other codecs - both video and audio.

The third thing I'd do is check your heat levels and monitor GPU and CPU utilisation when watching TV.

After the reinstall of MP it has been running fine so far. I have cleaned out all the unnecessary codecs and am only using LAV now. Cpu is around 20% and temps are ok at 65 c for the cpu and 75 c for the gpu.


Ades