Hibernation Problem (1 Viewer)

[mbuzina]

Plugins/Skins are only disabled in mode 1. Mode 2 runs normal and *should* not change behavior instead of setting log level to debug (true?).

Then run into the issue in "normal" mode, let it crash and after that collect the logs with option 3 from the debug tool

 

[eetaylog]

Plugins/Skins are only disabled in mode 1. Mode 2 runs normal and *should* not change behavior instead of setting log level to debug (true?).

Then run into the issue in "normal" mode, let it crash and after that collect the logs with option 3 from the debug tool

Ah ok, so what youre saying is open Mediaportal in normal mode, let it crash, then close MP and in de-bug choose Option 3 -> Proceed?

Many thanks, ill try it tonight.

 

[eetaylog]

Ok so ive now replicated the error and have created logs from option 3 of debug, can someone please have a look and tell me why my MP is crashing after resuming from hibernation.


Many thanks

 

[mm1352000]

The system event log reports the crash occuring in Kernel32.dll, which would suggest a deep problem to me. However, the fact that you can't reproduce with plugins disabled suggests a plugin problem, *not* an MP problem. What I was trying to say earlier was not to enable you to produce logs, but rather to ask you to use process of elimination to figure out if you can have a plugin that is causing this. That seems more logical to me given all the information that you've presented. So to be *very* clear: I would suggest you disable all your plugins (of which you have quite a few), and then enable them one by one and attempt to reproduce the problem again until the crashes start occurring again. If you can narrow it down to a single plugin then you can report the problem to the plugin developer.
mm

 

[eetaylog]

The system event log reports the crash occuring in Kernel32.dll, which would suggest a deep problem to me. However, the fact that you can't reproduce with plugins disabled suggests a plugin problem, *not* an MP problem. What I was trying to say earlier was not to enable you to produce logs, but rather to ask you to use process of elimination to figure out if you can have a plugin that is causing this. That seems more logical to me given all the information that you've presented. So to be *very* clear: I would suggest you disable all your plugins (of which you have quite a few), and then enable them one by one and attempt to reproduce the problem again until the crashes start occurring again. If you can narrow it down to a single plugin then you can report the problem to the plugin developer.
mm

Thanks for having a look, ill disable all my plugins and go from there. If this doesnt solve it though, i wonder whether my bios might need updating as im still using the out-of-the-box bios version on my motherboard (which is ~5 years old now).

 

[mm1352000]

*bump*
What did you find?

 

[eetaylog]

I was just about to update this thread, but thanks for checking up... it seemed to be an issue with both the MovingPictures plugin and my Hauupauge remote IR drivers.

I disabled all my plugins and started them one by one, everything was fine on MP start until i re-enabled MovingPictures, so i reinstalled it and things seemed to be much better, but i was still getting MP crashes occasionally and it always seemed to coincide with an HCWhelper crash, so i decided to try an MCE remote with microsoft IR receiver that i had laying around. Since uninstalling the hauupauge drivers and using the MCE remote everything seems to be pretty solid now. Fingers crossed

Only issue now is MP freezing on resume from standby......

https://forum.team-mediaportal.com/general-support-51/mediaportal-freezing-resume-100417/#post787816

...though i think this is something to do with my MP settings, ill have to investigate further.

Many thanks for checking up.