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-02T14:42:10+00:00

    Are you sure as i am running win 8 and I do not want to uninstall anything. If there is another solution please reply. Thank you.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-04-02T12:41:52+00:00

    Thank you.

    Would you please confirm the file hashes?

    I have (using the very good free Windows Shell Extension - HashTab from Implbits):

    system32 version:

    CRC32: 551068FF

    MD5: 40B228D05DB02F4A5F2452600999F53F

    SHA-1: BB43B0E7D2BF98E233DC949E81D27279074C175E

    SHA-256: A213084DAC8CF058EAB4D0FF8840F4AB8ACD3B7AD103CDDCEF1E643E36DFFEE8

    syswow64 version:

    CRC32: C564F65B

    MD5: 92124EF7B1BF5492EFCA17B3A208E4F4

    SHA-1: 50936E99FB6CB4E8FC66FED92AB2AB24E09492C9

    SHA-256: 6D6F956A48BB0845AD2DBBF4EF797C51ED1A60D2AD3F40D0167B680A7D42D75C

    I just searched again and http://www.processadvisory.com/library/mfmp4srcsnk-dll shows that these files and the MD5 hashes agree with what I have.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-04-02T10:42:14+00:00

    **post removed

    I assume this is an April fools joke !

    If not suggest you read this forum from beginning or at least page 9 onwards as

    this has already been discussed.

     Moderators, when is someone going to contact Microsoft ?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-04-02T06:37:25+00:00

    I believe I found a solution here http://www.bogdans.co.uk/tutorials/system-administration/faulting-module-name-mfmp4srcsnk-dll/

    Bear in mind: restart after each windows update package is removed otherwise the uninstall part will fail (I'll literally say that on the screen I think these packages are clashing somewhere)

    Was this answer helpful?

    0 comments No comments