MP crashes sometimes after resume from Standby (2 Viewers)

[blub]

i do have the AVR Audioguard running (or else i don't hear the navigation clicks anymore since Win 8).

Ok I don't have that program.

I will now test if the setting Volume to "Master" will help. But what after that!?

Should we
a) increase the MP delay to 20s - that would suck
b) try a different AMD driver? - if so which one - any suggestions from the devs?

 

[Sebastiii]

Try a delay of 20s for testing it could be nice to know if it's ok with it for sure.
About AMD driver why not but not sure for now

 

[Sebastiii]

Oooky here we go, MP crashed again:

MP was frozen and again the window from MP was small as it was the crash before with windows content beeing non visible - TV resolution was correctly full HD when I got the picture.
When I clicked on the MP taskbar icon it went back to fullscreen but was completely black.
That is in contrary to the behavior with version MP 1.6 where in all crashes MP stayed in fullscreen mode with visible GUI or black window content.

Could it be that the HTPC first sets the wrong resolution, for whatever reasons, and then when all HDMI links are up it switches to full HD resolution and that then kills MP!?

The log from the current crash is attached, it was still the standard 1.7pre. I think it looks worthless.


As for the post above my Volume setting in MP is set to "Wave" - I haven't touched this (at least I think I haven't)


I now installed the provided test version of 1.7 with the "delay option" beeing fixed and will report back.
Attached is a picture which option I ticked - is that the correct one?

Your online video is not compatible :

[2014-03-17 20:32:13,859] [Log    ] [MPMain   ] [INFO ] - PluginManager: Plugin file OnlineVideos.MediaPortal1.dll is broken or incompatible with the current MediaPortal version and won't be loaded!
[2014-03-17 20:32:13,859] [Log    ] [MPMain   ] [INFO ] - PluginManager: Exception: System.IO.FileNotFoundException: Die Datei oder Assembly "WindowPlugins, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null" oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.
Dateiname: "WindowPlugins, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null"
   bei System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes)
   bei System.Reflection.RuntimeAssembly.GetExportedTypes()
   bei MediaPortal.GUI.Library.PluginManager.LoadWindowPlugin(String strFile)

WRN: Protokollierung der Assemblybindung ist AUS.
Sie können die Protokollierung der Assemblybindungsfehler aktivieren, indem Sie den Registrierungswert [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) auf 1 festlegen.
Hinweis: Die Protokollierung der Assemblybindungsfehler führt zu einer gewissen Leistungseinbuße.
Sie können dieses Feature deaktivieren, indem Sie den Registrierungswert [HKLM\Software\Microsoft\Fusion!EnableLog] entfernen.

You can try this version : https://forum.team-mediaportal.com/...evidoes-mediaportal1-dll.124700/#post-1064664

 

[Sebastiii]

@blub

Can you test on installer with delay setting fixed ? (https://issues.team-mediaportal.com/browse/MP1-4420)
In this build it's based on 1.7.0 pre release + latest master code to try to catch some issue with audio device not fully ready and also some resume sequence fixed.

From your log we can see the version :
"Main: MediaPortal v1.6.100.0 is starting up on Compatibilty Mode: Windows 8 [6.2.9200.0]"
So it seems it's not this build used.

Thanks

Then clean your log and do a fresh start and when crash happen, can you write timestamp

 

[blub]

OK I changed the OnlineVideo version to the one u posted. However it always told me that MP is not loading the plugin, therfore I thought if itsn't beeing loaded it can't be responsible for the crashes [DOUBLEPOST=1395385946][/DOUBLEPOST]

@blub

Can you test on installer with delay setting fixed ? (https://issues.team-mediaportal.com/browse/MP1-4420)
In this build it's based on 1.7.0 pre release + latest master code to try to catch some issue with audio device not fully ready and also some resume sequence fixed.

From your log we can see the version :
"Main: MediaPortal v1.6.100.0 is starting up on Compatibilty Mode: Windows 8 [6.2.9200.0]"
So it seems it's not this build used.

Thanks

Then clean your log and do a fresh start and when crash happen, can you write timestamp

The version I am using is this one, which I think is the test version:

2014-03-21 08:08:26,728] [Log ] [MPMain ] [INFO ] - Main: MediaPortal v1.6.100.222 is starting up on Compatibilty Mode: Windows 8 [6.2.9200.0]

I installed it yesterday at around noon. And the crash-log from post 1071105 should already be the new version.
I have now cleaned the logs.

 

[blub]

Hi - it's me again with a hopefully more precise error log.

Here is what I did last (I think):

I was watching live TV and just turned the HTPC off.
When I turned it on there was a windows error message. I have attched the MP-crash log in the normal way and furthermore the Windows error log of:

a) MP when the HTPC resumed
b).Net when I shutdown the HTPC before
c) MP when HTPC shutdown

EDIT:
That crash was with the test version and Volume setting set to "Master" instead of wave.

 

[blub]

Ok just for information:

I am now using build 1.6.100.222 with Volume set to "Master". Record from TS Buffer is disabled.

Changed to AMD Catalyst 13.09 which is the oldest I think supporting my AMD A10 6700 graphic.

I will keep u posted if it either keeps crashing or get's better.

 

[skorz]

And here is my Information: 4 (!) days without any crash or problem. I never have this situation before, nevermind
Last detail i changed was to set Master instead of Wave.

So for now.. .... ... .. i am happy

 

[blub]

Ok

After almost exactly 4 days no crash either. Contrary to Skorz's observation the change from "Wave" to "Master" volume did not help in my setup and only changing driver to AMD catalyst 13.9 showed an effect.

What I am doing now is an attempt to verify Skorz' obersavation by setting the Volume setting to back to "Wave" and see if that again leads to the standby issue - if that would be the case even with the 13.9 driver there would be 2 issues.


@skorz:

Which driver version of AMD catalyst are you running?

I will report back

 

[skorz]

14.1