Media Portal freezes on wake (4 Viewers)

[HTPCSourcer]

Do you have full log ? to see what happen in event system etc. ?

I'll provide those later. It's the PC in the living and W and w are currently watching.

Also we have maybe a theory about PS fault but that not sure, could you reproduce the issue (always) and disable PS ?

Not sure that I fully understand: so you would like me to disable the PS and send the PC manually into standby/hibernate, right?

 

[HTPCSourcer]

Here is the full log including the event log etc. The resume logs may take some more time.

 

[HTPCSourcer]

I manually put the PC to sleep yesterday at 22:51 and just resumed. The PC came up with a smaller MP homescreeen on top of the Windows desktop together with the message that MediaPortal had stopped working. The latest log entry is from yesterday.

 

[mm1352000]

@HTPCSourcer
Windows application event log says:
[collapse]
"14.11.2015 04:09:19";".NET Runtime";"(0)";"Error";"Anwendung: MediaPortal.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.Reflection.TargetInvocationException
Stapel:
bei System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()
bei InfoService.Utils.FeedUtils.fWorker_RunWorkerCompleted(System.Object, System.ComponentModel.RunWorkerCompletedEventArgs)
bei System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(System.ComponentModel.RunWorkerCompletedEventArgs)
bei System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(System.Object)
bei System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
bei System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
bei System.Threading.ThreadPoolWorkQueue.Dispatch()
bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
";"1026"
"14.11.2015 04:09:19";"Application Error";"Anwendungsabsturzereignisse";"Error";"Name der fehlerhaften Anwendung: MediaPortal.exe, Version: 1.12.100.94, Zeitstempel: 0x56458371 Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.10240.16384, Zeitstempel: 0x559f3b2a Ausnahmecode: 0xe0434352 Fehleroffset: 0x000b3e28 ID des fehlerhaften Prozesses: 0x2c2c Startzeit der fehlerhaften Anwendung: 0x01d11e43b3fa8d02 Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Team MediaPortal\MediaPortal\MediaPortal.exe Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\KERNELBASE.dll Berichtskennung: 6428728c-e2ca-4546-b840-adc910731895 Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: ";"1000"[/collapse]

In other words, it looks like the InfoService plugin is responsible for the crash. I'm not able to help you with that.

 

[mm1352000]

Same InfoService-related exception in the earlier log file too:
[collapse]
"13.11.2015 15:56:08";".NET Runtime";"(0)";"Error";"Anwendung: MediaPortal.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.Reflection.TargetInvocationException
Stapel:
bei System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()
bei InfoService.Utils.FeedUtils.fWorker_RunWorkerCompleted(System.Object, System.ComponentModel.RunWorkerCompletedEventArgs)
bei System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(System.ComponentModel.RunWorkerCompletedEventArgs)
bei System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(System.Object)
bei System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
bei System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
bei System.Threading.ThreadPoolWorkQueue.Dispatch()
bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
";"1026"
"13.11.2015 15:56:08";"Application Error";"Anwendungsabsturzereignisse";"Error";"Name der fehlerhaften Anwendung: MediaPortal.exe, Version: 1.12.100.94, Zeitstempel: 0x56458371 Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.10240.16384, Zeitstempel: 0x559f3b2a Ausnahmecode: 0xe0434352 Fehleroffset: 0x000b3e28 ID des fehlerhaften Prozesses: 0x1ad8 Startzeit der fehlerhaften Anwendung: 0x01d11e041c14f877 Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Team MediaPortal\MediaPortal\MediaPortal.exe Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\KERNELBASE.dll Berichtskennung: d6339d53-4cc7-49d2-a989-89c30abd707c Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: ";"1000"
"13.11.2015 15:56:16";"Windows Error Reporting";"(0)";"Information";"Fehlerbucket 128954021701, Typ 5 Ereignisname: CLR20r3 Antwort: Nicht verfügbar CAB-Datei-ID: 0 Problemsignatur: P1: MediaPortal.exe P2: 1.12.100.94 P3: 56458371 P4: mscorlib P5: 4.6.127.1 P6: 561da455 P7: 157e P8: 219 P9: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB P10: Angefügte Dateien: R:\TMP\WER4077.tmp.WERInternalMetadata.xml Diese Dateien befinden sich möglicherweise hier: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MediaPortal.exe_84c5bce68696f954953f71a03e961cc6a92b14b_ce74f495_1d875f2b Analysesymbol: Es wird erneut nach einer Lösung gesucht: 0 Berichts-ID: d6339d53-4cc7-49d2-a989-89c30abd707c Berichtstatus: 0 Bucket mit Hash: 210fe3b81eea7edb378b0d44271de4ad";"1001"[/collapse]

 

[Sebastiii]

It was disable on my side, will try to enable it and see if it crash too

 

[HTPCSourcer]

In other words, it looks like the InfoService plugin is responsible for the crash. I'm not able to help you with that.

Well, if that's the only problem, I will disable it. However, out of interest, where do you see that it is related to InfoService? I did check the event log entries myself but could not read anything into them other than KERNELBASE.dll being the source of the issue.

 

[mm1352000]

However, out of interest, where do you see that it is related to InfoService?

In the stack trace, as posted:
bei InfoService.Utils.FeedUtils.fWorker_RunWorkerCompleted(System.Object, System.ComponentModel.RunWorkerCompletedEventArgs)

[edit: To be clear, I'm not saying that is the only cause/problem. Other issues may become apparent after disabling the plugin.]

 

[HTPCSourcer]

Some new findings: After manually hibernating the PC yesterday, it came up with the usual partial home screen on top of the Windows desktop, and stayed like this, yet did not crash. So removing the Info plugin did make an effect.

However, I found out that the server shares were not accessible, hence no wonder that MP is unresponsive because databases are remote on the server. The attempt to manually access the share (e.g. in Explorer via \\server) throwed an error message that this user was not allowed. As the PC is part of a domain, user acount names have the format domain/username. I suspect that after resume from hibernate something is going wrong with the autologon communication and only the username part got transmitted to the server.

Instead of entering the credentials directly into the registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon), I now used netplwiz to create entries from the user selection and password dialogues. And surprise, the data are different. DefaultDomainName now contains the name of the PC (!) whereas DefaultUserName is now domain\HTPC1. So it appears that for a year I have been working with the incorrect assumption that DefaultDomainName does what the name insinuates and stores the name of the associated domain - well it does not.

 

[mm1352000]

However, I found out that the server shares were not accessible, hence no wonder that MP is unresponsive because databases are remote on the server.

Indeed. You're very brave to share the databases in that way. It opens the door for so many things to go wrong in various contexts, including on resume.