Printable View
I can load my media into MM and edit my movie no problem, but when I try to
publish my movie to "This Computer", within a few seconds Vista is
complaining that MM is hung and wants to restart it.
Windows Vista Ultimate
NVidia GeForce 9600GS OC
ForceWare Release 100
Version: 100.59
2 GB RAM
Intel Pentium 4 3.2 GHz
any suggestions out there?
any help out there?
I'm running on a Dell Dimension 8400 and get the same problem
What information do you get about this crash/hang in the "Problem Reports and Solutions Center"?
Found this on another forum and it works if you have Nero installed!
Chris Says:
March 6th, 2007 at 1:39 pm
Thanks! For that, I just found that when I updated Nero 7 through the program that it also fixed it !! Try that, that way you can still use Nero 7
RP Says:
March 21st, 2007 at 2:57 am
I have nero 7.5.90 installed on vista. To fix the vista movie maker crash when rendering, I just renamed this folder
C:\Program Files\Common Files\Ahead\DSFilter
Renamed DSFilter to something else. VMM no longer crashes and when I want to use Nero again, just rename DSFilter back to normal.
Two months ago I purchased a new DELL XPS 410, WMM and WDVDmaker worked
great. then all of a sudden NOTHING. Each time I tried to burn, while
ENCODING it would JAM UP. DELL changed my DVD twice, now I can Burn with
WMC but I still can't use WMM or WDVD Maker. Is anyone else having the same
problems?
I am having a similar problem to those noted above. Here is my error message:
I'm no genius at this and any help would be appreciated.
First off, thank you so much for your help. I removed all Voxware and creashed again, but the message changed. Here's the new one:
I'm also curious how you were able to extract voxware out of that coding. If I knew how to do that I wouldn't have to bother you folks quite so much.
Aw shucks, I only have 4 sacrificial chickens and eye of gecko... I guess I'll have to leave the real witchcraft to the pros.
Thank you! It took some digging but I found the file and eliminated it and everything is running smoothly now. Your patience in dealing with me is very much appreciated.
That would be very difficult unless you have five sacrificial chickens
handy. Also, eye of newt. =\
If you wanted to do this yourself, you would want to get the Windows
Debugging SDK, get a welding mask, and cross your fingers. Actually the
Windows Debugging SDK is fairly straight-forward, but that's relative to my
working on Windows for a long time now.
What codec pack installed Voxware to your system?
You can also upgrade to Service Pack 1, which will make this particular
crash go away.
i found this solution to crashing while trying to publis a video!......
you are to rename string value in the registry "msacm.voxacm160" to "no.msacm.voxacm160" its located under HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NT/CurrentVersion/Driver32
now if its not there add it as a new string value....
START > RUN (or windows Key+R)
type: regedit
go to: HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NT/CurrentVersion/Driver32
right click "drivers32" folder > NEW > STRING
type: no.msacm.voxacm160
exit regedit
You should now be able to publish a movie!
Please let me know if this has solved other peoples query
Movie Maker constantly crashes when I click "publish". After it crashes
and is restarted, I can usually publish the video just fine, but
something in my graphics system seems wrong afterwards; that is: after a
crash (even when Movie Maker has been restarted) right clicking on the
desktop brings up a *faded" sub-menu ... when stays faded until the
mouse hovers over the menu. So, it is affecting the system after the
crash as well.
That's not really a crash with that issue - it's a hang. Note the Problem
Event Name is "AppHang". Are you getting any actual crashes? Those are
easier to figure out. You're killing Movie Maker here after it gets stuck
somewhere. I don't *think* anyone in this newsgroup would be able to debug
AppHangXProcB1 hangs for you just based off of that information.
If you think it's your graphics system: what video card do you have? What
driver version do you have? Does the video card maker have updated drivers
on their web site?
What file types are you converting *from* in Movie Maker?
It doesn't really matter to me if it's a hang or a crash , the fact is,
it won't recover, and the program has to be terminated. To me, that's
more or less a crash ... the window area turns transparent white ...
we've all seen it before :( It's very annoying :(
I am using a nVidia GeForce 7600 GT with the latest driver (175.19)
If nobody can help me (I'm surprised that nobody else is having this
problem), then can somebody direct me to an alternative program? There
is mention of another version of Movie Maker.
Also, I didn't mention in the last post: I am importing normal AVI files
from my Canon digital camera, so they are nothing out of the ordinary.
Also, after the program is restarted, I can usually publish the video
without another incident on Movie Maker's part.
I agree that a failure is a failure - I'm just curious there because a crash
is about twenty times easier to debug abstractly than a hang is. If you're
getting an actual crash, I would be much more able to help you. But Papa
just posted up with good advice, so that'd be the next place to go.
The only thing under the compatibility tab was "AVI Decompresser", and
that I had already unchecked, so that wasn't the problem. I've put the
check mark back for now.
Funny thing was that just now, when I opened Movie Maker to check on
this compatibility tab, Movie Maker stopped responding as soon as I
opened the program this time ... I didn't even have to click on publish
:shock:
If you have your setting in Tools > Options > General > 'Open last project
on startup' checked..... rename the project file so Movie Maker doesn't find
it when starting up. If it runs that way it's a clue that it's a corrupt
project file.
Open last project on startup wasn't checked, but it still crashed on me.
Something else must be going on. I wish Microsoft would start making
their own programs work properly. It's a shame, as I really think Movie
Maker is a nice simple tool for making quick video to upload to youtube.
I don't know what else I should be checking for. I don't have Nero
installed, so it can't be a problem with that. Any other suggestions?
My website's Problem Solving > Crashes and Hangs page has all of my
suggestions...
Okay I have read several different options on how to fix my movie maker
that crashes when I publish. I have already unchecked all the
compadabilty things, also I ahve tried the volume control instead of
mute when I edit my video. Im running a dell inspiron 530s with vista
home premium 32-bit and I'm going crazy trying to fix this. I even went
so far as to download the movie maker 2.6 and it wont work either
although I get an entirely different problem with it. Movie maker works
fine for me on my xp laptop just not on this ^&*^(*%^$%@# desktop.
What are the formats of your source files?
Is this a large project with many effects and transitions?
Are other programs running while you are using Movie Maker?
No other programs running, source files are jpgs, mpegs, maybe 20 clips
and pictures, mostly fades form one to the other and a bit of text over
video. That's about it.
i had the same problem. but then i found this, and it worked for me.
Windows movie maker for vista has a bug. In the bug, it will always crash when you try and publish it in any way, if you have muted the video's own sound. Basically, if you recorded a blooper to a video song (like me :P) and you want to overlay the actualy song and take off the video sound because you spoke in it for example, when you click on the video expand and choose mute on the right click menu for audio, it will crash when trying to publish. To work around this for now, right click audio under the video menu and choose volume. then instead of checking mute, slide the volume bar all the way down. You should now be able to publish your video! if you're interested in my videos btw. Hope this helps people, as I couldn't find any help on google, this should be added up soon and hopefully a fix released from microsoft.