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: Most helpful
  1. Anonymous
    2015-04-02T06:15:40+00:00

    In order to facilitate easy recovery from the problem (done three or four times now) I keep a copy of the requisite DLLs on a separate system.

    Quickly replacing mfmp4srcsnk.dll in two directories as previously documented has (so far) fixed the problem each time it has been reintroduced by different patches.

    The required versions are:

    system32:

    File version 12.0.9600.16477

    Created 12 Nov 2014 09:53:48

    Modified 04 Dec 2014, 14:59:43

    Signed ‎27 ‎Nov ‎2013 16:27:08 (only valid to 17 ‎Sep ‎2014 22:43:38)

    Size 809,872/811,008 bytes

    syswow64

    File version 12.0.9600.16477

    Created 12 Nov 2014 09:53:44

    Modified 04 Dec 2014, 14:59:39

    Signed ‎27 ‎Nov ‎2013 15:00:58 (only valid to 17 ‎Sep ‎2014 22:43:38)

    Size 663,680/667,648 bytes

    The created/modified dates may of course depend on whichever system it was that I copied them from.

    And yes, it SHOULD be fixed!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-04-01T17:22:30+00:00

    I had issues with both solutions (older files and Windows 10) and so I would be grateful if anyone who found either of these to work would kindly check something for me:

    1. When I used an older version of this file, Windows Media Player would not play these files (this is the non-Metro application "C:\Program Files (x86)\Windows Media Player\wmplayer.exe" V12.0.9600.17415).  Does this work for you and does it play the sound?
    2. When I used Windows 10 Technical Preview 9926, they would play with Windows Media Player but I had no sound.  This may be because I was running Windows 10 in a VirtualBox VM but it might not.  Did it play sound for you when not in a VM?

    Lastly, I would be reticent to say that the problem does not exist in Windows 10.  I suspect (but not working for MS, I could not confirm either way) that most of Windows 10 is actually Windows 8 or 8.1.  The version number has changed, as I mentioned in a previous post, but this can be done in a simple way to change the version number to the operating system base number en masse - for example the version contains the build number [in my case 9926 and I assume 11041 in the latest build] but I doubt that they have recompiled every single program/DLL whenever they release a new build.  It really depends on when MS took the copy from Windows 8/8.1 and whether they have yet re-applied all the fixes they have issued for Windows 8.1 onto Windows 10.  I doubt this will be confirmed until much nearer to the official Windows 10 release date!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-04-01T15:00:08+00:00

    Yes I know. I have had the issue and Microsoft have not the mind to fix this error. I can not view a video of my cat that sadly passed away a view months ago. I really hope the Microsoft employees actually fix or respond to this stupid error. The video was recorded on an iPhone 3 then transferred to an iPhone 5 and then to my PC. I also have YouTube videos trying to be transferred. Please fix this on Windows 8. Thank you.

    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