1.15.0 MediaPortal Invisible on Resume from Hibernate (2 Viewers)

[rmeredit]

After installing 1.15.0, I've been having a consistently recurring problem with MP waking from hibernate. Powerscheduler successfully puts the PC into hibernation as required, and wakes it up for recordings, etc. Whenever the PC resumes, now, whether automatically through Powerscheduler or manually, MP is running, but invisible, even though it's the only application running.

The symptoms are that the windows desktop is visible, as if no application is running. The pinned MP shortcut icon is underlined as you would expect for a running app. Alt-tab shows the MP window exists, but it's empty. Pressing Alt-F4 to quit doesn't work (the shortcutt'er plugin may be intercepting things here, but when MP is running normally, Alt-F4 works fine), and I have to resort to the Task Manager to quit MP and restart.

This happens every time that MP goes to sleep and wakes up. Very occasionally, after a long delay, the MP window will come back to life, but this is very rarely the case (maybe 2-3 times over the last two months).

Checking the logs shows an occasional DirectX error, but this is not consistent, and doesn't show up every time that MP has to be restarted.

All was fine under 1.14.0.

Logs attached.

 

[mm1352000]

Hello

Logs attached.

It looks like you collected these log files by opening MP with the Watchdog tool option 1 or 2, and then closing MP approximately 10 seconds later. Since the log files don't show any hibernate + resume cycle, they don't show the problem. Therefore I can't use these log files to help you.

Please can you try to collect new log files that actually show the problem.

 

[rmeredit]

Ah, sorry, I just assumed that the full logs with past events would be included by the Watchdog tool. Here are new logs. I started Watchdog, which launched MP. I then tuned in to some free to air TV for a moment, then stopped, returned to the home menu and selected hibernate. The machine shutdown for a few seconds, and I manually restarted. When the machine was back up, MP was invisible, and I quite by pressing Alt-F4 (which worked this time, sometimes it doesn't). Watchdog then packaged up the attached logs:

Cheers,

Rob

 

[mm1352000]

Ah, sorry, I just assumed that the full logs with past events would be included by the Watchdog tool.

No need to apologise - a simple mistake/misunderstanding.

All available historical log files are included... but only if you use Watchdog option 3 ("export..."). The disadvantage of option 3 is that we can't retroactively include full detail in the log files. On the other hand, options 1 and 2 require you to be able to reproduce the problem, and that's not always possible.

For those reasons we prefer the problem to be reproduced with the Watchdog using either option 1 or 2 whenever possible. For non-reproducible problems, option 3 is available as a fall-back.

Here are new logs...

Yeah, these show the problem nicely.

Are you running the latest available driver for your GPU?
I ask this because D3D errors like those in your log files often relate to GPU driver problems.

Also, could you check if you're able to reproduce the problem after [temporarily] disabling the MiniDisplay plugin?

 

[rmeredit]

Hi,

Are you running the latest available driver for your GPU?

Yes, as far as I can tell. The GPU is an on-board Intel chipset, using the Microsoft Drivers for Windows 10. I've opened Device Manager and right-clicked on the display adaptor and selected search for updated drivers - Windows says that it thinks the drivers are the most up to date.

Also, could you check if you're able to reproduce the problem after [temporarily] disabling the MiniDisplay plugin?

Sure, done. Here are logs with the MiniDisplay plugin disabled, resulting in the same symptoms as before.

Cheers,

Rob.

 

[Sebastiii]

Hi,

I remember that overriding 'OnDeviceLost' when resuming avoid such D3D issue because the GPU card was not ready, but here is seems that your GPU is really not even ready after resume is done

Maybe your can try to delay it when the setting in MP.

Try to use 30 on resume and see if the GPU can be ready at that time
It seems that you can reproduce it easily so that's good for testing

 

[rmeredit]

Hi,
Maybe your can try to delay it when the setting in MP.

Try to use 30 on resume and see if the GPU can be ready at that time

Yes, I actually tried playing with that setting earlier on when trying to diagnose the problem myself, with no success. However, I tried 3 seconds, I think, rather than 30.

I just gave 30 seconds a go, though, and the same problem occurs (again, logs attached).

(I also tried checking 'Ignore Windows resolution/size changes in fullscreen mode' just in case something was going on with Windows polling my TV, changing resolution and then causing MP to fail, but that too had no effect).

Cheers,

Rob.

 

[mm1352000]

Hi Rob

Thanks for the updated log files. I've had a look, and I confess I'm currently a bit puzzled on two fronts:

1. What the cause could be.
2. How this problem could have arisen since MP 1.14.

Are you certain that the problem appeared immediately after updating to MP 1.15?

If not, aside from updating to MP 1.15, have you made any other significant changes - installed new software or hardware, updated to Windows 10, updated drivers, connected a new TV or AV receiver etc. - that might be responsible for the problem?

Would it be possible to try [temporarily] going back to MP 1.14 to check if the problem goes away?
If this would be possible, this would be my next recommendation... and I'd be very keen to see log files showing MP 1.14 resuming without problem.

Best regards,
mm

 

[rmeredit]

Are you certain that the problem appeared immediately after updating to MP 1.15?

If not, aside from updating to MP 1.15, have you made any other significant changes - installed new software or hardware, updated to Windows 10, updated drivers, connected a new TV or AV receiver etc. - that might be responsible for the problem?

Yes, absolutely certain. The problem started in August, just after installing 1.15. I've been using MP since 2007, with a hardware upgrade about 3 years ago. Other than replacing the HD with an SSD about 18 months ago, nothing has changed in the setup for a long time. I upgraded to Windows 10 at the start of the year, when I was on 1.12 I think. Certainly we've been running Windows 10 for at least several versions of MP.

The only change in config (other than upgrading to 1.15) that I can think of is automatic Windows updates. It's possible that a Windows update broke something, but the GPU driver details suggest that I'm still using the same driver that was installed when the Windows 10 upgrade happened.

We haven't added any equipment at all, not even USB devices, for a couple of years.

Would it be possible to try [temporarily] going back to MP 1.14 to check if the problem goes away?
If this would be possible, this would be my next recommendation... and I'd be very keen to see log files showing MP 1.14 resuming without problem.

Best regards,
mm

I'd be happy to give it a go, but not too sure how to go about it without destroying the setup. Is there an easy way to downgrade while maintaining all of the settings and plugins etc.?

 

[mm1352000]

Yes, absolutely certain...

Okay.

The only change in config (other than upgrading to 1.15) that I can think of is automatic Windows updates. It's possible that a Windows update broke something, but the GPU driver details suggest that I'm still using the same driver that was installed when the Windows 10 upgrade happened.

This possibility was something that crossed my mind. Unfortunately your Windows system and application event logs (which contain Windows update logging) have been cleared since August, so I can't check which updates have been installed since then. Perhaps you could find a way to do that independently?

I'd be happy to give it a go, but not too sure how to go about it without destroying the setup. Is there an easy way to downgrade while maintaining all of the settings and plugins etc.?

I don't think you can maintain the plugins, but you can definitely maintain settings and databases. As documented in the wiki, a "standard uninstall" removes the program without removing the settings and databases:
http://wiki.team-mediaportal.com/1_...stalling_MediaPortal/Uninstalling_MediaPortal

After uninstalling MP 1.15 you can reinstall MP 1.14.

Having said this, you may want to hold off after you read the info below...


The thing that is so attractive about the GPU driver explanation is that in addition to all the D3D/DirectX-related messages/errors in the MediaPortal log files, your Windows system event log shows:
"10/3/2016 8:47:05 AM";"Display";"(0)";"Warning";"Display driver igfx stopped responding and has successfully recovered.";"4101"
"10/3/2016 8:47:04 AM";"Microsoft-Windows-Power-Troubleshooter";"(0)";"Information";"The system has returned from a low power state. Sleep Time: 2016-10-02T21:46:10.655875200Z Wake Time: 2016-10-02T21:47:02.989968500Z Wake Source: 0";"1"

...and the Windows application event log shows:
"10/3/2016 8:47:21 AM";"Windows Error Reporting";"(0)";"Information";"Fault bucket LKD_0x117_Tdr:3_TdrVTR:14_IMAGE_igdkmd32.sys_GEN5.75_DX10_DISPLAY, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 57546305-c358-43ac-bbf9-9bbe24805306 Problem signature: P1: 117 P2: f9ba21c0 P3: 8fc849d0 P4: 0 P5: 1b8c P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20161003-0847.dmp \\?\C:\Users\default.HomeTheatre\AppData\Local\Temp\WER-165208171-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF367.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_a62127c09bca18d7ceb8f9a1a76b0c8529e309d_00000000_cab_08791e7e Analysis symbol: Rechecking for solution: 0 Report Id: c2324adb-88e9-11e6-85d7-20cf30906730 Report Status: 0 Hashed bucket: ";"1001"

(In earlier log files the application event log shows even more errors:
[collapse]
"10/2/2016 2:50:54 PM";"Application Error";"Application Crashing Events";"Error";"Faulting application name: LogonUI.exe, version: 10.0.14393.0, time stamp: 0x5789917a Faulting module name: Windows.UI.Xaml.dll, version: 10.0.14393.187, time stamp: 0x57cf9c3e Exception code: 0xc000027b Fault offset: 0x008b7a98 Faulting process id: 0x2238 Faulting application start time: 0x01d21c6014557a33 Faulting application path: C:\WINDOWS\system32\LogonUI.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: d6662021-fec5-4227-8ade-dfafbcaa6b0b Faulting package full name: Faulting package-relative application ID: ";"1000"
"10/2/2016 2:51:00 PM";"Windows Error Reporting";"(0)";"Information";"Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 117 P2: f9b93008 P3: 8fc849d0 P4: 0 P5: 2674 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20161002-1450.dmp \\?\C:\Users\default.HomeTheatre\AppData\Local\Temp\WER-100637062-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB0A8.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_bd452fa269c0765eef9952e6d8ac46c9983964_00000000_cab_2063b0b8 Analysis symbol: Rechecking for solution: 0 Report Id: 6acf0d1d-8853-11e6-85d7-20cf30906730 Report Status: 4 Hashed bucket: ";"1001"
"10/2/2016 2:51:02 PM";"Windows Error Reporting";"(0)";"Information";"Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: LogonUI.exe P2: 10.0.14393.0 P3: 5789917a P4: StackHash12_2bf P5: 0.0.0.0 P6: 00000000 P7: 8007000e P8: 0 P9: P10: Attached files: \\?\C:\Windows\Temp\WER9A52.tmp.appcompat.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B8C.tmp.WERInternalMetadata.xml C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_cab_04ab9ba9\memory.hdmp C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_cab_04ab9ba9\triagedump.dmp These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_cab_04ab9ba9 Analysis symbol: Rechecking for solution: 0 Report Id: d6662021-fec5-4227-8ade-dfafbcaa6b0b Report Status: 4 Hashed bucket: ";"1001"
"10/2/2016 2:51:03 PM";"Dwminit";"(0)";"Warning";"The Desktop Window Manager process has exited. (Process exit code: 0x0000042b, Restart count: 1, Primary display device ID: Intel(R) HD Graphics)";"2147614720"
"10/2/2016 2:51:03 PM";"Desktop Window Manager";"(0)";"Information";"The Desktop Window Manager has registered the session port.";"1073750851"
"10/2/2016 2:51:08 PM";"Windows Error Reporting";"(0)";"Information";"Fault bucket LKD_0x117_Tdr:3_TdrVTR:14_IMAGE_igdkmd32.sys_GEN5.75_0_DISPLAY, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: cdbbf8b8-f473-4d9c-8497-869bca1b36af Problem signature: P1: 117 P2: de1504e0 P3: 8fc849d0 P4: 0 P5: 1b14 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20161002-1444.dmp \\?\C:\Users\default.HomeTheatre\AppData\Local\Temp\WER-100224937-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER68A0.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_c9168054591465e4a352e8f2dc2219e7b159f8_00000000_cab_0127d055 Analysis symbol: Rechecking for solution: 0 Report Id: 752b8c40-8852-11e6-85d7-20cf30906730 Report Status: 0 Hashed bucket: ";"1001"
"10/2/2016 2:51:10 PM";"Windows Error Reporting";"(0)";"Information";"Fault bucket 108401657857, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: LogonUI.exe P2: 10.0.14393.0 P3: 5789917a P4: StackHash12_2bf P5: 0.0.0.0 P6: 00000000 P7: 8007000e P8: 0 P9: P10: Attached files: \\?\C:\Windows\Temp\WER9A52.tmp.appcompat.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B8C.tmp.WERInternalMetadata.xml C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_cab_04ab9ba9\memory.hdmp C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_cab_04ab9ba9\triagedump.dmp These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_0127d71c Analysis symbol: Rechecking for solution: 0 Report Id: d6662021-fec5-4227-8ade-dfafbcaa6b0b Report Status: 0 Hashed bucket: 704281f1ca13f7a271922de1ba37194e";"1001"
"10/2/2016 2:51:15 PM";"Windows Error Reporting";"(0)";"Information";"Fault bucket LKD_0x117_Tdr:3_TdrVTR:14_IMAGE_igdkmd32.sys_GEN5.75_0_DISPLAY, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: e53f31b1-86ad-4f44-aa0d-a53d12a25dbd Problem signature: P1: 117 P2: f9b93008 P3: 8fc849d0 P4: 0 P5: 2674 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20161002-1450.dmp \\?\C:\Users\default.HomeTheatre\AppData\Local\Temp\WER-100637062-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB0A8.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_bd452fa269c0765eef9952e6d8ac46c9983964_00000000_cab_0127eb40 Analysis symbol: Rechecking for solution: 0 Report Id: 6acf0d1d-8853-11e6-85d7-20cf30906730 Report Status: 0 Hashed bucket: ";"1001"[/collapse]

These references to "ig..." are references to components of the Intel Graphics/GPU driver and associated software.

Of course the ultimate question is: do the Intel GPU error precede (and therefore presumably trigger) the MediaPortal problems, or is it the other way around?
I can't answer that with absolute certainty, but it sure looks like the answer is yes [the GPU driver errors are prior and cause the subsequent problems].


P.S. Interestingly, your Windows system event log also shows:
"10/3/2016 8:47:01 AM";"Microsoft-Windows-Kernel-General";"(5)";"Information";"Possible detection of CVE: 2016-10-02T21:47:01.500000000Z Additional Information: 2016-10-02T21:46:12.707306500Z This Event is generated when an attempt to exploit a known vulnerability (2016-10-02T21:47:01.500000000Z) is detected. This Event is raised by a User mode process. ";"1"

...right around the time that the system resumes from hibernate. Exploitation of a vulnerability sure doesn't sound good. I have no idea what to make of this message as it's the first time I've ever seen it, and official MP releases would never knowingly attempt to exploit security holes.