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
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

183 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2015-03-17T12:48:14+00:00

    I found that disabling MFMP4SRCSNK.DLL (by renaming to *.OLD) also disables video recording and playback function in the native CAMERA APP in Win 8.1

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-03-19T03:48:07+00:00

    Hello,

    Right, I uninstalled both updates - didn't fix the issue.

    This did though:

    Take ownership of the mfmp4srcsnk.dll file, rename it mfmp4srcsnk.dll.OLD.

    Immediately after I could play the file.

    Hope that helps.

    Thanks

    Brendan

    Been looking for a solution for 6 months and nothing was working. This solution worked!!! Thank.

    But I don't think this is a permanent or real solution as I'm sure it has broken other apps like the Camera in Windows 8. I'm willing to sacrifice as I never use the camera and I get too many crashes per day and it has stopped me from viewing Videos.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-03-24T02:44:35+00:00

    Hi All.

    Glad I'm not the only one suffering this problem - hit with it back in Nov 2014, and some updates have crept in to my system during March 2015 bringing the problem back, despite me telling it to block those 4 evil kbs (certainly 2 of them had reinstalled)!

    Here's a way I found to get back to the older mfmp4srcsnk.dll file version....

    Get hold of an ISO copy of Windows 8.1 or 8.0. I have access through my Microsoft Action Pack Subscription, but if you don't have this luxury, Google the download of the Win 8.1 Enterprise 90 day trial (at time of writing, I found it here).

    With the ISO downloaded, mount it in Windows by double clicking the file. Note the drive letter of the virtual DVD drive assigned for the mounted ISO image (for me it was 'F').

    Create a directory on your C drive called 'Win8-WIM'.

    Fire up the command prompt with admin rights. Execute the following command (change 'F' for the drive letter of your mounted ISO drive):

    Dism /Mount-Image /ReadOnly /ImageFile:F:\Sources\install.wim /index:1 /MountDir:C:\Win8-WIM

    This will mount the entire contents of install.wim in the C:\Win8-WIM directory; be patient, it might take a few mins, but you do get a percentage bar on the command line.

    With the mount complete, you can now find mfmp4srcsnk.dll in the sub directory C:\Win8-WIM\Windows\System32. Having gone through the process described elsewhere in this post of taking ownership of the dodgy mfmp4srcsnk.dll file and renaming it mfmp4srcsnk.dll.old, you should be able to just copy and paste in the 'new' mfmp4srcsnk.dll from the to your live C:\Windows\System32 folder. Once complete, run the following command to unmount the WIM file (again, this may take a few mins):

    Dism /Unmount-Image /MountDir:C:\Win8-WIM /discard

    I did this, and I now have thumbnails back and no longer .MOV files causing Explorer crashes. As others have pointed out on here, if you run certain patch consistency checks, it will probably mess up again, but this is working great for me at the moment with the latest patches from MS otherwise in place. mfmp4srcsnk.dll build version is now 12.0.9600.16384 (prob from RTM of Win 8.1 base install)

    I really hope that helps someone else. I really would be pleased to hear of others following this method and getting it to work, so feel free to reply. The above might be more long-winded than just sharing the file I extracted from the install.wim BUT I don't think this described method will violate any terms set out by Microsoft (as I don't have the rights to redistribute the mfmp4srcsnk.dll file, but Microsoft themselves won't stop making Win 8.1 Ent available as a trial download till long after Windows 10 is out - so legal and legit, all good!)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-03-25T15:31:37+00:00

    Thank you for this but after all my problems with renaming and removing/replacing files, I had to go back to the current status quo by using System Restore.  Changing to older versions, for me at least, stopped audio working and Windows Media Player refusing to even work on other files, in my case MP4.

    Replacing files by older files by the user is NOT the solution.  The ONLY answer is to get Microsoft to fix it. 

    The error code is simple - they are dividing by zero, which as any mathematician will tell you is not allowed!

    This problem has been in this particular file (mfmp4srcsnk.dll) since September 2014.  It should not take 6 months to fix!

    So the real question is - How do we get Microsoft to acknowledge the issue and then fix it?

    Some have suggested that the meta data in older MOV files (prior to iOS 7.1) is at fault but sensible programming can either work around it, fix it inflight after reading it and before using it or, at least, not crash explorer or any other calling program.  As a programmer, I know that part of any safe and secure application is to verify/check the input data before using it (failing to do so, for example, on addresses in memory causes a significant number security issues that occur i.e. buffer overruns, raised privilege etc.).  Even if it is correct that Apple made an error in the meta data, it is still unacceptable to use data without checking it and so crashing any application by dividing by zero.  I also know that it is difficult for a software company to cater for errors caused by another software company but again it is unacceptable to crash - these errors must be prevented by validating all input.

    So back to my question - How to get Microsoft to fix it?

    Thanks

    Was this answer helpful?

    0 comments