Need help with Error in module mxmpeg2.dll - in ProX

lauriemessage wrote on 12/15/2012, 11:35 AM

Hello,

We were making the finishing touches to a movie in Video Pro X4 when a "serious program error" displayed. The program crashes when we select the movie's folder and the thumbnail images begin to build, before we even load the movie onto the timeline. This only happens with this one movie/folder. The same problem occurs in Pro X3.

I attempted to link to a jpg of the error message here:

http://i884.photobucket.com/albums/ac45/LaurieDutch/Magixdllerror_zpse175bd32.jpg

If the link doesn't work, the error message reads:

A serious program error occurred. Error in module mxmpeg2.dll  and ends with ACCESS_VIOLATION.

OS is Windows 7, 64-bit.

Hardware is ASUS desktop PC, Core i5 CPU, 3.2 GHz, 8 GB RAM.

Thanks for any help.

Comments

emmrecs wrote on 12/15/2012, 2:35 PM

First, did you do as the error message said and choose to save the movie as an .mvd project?  Did you then close the program (as the message suggested)?  Having reopened the program, if you did all the above you should be presented with a screen that asks whether you want to send a crash report etc. etc., and whether you want to "restore project".  if you choose that option the program should open that .mvd file and allow you, having resaved the project to a name of your own choosing, to continue working.

If you've done all that and the project still won't open properly or crashes very quickly I think your project file (.mvp) may very well be corrupted.  In that case you may have no option to begin to rebuild it from the start unless you chose to have VPX create regular saves of your project.  in which case search your HDD for .BAK files.  Check the time of any such files you have which are part of this project.  Open the latest one.  Resave it immediately under a new name.  Check whether it exhibits the same problem.  If not, you should be able to continue.  If it does, go to the next oldest .BAK file and repeat the above.  Hopefully you will eventually find one which can run successfully.  Yes, you will lose any work done after that back up was created but at least you still have a part of your project and you may have some idea of what actually caused the original crash and error message.

If it's any consolation to you, I quite regularly receive a similar message when trying to edit/add effects to a title object.  Following the above procedures usually allows me to continue working with only minimal disruption.

Jeff

Last changed by emmrecs on 12/15/2012, 2:35 PM, changed a total of 1 times.

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, NVidia GTX 1660TI and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

lauriemessage wrote on 12/16/2012, 2:15 PM

Jeff:

First, many thanks for your detailed, helpful and sympathetic message.

-- First, did you do as the error message said and choose to save the movie as an .mvd project Did you then close the program (as the message suggested)?  . . .? --

Since nothing loads onto the timeline, this seemed pointless, but after getting your message, we tried. It didn't help.

--  . . . search your HDD for .BAK files.--

We started with BAK7 which loaded fine, then worked our way up to BAK1 which loaded okay. BAK0 gave the error message. So that's progress.

However, when we open the program and try to load the movie along with all its components, it crashes. We tried renaming the movie and loading it with the details displayed (as opposed to thumbnails) and it loaded, but when we try to work on it, it crashes and gives an error message that says "error in Quicktime qts" so we have the impression that a piece of video (as opposed to jpg's and mp3's) might be corrupted.

We will continue to experiment with different things. Perhaps we should remove 5-10 files, then reload and see what happens, and continue doing that until it does not crash.

Any ideas about what else we can try? Appreciate your help very much.

emmrecs wrote on 12/17/2012, 3:16 AM

 

--  . . . search your HDD for .BAK files.--

We started with BAK7 which loaded fine, then worked our way up to BAK1 which loaded okay. BAK0 gave the error message. So that's progress.

However, when we open the program and try to load the movie along with all its components, it crashes. We tried renaming the movie and loading it with the details displayed (as opposed to thumbnails) and it loaded, but when we try to work on it, it crashes and gives an error message that says "error in Quicktime qts" so we have the impression that a piece of video (as opposed to jpg's and mp3's) might be corrupted.

We will continue to experiment with different things. Perhaps we should remove 5-10 files, then reload and see what happens, and continue doing that until it does not crash.

Any ideas about what else we can try? Appreciate your help very much.

Hi.  Glad to hear you're making some progress!

However, I'm a little confused by your statement that "BAK1 loaded OK" but "when we open the program and try to load the movie...it crashes".  If BAK1 is still "usable" (i.e. no crash) that is the file you should rename to make it your new mvp file.  Or am I misunderstanding what you are doing?

As to your suggestion about removing "5 - 10 files", given the error message re "Quicktime", this could hint at a problem .mov file.  Do you have one or more of these in your project?  If so, I would start with removing them and see if the program still crashes.  If you do not have any .mov files, do you have Quicktime set as the default player for certain file-types, e.g. mp3?  Try removing one or more of them, until the problem, hopefully disappears.  This will be tedious and time-consuming but should, eventually, lead you to the file which is causing the problem.

Just one other question: I notice you say that "BAK0 gave the error message", whereas BAK files with higher numbers loaded fine.  I wonder whether you have the numbers reversed?  BAK7, as the highest number, should be the most recent; BAK0 should be the oldest and first to be made.

Jeff

