mfmp4srcsnk.dll crashing when .MOV file is selected

Anonymous
2014-09-09T18:37:17+00:00

I am running Windows 8.1 Pro fully patched (clean install of Windows 8, minimal patches to then upgrade to 8.1, then installed all updates).

Whenever I select a MOV (QuickTime Video) file explorer.exe crashes out and restarts, no message box is shown, just the below entry in Event Viewer. This happens both when browsing files and when using an Open File Control in applications.

I have tried:

  • sfc /scannow
  • Several Fix It's (sorry do not recall which ones)
  • Installing VLC Media Player
  • Installing K-Lite Codecs Pack Lite
  • A lot of Google searches
  • Moving the mov file to different Locations
  • sample files from apples site - these can be selected fine
  • including sample_iPod.m4v (same codecs) works, tried changing to a m4v extension still crashes
  • Downloading the video from source again
  • Playing/highlighting on other systems: Win Vista, Win 7, Linux, Mac, Android (MX Player), Synology NAS (via Photo Station) ... all works fine

This is the info that VLC can pull about the file:

  • Model : iPhone 4S
  • Software : 6.0.1
  • Record Company : Apple

The video in question was taken on an iPhone 4S then e-mailed to me (over a year ago) and has worked on all systems I have watched it on, if I manage to hit enter quick enough then it plays fine. Unfortunately I do not know how to find another video taken on an iPhone 4S for comparison

But even if this is a slightly corrupt file it should not crash out explorer or any application which highlights that file, should it???

Any advice would be very welcome as I watch this video quite often. I cannot think of any other info to include but if you need anymore info let me know. 

Event Details

Log Name:      Application

Source:        Application Error

Date:          09/09/2014 18:41:55

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      [removed]

Description:

Faulting application name: Explorer.EXE, version: 6.3.9600.17249, time stamp: 0x53e160b9

Faulting module name: mfmp4srcsnk.dll, version: 12.0.9600.17238, time stamp: 0x53d0c43e

Exception code: 0xc0000094

Fault offset: 0x000000000008ed0f

Faulting process ID: 0xfa0

Faulting application start time: 0x01cfcc55344567f7

Faulting application path: C:\WINDOWS\Explorer.EXE

Faulting module path: C:\WINDOWS\System32\mfmp4srcsnk.dll

Report ID: 96966394-3848-11e4-be71-6c71d9c2fc89

Faulting package full name: 

Faulting package-relative application ID: 

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2014-09-09T17:41:55.000000000Z" />

    <EventRecordID>6608</EventRecordID>

    <Channel>Application</Channel>

    <Computer>[removed]</Computer>

    <Security />

  </System>

  <EventData>

    <Data>Explorer.EXE</Data>

    <Data>6.3.9600.17249</Data>

    <Data>53e160b9</Data>

    <Data>mfmp4srcsnk.dll</Data>

    <Data>12.0.9600.17238</Data>

    <Data>53d0c43e</Data>

    <Data>c0000094</Data>

    <Data>000000000008ed0f</Data>

    <Data>fa0</Data>

    <Data>01cfcc55344567f7</Data>

    <Data>C:\WINDOWS\Explorer.EXE</Data>

    <Data>C:\WINDOWS\System32\mfmp4srcsnk.dll</Data>

    <Data>96966394-3848-11e4-be71-6c71d9c2fc89</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

Windows for home | Previous Windows versions | Files, folders, and storage

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2014-09-12T10:54:19+00:00

KB2975719 is the problem.

http://support.microsoft.com/kb/2975719/en-gb

I went back to an image prior to September updates and installed all except KB2975719 and problem solved. All MOV files play no problem.

I don't have ClassicShell so I doubt that is the issue

I am not sure if you can remove the update but it is certainly worth a try.

Hope it helps

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

183 additional answers

Sort by: Newest
  1. Anonymous
    2014-10-29T22:37:26+00:00

    Yeah I wish someone would fix this as well. Uninstalled the update last time and everything worked fine, now the update is still uninstalled and it's happening again after the latest patch tuesday, incredibly annoying!

    So, I think I might have found yet another culprit.

    Just like KyleGMD stated, something went wrong, after the 10/14/2014 Tuesday Update. Even with KB2975719 uninstalled, explorer.exe would still crash due to a mfmp4srcsnk.dll memory leak.

    In my case, I had to uninstall KB2995388 to go back to a previous working state.

    If you expand the "List of the Fixed Issues" in KB2995388, you'll see a reference to a memory bug related to MP4, with the ID 2998224 -- I suppose they tried to fix the issue with mfmp4srcsnk.dll but, it's definitely still present.

    This means that, there are now two big updates — that also fix a variety of other issues, not related to mfmp4srcsnk.dll — and we can't even install them, because of this single bug.

    We still need an official reply from Microsoft acknowledging what's happening.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-10-29T12:46:17+00:00

    Yeah I wish someone would fix this as well. Uninstalled the update last time and everything worked fine, now the update is still uninstalled and it's happening again after the latest patch tuesday, incredibly annoying!

    +1

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-10-29T12:38:12+00:00

    Yeah I wish someone would fix this as well. Uninstalled the update last time and everything worked fine, now the update is still uninstalled and it's happening again after the latest patch tuesday, incredibly annoying!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-10-29T10:46:36+00:00

    Has anyone heard anything or found a fix for this? Still no new updates to fix. Very unfortunate.

    Was this answer helpful?

    0 comments No comments