That's sad to hear that this wasn't corrected in 2014. I've had this issue in the 2010 version and the eventual fix was to identify the bad pieces of media that it was trying to find and removing them through SQL. Although I understand the concepts behind fixing it you need to pretty adept at using SQL and know how to identify the bad pieces of media. It took me six months of working with support to finally get it escalated to the correct person, but once in his hands it was resolved somewhat quickly. If you all continue to have these issues have you tried talking to the on-call duty manager or tried to get this escalated? Good luck and if not time to get rid of it.