home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
MP 1.12.0 TV crashes
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1216342" data-attributes="member: 82144"><p>Hello again Mike</p><p></p><p></p><p>A tip then... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p>The first place to look for the cause of a crash <strong>for any program</strong> is the Windows application event log. We look at the faulting module name to find the source of the crash and the exception code to understand the reason for the crash.</p><p></p><p>In this case we find...</p><p>"Yesterday"?</p><p>[collapse]</p><p>"3/25/2017 5:13:36 PM";"Application Error";"Application Crashing Events";"Error";"Faulting application name: MediaPortal.exe, version: 1.12.0.0, time stamp: 0x55885126 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x190fd090 Faulting process id: 0x2ea8 Faulting application start time: 0x01d2a569d4d7de00 Faulting application path: C:\Program Files (x86)\Team MediaPortal\MediaPortal\MediaPortal.exe Faulting module path: unknown Report Id: 9d2cbe97-e08c-40c7-b878-ea0a64a2b104 Faulting package full name: Faulting package-relative application ID: ";"1000"</p><p>"3/25/2017 5:13:43 PM";"Windows Error Reporting";"(0)";"Information";"Fault bucket 50, type 5 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: MediaPortal.exe P2: 1.12.0.0 P3: 55885126 P4: StackHash_2beb P5: 0.0.0.0 P6: 00000000 P7: PCH_53_FROM_ntdll+0x0006EB8C P8: c0000005 P9: 00000008 P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9700.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MediaPortal.exe_b1c1621bfc88fe8b6289ab9d9df7464688dfa1c6_af1dee06_3703ad19 Analysis symbol: Rechecking for solution: 0 Report Id: 9d2cbe97-e08c-40c7-b878-ea0a64a2b104 Report Status: 0 Hashed bucket: 0739e94433274bfb21722a7eff424e18";"1001"[/collapse]</p><p></p><p>"Last night"?</p><p>[collapse]</p><p>"3/26/2017 12:00:10 AM";"Application Error";"Application Crashing Events";"Error";"Faulting application name: MediaPortal.exe, version: 1.12.0.0, time stamp: 0x55885126 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x19d6d090 Faulting process id: 0x2be4 Faulting application start time: 0x01d2a5dbcf134a84 Faulting application path: C:\Program Files (x86)\Team MediaPortal\MediaPortal\MediaPortal.exe Faulting module path: unknown Report Id: a6f62ef0-ff2d-4c1e-b6e8-0edad70e0b28 Faulting package full name: Faulting package-relative application ID: ";"1000"</p><p>"3/26/2017 12:00:15 AM";"Windows Error Reporting";"(0)";"Information";"Fault bucket 116354609672, type 5 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: MediaPortal.exe P2: 1.12.0.0 P3: 55885126 P4: StackHash_2beb P5: 0.0.0.0 P6: 00000000 P7: PCH_53_FROM_ntdll+0x0006EB8C P8: c0000005 P9: 00000008 P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCD03.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MediaPortal.exe_b1c1621bfc88fe8b6289ab9d9df7464688dfa1c6_af1dee06_3cafdfef Analysis symbol: Rechecking for solution: 0 Report Id: a6f62ef0-ff2d-4c1e-b6e8-0edad70e0b28 Report Status: 0 Hashed bucket: 0739e94433274bfb21722a7eff424e18";"1001"[/collapse]</p><p></p><p>Unfortunately the faulting module name is "unknown". This really isn't helpful. Usually we get a specific DLL name.</p><p>The exception code (0xc0000005) means an access violation exception. In short: the faulting module caused the crash by trying to access a part of the computer memory that it wasn't meant to (eg. the memory allocated to the OS or another program).</p><p></p><p>When the module name is unknown we look at the context (ie. MediaPortal logs) and other crashes (which may have the actual module name) to try to get a better understanding. Having done that, I'm suspicious that the crash is still related to codecs. In particular I notice:</p><p></p><p>1. That although you've configured MediaPortal to use the LAV video codec, MediaPortal actually seems to be using other codecs:</p><p>[2017-03-25 22:51:30,622] [114d3440] [3118] - vidPin:CompleteConnect() ok, filter: ffdshow Video Decoder</p><p>[2017-03-25 22:51:30,934] [114d3440] [3118] - vidPin:CompleteConnect() ok, filter: CoreAVC Video Decoder</p><p>[2017-03-25 22:51:31,178] [114d3440] [3118] - vidPin:CompleteConnect() ok, filter: ArcSoft Video Decoder</p><p>[2017-03-25 22:51:31,464] [114d3440] [3118] - vidPin:CompleteConnect() ok, filter: Microsoft DTV-DVD Video Decoder</p><p></p><p>2. An older crash which references a codec:</p><p>[collapse]</p><p>"3/25/2017 9:13:47 AM";"Application Error";"Application Crashing Events";"Error";"Faulting application name: MediaPortal.exe, version: 1.12.0.0, time stamp: 0x55885126 Faulting module name: Mpeg2DecFilter.ax_unloaded, version: 1.0.0.4, time stamp: 0x46efe15a Exception code: 0xc0000005 Fault offset: 0x0001d090 Faulting process id: 0x2bc4 Faulting application start time: 0x01d2a565d4895c43 Faulting application path: C:\Program Files (x86)\Team MediaPortal\MediaPortal\MediaPortal.exe Faulting module path: Mpeg2DecFilter.ax Report Id: 882f4383-6840-4da8-98c4-463795f228f8 Faulting package full name: Faulting package-relative application ID: ";"1000"</p><p>"3/25/2017 9:14:21 AM";"Windows Error Reporting";"(0)";"Information";"Fault bucket 50, type 5 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: MediaPortal.exe P2: 1.12.0.0 P3: 55885126 P4: Mpeg2DecFilter.ax_unloaded P5: 1.0.0.4 P6: 46efe15a P7: 0001d090 P8: c0000005 P9: 00000008 P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4CEF.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MediaPortal.exe_d7683779fa2eb4f6fd3dc6a334507ca3f7b3df_af1dee06_2124cfea Analysis symbol: Rechecking for solution: 0 Report Id: 882f4383-6840-4da8-98c4-463795f228f8 Report Status: 0 Hashed bucket: b9b03bf5478f7570192a3b1a10ed34f6";"1001"[/collapse]</p><p></p><p>Mpeg2DecFilter.ax = MPEG Video Decoder (Gabest)</p><p>That's an extremely old codec now. No longer maintained as far as I know. Wouldn't advise using it.</p><p></p><p>So the question for me is: why is MediaPortal not using LAV as configured.</p><p></p><p>Can you please:</p><ol> <li data-xf-list-type="ol">Supply a screenshot of the LAV video codec settings.</li> <li data-xf-list-type="ol">Supply fresh log files:<ol> <li data-xf-list-type="ol">Start MP with Watchdog option 1 ("report a bug...").</li> <li data-xf-list-type="ol">Play any TV channel for 30 seconds.</li> <li data-xf-list-type="ol">Close MP.</li> <li data-xf-list-type="ol">Attach the resulting zip file.</li> </ol></li> </ol><p>Thanks. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p></blockquote><p></p>
[QUOTE="mm1352000, post: 1216342, member: 82144"] Hello again Mike A tip then... :) The first place to look for the cause of a crash [B]for any program[/B] is the Windows application event log. We look at the faulting module name to find the source of the crash and the exception code to understand the reason for the crash. In this case we find... "Yesterday"? [collapse] "3/25/2017 5:13:36 PM";"Application Error";"Application Crashing Events";"Error";"Faulting application name: MediaPortal.exe, version: 1.12.0.0, time stamp: 0x55885126 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x190fd090 Faulting process id: 0x2ea8 Faulting application start time: 0x01d2a569d4d7de00 Faulting application path: C:\Program Files (x86)\Team MediaPortal\MediaPortal\MediaPortal.exe Faulting module path: unknown Report Id: 9d2cbe97-e08c-40c7-b878-ea0a64a2b104 Faulting package full name: Faulting package-relative application ID: ";"1000" "3/25/2017 5:13:43 PM";"Windows Error Reporting";"(0)";"Information";"Fault bucket 50, type 5 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: MediaPortal.exe P2: 1.12.0.0 P3: 55885126 P4: StackHash_2beb P5: 0.0.0.0 P6: 00000000 P7: PCH_53_FROM_ntdll+0x0006EB8C P8: c0000005 P9: 00000008 P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9700.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MediaPortal.exe_b1c1621bfc88fe8b6289ab9d9df7464688dfa1c6_af1dee06_3703ad19 Analysis symbol: Rechecking for solution: 0 Report Id: 9d2cbe97-e08c-40c7-b878-ea0a64a2b104 Report Status: 0 Hashed bucket: 0739e94433274bfb21722a7eff424e18";"1001"[/collapse] "Last night"? [collapse] "3/26/2017 12:00:10 AM";"Application Error";"Application Crashing Events";"Error";"Faulting application name: MediaPortal.exe, version: 1.12.0.0, time stamp: 0x55885126 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x19d6d090 Faulting process id: 0x2be4 Faulting application start time: 0x01d2a5dbcf134a84 Faulting application path: C:\Program Files (x86)\Team MediaPortal\MediaPortal\MediaPortal.exe Faulting module path: unknown Report Id: a6f62ef0-ff2d-4c1e-b6e8-0edad70e0b28 Faulting package full name: Faulting package-relative application ID: ";"1000" "3/26/2017 12:00:15 AM";"Windows Error Reporting";"(0)";"Information";"Fault bucket 116354609672, type 5 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: MediaPortal.exe P2: 1.12.0.0 P3: 55885126 P4: StackHash_2beb P5: 0.0.0.0 P6: 00000000 P7: PCH_53_FROM_ntdll+0x0006EB8C P8: c0000005 P9: 00000008 P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCD03.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MediaPortal.exe_b1c1621bfc88fe8b6289ab9d9df7464688dfa1c6_af1dee06_3cafdfef Analysis symbol: Rechecking for solution: 0 Report Id: a6f62ef0-ff2d-4c1e-b6e8-0edad70e0b28 Report Status: 0 Hashed bucket: 0739e94433274bfb21722a7eff424e18";"1001"[/collapse] Unfortunately the faulting module name is "unknown". This really isn't helpful. Usually we get a specific DLL name. The exception code (0xc0000005) means an access violation exception. In short: the faulting module caused the crash by trying to access a part of the computer memory that it wasn't meant to (eg. the memory allocated to the OS or another program). When the module name is unknown we look at the context (ie. MediaPortal logs) and other crashes (which may have the actual module name) to try to get a better understanding. Having done that, I'm suspicious that the crash is still related to codecs. In particular I notice: 1. That although you've configured MediaPortal to use the LAV video codec, MediaPortal actually seems to be using other codecs: [2017-03-25 22:51:30,622] [114d3440] [3118] - vidPin:CompleteConnect() ok, filter: ffdshow Video Decoder [2017-03-25 22:51:30,934] [114d3440] [3118] - vidPin:CompleteConnect() ok, filter: CoreAVC Video Decoder [2017-03-25 22:51:31,178] [114d3440] [3118] - vidPin:CompleteConnect() ok, filter: ArcSoft Video Decoder [2017-03-25 22:51:31,464] [114d3440] [3118] - vidPin:CompleteConnect() ok, filter: Microsoft DTV-DVD Video Decoder 2. An older crash which references a codec: [collapse] "3/25/2017 9:13:47 AM";"Application Error";"Application Crashing Events";"Error";"Faulting application name: MediaPortal.exe, version: 1.12.0.0, time stamp: 0x55885126 Faulting module name: Mpeg2DecFilter.ax_unloaded, version: 1.0.0.4, time stamp: 0x46efe15a Exception code: 0xc0000005 Fault offset: 0x0001d090 Faulting process id: 0x2bc4 Faulting application start time: 0x01d2a565d4895c43 Faulting application path: C:\Program Files (x86)\Team MediaPortal\MediaPortal\MediaPortal.exe Faulting module path: Mpeg2DecFilter.ax Report Id: 882f4383-6840-4da8-98c4-463795f228f8 Faulting package full name: Faulting package-relative application ID: ";"1000" "3/25/2017 9:14:21 AM";"Windows Error Reporting";"(0)";"Information";"Fault bucket 50, type 5 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: MediaPortal.exe P2: 1.12.0.0 P3: 55885126 P4: Mpeg2DecFilter.ax_unloaded P5: 1.0.0.4 P6: 46efe15a P7: 0001d090 P8: c0000005 P9: 00000008 P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4CEF.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MediaPortal.exe_d7683779fa2eb4f6fd3dc6a334507ca3f7b3df_af1dee06_2124cfea Analysis symbol: Rechecking for solution: 0 Report Id: 882f4383-6840-4da8-98c4-463795f228f8 Report Status: 0 Hashed bucket: b9b03bf5478f7570192a3b1a10ed34f6";"1001"[/collapse] Mpeg2DecFilter.ax = MPEG Video Decoder (Gabest) That's an extremely old codec now. No longer maintained as far as I know. Wouldn't advise using it. So the question for me is: why is MediaPortal not using LAV as configured. Can you please: [LIST=1] [*]Supply a screenshot of the LAV video codec settings. [*]Supply fresh log files: [LIST=1] [*]Start MP with Watchdog option 1 ("report a bug..."). [*]Play any TV channel for 30 seconds. [*]Close MP. [*]Attach the resulting zip file. [/LIST] [/LIST] Thanks. :) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
MP 1.12.0 TV crashes
Contact us
RSS
Top
Bottom
