Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
microsoft.public.windowsxp.moviemaker
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion MM" Crashes when initially going in to program
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Dean Rowe [MS]  
View profile  
 More options Jan 2 2005, 5:28 pm
Newsgroups: microsoft.public.windowsxp.moviemaker
From: "Dean Rowe [MS]" <dea...@online.microsoft.com>
Date: Sun, 2 Jan 2005 14:28:02 -0800
Local: Sun, Jan 2 2005 5:28 pm
Subject: Re: MM" Crashes when initially going in to program
Print | View thread | Show original | Report this message | Find messages by this author
Looks like you're running into the same problem as the original poster on
this thread. Here is my response to him which should hopefully do the trick
for you too.

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 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".

Hope this makes sense, and let me know if you have any other questions.
Regards
Dean Rowe
This posting is provided "AS IS" with no warranties, and confers no rights.

"NHGoodrich" <NHGoodr...@discussions.microsoft.com> wrote in message

news:31382D8E-267B-4671-A225-1CF7F0C5B81E@microsoft.com...

> Fault bucket 127394354.

> "Dean Rowe [MS]" wrote:

>> When MovieMaker crashes, click the button to send the report to
>> Microsoft.
>> Then find the "bucket number" of that crash and send it to me. (See my
>> other
>> reply in this thread to see how to get the bucket number"). Then I'll see
>> if
>> I can track down what's going on.
>> Regards
>> Dean Rowe

> Fault bucket 127394354.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google