[further infos missing] D3DERR_INVALIDCALL (2 Viewers)

[morpheus_xx]

I am currently checking how to recover from this kind of D3D exceptions...

 

[akayani]

If I was testing this, I'd suggest 2 monitors with one set at a below HD resolution. If you think you need a video to see what I'm talking about let me know. It was post a Windows update 2 weeks ago that the problem started.

It 'feels like' an MS update interacting with an old library that needs a code update. I don't see any reason in particular to look at MP2 code as it was all just fine until the MS update. And it is of course fine as long as you don't go full screen without chrome.

Yani

 

[morpheus_xx]

@akayani can you please try the attached patch?

Please extract the dll into C:\Program Files (x86)\Team MediaPortal\MP2-Client\Plugins\SkinEngine folder (take backup of existing file before!). And then try to reproduce the issue.

I changed the exception handling so that the devices gets reset.

 

[Lehmden]

Hi.
Tried it and it looks as if the client is much more stable with this dll.

One small thing I noticed nevertheless

[2018-02-10 22:56:34,404] [14046314] [AMQ 'ScreenManager'] [WARN ] - Name '' was registered twice in namescope 'MediaPortal.UI.SkinEngine.Xaml.NameScope'
[2018-02-10 22:56:34,405] [14046315] [AMQ 'ScreenManager'] [WARN ] - Name '' was registered twice in namescope 'MediaPortal.UI.SkinEngine.Xaml.NameScope'

This only is a warning, no error but it should be fixed if possible imho.

 

[akayani]

Sure boss, I try the patch tonight.

I just did some more testing. I have no issues on the HD or UHD monitor. Works perfectly. The issue happens on the 1360X768 TV.

 

[akayani]

NUP! Sorry about that.


Log Name: Application
Source: Application Error
Date: 14/02/2018 11:01:04 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Maud-64
Description:
Faulting application name: MP2-Client.exe, version: 2.1.1712.10518, time stamp: 0x5a3969a1
Faulting module name: KERNELBASE.dll, version: 10.0.16299.15, time stamp: 0x2cd1ce3d
Exception code: 0xe0434352
Fault offset: 0x001008b2
Faulting process ID: 0x3ee0
Faulting application start time: 0x01d3a52f1f92bade
Faulting application path: C:\Program Files (x86)\Team MediaPortal\MP2-Client\MP2-Client.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 627c6f1f-bce0-4ba3-b0dc-cb0d51bd33e0
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-02-14T01:01:04.247810400Z" />
<EventRecordID>10270</EventRecordID>
<Channel>Application</Channel>
<Computer>Maud-64</Computer>
<Security />
</System>
<EventData>
<Data>MP2-Client.exe</Data>
<Data>2.1.1712.10518</Data>
<Data>5a3969a1</Data>
<Data>KERNELBASE.dll</Data>
<Data>10.0.16299.15</Data>
<Data>2cd1ce3d</Data>
<Data>e0434352</Data>
<Data>001008b2</Data>
<Data>3ee0</Data>
<Data>01d3a52f1f92bade</Data>
<Data>C:\Program Files (x86)\Team MediaPortal\MP2-Client\MP2-Client.exe</Data>
<Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
<Data>627c6f1f-bce0-4ba3-b0dc-cb0d51bd33e0</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
Log Name: Application
Source: .NET Runtime
Date: 14/02/2018 11:01:03 AM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Maud-64
Description:
Application: MP2-Client.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: SharpDX.SharpDXException
at System.Windows.Forms.Control.MarshaledInvoke(System.Windows.Forms.Control, System.Delegate, System.Object[], Boolean)
at System.Windows.Forms.Control.Invoke(System.Delegate, System.Object[])
at System.Windows.Forms.Control.Invoke(System.Delegate)
at MediaPortal.UI.SkinEngine.DirectX.GraphicsDevice.ExecuteInMainThread(MediaPortal.UI.SkinEngine.DirectX.WorkDlgt)
at MediaPortal.UI.SkinEngine.DirectX.GraphicsDevice+<>c.<Reset>b__68_0()
at MediaPortal.UI.SkinEngine.ScreenManagement.ScreenManager.ExecuteWithTempReleasedResources(System.Action)
at MediaPortal.UI.SkinEngine.DirectX.GraphicsDevice.Reset()
at MediaPortal.UI.SkinEngine.DirectX.GraphicsDevice.Render(Boolean)
at MediaPortal.UI.SkinEngine.GUI.MainForm.RenderLoop()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()


Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-02-14T01:01:03.920221000Z" />
<EventRecordID>10268</EventRecordID>
<Channel>Application</Channel>
<Computer>Maud-64</Computer>
<Security />
</System>

