MP 1.12.0 TV crashes (1 Viewer)

[neurosis]

Hello,

Thank you Team for an excellent product. It truly is great to have my IPTV->Colossus running through my Win10 PC as a great HTPC.

My system has been very stable (MP 1.12.0) until about a month ago when it started crashing MP every time I closed a TV viewing session. Just last week it got worse, I can no longer open the TV stream at all (or play any videos or access the TV config panel from within MP) without it crashing MP immediately. My WAF is way low at the moment!

So before I go posting logs (as best I can) and asking questions about fixes, should I simply try upgrading to MP 1.15. first? Please help.

Mike

P.S. I see there have been 3 or 4 Windows updates in the last month, so I may try unistalling those as a possible fix.

 

[mm1352000]

Hi Mike

So before I go posting logs (as best I can)...

It really helps us if you could make this the first thing you do every time you ask for help. Without log files, we're guessing blind.

With that said, in this case I suspect you have the same problem as discussed here:
1.16 Pre Rel. crashes after w10 update

In short: a Windows update broke Microsoft's codecs. Any software that tries to use them will crash.
Microsoft provided a fix for the original update:
1.16 Pre Rel. crashes after w10 update

If my guess is correct, installing that fix will solve your problems.
If not, you'll have to provide log files. Please use the provided Watchdog tool with option 1 ("report a bug..."). It makes gathering logs trivial.

 

[neurosis]

Wow, you're reply was very fast! Thank you. In the meantime I uninstalled a couple of Windows updates and the problem is fixed. So yes, I'm sure your solution would work, too. Now do I reinstall the updates and the fix or stay on the old ones? hmmm.

 

[neurosis]

Ok, so my 1.12.0 system still crashes occasionally. It crashed yesterday after the TV had been on for an hour or so (maybe the screen saver tried to interfere?), and last night it crashed when trying to close it. The logs from last night are attached. I wish I knew how to read them...any help is much appreciated. Fortunately, this crashing is just an annoyance and the system is still usable.

Mike

 

[mm1352000]

Hello again Mike

I wish I knew how to read them...

A tip then...
The first place to look for the cause of a crash for any program 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:

1. Supply a screenshot of the LAV video codec settings.
2. Supply fresh log files:
   1. Start MP with Watchdog option 1 ("report a bug...").
   2. Play any TV channel for 30 seconds.
   3. Close MP.
   4. Attach the resulting zip file.

Thanks.

 

[neurosis]

OK, so I did as you asked. I didn't attach the logs though, because after taking the snapshot and being asked to save the setting, I saved them and the crashing stopped! I couldn't repeat the crash even after multiple opens and closings of the TV. Thank you!

Uh, oh! Spoke too soon. Just as I was typing this message the TV crashed mid-stream. Watchdog would not let me pick option 1, it was grayed out. Attached is the comprehensive log.

Mike
P.S. Screenshot is attached.

 

[mm1352000]

Mike, a handful of points:

1. The crash symptoms seem to be identical to before.
2. You're using an older version of LAV. Any particular reason for that? If not, I'd advise to update to the latest.
   
3. The screenshot only shows the first tab of the LAV settings. Please can you provide another screenshot showing the second tab. I'm particularly interested to see any formats/codecs that are not ticked (enabled).
   
4. This looks like an external problem. Nevertheless, any chance of updating to MP 1.15 or 1.16 PR just to rule out the possibility that it's caused by a bug that's already been fixed?

...and finally:

Watchdog would not let me pick option 1, it was grayed out.

I suspect that happens when MediaPortal is already running. Try closing MP first, then following the previous procedure to collect new log files. The debug-level detail (which is missing from the logs you've just provided) is really needed.

 

[mm1352000]

Oh, one more thing: the screenshot of MP Config is showing the video codecs tab. Those settings aren't used for TV. Please take a screenshot of the TV codecs tab.

 

[mm1352000]

Argh, another thing....
I think I may have guessed the reason that MP is not using the LAV video codec: a dependency (eg. a certain version of Visual C++ redistributable) is missing.
Dependency Walker can help to figure out which dependencies are missing... or alternatively, I think updating to the latest version should ensure the dependencies are installed.

 

[neurosis]

I am still unable to get MP watchdog to write a file using Option 1, report a bug. If I make sure MP is closed then open it, it doesn't give me the option. Every time I crash it, it doesn't let me select anything but option 3. I will go ahead and install the latest LAV decoders and let you know if that fixes the problem. If it doesn't, I will probably update to the latest version, as you also suggested. More soon...THANK YOU!