VS10 started crashing on Win XP mfc42.dll

[rgbainbridge]

Have been happily running VS10 on my Win XP platform for some time. Recently it started crashing in a peculiar way. Basically the application starts fine and displays the library then as soon as I attempt to access any video file VS10 just exits no error message.

If you look in the Event Manager you find an application error stating that VS10 had an application exception with mfc42.dll being the offending link library.

Has anybody had the same problem I just thought it might be recent Windows update or something that could have caused it. Although I guess I am even more interested in how to resolve!

[mitchell65]

Hello and welcome to the forum
The error message you are getting indicates a registry problem. Some more senior members on this Forum seem to be against the use of a third part Registry Cleaners but I have to say I have used one for a number of years with great success. You can download one such as Reg Cure and scan your system. it will come up with about 400 errors in the registry, all of the progs. always do but to fix the errors you must purchase the software. Hang on here until the bigger brains come on to look at it for you. There may be a better, and some say safer way of solving the issue.

[rgbainbridge]

Thanks for the advice it certainly speeded up the PC. However problem is now very strange.

Basically the VS10 application behaves in the same way e.g. it runs for 20-30 seconds of video and then exits with no error messages.

This time the error message in the Event Log was that the PfMODNT service couldnt be found on Start up but no application error message like before. So cured that one by copying the appropriate drivers from the Creative Programme Directory in Win/System32/Drivers.

However VS10 still behaves in the same way e.g. starts up runs ok till I access a project or video in the library then exits with no errors after 20-30 seconds of playing the video. However now there are no error message in the event log file either. So no real clues on what the problem might be at all!

Anybody got any bright ideas where to look?

[Trevor Andrew]

Hi

Not sure if this related to your problem but Adobe Acrobat Reader gave some problems.

Read this article from chris hargrave ( also West Yorkshire)

Hi everybody
Sorry I have taken so long to continue with this topic....
After recently having numerous problems unrelated to VS (unresponding programs, sound cutting out etc) I finally bit the bullet and did a clean reinstall of Win XP....formatting hard drive etc.
I have then done a controlled reinstall of the programs I use starting with VS 10+.(even before doing all the windows updates including SP3)
On first install VS worked pefectly and subsequently after installing updates and other programs one at a time until.... I downloaded the latest version of Adobe acrobat reader (9.**)
VS promtly started closing again.
uninstalled Reader and VS OK again.
Did this a couple of times with same result.

Then tried Reader 8.1 --Same result.

Now found Version 7 of Reader on an old programe disc (Photoshop elements 5) and tried that.

This time VS worked properly.

So for me it looks like the culprit(s) are the newer versions of Adobe Reader!

Hope that helps.

Chris H

For full post:-
http://forum.corel.com/EN/viewtopic.php?t=34971

[jparnold]

I had a similar problem recently using VS9.
I had been working on a particular project and saved it. The following day when I attempted to load that project VS9 would exit without displaying any error.
After a few unsuccessful attempts in loading the project I decided to load a different project which DID load ok. With the project loaded I then selected the other project (the one I wanted) and it loaded ok.

Why don't you try selecting say an audio file (from the audio library) or an image file an then try to select a video file to see if it will then load ok.

[rgbainbridge]

Thanks to all who contributed. I un-installed Adobe Photoshop and so far that seems to have done the trick, although I have no idea why. Will keep you posted (no pun intended) on how things go, thanks again.