I read this on a site:
Okay, so after months of stressing out, I think I've found a fix for my problem.
When the stupid "sorry for the inconvenience" error window pops up and I check the details, there seems to be a problem with a file called "qedit.dll". I also got problems coming from "qedit.dll" when I go to My Computer(RightClick)>Manage>SystemTools>EventViewer. So, I did a search on my computer for all qedit.dll files. I renamed the ones at C:\WINDOWS\system32 and the one at C:\WINDOWS\ServicePackFiles\i386 to "tempqedit.dll".
I then opened up Windows Movie Maker 2.1, and voila! It's working just fine again!
Another site had this to say:
11/11/03 - Tim - I am compiling a slideshow in WMM. I constantly get told that WMM has encountered an error and must close. The error report details are as follows: AppName: moviemk.exe, AppVer: 2.0.3312.0, ModVer: 6.5.1.900, ModName: qedit.dll, offset: 0000ad31 > Richard - I am having the same error, I also get it when I go to my pic folder on my other drive I have? I was thinking maybe a ram problem but with 256 I don't think so... > I doubt that this applies, but just in case... If you have DirectX 8.1 or earlier installed and have two programs trying to use this dll at the same time, the second program will crash. This is a forced condition by Microsoft... I would suggest that you do the following (if you have not already done so). Install the latest version of DirectX from Microsoft (I think the latest is Ver 9.0b). Install Windows Media Player 9.
2/10/03 - Brian Ahern - installed DirectX9 and this resolved the problem with QEDIT.DLL and seems to have stopped all crashes. I still can't produce a movie, but I think it runs out of real memory before it finishes. I end up with a movie that is incomplete. I'm going to buy another 512Mb of RAM and see if that helps. > 2/11/03 - OO - I tried DirectX9 to no avail. I thought mem paging should prevent an app running out of real mem? If this is the problem it could explain my issue - but I am not sure it is.
2/8/03 - heattreater - I found out what caused the crash. It's the beta version of WinDVD Creator from Intervideo. I uninstalled it and qedit.dll does not crash MM2 on load.I have no idea if the released version has the same bug.
2/7/03 - heat treater - crash at load time - ModName: qedit.dll ModVer: 6.5.1.900 Offset: 00018c80
2/7/03 - Brian Ahern - tried renaming QEDIT.DLL, but Windows XP® is too clever for that. As soon as I did it, the DLL was replaced with a file of the same attributes. Anyway, I tried saving again and got the same crash with QEDIT.DLL. I tried forcing the movie to save with a maximum size. Again, the problem always occurs at the end of producing the movie. At one point the movie saved slightly more than normal before crashing. (an extra 8 photos made it). It is a pain when it crashes because it always seems to happen at around 90% (which takes around 30 mins to get this far).
2/6/03 - heat treater - I'm having qedit.dll crash MM2 at startup. - ModVer: 6.5.1.900 Offset: 00018c80 - I tried DirectX 8.1 or 9.0 they both crash. Checked for another instance qedit.dll loaded by another app, using system info. Only time I can see it load is when I start up MM2 and Crash. This bug occurs on two systems. Other systems seem to work fine. Tried changing Video board of system that worked but I have the same error. It does not seem to be a video driver problem. Running it through Visual Studio Debugger I get a unhandled exception error.
2/6/03 - OO - BINGO! - I renamed the two instances of qedit (win32 and servicepack files) to qedit.dll_ and I can now save in DV- AVI, send to camcorder..etc...
Good luck getting it to work.
