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: Oldest
  1. Anonymous
    2015-03-30T01:17:15+00:00

    When I replaced the new 2014 mfmp4srcsmk.dll files with the older 2013 mfmp4srcsmk.dll files - Windows Explorer no longer crashed!  I think I have found the best fix yet.

    I would lightly suggest that the fix I came up with (mounting the install.WIM file with DISM, from an ISO of Win 8.1 install) is a better move. What you're potentially running (with your described method) with is a version of the dll designed for Win 8.0 and not 8.1 (or if nothing else just an older dll than necessary to fix the issue). The method I have detailed previously (one or two pages back for those reading this) will get a copy of mfmp4srcsnk.dll from the RTM (Original Release) of Windows 8.1. This may or may not be the same as the version you've extracted from Win 8.0.

    Bottom line is that with the DISM method and no more than 10 mins of work, you can get the file without having to install an older version of Windows in any VM or the like, and with a lot less hassle. If you did want to take this more long winded approach, you may as well just install the Win 8.1 RTM and get the file that way first before running all patches, instead of Win 8.0 :-) I can also vouch this has been working perfectly on my [otherwise] completely patched up-to-date install of Windows 8.1 for the last week :-)

    Sorry stormgoose - I didn't understand your March 24 post (I lack techy knowledge and got thrown by the acronyms, ISO, RTM, etc).  But I do understand what you mean above, and can now see what you meant originally.   And yes, I agree, that's a much faster, easier solution. :-)

    I actually tried the DISM method, but unfortunately it didn't work, and neither did refresh or restore. So, I had to revert back to Windows 8.

    Hopefully others will have luck with the DISM method. If it doesn't work, at least my longer method will.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-03-30T21:16:36+00:00

    SCGHSCGH/Stormgoose and others earlier in thread.......appreciate your time giving optons on fixing the issues.

    We now have a few workarounds here but no true solution from Microsoft, which is pretty damn poor.

    I assume they have a select few testers/beta users who can report back bugs after updates etc. and track all stuff like this.....anyone know how they work or how to become a tester?

    Do we know any names of mods on here so we can bring this to their attention?

    I'd be happy with a problem reference or whatever just to show they acknowledge the issues.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-03-31T23:42:21+00:00

    I can't believe this topic remained active from Sept 2014 until now, I still have the same problem on both my laptop and my brand new Surface. it's pathetic really.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-04-01T11:22:18+00:00

    I totally agree and I am very disappointed that Microsoft do not even have the respect for its customers to acknowledge this issue.

    Build 10041 of Windows 10 seems to work for me for all the iPhone clips that I have - so hope is just over the horizon.

    I really do not understand the company's attitude - and I know that Microsoft employees read these posts.  It is just appalling that none of them has the ability to reply ....

    Was this answer helpful?

    0 comments No comments