HELP, Movie maker crashes when I attempt to publish to My computer

[Trevor]

I, like most people, have been having some problems with movie maker. My
problem is that whenever I try to publish to my computer movie maker crashes.
I get to the window where you name the file and select the output folder, but
once I press the next button it crashes. The only message I get is "movie
maker has stopped working" and then "movie maker is restarting." I have tried
removing .ax filters from the compatibility menu, no help. I tried publishing
a small clip (40 seconds) with no fades transitions or effects on it, movie
maker still crashes in the same manner as if I were publishing a large
complexe multi-clip piece. I have tried publishing through the task menu and
the file menu with the same results. I have no problems what-so-ever
publishing to dvd, I've done this many times with no problems.

I guess I'm a little perplexed as to what the problem is, I'm no computer
wiz but it seems to me that if it can publish to dvd then it shouldn't have
any problems publishing to my computer. I'm totally lost, I've been to the
papajohn.org and windowsmoviemakers.net, I didn't find any solutions at these
sites. If anyone can help me out or point me in the right direction it would
be much appericiated, thanks.

 

[Trevor]

Can anyone help me out here?

 

[Cal Bear '66]

Go to Control Panel (Classic view) > Problem Reports and Solutions > View
problem history > right click on a problem and select View problem details > use
the Copy to clipboard link in the lower left corner of the details window and
paste into a reply to this thread.


I Bleed Blue and Gold
GO BEARS!

 

[Trevor]

Problem Event Name: APPCRASH
Application Name: MOVIEMK.exe
Application Version: 6.0.6000.16386
Application Timestamp: 4549b5b6
Fault Module Name: StackHash_f3f2
Fault Module Version: 6.0.6000.16386
Fault Module Timestamp: 4549bdc9
Exception Code: c0000374
Exception Offset: 000af1c9
OS Version: 6.0.6000.2.0.0.768.3


Locale ID: 1033
Additional Information 1: f3f2
Additional Information 2: ccaac2bb907d8c8ce645deac808c5977
Additional Information 3: 489c
Additional Information 4: 0111458a532923ed4d94dccd584bb5d1

Tried checking for solutions, no solutions are available.
Let me know if you can help me out, thanks cal bear.

 

[Cal Bear '66]

You should press the "Check for solutions" link to report the crash to Microsoft
and get a bucket number which can be very useful in diagnosing the problem.


I Bleed Blue and Gold
GO BEARS!

 

[Trevor]

All crashes have been reported to microsoft. I have checked for solutions
several times, no solutions are available. What's a bucket number and how do
I get one? Thanks again cal bear.

 

[Cal Bear '66]

When you click on the "Copy to clipboard" link in the lower right corner the
Bucket ID (under Extra information about the problem, at the bottom of the
report details) should be included.


I Bleed Blue and Gold
GO BEARS!

 

[zachd [MSFT]]

Sorry, this is a random crash caused by Voxware MetaSound causing memory
corruption. The file msms001.vwp is on the system, right?

What codec pack did you install to this system from where?

 

[Trevor]

There is no msms001.vwp file on my system. Is this causing the problem, if so
is there somewhere I can get this file?

I recently downloaded and installed a divx codec pack from thier website and
a vista codec pack from the microsoft website.

Thanks for the help zachd, sorry I took so long to respond.

 

[zachd [MSFT]]

What are the specific and exact names of the codec packs you installed?
Codec packs are generally pretty bad plans.

What's the current crash data for your crash?
You don't want that file.

What are the results of WMP's Help:About:Technical Support Information menu
tool?

 

[Trevor]

The file name of the vista codec pack is VistaCodecs_v454 (not sure if this
is what you're asking for). The divx codec isn't a pack just divx codec
6.7.0, sorry for the confusion with that one I know I called it a pack.

Not sure what you mean by crash data, but if you're asking for the problem
signature from the promlem history...

Problem Event Name: APPCRASH
Application Name: MOVIEMK.exe
Application Version: 6.0.6000.16386
Application Timestamp: 4549b5b6
Fault Module Name: StackHash_b7ab
Fault Module Version: 6.0.6000.16386
Fault Module Timestamp: 4549bdc9
Exception Code: c0000374
Exception Offset: 000af1c9
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033
Additional Information 1: b7ab
Additional Information 2: 645ae73cf2b5e8da0c3e4d335f7630d9
Additional Information 3: 6528
Additional Information 4: 141271a624d3a80e32f7b2e942f44eab

Sorry I'm not very tech savy, if this isn't the info you were asking for let
me know.

I'm not sure what results from windows media player you are refering to, I'm
having a problem with movie maker, I think I may have missed something here.

I installed these codecs because I was having the no video in the preview
screen problem with movie maker. After I installed the codecs the problem was
fixed, but I never tried publishing before that so I don't know if movie
maker would have crashed before the install. Should I consider removing all
codecs to and installing new ones?

Thanks again zachd.

 

[zachd [MSFT]]

That still very specifically points to msms001.vwp being on your system. =\

Are vct3216.acm or vct3216.dll on your system? Are voxmsdec.ax or
voxmvdec.ax on your system?

What are the registry *values* under:
HKEY_LOCAL_MACHINE, SOFTWARE\Microsoft\Windows NT\ CurrentVersion\Drivers32
that begin with "msacm"?

 

[Trevor]

Didn't find any of the listed files, I'm using the search in start menu is
there somewhere else I should be looking?

Here's the list from my registry

msacm.divxa32
Value: divxa32.acm

msacm.imaadpcm
value: imaadp32.acm

msacm.l3acm
Value: c:\Windows\System32\l3codeca.acm

msacm.msadpcm
value: msadp32.acm

msacm.msaudio1
value: msaud32.acm

msacm.msg711
value: msg711.acm

msacm.msgsm610
value: msgsm32.acm

msacm.sl_anet
value: sl_anet.acm

msacm.tssoft32
value: tssoft32.acm

msacm.vorbis
value: vorbis.acm

msacm.voxacm160
value: vct3216.acm

 

[zachd [MSFT]]

See the part here:
msacm.voxacm160
? That's the bad part. Delete that registry value or rename it to
"dontuse.msacm.voxacm160". Once that's gone, you should be good to go.

--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Trevor]

Yes! That did it, thank you very much my friend. You have been a great help.
-Trevor

 

[Trevor]

Just finished publishing my first video, everything worked perfectly. Just
wanted to say thanks again.
-Trevor