I read where someone else had this problem, and ultimately he solved it by re-formatting his hard drive and starting over. Well, that's not an option here, so I will pose the question again:
Why am I receiving a "VideoStudio has encountered an unexpected error and must close" message when I FIRST RE-BOOT my computer? I have NOTHING in the start-up folder that has anything to do with Video Studio. I don't understand why anything from VS should even be TRYING to load when I first start-up.
I am still using the trial version, as I don't want to purchase the program if I am going to have to deal with this all of the time.
I love Ulead products--and use several of them--and this is the first time I have encountered a problem like this.
And yes--everything is up-to-date on my computer, including DirectX, etc.
Thanks for any help anyone might offer.
LadyJack
Error Message on Windows Start-up
Moderator: Ken Berry
-
sjj1805
- Posts: 14383
- Joined: Wed Jan 26, 2005 7:20 am
- System_Drive: C
- 32bit or 64bit: 32 Bit
- motherboard: Equium P200-178
- processor: Intel Pentium Dual-Core Processor T2080
- ram: 2 GB
- Video Card: Intel 945 Express
- sound_card: Intel GMA 950
- Hard_Drive_Capacity: 1160 GB
- Location: Birmingham UK
Check the following 2 registry locations
(Windows Start button | Run | Regedit)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
These locations contain things that will run at startup - just like the location
Windows Start button | All Programs | Startup
To be on the safe side export the above two registry locations (File | Export) - your desktop will be a handy location so that you can easily find them again. They can be deleted when they are no longer required.
Right click an entry that you think might be causing the error and delete the entry.
If you need to restore the deleted entries then double click the registry files you created above.
If this still fails to cure the problem then take a look at this link:
Troubleshooting your computer
(Windows Start button | Run | Regedit)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
These locations contain things that will run at startup - just like the location
Windows Start button | All Programs | Startup
To be on the safe side export the above two registry locations (File | Export) - your desktop will be a handy location so that you can easily find them again. They can be deleted when they are no longer required.
Right click an entry that you think might be causing the error and delete the entry.
If you need to restore the deleted entries then double click the registry files you created above.
If this still fails to cure the problem then take a look at this link:
Troubleshooting your computer
-
ladyjack
-
skier-hughes
- Microsoft MVP
- Posts: 2659
- Joined: Thu Jul 21, 2005 10:09 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: gigabyte
- processor: Intel core 2 6420 2.13GHz
- ram: 4GB
- Video Card: NVidia GForce 8500GT
- sound_card: onboard
- Hard_Drive_Capacity: 36GB 2TB
- Location: UK
ladyjack wrote: Now what?
Thanks!
LadyJack
sjj1805 wrote:Check the following 2 registry locations
(Windows Start button | Run | Regedit)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
These locations contain things that will run at startup - just like the location
Windows Start button | All Programs | Startup
To be on the safe side export the above two registry locations (File | Export) - your desktop will be a handy location so that you can easily find them again. They can be deleted when they are no longer required.
Right click an entry that you think might be causing the error and delete the entry.
If you need to restore the deleted entries then double click the registry files you created above.
If this still fails to cure the problem then take a look at this link:
Troubleshooting your computer
-
ladyjack
I dont know if this is related (other than mfc80)
My VS 11 Plus is almost unusable. I have to do a save every few minutes after doing just a couple of things with the movie. If I dont, all of a sudden the application freezes and the standard msg about encountering an error and has to close comes up.
What is interesting is that if I click on the message to see it, everything ends and I cant try to determine what happened.
However, if I first close VS11, I can then click all I want on the error screen to see the modules involved; I tcopied down the modules involved.
AppName: vstudio.exe AppVer: 11.0.0.0 MonName: Mfc80.dll
ModVer: 8.09.50727.762 Fooset: 0030293
I am putting the message here in hopes someone can shed some light on this subject.
I have seen numerous posts about the consistant VS11 crashes and it is most disconcerting that Ulead/Corel will not place emphasis on problem resolution.
Anyway, does anyone have any ideas?
Thanks in advance,
Bob
What is interesting is that if I click on the message to see it, everything ends and I cant try to determine what happened.
However, if I first close VS11, I can then click all I want on the error screen to see the modules involved; I tcopied down the modules involved.
AppName: vstudio.exe AppVer: 11.0.0.0 MonName: Mfc80.dll
ModVer: 8.09.50727.762 Fooset: 0030293
I am putting the message here in hopes someone can shed some light on this subject.
I have seen numerous posts about the consistant VS11 crashes and it is most disconcerting that Ulead/Corel will not place emphasis on problem resolution.
Anyway, does anyone have any ideas?
Thanks in advance,
Bob
-
andvar
VS 11 crash at opening
I have the same problem as Bob, with the difference that:
1. it crashes with "VideoStudio has encountered a problem and must shut down." message within 0-5 seconds after opening
2. after 1 to 3 reopenings the application is running correctly
I am also waiting for a solution...
Andvar
1. it crashes with "VideoStudio has encountered a problem and must shut down." message within 0-5 seconds after opening
2. after 1 to 3 reopenings the application is running correctly
I am also waiting for a solution...
Andvar
