Extract Edit Across a Dissolve causes Serious Error Crash

Hoping that:
1 - There's an update soon - it's been a while since we've had anything significant.
2 - This particular bug gets addressed.
I'm on a new Mac Pro - 64 GB Dual Hexacore 2.93 GHz. Running Raid 0 internal with a Blade SSD in the 16x PCI slot. Other than Chrome, Motion (To get the Pro Codecs) and the Adobe Suite, I've installed nothing else on this rig. Software updates are latest version
Quadro 4000 updated to latest published non-beta CUDA drivers.
I'm doing trim edits on a feature. The timelines I'm working in are about 6 minutes long (Broken up by sequences). Working in ProRes 422.
Issue:
When I try to do an extract edit and either the in or the out point touches an audio dissolve, I get a Serious Error Crash.
My current Work-Around is to remove all the dissolves before I extract - but I have 8 channels of Audio and its an action film, so there's a LOT to remove.
Eager for an update.

Since this is a new rig, I'm assuming this is a PPro CS6 installation you're referring to?

Similar Messages

Exporting an already-rendered Sequence causes serious error.

Several times, I have tried clicking File->Export->Media, and suddenly adobe premiere pro would tell me that a serious error has occurred and then the program closes. This was during a 1280 x 1024 square pixel resolution video. I have not tested any other resolution. This error would occur if I had rendered my media and then clicked File-Export->Media. If I delete the render files and then click File->Export->Media, the adobe media encoder runs fine and no problems are seen.
I am running Windows Vista Ultimate 32-bit
Thank you for your help!

On your timeline you should see a colored strip on the top of your sequence. If its red you have to render. If its green then you are using a dynamic preview that allows you to watch things at real time.
To be sure everything is rendered click on:
Sequence>Render All
Then make a CHECK next to all the selections. Click back on your sequence and press option+R. This will render everthing in your sequence bypassing realtime effects and should allow you to export your file.

Serious Error crashes CS and CS2 when importing XML

Hello,
I'm trying to import XML carrying text and images into a 130+ page brochure. I have been working on it for several weeks and have been re importing the XML successfully although something has changed.
Now when I try to import I get an error message and InDesign closes.
I've created new blank documents to test it and the initial import works fine. Although after items have been placed and tagged a re import causes an error message to pop up that states: Indesign has discovered a serious error and is shutting down.
There is nothing that we can see in the code that would cause this. We were trying to overcome a formatting issue and had tweaked the XML. but even after we returned the XML back to its original form we still get an error message. even in new test documents.
Any ised?

I don't work with XML, but in my experience, "serious errors" are often caused by bad fonts.
You might want to try changing the fonts in the code and see if that helps. You should also look through the error logs to see if you can isolate the module causing the problem. There should be a log in the InDesign application root folder, even if there isn't one in Event Manager.
Peter

InDesign Serious Error, Crashing

I was working on an InDesign file and the program suddenly shut down. When I attempted to reopen, it immediately crashed and gave me the message that a serious error has occurred. I have tried deleting preferences from my Library, made sure I'm using the most updated version, that my OS is updated, but I'm stuck. It's now 2:40 and I'm working on a proposal that's due by the end of the business day. HELP!!! Oh, I'm using Mac OS X Mavericks on a MacBook Pro Retina Display.

Empty the InDesign Recovery folder and you'll be able to restart ID, though your file may be toast at this point.
The folder is hidden in Mavericks, so see Access hidden user library files | Mac OS 10.7 and later if you don't know how to look in your user library.

Pro CC 2014 constantly has "serious error" crashes - forces me to make new projects

Since upgrading to PP CC 2014 - doing the most basic operations (dragging a clip from source to timeline) the app shuts down - gives "Serious error, will attempt to save current project" dialog, then on relaunch prompts to "open previous project," then I get "opening recovery project, but we make no guarantees, please save to a new file."
Which I do, but it happens all over again after. Super frustrating, as you can imagine. I'm on a 2014 iMac 16g ram, 3.2 Intel core i5 OSX 10.9.4

