MediaPortal crashes with TV playback & Live TV (1 Viewer)

[Dark Eyes]

Hello folks,

I was wondering if somebody could enlighten me as to why MP is crashing every time I try and playback a recorded TV programme or watch live TV. It just suddenly seems to be happening, and I'm not aware of anything changing. All codec settings are LAV (v66 is installed) expect the Audio Renderer which is MP's. I have attached the watchdog logs, the hope that it helps diagnose the problem.
Is it a TsReader issue ?

 

[mm1352000]

expect the Audio Renderer which is MP's.

Please switch to one of the DirectSound options. MPAR doesn't always work well with TV streams. I'm not sure if it's causing the crash, but it could be.

 

[Dark Eyes]

Okay, I have switched to Default Direct Sound Device, and it now plays the TV recordings, but only for a few seconds before it crashes MP as before; the logs are attached.
What is strange is that it was working before with MPAR, but recently I have noticed that when I started playback , it played the audio from the start, but the video took a good few seconds before it was shown.
Now it crashes on startup, or soon after. I don't know if that helps you...

 

[mm1352000]

No, it doesn't really help. The crash log entry in the Windows application event log is the same:
[collapse]
"11/02/2016 00:39:07";".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 E8580045
";"1026"
"11/02/2016 00:39:08";"Application Error";"Application Crashing Events";"Error";"Faulting application name: MediaPortal.exe, version: 1.7.1.0, time stamp: 0x535b90f2 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0xe8580045 Faulting process id: 0x668 Faulting application start time: 0x01d164635e853edf Faulting application path: C:\Program Files (x86)\Team MediaPortal\MediaPortal\MediaPortal.exe Faulting module path: unknown Report Id: dc18d901-d057-11e5-a2a7-bcaec51afc40";"1000"
"11/02/2016 00:39:22";"Windows Error Reporting";"(0)";"Information";"Fault bucket 51689338, type 19 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: MediaPortal.exe P2: 1.7.1.0 P3: 535b90f2 P4: StackHash_0a9e P5: 0.0.0.0 P6: 00000000 P7: e8580045 P8: c0000005 P9: 00000008 P10: Attached files: C:\Users\MediaCentre64\AppData\Local\Temp\WER7A2A.tmp.WERInternalMetadata.xml These files may be available here: C:\Users\MediaCentre64\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_MediaPortal.exe_65a21a60e18c40ce446fcbc0885db77520bd132a_1003aed0 Analysis symbol: Rechecking for solution: 0 Report Id: dc18d901-d057-11e5-a2a7-bcaec51afc40 Report Status: 0";"1001"[/collapse]

Exception code c0000005 means an access violation occurred. It's a very generic sort of error which can be triggered by buggy software or unstable hardware.

I wonder if the problem is that your system HDD (c: drive) hasn't got enough free space. The log file is telling me:
[collapse]
Drive: C:
Free Space: 0.2 GB
Total Space: 61.4 GB
File System: NTFS
Model: ST2000DL004 HD204UI ATA Device

Drive: E:
Free Space: 1.0 GB
Total Space: 1907.7 GB
File System: NTFS
Model: SAMSUNG HD204UI ATA Device

Drive: F:
Free Space: 0.3 GB
Total Space: 1907.7 GB
File System: NTFS
Model: SAMSUNG HD204UI ATA Device

Drive: G:
Free Space: 0.1 GB
Total Space: 1907.7 GB
File System: NTFS
Model: SAMSUNG HD204UI ATA Device

Drive: I:
Free Space: 5.3 GB
Total Space: 1857.7 GB
File System: NTFS
Model: SAMSUNG HD204UI ATA Device

Drive: J:
Free Space: 1529.6 GB
Total Space: 1907.7 GB
File System: NTFS
Model: WDC WD20EZRZ-00Z5HB0 ATA Device

Drive: K:
Free Space: 0.7 GB
Total Space: 1846.2 GB
File System: NTFS
Model: ST2000DL004 HD204UI ATA Device

Drive: L:
Free Space: 35.8 GB
Total Space: 49.9 GB
File System: NTFS
Model: SAMSUNG HD204UI ATA Device

Drive: R:
Free Space: 0.1 GB
Total Space: 0.1 GB
File System: NTFS
Model: SAMSUNG HD204UI ATA Device

Drive: S:
Free Space: 0.1 GB
Total Space: 0.1 GB
File System: NTFS
Model: ST2000DL004 HD204UI ATA Device

Drive: D:
Model: LITE-ON DVDRW SOHW-1633S ATA Device
Driver: c:\windows\system32\drivers\cdrom.sys, 6.01.7601.17514 (English), , 0 bytes

Drive: H:
Model: ELBY CLONEDRIVE SCSI CdRom Device
Driver: c:\windows\system32\drivers\cdrom.sys, 6.01.7601.17514 (English), , 0 bytes[/collapse]

0.2 GB free space on the C: drive is not very much...

 

[Dark Eyes]

Okay, I have cleared out a bit of space, so now the C: drive has over 1GB of free space (I know I have run MP with less) and I have repeated the test - logs attached.
The TV recording I tested with, plays in Windows Media Player (although without audio - probably due to the format) and in MMPC-HC with LAV.
Does this give you nay more insight as to what is going wrong ?

 

[mm1352000]

Hmmm, same error in the log files.

Does this give you nay more insight as to what is going wrong ?

No, not really.
Did you actually get to the point where your system partition c: ran out of space? I mean, I can see your recording partition has run out of space so none of your new recordings will be playable. However if the system partition also ran out of space that may have caused file corruption which in turn could be causing what you're seeing. In that case a full and clean LAV, MP or even Windows reinstallation may be required to resolve. I say reinstallation because it may be prohibitively difficult to identify and fix/replace all the files that have corrupted.


On the other hand, I note the entries in the Windows system event log:
"12/02/2016 00:32:48";"amdkmdag";"DVD_OV";"Information";"UVD Information";"1073804288"

...which people have previously suggested may point to GPU driver problems. For example:
https://forum.team-mediaportal.com/threads/mp-crash-while-switching-to-hd-channel.53343/

However, that's quite an old thread, so I'm not exactly confident in the advice. Especially considering that MPC-HC can play the file.
Is it possible that the problem started when you updated the LAV codecs to v0.66?
...or have you changed the LAV configuration recently?
...or have you updated drivers (particularly the GPU driver) recently?


Ultimately the underlying assumption I make is that problems don't just start for no reason. Something must have changed for the problem to start. Whether it was an unexpected power loss, HDD running out of space, driver update, configuration change, LAV update, Windows update... I don't know. You know better than us when the problem started, what your PC might have been doing at/around that date/time etc. etc. etc. Therefore I would hope you're in a better position than us to recognise the cause of the problem. I can only try and point out things which I think are somewhat suspicious...

 

[Dark Eyes]

Thanks for the advice.

I updated LAV to 0.67, but that didn't help.
Reinstalled MP 1.7.1, but that didn't help.
Then I installed MP 1.13, and that sorted the problem out and it seems to be working as expected.

Unfortunately the PC is operated by a variety of people, most less technically aware than myself, so I don't know what happened to break 1.7.1 but the upgrade 1.1 has fixed it.