Immediate lockup...

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

My MovieMaker locks up immediately upon opening. The page lites then locks
within 3 to 4 seconds of opening! I figure there is either something corrupt
or there is a conflict with other video software on my computer.

I figured I would try to re-install WMM to see if that would work the bug
out. Problem is MS makes it just about impossible to do that. It's bundled up
with SP2 and can't be separated. So, I get the SP2 disk to see if I could
find it there, but no!

OK, that figures... So, I re-install SP2 to see if that would work. Not a
chance! That bothers me to no end. Why does MS do that? Why do they make it
nearly impossible to make things work? I thought I found a separate D/L for
WMM at one time but I can't find it now.

I have other video software up and running it just errks me when I can't get
what seems like it should be a quick fix to work. If anywone has suggestions
I would appreciate it.
 
XJHay said:
Hello,

My MovieMaker locks up immediately upon opening. The page lites then
locks within 3 to 4 seconds of opening! I figure there is either
something corrupt or there is a conflict with other video software on
my computer.

I figured I would try to re-install WMM to see if that would work the
bug out. Problem is MS makes it just about impossible to do that.
It's bundled up with SP2 and can't be separated. So, I get the SP2
disk to see if I could find it there, but no!

OK, that figures... So, I re-install SP2 to see if that would work.
Not a chance! That bothers me to no end. Why does MS do that? Why do
they make it nearly impossible to make things work? I thought I found
a separate D/L for WMM at one time but I can't find it now.

I have other video software up and running it just errks me when I
can't get what seems like it should be a quick fix to work. If
anywone has suggestions I would appreciate it.
=======================================
Some users have reported problems
after installing IE7. If this applies to your
situation ...uninstalling IE7 may be worth
a try.

(927177) How to uninstall Internet Explorer 7
http://support.microsoft.com/kb/927177/en-us

I've also seen a report that disabling the
ffdshow codec could be the fix. To accomplish
this...open Movie Maker and go to...Tools /
Options / Compatibility tab...Uncheck...
ffdshow / OK.

===
(You can disable ffdshow with this command:
regsvr32.exe /u "C:\Program Files\ffdshow\ffdshow.ax"
After running that command, the regular
DivX/XviD codecs will be used instead of ffdshow.
You can enable ffdshow again with this command:
regsvr32.exe "C:\Program Files\ffdshow\ffdshow.ax" )
===

More info:

Movie Maker 2 Crashes and Hangs
http://tinyurl.com/bqgyx


--

John Inzer
MS Picture It! -
Digital Image MVP

Digital Image
Highlights and FAQs
http://tinyurl.com/aczzp

Notice
This is not tech support
I am a volunteer

Solutions that work for
me may not work for you

Proceed at your own risk
 
Recent versions of FFDSHOW should be Okay with Movie Maker but in any case
instead of going to the extreme of disabling it completely the user can go
into FFDSHOW configuration and simply disable FFDSHOW's support for any
particular CODECs they don't want it to handle, like say the various WMV
codecs or MPG2.

Movie Maker seems to have a problem handling large numbers of DirectShow
effects filters. Installing IE7 might be making changes to the system that
trigger this problem in MM. Large numbers of DirectShow effects filters
from 3rd party software are preloaded and MM crashes on startup. If the
folders for the programs which provide those filters (eg. WinDVD creator is
one) are temporarily renamed so that the filters cannot be found by Windows
(a reboot might neccessary if it doesn't work immediately) and then Movie
Maker is run it should start normally. MM should continue to startup and
function normally even after the folders are renamed back to their correct
names. I did have the MM crashing problem and solved it using those steps.
IE7 and FFDSHOW are currently both installed, without affecting MM.
 
Hello RalfG,

WMM was working ok while IE7 was installed so I agree that removing IE7
won't fix the prob. A couple of people I have talked to have mentioned
"ffdshow" and I have tried to locate it without any luck. I can't find the
codec that corresponds to it either. So, I don't know what to do about that.
I suppose nothing because maybe I don't have "ffdshow" to worry about. I have
many codecs however, I have no idea how to figure out which one(s) may be
causing the problem if in fact they are.

Thanks for the input!
 
Aloha,

I am not a pro with computers etc... So forgive me if I am telling you
something you allready know......

I know that somehow the microsoft movie maker (MMM) can not handle
transitions and effects in 1 picture (what to think of many more) at the
same time and I am working with Vista, wich should work even better. I also
still have that problem..... screen clears en MMM stops. And about trying to
get Moviemaker installed again..... the website
http://www.windowsmarketplace.com can provide you with new free software to
re-install moviemaker.....

I hope this was usefull info.

Kind regards,

Laurence
 
FFDSHOW is something you would have had to to source, download from the web
and install yourself unless you happened to get it included with one of
those downloadable mega-codec packs. On its own it replaces most of the
codecs found in those codec packs. I used to use it just to provide playback
support for uncommon or otherwise commercial-only codecs, like h.264, 3ivX,
Divx:), but for almost a year now I use it for playing pretty much
everything but the standard codecs that come with XP MCE and the commercial
software installed on the PC.

