Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1223676" data-attributes="member: 82144">HelloThanks for the report.There's no 64 bit version of MP.It's difficult to be sure, but I suspect that the system failed to suspend properly at 19:32, and that in turn caused the TV Server to fail to resume properly at 20:07.If you check the Windows application event log you can see that Windows thought the MP Watchdog hung at 19:32:[collapse]03.06.2017 19:32:13,Windows Error Reporting,(0),Information,&quot;Fehlerbucket , Typ 0 Ereignisname: AppHangB1 Antwort: Nicht verfügbar CAB-Datei-ID: 0&nbsp; Problemsignatur: P1: WatchDog.exe P2: 1.15.0.0 P3: 576f98e8 P4: ae8b P5: 134217984 P6:&nbsp; P7:&nbsp; P8:&nbsp; P9:&nbsp; P10:&nbsp;&nbsp; Angefügte Dateien: C:\Users\Peter\AppData\Local\Temp\WERC4A5.tmp.appcompat.txt C:\Users\Peter\AppData\Local\Temp\WERCEE7.tmp.WERInternalMetadata.xml C:\Users\Peter\AppData\Local\Temp\WERCF46.tmp.xml C:\Users\Peter\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppHang_WatchDog.exe_63354344e9720b915f723ace34561206224357e_d4a35241_cab_0d59cf73\memory.hdmp C:\Users\Peter\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppHang_WatchDog.exe_63354344e9720b915f723ace34561206224357e_d4a35241_cab_0d59cf73\triagedump.dmp WERGenerationLog.txt&nbsp; Diese Dateien befinden sich möglicherweise hier: C:\Users\Peter\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppHang_WatchDog.exe_63354344e9720b915f723ace34561206224357e_d4a35241_cab_0d59cf73&nbsp; Analysesymbol:&nbsp; Es wird erneut nach einer Lösung gesucht: 0 Berichts-ID: 1b68628d-4956-11e6-82ac-bc5ff477f912 Berichtstatus: 96 Bucket mit Hash: &quot;,1001,,[/collapse]I don't know why Windows thought that, but in my opinion that's the reason for everything you've seen (failed recordings, MP not full screen etc.).</blockquote>

[QUOTE="mm1352000, post: 1223676, member: 82144"] Hello Thanks for the report. There's no 64 bit version of MP. It's difficult to be sure, but I suspect that the system failed to suspend properly at 19:32, and that in turn caused the TV Server to fail to resume properly at 20:07. If you check the Windows application event log you can see that Windows thought the MP Watchdog hung at 19:32: [collapse]03.06.2017 19:32:13,Windows Error Reporting,(0),Information,"Fehlerbucket , Typ 0 Ereignisname: AppHangB1 Antwort: Nicht verfügbar CAB-Datei-ID: 0 Problemsignatur: P1: WatchDog.exe P2: 1.15.0.0 P3: 576f98e8 P4: ae8b P5: 134217984 P6: P7: P8: P9: P10: Angefügte Dateien: C:\Users\Peter\AppData\Local\Temp\WERC4A5.tmp.appcompat.txt C:\Users\Peter\AppData\Local\Temp\WERCEE7.tmp.WERInternalMetadata.xml C:\Users\Peter\AppData\Local\Temp\WERCF46.tmp.xml C:\Users\Peter\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppHang_WatchDog.exe_63354344e9720b915f723ace34561206224357e_d4a35241_cab_0d59cf73\memory.hdmp C:\Users\Peter\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppHang_WatchDog.exe_63354344e9720b915f723ace34561206224357e_d4a35241_cab_0d59cf73\triagedump.dmp WERGenerationLog.txt Diese Dateien befinden sich möglicherweise hier: C:\Users\Peter\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppHang_WatchDog.exe_63354344e9720b915f723ace34561206224357e_d4a35241_cab_0d59cf73 Analysesymbol: Es wird erneut nach einer Lösung gesucht: 0 Berichts-ID: 1b68628d-4956-11e6-82ac-bc5ff477f912 Berichtstatus: 96 Bucket mit Hash: ",1001,,[/collapse] I don't know why Windows thought that, but in my opinion that's the reason for everything you've seen (failed recordings, MP not full screen etc.). [/QUOTE]

Verification