Movie Maker Crashing

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

Guest

I'm trying to combine three clips for now for a test using movie maker and
the application crashes when the process is from 59% to 69% complete. I'll
try to be as complete with the information as possible.

Clip 1 is a 1.962Mb WMV file which was created by Movie Maker.
Clip 2 is a 73.846Mb WMV file which was created by Photo Story 3
Clip 3 is a 15.483Mb WMV file which was created by Photo Story 3

Yesterday I had this problem when the process was 59% complete. I then read
the Crash information on Papa Johns page and removed the Nero Codecs from
Movie Maker even though they are not on the list. I also lowered the hardware
accelleration to level 3. Making those changes allowed the process to
complete 69% today, but with the same result.

So, I checked the event log and found the following information:

Faulting application moviemk.exe, version 2.1.4026.0, faulting module
wmvadvd.dll, version 10.0.0.3802, fault address 0x000b06eb.

Looking at the events from yesterdays failures I saw the same problem. Is
there an issue with the mentioned dll?

I'm a little confused by the error message becuase combining the first and
third clip mentioned above with a third clip smaller than the second clip
listed Movie Maker works fine and I was able to write the output file to a
DVD. It would seem that there is a size limitation, but that doesn't make
sense to me bacuase the faulting component, wmvadvd.dll, is the Windows Media
Video 9 decoder.

I would appreciate any help, as I have about 24 clips to combine into a
movie for a DVD which will last about an hour and 55 minutes.

Thanks.

Greg
 
gjbilik said:
I'm trying to combine three clips for now for a test
using movie maker and the application crashes when the
process is from 59% to 69% complete. I'll try to be as
complete with the information as possible.

Clip 1 is a 1.962Mb WMV file which was created by Movie
Maker.
Clip 2 is a 73.846Mb WMV file which was created by Photo
Story 3
Clip 3 is a 15.483Mb WMV file which was created by Photo
Story 3

Yesterday I had this problem when the process was 59%
complete. I then read the Crash information on Papa Johns
page and removed the Nero Codecs from Movie Maker even
though they are not on the list. I also lowered the
hardware accelleration to level 3. Making those changes
allowed the process to complete 69% today, but with the
same result.

So, I checked the event log and found the following
information:

Faulting application moviemk.exe, version 2.1.4026.0,
faulting module wmvadvd.dll, version 10.0.0.3802, fault
address 0x000b06eb.

Looking at the events from yesterdays failures I saw the
same problem. Is there an issue with the mentioned dll?

I'm a little confused by the error message becuase
combining the first and third clip mentioned above with a
third clip smaller than the second clip listed Movie
Maker works fine and I was able to write the output file
to a DVD. It would seem that there is a size limitation,
but that doesn't make sense to me bacuase the faulting
component, wmvadvd.dll, is the Windows Media Video 9
decoder.

I would appreciate any help, as I have about 24 clips to
combine into a movie for a DVD which will last about an
hour and 55 minutes.

Thanks.

Greg
======================================
Maybe the following article will offer some ideas:

MM2 - Problem Solving - 'Can't Save A Movie'
http://www.papajohn.org/MM2-Issues-CantSaveMovie.html

--

*********Notice**********
This is not tech support.
....I am only a volunteer...

Solutions that work for
me may not work for you.

Proceed at your own risk.

John Inzer
Picture It! MVP

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

I've read that page before but went back and looked at it again. I was able
to make a movie using three clips that I have saved. I made another movie
this morning with two different clips, which worked fine. When I tried to
combine the five clips into a movie MM2 worked fine till about 20% and then
just seemed to quit working. CPU usage went to 0. I still have about 650Mb
or RAM left so that shoudln't be a problem. I am now going to restart my
computer and try making the movie that just stopped again. I'll open task
manager first and see what happens.
 
gjbilik said:
Thanks John.

I've read that page before but went back and looked at it
again. I was able to make a movie using three clips that
I have saved. I made another movie this morning with two
different clips, which worked fine. When I tried to
combine the five clips into a movie MM2 worked fine till
about 20% and then just seemed to quit working. CPU
usage went to 0. I still have about 650Mb or RAM left so
that shoudln't be a problem. I am now going to restart
my computer and try making the movie that just stopped
again. I'll open task manager first and see what
happens.
================================
Sounds like resource issues. What size is
your hard drive and what percent is free?

--

*********Notice**********
This is not tech support.
....I am only a volunteer...

Solutions that work for
me may not work for you.

Proceed at your own risk.

John Inzer
Picture It! MVP

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

