View Full Version : Neo HDV causing Windows Live Messenger to crash


John Telleria
January 6th, 2008, 01:14 AM
I just downloaded and installed tonight the 15-day trial of Neo HDV so I could try it out with my new Canon HG10's AVCHD recordings. It's the latest build of Neo HDV. As soon as I installed Neo HDV and rebooted my system, Windows Live Messenger stopped working. Windows Messenger won't start up during bootup or trying to manually start it. It immediately crashes with the "Windows Live Messenger has stopped working" popup dialog. I also get a "Ulead Video Studio 11 has stopped working" error popup during system bootup. That error also started happening after installing Neo HDV. I'm running 32-bit Vista Ultimate Edition and Windows Live Messenger version 8.5.1302.1018. I uninstalled Neo HDV. Windows Live Messenger started working again, and the Ulead error also went away. Is anyone else having this issue with latest build of Neo HDV causing Windows Messenger to crash?

Matti Remonen
January 6th, 2008, 09:59 AM
I actually got the same behaviour from Messenger while testing with NEO HDV 3.2 build 150. It also crashes Sound Forge, could these be related?

My setup:
Intel quadcore Q6600; Intel BadAxe Mobo; 4 GB RAM; Vista Ultimate

Bill Ravens
January 6th, 2008, 10:02 AM
Hmmm...b150 is crashing soundforge for me, as well. glad I'm not alone ;o)

John Telleria
January 6th, 2008, 10:52 AM
Is the previous build of Neo HDV available for download? I'd like to see if that version behaves with Live Messenger. It wouldn't be a big deal if I had a dedicated PC just for editing video where I wouldn't need Messenger installed. But on this PC I do use Messenger a lot for communicating with family/friends and co-workers when I'm telecommuting. So it definitely is a dealbreaker if Neo HDV can't co-exist with it. Hopefully this issue gets resolved in the next build.

John Telleria
January 6th, 2008, 11:14 AM
I forgot to mention earlier that the uninstallation for Neo HDV build 150 is crashing everytime. It never gets to completely finish uninstalling. During the uninstall I get the popup Windows error dialog "Au_.exe has stopped working. A problem caused the program to stop working correctly...". Enough of it does get uninstalled though to get Messenger working again.

Matti Remonen
January 6th, 2008, 11:30 AM
I believe that when David Newman chimes in here he will be able to provide the earlier version for you. I do have the version myself, but I would like to know what is Cineform's standing concerning this kind of requests (i.e. can we lowly end users provide earlier versions for other people).

Bill Ravens
January 6th, 2008, 11:33 AM
If you guys have read my original post concerning soundforge, you'd see that David is working as fast as he can on this issue. If he takes today off(sunday) it's ok with me. I've reinstalled build 148 and soundforge works fine. Don't know about messenger.

John Telleria
January 6th, 2008, 12:00 PM
If you guys have read my original post concerning soundforge, you'd see that David is working as fast as he can on this issue. If he takes today off(sunday) it's ok with me. I've reinstalled build 148 and soundforge works fine. Don't know about messenger.


I definitely wasn't expecting a resolution this weekend. I work in software development myself and know these bug fixes can take time. My workaround for now is to uninstall Neo when I'm done testing with it.

Matti Remonen
January 6th, 2008, 12:38 PM
Yeah. If just all the sw would have the same level of support as Cineform people give us. So far I have had only 100% positive experience with CF people.

Alan Mills
January 7th, 2008, 03:41 PM
For the record, Windows Live Messenger has also stopped working for me after installing latest build of Aspect HD. Build 103. Uninstall build 103 and messenger works again.

Bill Ravens
January 7th, 2008, 03:48 PM
There's another thread reporting the workaround. The culprit causing the trouble is "AJACapturefilter.ax" Unregister this from your computer to fix the other problems. If you're using an AJA capture card, obviously this workaround has problems.

David Newman
January 7th, 2008, 04:27 PM
The problem doesn't occur if you have an AJA card. New build going up today.

Alan Mills
January 8th, 2008, 03:20 AM
There's another thread reporting the workaround. The culprit causing the trouble is "AJACapturefilter.ax" Unregister this from your computer to fix the other problems. If you're using an AJA capture card, obviously this workaround has problems.

D'oh! I read that other thread as well. I just never put 2 and 2 together properly.

David Newman
January 8th, 2008, 10:14 AM
New builds went up yesterday. All is working again.