mfmp4srcsnk.dll crashing when .MOV file is selected

Has anyone tried reinstalling Windows?

While I have used the workaround of renaming as .old for months now, I am frustrated that I can't edit videos any longer, nor see thumbnails of the .mov files.  Also, after a recent windows update, I am now have no audio (drivers are not the problem).  So I planning to reinstall windows, make a copy of the relevant .dll's and then see what happens when I start updating windows. 

Unfortunately I don't have any restore points to work with.  But I intend on making regular restore points as I reinstall other software.  While many of us are experiencing the problem, the majority of the world seems to be avoiding it, so I am thinking there must be an underlying software onflict inlvolved. 

I am curious to know if anyone has attempted to resolve the problem with reinstalling windows?  If so, what was the outcome?

Hey DrK273.

I totally concur that Microsoft should fix it, but sadly (after many years of tolerating this sort of nonsense) I am cynically resigned to the reality that we might be waiting a time. If they haven't fixed it in 6 months already, despite a 14 page long complaint in just this post, then who knows when they will. My best guess is that we might see things resolved as Windows 10 is released, but even that I won't hold my breath for.

Basically, I posted my 'solution' to help others in the interim - for me it has worked, and whilst I too would rather be running with a correct and current version of the dll, this is better than nothing. It at least allows me to check the validity of my MOV files before clearing space on my iPhone (for me, just opening a folder in ANY view caused Explorer to crash before). This time I didn't have the luxury of any System Restore points, as for best reasons known to the OS, this feature has become disabled!

In terms of Microsoft responding, is anyone at MS reading this? If you want to see your OS continue to succeed in a rapidly receding Windows World, when there are a wealth of alternatives, then I advise we see a fix shortly. I still love Windows, but hate these kind of problems which I suspect could and should be fixed quite easily. We're not in 2002 anymore ;-)

See my reply on Page 12 (bottom of page)

Unless some one else would like to contact MS and pay

and then hopefully get a refund on the basis it is their updates that is causing the problem.

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

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