First, I have a 56Gb hard drive with over 50% free. Also, I tried making a
movie as I stated below with 5 clips which MM2 has used before to make a
movie successfully and the process crashed at the 68% mark. Probably from a
timeline perspective about the time I was having problems the other day. I
had task manager running and had plenty of RAM left, about 290Mb available.
No parameters where near their limits.

Also, when checking event manager the errors reported are the same as when I
was using a clip which MM2 hadn't successfully made into a movie yet. Since
I was using clips MM2 already was successful with I am even more confused by
the error message because the wmvadvd.dll where the reported error is
happening is the Windows Media Video 9 Decoder. Which, if I understand the
documentation on the Microsoft Developers Network, is used to decode the
input video stream a different dll, don't know the file name, is used to
encode the output stream.

And since MM2 has already made a movie with these clips, when only two or
three of them are used, I would assume, I know bad thing to do, that MM2 has
already decoded the input streams successfully.

I'll keep thinking and looking. If only the error message in the event log
would tell which function in the dll is failing it might lead to a better
understanding of the problem.

Thanks for the ideas.
 
gjbilik said:
Hi John,

First, I have a 56Gb hard drive with over 50% free.
Also, I tried making a movie as I stated below with 5
clips which MM2 has used before to make a movie
successfully and the process crashed at the 68% mark.
Probably from a timeline perspective about the time I was
having problems the other day. I had task manager
running and had plenty of RAM left, about 290Mb
available. No parameters where near their limits.

Also, when checking event manager the errors reported are
the same as when I was using a clip which MM2 hadn't
successfully made into a movie yet. Since I was using
clips MM2 already was successful with I am even more
confused by the error message because the wmvadvd.dll
where the reported error is happening is the Windows
Media Video 9 Decoder. Which, if I understand the
documentation on the Microsoft Developers Network, is
used to decode the input video stream a different dll,
don't know the file name, is used to encode the output
stream.

And since MM2 has already made a movie with these clips,
when only two or three of them are used, I would assume,
I know bad thing to do, that MM2 has already decoded the
input streams successfully.

I'll keep thinking and looking. If only the error
message in the event log would tell which function in the
dll is failing it might lead to a better understanding of
the problem.

Thanks for the ideas.
=================================
If you plan to continue working with video,
you may want to consider installing a larger
hard drive and more RAM...2GB is not
unreasonable these days.

I know this could be caused by some highly
technical issue that only NASA could decipher
but the following ideas may help also.

Increasing the size of your virtual memory
paging file may be worth a try. The following
article discusses how:

(308417) HOW TO: Set Performance Options
in Windows XP
http://support.microsoft.com/?kbid=308417

And regular maintenance like Disk Cleanup,
Error Checking and Defrag can make a
difference.

(310312) Description of the Disk Cleanup
Tool in Windows XP
http://support.microsoft.com/?kbid=310312

(315265) How to Perform Disk Error Checking
in Windows XP
http://support.microsoft.com/?kbid=315265
(check the two boxes..."Automatically fix file
system errors" and "Scan for and attempt
recovery of bad sectors") the utility will run
the next time you restart your computer.
(run error checking repeatedly until it finds
no errors)

(314848) How to Defragment Your Disk
Drive Volumes in Windows XP
http://support.microsoft.com/?kbid=314848

Another possible location for memory
hogging temp files is explained in the
following tutorial from Yves Alarie:

Files downloaded from the internet or e-mail
may be in a subfolder of your Temporary
Internet Files folder.

The folder name will start with OLK and
there will be a number after OLK. The easiest
way to find this folder is to search for OLK*
and once found open it and see if the files
are there.

Click on Start and Search and then:
All files and folders
More advanced options
Search system folders
Search hidden files and folders
Search subfolders

In the top textbox "All or part..."
type in exactly this OLK*
and click search

This search will take a while but should
return all folders starting with OLK.

Open the folders, select the files and delete.
They will go to your Recycle bin, delete them
from there also. Or, hold the Shift key down
when you delete them in order to prevent them
from going into your Recycle bin.

--

*********Notice**********
This is not tech support.
....I am only a volunteer...

Solutions that work for
me may not work for you.

Proceed at your own risk.

John Inzer
Picture It! MVP

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

Thanks for the suggestions. I'll try the cleanup stuff first. I can also
write the video clips to a CD and try them on a computer where I work which
has much more RAM and hard drive space.

Of course, I tried to debug the problem with Dr. Watson when it just failed
again and I got a message that Dr. Watson had experienced a problem and had
to close.

Some days it's just better to turn off the PC and watch football for a while.

Thanks again.

Greg
 
Back
Top