I just recently upgraded VS 10 Plus to VS 11 Plus. I got a new computer & installed VS 11 Plus on it. And ever since, I have been having, as it seems a lot of people here are having, problems with this upgrade.
Here is one (others to be addressed later) that is driving me totally crazy:
Almost every single time I close VS 11, whether it's by clicking on the red x button on the top right or by clicking File: Exit, I end up getting the error message, "VideoStudio has encountered a problem and must shut down."
Usually I have saved the project I've been working on first, then closed it. I close it being the operative word here. Then next time I open the program, it wants to know if I want to recover the previous project.
WTF? Why is it doing this?
BTW, I tried searching the forum first and while I've found a few threads that are similar, I haven't been able to find anything that is exactly like this problem; but my apologies if this has already been addressed here and I just didn't see it. Thanks.
This happens to me once in a while with v10+ (I have not upgraded). If it only does it after you save your project and close it, and you have no problem when you re-open your project I wouldn't worry about it.
BTW, if you have saved your project I would not use the recover function, I would just "open" the project.
Thanks for the feedback, Black Lab. I'm not worried about it, it's just becoming really irritating, ya know? Cause while it doesn't happen every single time, it happens to me a lot more than once in a while, it's happening most of the time.
At this point, there is some foul language involved when that box pops up helpfully informing me that there was a problem and it needed to shut down and do I want to inform Microsoft of the problem. I'm like NO, I do NOT want to (expletive deleted) Microsoft of the (expletive deleted) problem!!!
And yes, I do just "open" my project, I don't use the recover function.
There was a post on here within the last week or so that told how to turn that error reporting off. I can't find it, but maybe someone else will come along and will know which thread that was in.
I don't have the thread, but it is easy-peasy anyway. In XP, go to Control Panel > System, then choose the Advanced tab. Down in the bottom right of that tab is a button 'Error Reporting'. Click that and you can choose to enable or disable error reporting, with the latter also having the option to at least tell you if an error was critical or not...
Well, I tried Ken's fix and the first time I closed VS afterward, it seemed to have worked because bingo, no error message. But now I am getting an error message again. It is now slightly different--it doesn't ask me if I want to report this to Microsoft, and it includes more info. It says:
"Ulead VideoStudio has encountered a problem and needs to close. Sorry for the inconvenience, blah blah blah. For more info, click here:"
In selecting not to report the error to Microsoft, did you leave the second box (to advise you, the user, not Microsoft, of a critical error) ticked? If so, and you don't want such huge error messages, then untick it...
First, let me introduce my self. My name is Bob and I come from the age of the computer before there were Personal computers (that folks is before 1980).
Second, I was born, raised, lived and will probably die in the Computer Space (although no longer activatily employed in same).
I was there when we could diagonose problems with what they call Core Dumps of IBM mainframe systems that were literally 8 inches high and totally printed in hexidecimal!
Ok, enough of that BS. and now to the problem. PC's have nowhere (at least in the consumer market place) easy tools to diagonose problems. So, many times we have to go on the "seat of our pants".
I installed VS11Plus, and from the get go, I received so many system crashes (in the dionasar world these were called abends (abnormal end ) to where the product was almost unusable (as I even mentioned on this forum).
I triec multiple things to fix it (turned off Error Reporting in Services, did not click on the MS Have to shut down message before saving work, etc.), but nothing worked.
I did not have the proper tools to see what instruction was abending and more importantly where in the source code it bombed out.
So, I had to just start playing.
As the MS messages were deschibing msc80.dll you would think that might be it. But as one of our moderaters pointed out (correctly) this involved another product. Hmmmmmm great error tracking MS thanks Bill>
So, other than trying another product, and after learning somewhat what the product was doing, I decided to drop back to ground zero and start again, but this time in a very controlled envrionement.
I uninstalled every thing to do with VS11 Plus (after I saved my own images and videos in a safe place first.)
I then ran a product to check the registery for bad entries (you determine which one you want to use).
I then created a 0Ulead directory in my My Documents folder. This is where I saved all my projects. No other file went into this directory.
I made sure the Working directory was in the same directory as the program was. I then created librarys using the library manager for all my images, videos, sounds etc. I would make a Bobs Videos in the Videos directory of VS11, I would make Bobs Images in the Images protion. I combined the extra bonus stuff into the correct respective libraries.
If I wanted to use a media file, I would import it to the correct Bobs directory (Images, Videos, sounds, titles etc). I never imported it into the time line.
I made sure (and I am not sure how it got there) that VS11 did not use a Video Studios 11 directory in the My Documents directory.
I am (once again with out diogonistic tools), fairly convinced the high amount of crashes (abends), were due to linkage problems. By putting everything in one place (the Main Program Files Video studio) directories, and by always importing any media files into those libraires, I have totally elimanted any crashes since doing so.
I may have other things to add after posting this, but for now, these are the most salient items for (in my case) problem resolution.
Ken Berry wrote:In selecting not to report the error to Microsoft, did you leave the second box (to advise you, the user, not Microsoft, of a critical error) ticked? If so, and you don't want such huge error messages, then untick it...
I did leave that second box ticked...as a just in case thing, I guess.
The error message itself is not huge until I click on the "expand" link. It's not that the error message is huge. It's that I am still getting an error message and I'd been all hopeful that your fix was the solution. Ah well.
I have VS 11 Plus installed on my C drive, and the working folders are on another drive. (As is advised by Ulead, I think? I seem to remember back when I first installed VS 7 that you should keep the program on one drive and your work on another if you have it).
I do have individual libraries set up in the library manager for all my images, videos, sounds and so forth related to each individual project I'm doing, and anything I import is imported into the libraries.
I don't think the issues I'm having with VS 11 so far are related to crashes because of incorrect linkages, but who knows. I'm just thinking this VS 11 is the buggiest thing since...well...I dunno...
Sorry -- we must have been talking at cross purposes. All I was doing was pointing out how not to constantly get those error messages and referrals to Microsoft. The way I suggested was the way of turning off the referral to Microsoft, but by leaving the other box ticked (to tell you about critical errors) then yes, certainly you will continue to get error message. To avoid them, untick that box...
But if you thought what I suggested would resolve the problem of your VS11 crashes, then no, that would certainly not be the case...
System crashes, apart from those discussed here often happens when VS11+ runs short of memory and / or CPU is unable to cope up. It is therefore advisable to keep SWAP memory size larger for VSP11+ to dump huge chunks of data. Corel knowledge base advises us to keep SWAP file size as : Minimum = 1024 MB and Maximum = 4096 MB.
Again this works best with faster Hard drives and good processors.
Cause while it doesn't happen every single time, it happens to me a lot more than once in a while, it's happening most of the time. 
