ulead Has Encountered an Error and Must Close

[alfredo_gz]

Hello Friends,

I've installed the ulead studio 11 in my Intel Core 2 Duo but im getting this error when i open the software... :
Has Encountered an Error and Must Close

what can i do?

[Clevo]

You try re-installing it.

Did you have any problems during the installation?

Are you installing from CD's or from Download?

What is your system specifications?

[heinz-oz]

Just the other day I got that error with any program I tried to run, not just Ulead's. Had to change the power supply to fix.

Once, on a new PC, just built, I couldn't install Win XP. The system told me that the CD was faulty. Turned out a faulty memory stick was to blame for that one.

What I'm trying to say here is this: It ain't necessarily the obvious and seldom the program which causes the error to appear. It could be hardware also.

You can only find out by elimination. A clean install might do the trick. Failing that look at your memory (run a memory tester, available at the MS web site) and scan your HDD's for errors. Check your DEP settings as well.

[screwball2]

Have had this message constantly from UVS9 through to 11. Not the computer, changed it twice. Not underpowered - quite the opposite. I have noticed though, that if you can ignore the message and slide the pop-up to one side, you can happily continue working and saving. Recently I discovered that by turning off windows 'Error reporting' for a while it cured the problem, but I'm afraid it returned, but to a lesser degree. What I would give to be rid of this annoyance. Like me you could try other software, but at the end of the day, for me UVS has no equal, so like any other aspect of life, one has to accept the wart on an otherwise super programme. If you DO find the solution, I believe you will be in line for a Nobel prize, cos in three years I have yet to solve the frustrating problem, and I suspect no-one else has? If they had the queen would have declared a UVS bank Holiday. Obviously, there are many that do not have this problem, if only we could establish the difference between the have's and have nots!(

[lancecarr]

I used to have this problem too on both VS9 and VS10. My solution for 10 was to create a separate "video editing" hardware profile per the instructions written by sjj1805.
Instructions for that are here:
http://phpbb.ulead.com.tw/EN/viewtopic.php?t=13950

In addition to that I am meticulous about defragging prior to capture, after capture and after rendering to a DVD compliant MPEG2 file prior to burning. I also make sure my work flow means that I am not rendering to the same hard drive that has the raw footage on it.
In short, I try to place the minimum stress possible on the system even if it takes a little longer to do things.

[screwball2]

Thanks for the reply, but have done all these things including a seperate bootable hard drive just for ulead - and much more. I believe the answer is very, very simple - but I don't know what it is???? ('')

[2Dogs]

Have had this message constantly from UVS9 through to 11. Not the computer, changed it twice.

Hi screwball2,

unfortunately, you can't rule out a problem with the hardware simply because it occurred on two of your pc's. It's entirely possible that something you do, or some software you install causes the problem. I can say I've had VS7SE Basic thru VS11+ installed on five pc's and cannot recall getting the error.

I know that many programmers are irritated by the lack of debugging ability in Windows, but the event viewer logs can sometimes give you a clue.

Setting up a dedicated profile should help - but I wonder if there are users out there that still insist on having stuff like instant messaging enabled when editing - I could see that being problematical. I've also always turned off system restore and the indexing service. Maybe the fact that you can ignore the pop-up and carry on working without losing the project indicates that it is a problem conjured up by Windows, perhaps some conflict with a default Windows service.

[Hollywood Gothique]

I have been getting this message a lot, too, but with an odd peculiarity: it seems to pop up when I am adding titles to a video.

It also happens when I am trying to render a DVD-compatible MPG2 file that includes titles.

MPG1 files - VCD or SVCD - work fine. So I assume the problem has to do with the amount of stress being put on the system.

The thing is, I never had this problem on my six-year-old rundown computer, only on the brand-new one I'm now using.

Can subtitles really be adding that much strain, so that ULead has to shut down?

[screwball2]

I omitted to say that, rather like the previous post, my wifes steam driven laptop running UVS9 has no problems whatsoever!!! (Nothing so irritating as a very smug wife - should bring back ducking stools) so as you say I have something installed somewhere that vs doesn't agree with. It's just pinpointing the problem.

[Ken Veal]

Have you tried a disc clean up to get rid of all the temp files ?

[Hollywood Gothique]

I have tried a disc clean-up and defraging the hard drive. Now, ULead takes a few seconds longer before delivering the dreaded error message.

[Ken Veal]

Make a note of the files concerned that will display when you go to the details in the error message dialogue box and post them here so that a learned member may be able to help with the problem

[Hollywood Gothique]

According to the error message, the file in question is:

C:\DOCUMEN~1\STEVE\NEWLOCALS~1\TEMP/5150_appcompact.txt

The "Exeption Information' is:

CODE0x0000005
FLAGS: 0x00000000
RECORD: 0x0000000000000000
ADDRESS: 0x000000007E41B5BA

[Ken Berry]

It seems strange that a text file should be causing any sort of problem. Have you actually found that particular file in that Temp folder and deleted it (and anything else there -- I know you say you have cleaned out the temp folders but Vista has them in a different place to XP... And if it is telling you it is causing the error, then obviously it is still there)?

[Ken Veal]

Ken,
You replied to a post of mine in OCt 2005 that was asking the exact same question re VS9 with the same type of .txt file in the error message
(That one had a different number though) .Dont know what this proves but there must be a continuing problem for this to happen agian.
regards Ken V