Did you try the "filters" workaround? WinDVD Creator is only one example of
software that includes a lot of filters but any other video software could
be implicated.
 
RalfG,

Thanks for hanging in there!
As for: Did you try the "filters" workaround? WinDVD Creator is only one
example of software that includes a lot of filters but any other video
software could
be implicated.

I got a little confused with that one. I think I tried to do that however,
when it did not work even after a reboot. I thought I must have made a
mistake somewhere along the line. I tried renaming "InterVideo" to
"TempInterVideo" to no avail.

Maybe the problem is not with Intervideo. By the way, "InterVideo DVD
Creator 2" is one of the other video programs that works fine.

I am thinking this is one that I am not going to win. As much as it pains me
to say that I think it's going to take a miracle or an accident to fix this
one!

I do appreciate you kicking it around a bit with me though!
 
Laurence,

I'm no pro either so you're amongst friends here.

I went to that website you provided the link for and was not able to find
WMM there. I do not know if I did not look in the right place or not but I
could not find it non the less. If you know something that I missed I would
appreciate a heads up, if not, not to worry!

Thanks for the help.
 
WinDVD Creator is one source of the filters that MM chokes on but it isn't
the only one. It happened to be the only program involved on my system but
somebody could concievably have several different programs supplying effects
filters that MM will try to use. It would be nice to have a list of the
"usual suspects" that people with this symptom could refer to, but I haven't
seen one. What's left is a trial and error process where all the possible
sources need to be disabled at the same time.

Stated a different way:

=====begin quote

Subject: Re: Movie Maker always has to close


There's a component in Direct Show which caches the information about the
effects and transitions that are registered upon your system. Unfortunately
there's a bug in that component which causes it to crash if you have a lot
of transitions and effects installed. MovieMaker calls this routine on
startup which is probably why you're seeing MovieMaker crash.

Fortunately there is a workaround by doing something like the following.


1. Find an application which has registered a bunch of effect filters.
2. Rename the directory that the application is installed into to
something else - which will temporarily cause those effect filters to fail
to load.
3. Start MovieMaker. As less effects are successfully created,
MovieMaker should hopefully launch.
4. Rename the directory in step 2 back to it's original name so the
original application still works.
5. Start MovieMaker again. As everything was successfully cached in step
3 it shouldn't try to recache things so it should continue to work..


As an example of an application for step 1, I've seen people run into this
problem with applications installed from InterVideo. (This isn't a bug in
InterVideo's application - it's a Microsoft bug it's just that InterVideo
applications can install a bunch of DirectShow filters). In this case you
would go to your "C:\Program Files\InterVideo" directory and rename
"InterVideo" to something like "TempInterVideo". Then start MovieMaker. Once
it has launched, close it down and rename "TempInterVideo" back to
"InterVideo".


Good luck
Dean Rowe
This posting is provided "AS IS" with no warranties, and confers no rights.

=== end quote
 
my website's Problem Solving > Crashes and Hangs page includes a running
list of the codecs that are typically involved in Movie Maker issues.
 
Interesting list you have on that site. Seems I have 150 .ax files installed
here, not including those hidden in .CAB files or install folders (281
total).

I have 2 of the Nero filters (video+ mpg) disabled in Movie Maker but
FFDSHOW and others haven't been a problem. That is possibly because I
disabled Windows Media, DV and MPEG1&2 support within FFDSHOW.

I noticed you have a few commercial filters in your problem list that are
floating around the web as illicit hacked versions, like l3codecx.ax - the
Frauenhoffer MP3 codec and mmswitch.ax - the Morgan Stream Switcher. Those
are often included in codec packs.
 
my rule of thumb is to add one to the list if I hear from two Movie Maker
users that doing something to take them out of the equation worked to
resolve their crashing/hanging issues.
 
Back
Top