MePo Crashing (1 Viewer)

[Sepulchre]

Hi,

This evening MePo has crashed twice, each time live TV picture and sound stops and I'm left with a black screen. Eventually I get back to the widows desktop which appears but is unresponsive and then goes to a black screen for several seconds before appearing again but remains unresponsive. My only solution has been a re-boot.

Any advice on this is really appreciated!

Logs (i hope the correct ones) are attached.

Thanks

Seppy

 

[mm1352000]

Hello

Logs (i hope the correct ones) are attached.

Yep, they're good - thanks.

I think this is the first crash:
[collapse]
"28/02/2015 17:29:13";".NET Runtime";"(0)";"Error";"Application: MediaPortal.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 08728CC8
";"1026"
"28/02/2015 17:29:13";"Desktop Window Manager";"(0)";"Information";"A request to disable the Desktop Window Manager was made by process (4)";"1073750834"
"28/02/2015 17:29:17";"Desktop Window Manager";"(0)";"Information";"The Desktop Window Manager was unable to start because composition was disabled by a running application";"1073750837"
"28/02/2015 17:29:21";"Windows Error Reporting";"(0)";"Information";"Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\LiveKernelReports\WATCHDOG\WD-20150228-1729.dmp C:\Windows\Temp\WER-268632765-0.sysdata.xml C:\Windows\Temp\WER33A.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_2aeb034a Analysis symbol: Rechecking for solution: 0 Report Id: 546f0e4b-bf6f-11e4-909b-00012e2c9b80 Report Status: 4";"1001"
"28/02/2015 17:29:34";"Application Error";"Application Crashing Events";"Error";"Faulting application name: MediaPortal.exe, version: 1.10.0.0, time stamp: 0x548c1054 Faulting module name: igdumd32.dll, version: 8.15.10.2622, time stamp: 0x4f0cb935 Exception code: 0xc0000005 Fault offset: 0x000c8cc8 Faulting process id: 0x3580 Faulting application start time: 0x01d0537b7c353e8e Faulting application path: C:\Program Files (x86)\Team MediaPortal\MediaPortal\MediaPortal.exe Faulting module path: C:\Windows\system32\igdumd32.dll Report Id: 5bd3348d-bf6f-11e4-909b-00012e2c9b80";"1000"
"28/02/2015 17:29:41";"Windows Error Reporting";"(0)";"Information";"Fault bucket 876182538, type 17 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: MediaPortal.exe P2: 1.10.0.0 P3: 548c1054 P4: igdumd32.dll P5: 8.15.10.2622 P6: 4f0cb935 P7: c0000005 P8: 000c8cc8 P9: P10: Attached files: C:\Users\Media PC\AppData\Local\Temp\WER33C0.tmp.WERInternalMetadata.xml These files may be available here: C:\Users\Media PC\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_MediaPortal.exe_5a86d450356793d5216aad892157b5eb7f925b25_282f4f08 Analysis symbol: Rechecking for solution: 0 Report Id: 5bd3348d-bf6f-11e4-909b-00012e2c9b80 Report Status: 0";"1001"[/collapse]

Note the references to igdumd32.dll. That means that your Intel graphics driver caused MP to crash. The only suggestion I can offer for that is to ensure you're using the latest version of the driver for your hardware.

A few minutes later we have what I think is the second crash:
[collapse]
"28/02/2015 17:33:28";".NET Runtime";"(0)";"Error";"Application: MediaPortal.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at <Module>.D3DXCreateTextureFromFileExW(Microsoft.DirectX.PrivateImplementationDetails.IDirect3DDevice9*, UInt16*, UInt32, UInt32, UInt32, UInt32, Int32, Int32, UInt32, UInt32, UInt32, Microsoft.DirectX.PrivateImplementationDetails._D3DXIMAGE_INFO*, Microsoft.DirectX.PrivateImplementationDetails.tagPALETTEENTRY*, Microsoft.DirectX.PrivateImplementationDetails.IDirect3DTexture9**)
at Microsoft.DirectX.Direct3D.TextureLoader.FromFile(Microsoft.DirectX.Direct3D.Device, System.String, Int32, Int32, Int32, Microsoft.DirectX.Direct3D.Usage, Microsoft.DirectX.Direct3D.Format, Microsoft.DirectX.Direct3D.Pool, Microsoft.DirectX.Direct3D.Filter, Microsoft.DirectX.Direct3D.Filter, Int32, Microsoft.DirectX.Direct3D.ImageInformation ByRef, Microsoft.DirectX.Direct3D.PaletteEntry[] ByRef)
at Microsoft.DirectX.Direct3D.TextureLoader.FromFile(Microsoft.DirectX.Direct3D.Device, System.String, Int32, Int32, Int32, Microsoft.DirectX.Direct3D.Usage, Microsoft.DirectX.Direct3D.Format, Microsoft.DirectX.Direct3D.Pool, Microsoft.DirectX.Direct3D.Filter, Microsoft.DirectX.Direct3D.Filter, Int32, Microsoft.DirectX.Direct3D.ImageInformation ByRef)
at MediaPortal.GUI.Library.TexturePacker.LoadPackedGraphics(Int32)
at MediaPortal.GUI.Library.TexturePacker.Get(System.String, Single ByRef, Single ByRef, Single ByRef, Single ByRef, Int32 ByRef, Int32 ByRef, Microsoft.DirectX.Direct3D.Texture ByRef, Int32 ByRef)
at MediaPortal.GUI.Library.GUIImage.AllocResources()
at MediaPortal.GUI.Library.GUIWindow.AllocResources()
at MediaPortal.GUI.Library.GUIWindow.Load(System.String)
at Common.GUIPlugins.GUIMixerOverlay.Init()
at MediaPortal.GUI.Library.PluginManager.LoadWindowPlugin(System.String)
at MediaPortal.GUI.Library.PluginManager.LoadWindowPluginsNonThreaded()
at MediaPortalApp.InitializeDeviceObjects()
at MediaPortal.D3D.InitializeDevice()
at MediaPortal.D3D.Init()
at MediaPortalApp.Main(System.String[])
";"1026"[/collapse]

This is connected with graphics again... but I'm not able to point to a cause or solution.

Regards,
mm

 

[Sepulchre]

Thanks mm, this happened last week, I came to the same conclusion as you and checked the driver. Windows update tells me it's the latest version, I will check with the manufacturer also. If it is the latest version then I'm at a total loss as to what I can do to resolve this

Update - Windows update is telling some huge porkies here. Driver is dated 10/1/2012 and appears to have had many many updates. Updating now. from version 8.15.10.2622 to 15.22.58.64.2993!!

I will report back how this turns out.

 

[Sepulchre]

update, lasted two hours before hitting the same issue, I cant find anything in the logs about this though...

I'm going to try uninstalling the driver and loading again from fresh