Adobe support has been a catastrophe for me today. Had a chat with a rep, they said they'd call me to talk it through, hours passed, no call. I called them, and had a tech try to fix my issue for almost 2 hours. Finally "fixed" it. Turned out it was one of the mouse pointer icons that is used by PP was missing in my prefs file, so every time I did certain mouse actions, when that pointer icon was needed the whole app crashed. Um, ok.
But now the issue is back.
Also when he took over my computer, he zeroed out a ton of my other user settings on my computer - a time killer for me. Add to that I get auto support emails from a "do not reply" account saying that if my issue isn't resolved to reply to the email. Plus today CC login was just screwed, so my TypeKit fonts were all inaccessible.
How is it possible for your support to be this bad, Adobe?

Editing titles or clicking on clips causes serious error

Problem with new mac mini (purchased two days ago), no problem on iMac (with
same software install, checked with system profiler). Tried with two mac minis
(replaced the just purchased one with a replacement after a discussion with a genius)
Mac OS X : 10.5.7
iMovie 09' : 8.0.2 (741)
Editing titles/text, changing titles/back ground lengths causes. Could be associated with generally clicking on clips (possibly double clicking)
1) Loss of control of inspector window
2) Inability to share the video (the options are greyed out)
3) Inability to return to the project selection window
4) Inability to add more titles/backgrounds
5) Inspector seems trapped in a strange state, unable to close
iMovie reports the following messages via console(as example)
18/05/2009 16:23:11 iMovie[325] NSMutableRLEArray objectAtIndex:effectiveRange:: Out of bounds
this error repeats many times.
Anyone please help!

Since this is a new rig, I'm assuming this is a PPro CS6 installation you're referring to?

Kernel panic defeated, 'serious error' remains

Hi,
As most posters around here, I've been having severe problems with Premiere Pro 6.02 on OS 10.7.4 FW800 drive, eSATA external drive for project and clips, Macbook Pro 8,3 (early 2011, 16GB RAM, AMD Radeon HD 6750M 1024MB). The project is 1080p50 AVCHD material and psd stills. I'm using Mercury and I have set the System to never use Intel graphics.
The major hurdle was apparently random kernel panics, especially when I tried to scrub using the left/right arrow keys.
That problem was solved when I followed the advice of a poster in this forum, who created a fresh admin account. No more kernel panics!
The 'serious error' crashes remain and are easily recreated:
• I double click a clip (AVCHD or still) in the Timeline to load it into the Source monitor.
• I close the Source monitor by clicking in the 'x' close box in the upper r/h corner.
BAM!
Luckily, Premiere manages to save the file before shutting down and the file is good to go. The original project file causes a kernel panic if I try to open it, though.
However, I can unload the clip in the Source monitor by using Close in the drop-down.
Also, I can close the Source monitor after it's empty by clicking on the 'x' – no crash.
So, it's the act of clicking on the Source monitor 'x' icon when it's loaded with a clip that triggers the crash, every time.
I suspected that the Microsoft IntelliMouse driver might be the culprit and uninstalled it. Didn't change anything.
I take the liberty of attaching the crash report below, in the hope that someone with better log reading chops than I can spot some crucial lead.
Best regards,
Joachim
Process:
Adobe Premiere Pro CS6 [891]
Path:
/Applications/Adobe Premiere Pro CS6/Adobe Premiere Pro CS6.app/Contents/MacOS/Adobe Premiere Pro CS6
Identifier:
com.adobe.AdobePremierePro
Version:
6.0.2 (6.0.2)
Code Type:
X86-64 (Native)
Parent Process: launchd [259]
Date/Time:
2013-02-26 15:31:01.999 +0500
OS Version:
Mac OS X 10.7.4 (11E53)
Report Version: 9
Interval Since Last Report:
19955 sec
Crashes Since Last Report:
5
Per-App Interval Since Last Report: 16869 sec
Per-App Crashes Since Last Report:   3
Anonymous UUID:
120ECC69-5B41-4EFF-A88F-2D877C7A261B
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
VM Regions Near 0:
-->
__TEXT
0000000100000000-0000000100004000 [   16K] r-x/rwx SM=COW /Applications/Adobe Premiere Pro CS6/Adobe Premiere Pro CS6.app/Contents/MacOS/Adobe Premiere Pro CS6
Application Specific Information:
objc[891]: garbage collection is OFF
abort() called