<EventData>
<Data>Application: MP2-Client.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: SharpDX.SharpDXException
at System.Windows.Forms.Control.MarshaledInvoke(System.Windows.Forms.Control, System.Delegate, System.Object[], Boolean)
at System.Windows.Forms.Control.Invoke(System.Delegate, System.Object[])
at System.Windows.Forms.Control.Invoke(System.Delegate)
at MediaPortal.UI.SkinEngine.DirectX.GraphicsDevice.ExecuteInMainThread(MediaPortal.UI.SkinEngine.DirectX.WorkDlgt)
at MediaPortal.UI.SkinEngine.DirectX.GraphicsDevice+&lt;&gt;c.&lt;Reset&gt;b__68_0()
at MediaPortal.UI.SkinEngine.ScreenManagement.ScreenManager.ExecuteWithTempReleasedResources(System.Action)
at MediaPortal.UI.SkinEngine.DirectX.GraphicsDevice.Reset()
at MediaPortal.UI.SkinEngine.DirectX.GraphicsDevice.Render(Boolean)
at MediaPortal.UI.SkinEngine.GUI.MainForm.RenderLoop()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

</Data>
</EventData>
</Event>

Here's the error in Event Viewer as it farts the screen until the display driver gives up.

I keep everything uptodate but for the sake of being sure I'll load the latest video driver.

 

[morpheus_xx]

@akayani can you please try again with attached version 2 on the problematic system?
No real code change, but catching exceptions. This probably will not work at all, because the DX device needs to be initialized again...

 

[akayani]

The only difference I see is less error reporting. I was hoping to be able to say that it was only when videos were played that the error occurs but the interface alone will trigger the error. I'm 99% sure that this was caused by an update from Microsoft. Hence why I suspect it is between a library and that update.

Is there a way to list what files MS has updated?

 

[akayani]

NsAppName=MP2-Client.exe
AppSessionGuid=00003ee0-0001-0015-deba-921f2fa5d301
TargetAppId=W:00069db8b72f1116f54f31e7110ab532479500000000!0000bad073e6becd266252e4b78245570e1f22c71df1!MP2-Client.exe
TargetAppVer=2017//12//19:19:33:53!0!MP2-Client.exe
BootId=4294967295
ServiceSplit=1401238585
TargetAsId=1247
Response.BucketId=2dc4bfbb3fdcee0e477d6915447c767e
Response.BucketTable=5
Response.LegacyBucketId=1692624575025411710
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=MP2-Client.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=2.1.1712.10518
Sig[2].Name=Problem Signature 03
Sig[2].Value=5a3969a1
Sig[3].Name=Problem Signature 04
Sig[3].Value=SharpDX
Sig[4].Name=Problem Signature 05
Sig[4].Value=2.6.3.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=5450f8ae
Sig[6].Name=Problem Signature 07
Sig[6].Value=a4d
Sig[7].Name=Problem Signature 08
Sig[7].Value=14
Sig[8].Name=Problem Signature 09
Sig[8].Value=SharpDX.SharpDXException

Does that ring any bells?

 

[HTPCSourcer]

@akayani can you please try the attached patch?
[snip]
I changed the exception handling so that the devices gets reset.

Tried it and it looks as if the client is much more stable with this dll.

Was this included in 2.2pre? If not, how do we proceed from here as neither @gibman nor @akayani have contributed for some time.