This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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:
This is the info that VLC can pull about the file:
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>
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.
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
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 :-)
Pretty much same fix/workaround as I suggested but without having to revert to windows8?
I have found another workaround... reinstalling Windows 8 and not updating to 8.1 ...
... I am tempted to copy the mfmp4srcsnk.dll from the Windows 8, upgrade to 8.1, and copy
mfmp4srcsnk.dll over the 8.1 version of the see if this prevents the problems. Anyone tried this?
Well, after a successful day of reloading Windows 8 and being able to view and watch .mov files without Window Explorer crashing... I decided to try copying the Windows 8 mfmp4srcsnk.dll files (dated 04-05-2013), upgrade again to 8.1, and replace the new mfmp4srcsmk.dll files (dated 22/11/2014) with the older 2013 files. Although there were a number of files named mfmp4srcsmk.dll, I only replaced those in the following folders - C:\Windows\System32 and C:\Windows\SysWOW64
Before copying over the old mfmp4srcsmk.dll files, Windows Explorer crashed whenever I opened a folder with .mov files. Only Windows 8.1 was on my computer, no other software was installed, so this ruled out a software conflict.
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.
Yes, it has been a pain to do, and I have had to take ownership of the files again. And may have to keep replacing the files with the older 2013 files after each windows update (although so far, I haven't needed to even after installing a number of recent updates). But I am happy to do this , to at last be able to view thumbnails and properties and, watch and edit my .mov files.
I hope this helps someone else like me who is getting fed up with the crashes and the problems resulting from renaming .old.
I have found another workaround... reinstalling Windows 8 and not updating to 8.1
As mentioned earlier, I had being working with the renamed mfmp4srcsnk.dll.old files for months now, but was frustrated by not being able to see the .mov thumbnails and file properties or edit video files on any software application. I then began to experience other windows problems. After having no luck at all with the numerous Windows scans and built in fixing capabilities, I reinstalled Windows 8. It wasn't as painful as I thought it would be, as I only reinstalled it on the small partition where the programs were located, and all of my data remained untouched (of course the" data was backed up elsewhere, just in case).
I found that with a fresh reinstall of Windows 8, and with all the updates (excluding Windows 8.1 upgrade), there was no problem at all with Windows explorer crashing, thumbnails were visible, and I could easily watch and edit video files again. Brilliant.
Out of curiosity, I upgraded to Windows 8.1. Big mistake. Windows Explorer starting crashing immediately, and as it was freshly installed, there were no restore points (I had just created several after installing Windows 8 but these were gone), and the problem updates weren't available to deselect.
So I am just about to reinstall Windows 8 again, forget about Windows 8.1 upgrade, and await the Windows 10 release in a few months (which is reported to fix the problem, but not be stable enough at the moment to justify installing the preview version on my sole laptop).
I should point out that Microsoft say "We strongly recommend that you install Windows 8.1 Update.
This is a critical update that is required for future updates to Windows. If you prevent it from installing or if you uninstall it, you won’t get some future bug fixes, security updates, and new features. In some cases, if you uninstall this update from a new PC after signing in with a Microsoft account, OneDrive might not work as expected." Ummmmm well, it seems 8.1 has a nasty bug in it that is causing me far more headaches!
So for me, Windows 8 is the best workaround for now.
I am tempted to copy the mfmp4srcsnk.dll from the Windows 8, upgrade to 8.1, and copy
mfmp4srcsnk.dll over the 8.1 version of the see if this prevents the problems. Anyone tried this?
