Have you contacted Adobe Tech Support?
yes i have and i even got the update and still it doesn't work
i> 256 MB of RAM
Before I upgraded to a computer with a faster processor, a larger hard drive, and more RAM, I got that message frequently.
Premier Elements is resource hungry. Be sure to do a disk clean and defrag often.
Try starting Premiere Elements while holding down the LEFT Shift and Ctrl keys, this will flush the cache and preferences.
Other thing to try with PE3 is to delete your prefences folder in
C:\Documents and Settings\YOUR NAME\Application Data\Adobe\Premiere Elements\3.0 (delete the complete Premiere Elements folder) it will be rebuilt next time you start PE3. Note it might be a hidden file on your PC and so you need to go to into Tools>Folder Options>View and select Show hidden files and folders.
Note that the folder contains any custom preset settings you created, these will be lost.
that didn't work either
It didn't work to contact Tech Support?
And, per the above, did you upgrade to the necessary 1 gig of RAM? It's virtually impossible for this program to run on 256 meg of RAM. In fact, XP can barely run on that!
I'm having the same error message too.
I was rendering a project into a mpeg file when my computer informed me of an update that was available.
It was for a new driver for my video card and this was being downloaded/installed while PE3 was running. My computer crashed and now every time I start up PE3, I get the Sorry, a serious error has occurred.
I dont know if that helps isolate my particular problem but I tried about 5 or 6 of the solutions suggested but to no avail so far.
There are a couple of similar threads, so I will post my solution to you also. This worked when I had the same problem.
I have found a couple of steps for a solutions that worked for the "encountered serious error" message when attempting to share the project to disk or computer file. Here was my solution that worked.
1. I already compiled a project that took me 2 months and used video, photo, music. I added a new video track 'before' the other tracks and inserted a black jpg image, stretch it the entire timeline and make the opacity 0%. This covers any unseen 'gaps' in the project and won't interfere or cover anything else in the project.
2. Go to file - project archiver - copy project to a new folder away from the current folder (this will include a copy of all media used in the timeline of the project - trust me it's worth the duplication!).
3. Go to preferences - clear your media cache. Close the program.
4. Hold down the left ctrl + shift and then click on the Premiere program icon. Keep holding the ctrl + shift until the welcome screen for Premiere appears.
5. Open the new *.prel project you had saved in the new folder in step 2.
6. Go to share and make your disk or computer file.
After trying all the recommendations of the various posts, this is what I found that worked (I didn't find step 2 in a post but was just trying to back up the work I did and found that it created a new *.prel file!). For some reason, when previously trying to share the project with the original *.Prel file, it didn't like having all the media in different folders from the project, even if they were a in a sub-folder within the project folder. It wanted all the media in the SAME FOLDER as the project.
I just now have a new error that I can't find the solution for in support or the forum yet. But that's another post.
I hope this helps someone else!
I am also having this problem and it randomly occurs in several projects that I'm working with (this is with PE4).
I have a fully patched and updated Inspiron 1520 (Vista Home Premium 32 bit) Core 2 duo T7500, NVidia Geforce 8600M (256MB) with 4GB Ram and around 80GB HD space free (fully 'cleaned' and defragged) so it is definitely not a resource or computer power issue.
The 'left shift and ctrl' keys startup option appears to do nothing.
If I look in C:\Users\User\AppData\Local\Adobe there is no Premier Elements folder. However, there is in C:\Users\User\AppData\Roaming\Adobe\Premiere Elements so I deleted that.
I'll let you know if this fixed the problem, PE4 is currently not my favourite application!
- Try this:
- Delete Plugin chache from Registry (HKCU>Software>Premiere Elements>4.0>Plugin Cache)
- Delete old preferences from (C:\documents and settings>Current User>Application Data>Adobe>Premiere Elements>4)
- Launch application and create new project.
I have also crashes of Adobe Premiere Elements 4 under Vista Premium 32bits SP1. I tried a lot of thinks without any success.
As I have dual boot XP/Vista, I would like to mentionne under XP, exact same machine Adobe Premiere Elements run without any problem.
As this problem last for a long time I don't understand why we didn't get a patch from Adobe to solve these crashes which made that product unuseful on VISTA.
Actually, it's Vista that's getting patched, Michel. You should see the roll-out of SP1 in your automatic updates over the next few weeks, which should resolve many of these problems.
In order to ensure Vista is able to update to Vista SP1, it's important that you ensure your drivers and firmware and Quicktime are all up to date, as we recommend dozens of times every day.
hiya is it possible for you to e mail me, you seem to know a lot about pe4, could you please help me, im having no joy with technical support
I'm not sure I can offer much help if tech support can't, Maria. Sorry.
However, updating Windows manually, updating drivers and firmware (including RealTek drivers and Quicktime), optimizing Vista or XP for best performance and having adequate RAM and free, defragmented hard drive space (at least 15% of your hard drive free), as I've recommended above, resolves most problems.
I get a message saying that Adobe premier elements is running short of resources which then shuts me down I have 4gig of ram on a newish Toshiba Satellite laptop with a 250 gig hard drive
Anybody got any answers?
<Brian_Hemmings@adobeforums.com> wrote in message<br />news:firstname.lastname@example.orgNXanI<br /><br />> I get a message saying that Adobe premier elements is<br />> running short of resources which then shuts me down I<br />> have 4gig of ram on a newish Toshiba Satellite laptop<br />> with a 250 gig hard drive Anybody got any answers?<br /><br />Shouldn't happen if Elements is all that you are running at the time and <br />your video is reasonable.<br /><br />What else is running, and what video and pictures are in that video?
And remember, per our FAQs, the most common reason for the program to choke with a lack of resources message is photos used directly from a digital camera rather than optimized for video.
The second most common reason is a poorly maintained computer with outdated drivers and too many "invisible", fragmented files.
Other problems include a Vista or XP system that hasn't been optimized for video.
It's amazing how much information is in the FAQs at the top of this forum! ;)
Same issue with me - running 4 gig RAM. I have done all the trouble shooting posted elsewhere. I get the out of memory error when viewing the timeline (occasionally) and always when trying to export/render/burn. The memory used by the application as well as the virtual memory used gradually climbs during the export/burn process, and the application always crashes when virtual memory hits 1473 meg - and this was after fiddling with the virtual memory setting as suggested and turning off ALL other processes and startup files.
I have several high def .MOV files in the 65 minute project - some last 7-9 minutes. Are these the culprit? I have spent a lot of work editing and hate to start over.
I'd say most likely.
If you convert them to DV-AVIs using Quicktime Pro or the free download Super, they will likely work just fine.
Finally got this to work by chopping up movie into segments by using the "export to DVI" function and using the work bar to define 5-7 minute segments. Virtual memory work peak out at bout 1.4 meg but I could encode a segment before the app crashed. I then started a new project and stiched together all the separate DVI segments, and then burned a DVD successfully.
Next time I will reduce the pixels in the still photos before bringing them into the project.
Nonetheless, after upgrading my P3 800 mhz PC with a new graphics card and 4 meg of RAM, turning every non-essential process off, defraging, etc. -- this program still crashes repeatedly and I cannot get the menu creation to work at all (even with a blank project)
This happens to me too, delete the 2 files in: C:\Documents and Settings\USER\My Documents\Adobe\Premiere Elements\3.0\Styles
Just delete the 2 files in there, & it always works for me, I called tec. support once and they didn't help me, but then one time I called and this guy told me to do this. It worked & when ever I called again no one else knew anything about it. Any ?'s? Email = Lman_92@hotmail.com
I had this problem recently.
The one thing that worked was creating a new user for Windows XP.
Premiere Elements worked for that, but I didn't like having a new user just for that, so I did a system restore to a point where Premiere was working, then uninstalled and reinstalled PE3, now it works fine.
It worked for me- thanks!
Is anybody that is having this problem with VISTA using folder redirection on AppData?
Is anybody that is having this problem with VISTA using folder redirection on AppData?
AFTER USING PREMIERIE ELEMENTS 3 FOR TWO YEARS I STARTED GETTING THE 'SORRY ...SERIOUS ERROR...MUST SHUT DOWN' MESSAGE EVERY TIME I TRY TO OPEN AN OLD OR NEW FILE. I HAVE READ SO MANY ITEMS ON INTERNET ON THE SUBJECT BUT NOTHING SO FAR HAS HELPED. THIS HAS BEEN GOING ON FOR FOUR DAYS, AND I HAVE UNINSTALLED AND INSTALLED MANY TIMES TO NO AVAIL. IS THERE A SOLUTION THAT WORKS? -GREG COX, PHILIPPINES.
Greg, please start your own thread rather than tagging onto this old one. Also, give us more details -- like your operating system and what type of camcorder your video is coming from.
Also, please turn off your Cap Locks. Posts written in all capital letters are very difficult to read.
Welcome to the forum.
Steve makes a very good point about starting a new thread. In an old one, like this, other folks' systems and Projects have been discussed. It is very easy for someone to confuse your problem with someone else's. Though they sound alike, they can be very different. To most effectively handle your problem, a new thread with the proper info will go a very long way to getting it resolved. Take a look at this ARTICLE for some tips on what to put into your new post and why.
Good luck, and we'll be looking for your post,