Last changed by emmrecs on 12/17/2012, 3:16 AM, changed a total of 1 times.

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, NVidia GTX 1660TI and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

lauriemessage wrote on 12/17/2012, 10:33 AM

-- If BAK1 is still "usable" (i.e. no crash) that is the file you should rename to make it your new mvp file.  Or am I misunderstanding what you are doing? --

As soon as we try to edit the movie by accessing a file in the folder with the source files (mp3, jpg, mov, effects, etc.), the program crashes and the dreaded error message appears. We are trying to create a series of avi files, then will piece them together in a new movie and will not deal with any of the old source files. Something in that folder has been corrupted.

One of the times the movie crashed yesterday, the error message was strange in that it named a video file that doesn't exist. The file original file name in the source file was John.mov, yet the error message referred to a nonexistent file called battleshipJohn.mov. None of the files in the movie have anything to do with a battleship!

Perhaps the build of the movie was complex for the computer to handle.

The date order of the BAK files keeps BAK0 as the most recent, and older versions have higher numbers, so BAK7 was the oldest build. Perhaps it's a UK vs US difference.

Thanks again!

emmrecs wrote on 12/17/2012, 11:47 AM

 

As soon as we try to edit the movie by accessing a file in the folder with the source files (mp3, jpg, mov, effects, etc.), the program crashes and the dreaded error message appears. We are trying to create a series of avi files, then will piece them together in a new movie and will not deal with any of the old source files. Something in that folder has been corrupted.

One of the times the movie crashed yesterday, the error message was strange in that it named a video file that doesn't exist. The file original file name in the source file was John.mov, yet the error message referred to a nonexistent file called battleshipJohn.mov. None of the files in the movie have anything to do with a battleship!

Perhaps the build of the movie was complex for the computer to handle.

The date order of the BAK files keeps BAK0 as the most recent, and older versions have higher numbers, so BAK7 was the oldest build. Perhaps it's a UK vs US difference.

Thanks again!

Very strange!  I'm going to comment on your points in reverse order!  If BAK0 is the newest one available then that is completely the reverse of how they work for me!  I don't think this is anything to do with UK v US; I'm in UK, are you in US?

It is possible that the movie was becoming very complex.  How many objects/tracks are you using?  (Though I have to say that, for me, VPX has been well able to handle projects with a large number of objects, possibly in excess of 50 or 60, spread over 12 or more tracks.)

Not sure I understand what you mean by your first paragraph "As soon as we try to edit...".  Are you saying that the moment you add almost ANY type of file to your project it crashes?  If so, I've never seen that happen before!  However, I think it could point to a severely corrupted project file (mvp) or a VPX installation that needs a Repair or even an uninstall and reinstall.

In order to verify whether the project file is corrupt, is it possible to create a brand new project, by importing a random selection of files (video, audio and image), saving this "test", closing, reopening the program and this project.  Can you then add more files?  If so, this might suggest a corrupt original project file; if not, I think VPX itself may need the rather drastic surgery I mentioned in the previous paragraph.  I think also the phantom renaming of a file could well indicate some corruption somewhere; my fear is this might be in VPX itself.

Jeff

Last changed by emmrecs on 12/17/2012, 11:47 AM, changed a total of 1 times.

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, NVidia GTX 1660TI and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

lauriemessage wrote on 12/17/2012, 12:20 PM

I'm in the US; I noticed you are in the UK, and that's what made me think the BAK order might be due to the different ways computers write dates.

--  How many objects/tracks are you using? --

Just 5 tracks, which we have used in many other movies. The folder with the souirce files (mp3's, jpg's, etc) lists 304 items in the folder, but I don't know if this is what you mean by "objects".

-- Are you saying that the moment you add almost ANY type of file to your project it crashes? --

In the old corrupted movie, the as the folder with the source files was being populated, the program would crash. In the version created using a BAK file, we if we tried to access any of the mp3's, jpg's, etc in an attempt to edit, the program crashed.

The good news is, we have managed to create 6 avi files that contain all sections of the movie, so we will use them and forget about using anything from that folder that seems to be corrupted.

Thanks again!

 

  If so, I've never seen that happen before!  However, I think it could point to a severely corrupted project file (mvp) or a VPX installation that needs a Repair or even an uninstall and reinstall.

In order to verify whether the project file is corrupt, is it possible to create a brand new project, by importing a random selection of files (video, audio and image), saving this "test", closing, reopening the program and this project.  Can you then add more files?  If so, this might suggest a corrupt original project file; if not, I think VPX itself may need the rather drastic surgery I mentioned in the previous paragraph.  I think also the phantom renaming of a file could well indicate some corruption somewhere; my fear is this might be in VPX itself.

lauriemessage wrote on 12/18/2012, 8:36 AM

Hello again, Jeff.

Once we "rescued" the movie by creating a series of avi files and building a new version, we went back to the problem folder containing the source files and deleted all the mx files (effects plus a few downloads from YouTube) since the error messages always referred to mx files (Error in module mxmpeg2.dll). After doiing so, we were pleasantly surprised to see that the original version now loads just fine, that we can access the "problem" folder and edit the original version of the movie! One of the mx files must have been corrupted.

Thanks once again for your help and support!