First off, upgrade to 10.7.5 without delay. Pr much prefers that to any other 10.7 build.
KPs are almost always driver related. Run Disk Warrior after each KP. Reinstall new drivers if that doesn't help. Which one? The one you installed right before your KP.
Serious Errors on my system are almost always related to corruption in the Media Cache. Deleting the contents usually sends them on their way, for a while.
Delete your Pr prefs at any sign of weirdness. I need to do this frequently (several times a week), so I use Digital Rebellion's Preference Manager.

While editing metadata, "After a serious error, Premiere Pro will now exit."

Hello all,
So here I am, starting on a new project with Premiere Pro CS6.0.0 (319 (MC: 264587)). Using a slightly modified "metadata" workspace, I go on to editing info about all my 300 clips - scene, shot, description, remarks ...
And every now and then (sometimes right after I started, sometimes more than half an hour later, and sometimes anything in between) I get this unhelpful message that "After a serious error, Premiere Pro will now exit. The program will try to save your work" (I'm translating from French, so this might not be 100% accurate). I have not identified a particular action that causes that (i.e. editing a specific metadata field or whatever).
My clips are in a normal folder, nothing fishy here I don't think (except that the search bar is greyed out, which renders my metadata campaign fairly useless - will make another post about that). I am not using any plugin or patch (not knowingly at least). I run Mac OS 10.9.4 without known problems. I have 12 Go out of 621 free on my hard drive, 8 Go RAM, and AMD Radeon HD 6750M graphics card with 1024 Mo VRAM as well as an Intel HD Graphics 3000 with 512 Mo VRAM (chosen depending on energy needs vs. computation needs).
Any clues ? For example, can I find an error or activity log from Premiere Pro ? Thanks in advance.
Charles
EDIT : Here an error log, from the OS : Error log : Premiere Pro Crash - Pastebin.com
EDIT2 : looks like it's scrolling through the clips in my main bin that's the problem ... Is that even possible ?
EDIT3 : Definitely the scrolling.

Your error report indicates that Photoshop is not up to date. Choose Help>Updates... and update to 11.0.2
I'd also try restoring your prefs: http://adobe.ly/PS_Prefs

Itunes causes a "itunes has encountered a serious error and needs to close"

Ok everytime i try to open up itunes it immediatly opens up a window that says itunes has encountered a serious error and needs to close....i send the error report microsoft directs me to check out that apple page to uninstall qt and then repair...i have tried everything that i read in these forums, even the one where it says to go into dos mode(F8 to get to safe mode) and delete the files that have a random 4 or 6 letter file ending in .exe
i am at my whits end here please help i need my itunes
by the way it worked fine when i first installed it for about 2 days then i get nothing...

oh yeah and when i go to uninstall it from add\remove programs when the wizard comes up and is running i get that same error and needs to close message, but i doenst effect the uninstall wizard(i dont think)........PLEASE HELP

Sorry, a serious error has occurred... Rant and a solution

Warning. Much of this post is frankly a rant against a poorly written program and the so-called experts who offer up solutions here. If you are one of these experts and you have a thin-skin, don't read this post.
If you just want a solution to the problem skip to the bottom of the post.
INTRODUCTION
Adobe, I want my money back! I rarely buy Adobe products and always wind up regretting it when I do. This product was no exception.
I tried the trial version. Bought the product along with Photoshop Elements as part of a promotion.
Produced a couple of videos with it, no problems. Then, inexplicably, it stopped working for me and I would get the infamous "Sorry, a serious error has occurred..." message while trying to start or open a project. This would happen almost immediately, as it was drawing its intial screen layout.
MY FIRST BIG COMPLAINT... USELESS ERROR MESSAGE
This has to be the most useless error message I've ever read. The few times I've had programs crash on me, the error message that results usually gives me enough clues to find and fix the root problem.
ONWARD...
Uninstalled it with Revo Uninstaller, re-installed it.
Deleted all old project files.
Tried to re-start by clicking 'New Project' button.
Prompts me for a location for the project. I accepted the default.
Immediately gives me the "Sorry, a serious error has occurred..." message and shuts down when I press okay.
MY SECOND BIG COMPLAINT... INCOMPLETE UNINSTALL
I did observe that when I went to use the Organizer after the re-installs, the thumbnails of previous videos were still there. Clearly some cache wasn't removed during the uninstall.
If a cache wasn't removed, perhaps other remnants of the the program were still lying about on my machine. If they were the problem, then no amount of uninstalling/ re-installing would solve the problem.
CONTINUING...
At this point, I came to the forums for help and my worst fears were confirmed. This error message is a common problem. The suggestions to solve it were all over the place. The sheer depth and width of this faultfinding indicated to me that this is a seriously buggy piece of software.
With one or two exceptions it seems that nobody ever resolves this problem.
MY THIRD COMPLAINT... WELL-MEANING BUT UNHELPFUL 'SOLUTIONS'
These are some of the typical solutions I read on these forums:
- Your computer is probably underpowered. Give us a list of all your specs.
- Your computer doesn't have enough hard drive space. Give us a list of all your specs.
- Your computer doesn't have enough RAM. Give us a list of all your specs.
- Something on your computer has 'changed'. Give us a list of all your specs.
- Your hard drive is dying. Back it up quick!
- It's probably your anti-virus software. Turn it off.
- Some of your drivers are probably out of date. Update them all. Give us a list of all your specs.
- That's a different issue... start a new thread. (Lame...)
Most of that advice is... well, lame. It's pretty obvious that these people are just winging it, i.e. throw everything up there and hope something works. Sorta like that tech guy on the support line who always ends up telling you to 're-install the program' because he really has no clue what the problem is and just wants you off the line.
As someone who has used video editing programs for years, I'm here to tell you that the problem is rarely the computer specs. The specs listed by Adobe for this program aren't that onerous and my three-year-old Dell 1525 laptop with less than 20 megs of space on its 136 HD and 2 megs of RAM was able to produce videos with no problem.
Most computers sold within the last three or four years are pretty robust and should have no problem with consumer level video editing.
Sending people off on a quest to 'fix' their computer and research a lot of computer specs is a time-waster. That should be the LAST thing you recommend after first eliminating the program as a problem.
ONLINE SUPPORT
This is worthy of its own post, but I won't bore you here. Suffice it to say that Adobe tech support deserves some sort of industry recognition for its ineptitude.
MY SOLUTION
First, let me reinterate. The problem is probably the buggy program and not your computer, assuming your computer is relatively new and mid-range or better.
In my case, the clue was in the fact that not all of the program is uninstalled when you try to do a uninstall / re-install. The program likely had some sort of corrupted cache that stopped the program and that remained after an uninstall.
I unstalled it again, but after some research I came across this tool:
Adobe Creative Suite Cleaner Tool at http://kb2.adobe.com/cps/829/cpsid_82947.html
and this reference:
http://kb2.adobe.com/cps/859/cpsid_85966.html
The reference above applies to Photoshop, but the Organizer elements applies to Premiere unintalls as well.
After applying these two solutions and then re-installing, my Premiere Elements is working once again.
Had I followed the typical advice I would have spent days updating drivers, installing RAM, de-fragging and cleaning up my hard drive, listing specs to post here, etc. And none of it would have mattered a wit.
The program is still buggy though and my original problem may re-occur, I admit. I will certainly never buy another version of this POS program again, but, in the meantime, I hope I can save someone here some time in looking for a fix for their own message.

Your post count is 2 (as I write this) beginning July 17 - which indicates to me that you never asked for help in this forum (or you did so under another name)
As Steve said (and which you may not have known) this is not Adobe support, this is a place provided by Adobe for users to try and help each other
Yes... Adobe has less than good telephone support... a year or so ago that was even admitted to by the Adobe CEO, with discussion of that over in http://forums.adobe.com/community/general/forum_comments or maybe it was http://forums.adobe.com/community/general/forum_comments (been long enough ago that I don't really remember)
If you do have future questions... come back and ask and someone will try to help
Just as advance notice... don't come in saying "my file won't work... why?" without providing details... such as
This is not pointed at you, at least right now... this is just for the future
More information needed for someone to help http://forums.adobe.com/thread/416679
Some specific information that is needed...
Brand/Model Computer (or Brand/Model Motherboard if self-built)
Build a Configuration file http://forums.adobe.com/thread/877653?tstart=0
How much system memory you have installed, such as 2Gig or ???
Operating System version, such as Win7 64bit Pro... or whatevevr
-including your security settings, such as are YOU the Administrator
-and have you tried to RIGHT click the program Icon and then select
-the Run as Administrator option (for Windows, not sure about Mac)
Your Firewall settings and brand of anti-virus are you running
Brand/Model graphics card, sush as ATI "xxxx" or nVidia "xxxx"
-or the brand/model graphics chip if on the motherboard
-and the exact driver version for the above graphics card/chip
-and how much video memory you have on your graphics card
Brand/Model sound card, or sound "chip" name on Motherboard
-and the exact driver version for the above sound card/chip
Size(s) and configuration of your hard drive(s)... example below
-and how much FREE space is available on each drive (in Windows
-you RIGHT click the drive letter while using Windows Explorer
-and then select the Properties option to see used/free space)
Windows Indexing is BAD http://forums.adobe.com/thread/676303
While in Properties, be sure you have drive indexing set OFF
-for the drive, and for all directories, to improve performance
Some/Much of the above are available by going to the Windows
Control Panel and then the Hardware option (Win7 option name)
OR Control Panel--System--Hardware Tab--Device Manager for WinXP
And the EXACT type and size of file that is causing you problems
-for pictures, that includes the camera used and the pixel dimensions
Plus Video-Specific Information http://forums.adobe.com/thread/459220?tstart=0
Read Bill Hunt on a file type as WRAPPER http://forums.adobe.com/thread/440037?tstart=0
What is a CODEC... a Primer http://forums.adobe.com/thread/546811?tstart=0
What CODEC is INSIDE that file? http://forums.adobe.com/thread/440037?tstart=0
Report back with the codec details of your file, use the programs below
For PC http://www.headbands.com/gspot/ or http://mediainfo.sourceforge.net/en
For Mac http://mediainfo.massanti.com/

Error Message: Sorry...serious error PRE 7 must shut down

PRE 7 was running well. In fact I edited four movies successfully.
But now whenever I attempt to Open Project or New Project I get the message:
"Sorry...serious error encountered...must shut down.
It is really frustrating to pay for a product and then not have it work.
Any suggestions will be sincerely appreciated.
Henry-11

I am running Windows XP. (latest version).
The properties window for my drives says:
C Drive
Used Space 27.3 GB
Free Space 205 GB
Capacity 232 GB
E (External Drive)
Used Space 27.3 GB
Free Space 205 GB
Capacity 232 GB
I use camcorder: Sony VX2000.
I have deleted all previously made (4) movies, hoping for a clean start and hoping that would help. It did not.
So now I don't even get a chance to load from the camecorder because when I click on New Project, I get the message: "Sorry..."
Since PRE 7 has worked in the past, I can only assume that somewhere in there I did something wrong to cause this problem.
Side note: I down loaded a tril version of PRE 8 to see if that would work. Same thing. I have since removed PRE 8.
I will most sincerely appreciate any help because I am a total computer dummie.
Note that I did update to the latest version of Quick Time. Did not help.
I am so frustrated over this. I recently videoed a Puppet Show and gal is really on my case for the finished product.

A view, function and TO_DATE causing an error.

I have the following statement which calls a view, VW_DIST_RPT_WORK_LIST which in turn calls a function which returns either 'Null' or a date string e.g. '07 Oct 2003' as a VARCHAR2 (alias PROJECTED_DELIVERY_DATE).
Statement:
SELECT CUSTOMER_NAME, PROTOCOL_REFERENCE, SHIPPING_REFERENCE, CUSTOMER_REFERENCE, COUNTRY, PROJECTED_DELIVERY_DATE, STATUS, NOTES,
TO_DATE(PROJECTED_DELIVERY_DATE)
FROM VW_DIST_RPT_WORK_LIST
WHERE EXPECTED_DESP_DT IS NOT NULL
AND UPPER(PROJECTED_DELIVERY_DATE) NOT LIKE('NULL%')
AND EXPECTED_DESP_DT <= TO_DATE('07/10/2003', 'DD/MM/YYYY')
AND TO_DATE(PROJECTED_DELIVERY_DATE) <= TO_DATE('31/12/2003', 'DD/MM/YYYY') --< Problem here
I need to be able to specify a date filter on the PROJECTED_DELIVERY_DATE field and hence used the TO_DATE(PROJECTED_DELIVERY_DATE) <= TO_DATE('31/12/2003', 'DD/MM/YYYY') but this is generating an ORA-01858: a non-numeric character was found where a numeric character was expected.
I think the problem lies with the fact that this field can contain 'Null' which cannot be converted to a date using TO_DATE. I've tried adding a NOT LIKE ('NULL%') statement to catch any nulls which may be creeping in bu this doesn't solve the problem.
I've added TO_DATE(PROJECTED_DELIVERY_DATE) to the select above to determine if the nulls are being caught and if the TO_DATE in performing the conversion correctly which it is on both counts.
Any ideas anyone ?

The answer provided above by Monika will work for this situation. However, you should seriously think whether you should be using a string for date datatype. Ideally, you should rewrite the function that returns PROJECTED_DELIVERY_DATE and change the return type to DATE. The least you should do is to return NULL (instead of the string 'NULL') from the function. Oracle handles nulls perfectly, there is no reason you should write code to handle nulls;
One more thing. Looking at the type of error you are receiving, it seems that you are using rule based optimizer. Why do I think so? Because, in rule based optimizer, the conditions are evaluated in a specific order (viz, bottoms-up for AND clauses). To show this, look at the following simple demonstration. I did this in Oracle 8.1.6 (also in 9.2.0.4.0 on Windows).
-- Check the database version
select * from v$version;
BANNER
Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
PL/SQL Release 8.1.6.1.0 - Production
CORE 8.1.6.0.0 Production
TNS for Solaris: Version 8.1.6.0.0 - Production
NLSRTL Version 3.4.0.0.0 - Production
-- Create the test table
create table test (a number(2));
insert into test(a) values (0);
insert into test(a) values (1);
insert into test(a) values (2);
insert into test(a) values (3);
insert into test(a) values (4);
insert into test(a) values (5);
insert into test(a) values (6);
insert into test(a) values (7);
commit;
-- See that I have not analyzed the table. This will make use of RULE based optimizer
select * from test
where a > 0
and 1/a < .25;
and 1/a < .25
ERROR at line 3:
ORA-01476: divisor is equal to zero
-- Look at the query clause. Even though I specifically asked for records where a is positive
-- the evaluation path of rule based optimizer started at the bottom and as it evaluated the
-- first row with a=0, and caused an error.
-- Now look at the query below. I just re-arranged the conditions so that a > 0 is evaluated
-- first. As a result, the row with a=0 is ignored and the query executes without any problem.
select * from test
where 1/a < .25
and a > 0;
A
5
6
7
-- Now I analyze the table to create statistics. This will make the query use the
-- cost based optimizer (since optimizer goal is set to CHOOSE)
analyze table test compute statistics;
Table analyzed.
-- Now I issue the erring query. See it executes without any problem. This indicates that
-- the cost based optimizer was intelligent enough to evaluate the proper path instead of
-- looking only at the syntax.
select * from test
where a > 0
and 1/a < .25;
A
5
6
7
Does the above example seem familiar to your case? Even though you had the AND UPPER(PROJECTED_DELIVERY_DATE) NOT LIKE('NULL%') in your query, a record with PROJECTED_DELIVERY_DATE = 'NULL' was evaluated first and that caused the error.
Summary
1. Use dates for dates and strings for strings
2. Use cost based optimizer
Thanks
Suman

A serious error has occured......a bazillion different ways.

Hello, I've seen many posts on the web about the infamous Premiere Pro "A Serious Error has occured and Premiere needs to close the program..." I've encountered this error doing numerous different things while editing my project and can never seem to pinpoint the direct cause of my error. I received the error while:
Playing footage on sequence using scrubbing
inserting a photo into the timeline
adding keyframes to a clip
duplicating a sequence
This is what I am working on:
MAC Book Pro - Processor 2.4 GHz Intel Core i7
Memory - 16GB 1600 MHz DDR3
Graphics NVIDIA GeForce GT 650M 1024 MB
Software OS X 10.8.4 (12E55)
Adobe CS6 - Premiere Pro Version 6.0.2
I have numerous amount of photos that are never more than 700KB and all are either .jpg or .png. I also have .mp4 video files I am working with. I never had any issues importing the files. I worked fine on the project for a few days. Then the errors started to come.
I am pulling my hair out because each time I have to go back to an earlier version of my project to re-edit it. I'm never going to get this done at this rate. Does anyone have any techincal suggestions? Will Adobe be coming out with an update for MAC to fix this any time soon????????? Thanks.

If GPU acceleration is enabled, try disabling it. That worked for me on a very similar laptop. A developer familiar with problems in this area told me that restarting the computer resolves the problem in many cases.
Incidentally, with the crash that I encountered, we have not yet determined whether the problem is rooted in our software our on the hardware side. We're investigating in collaboration with the hardware manufacturer to determine exactly that.

Another 'Sorry, a serious error has occurred...'

Hi Folks,
I searched and tried some of the solutions... deleting style folder, creating a new cache with no joy so far.
Hoping someone here can help.
Hardware/OS specs at http://dl.dropbox.com/u/9233828/PRE_hardwareinfo.txt (dumped from speccy today)
Prem Elements version 9.01 (N224.08092010.240488) - I tried an update a couple of days ago, so hopefully that's the current flavour of 9.x
Issue:
Elements has been working perfectly on this machine since buying and installing it back in August 2011 (a couple of weeks before 10 came out )
This week however it has stopped working.
Starting Elements produces the following behaviours
The welcome screen loads
I get the Organize/New Project/Open Project screen
If I open an existing project:
Project appears to load (status bar completes)
Nothing happens
Menus are accessible but most options are greyed out - I can't even deactivate to try a re-install
If I start a new project
I get the New Project Dialog
Nothing happens as above
If I then try to either open a project or start a new one from the file menu I get the 'Sorry, a serious error has occurred that requires Adobe....'
Clicking OK does not however close elements down - I can repeat the process ad-nauseum until I shut it down
All other Adobe progs (CS5 Design Premium) are working fine
Any suggestions?

Thanks everyone for your suggestions I've tried most of them, but I think I'll cut my losses and get a different NLE.
I'll sum up the experience here, not so much for the forum regulars but for those who have come here via a web search having also entered the dead-end street of "Sorry, a serious error has occurred...", or, as I'm coming to know it, the Adobe Grey Screen of Death (or GSOD as it's easily as annoying and difficult to do anything about as the dreaded Windows BSOD).
So, if I understand it correctly, this error is thown up when some unspecified circumstance occurs that Premiere can't cope with.
No clue is provided to the user of what may have caused it
No log files are created
No entry is made to to the Windows application log
There is no debug mode
There are at least 20 recorded possible causes for the error
Adobe takes no resonsibility for the issue - it's a problem on the user's machine
Diagnosing the problem, working through all of the documented causes may require a massive commitment in terms of time and effort with no guarantee of success and, looking at some of the many posts on the subject, be detrimental to other applications or the system as a whole.
Premiere is a powerful and relatively easy to use tool, when it was working I thoroughly enjoyed using it. However, when it goes wrong (and reading posts here and elsewhere, it seems to go wrong quite a lot) it crosses the border into crapware - software that is poorly engineered and does not adhere to best practice with regard to error handling. As with any service - the quality of the product is often best measured by what happens when something goes wrong, rather than by how it behaves when everything works.
A sincere thanks to those in this little community that tried to help, but life is too short and my time is too valuable to spend more than a couple of days on this.
I'd advise anyone finding this post when researching for a purchase to look at Premiere as a question of risk management - if it works and continues to work then it's brilliant and offers great value for money. If it breaks then there is a very good chance that you're thoroughly stuffed...
I'm off now to decide between Corel and Sony for my next go at video editing
Good luck

A serious error has occurred message

Hi guys,
   I did a search and found some older threads on the topic, but the situation and circumstances are different here, so I thought it best to start a discussion.
   Essentially, I took over a project from a co-worker, and it has been very problematic. 5 times in the last 90 minutes, when doing something as mundane as scrubbing in the timeline, I get the crash message, "Sorry, a serious error has occurred that requires Adobe Premiere Ori to shut down. We will attempt to save your current project."
    This is fairly frustrating as the message is so extremely vague, I can't possibly troubleshoot the cause. But, let me give you specifics...
    HARDWARE - I am presently running on a 2013 27" iMac. 3.4GHz i7 with 16GB of RAM, and the stock NVIDIA GeForce GTX680MX graphics card.
    SOFTWARE - OSX 10.8.4, Premiere Pro CC 7.0.1 (105)
    PROJECT SETUP - this is a little unusual as it has a very specific delivery, but the sequence is at 540 x 1920, making it tall and thin. I am missing the Cosmo plugin that the other editor was using, but this should only result in the effect being turned off on any applicable layers, which appears to be the case. All of the media and assets are on a common SAN, and I started out by saving a new version of the project into my partiion (as we each have write access to only 1 partition), but it is linked with and pointing to all the same footage and assets as the original project. Other than that, there is nothing atypical about the project.
   So, each time this error has occurred, it has done so when I have moved the playhead in the timeline, either by scrubbing or clicking. It has not occurred the same place, it seems that it can happen anywhere. There is nothing else (besides Safari and Text Edit) open, and only 4 video layers (no audio), so the machine nor the software are being pushed at all, but something is definitely amiss... timeline navigation is about as basic as it gets.
   Any help or insight into this would be very appreciated. Tomorrow, I am going to have the client over my shoulder, and having my program crash constantly is both embarrassing and unproffessional.
   Thanks
     - Will Frazier

Well, I may have solved the issue.
It occured to me that the original project was made on an older MacPro... one that has a graphics card with little or no Open CL support, and my Premiere settings on the iMac were at default which has Mercury OCL engine engaged. I changed that to software only, eliminating the GPU from the equation, and so far things have been much more stable.
I'll report back if I have another crash

Extract Edit Across a Dissolve causes Serious Error Crash

Similar Messages

Maybe you are looking for