Modified CRBO lead to serious errors

Hi Guys,
I am new to labview and I was playing around with labview file and accidently changed the CRBO for control relay output block to a pushbutton,now I cannot/ dont know how to revert it back.
Now Labview is showing many errors,like "subVI" not executable,polymorphic sub VI is broken.I have no cluse what these means.
I am using labview 2013.
I am using labview 2013 as a dnp3 master to some sel relays.
I made this dnp3 file by modifing the example dnp files form NI.
Pls help me get this setting back.I have also attached an image regarding the same and also the labview file.
Do I have to reinstall Laview completly to get the old settings back.I am quite sure the files I made are working fine because I had checked it before trying to modify the CRBO(trying to make it look simple)
Please Help mE
Leon Koshy
Attachments:
crbo changed.jpg ‏136 KB
Master_AI_vol_freq_trialLLOP.vi ‏45 KB
plethora of errors,dnp3 master blocks not working.png ‏262 KB

Hi Leon,
You may have modified the typedef of the terminal CROB.
Reinstalling DNP3 alone will cure the problem, I believe. You don't have to reinstall LabVIEW.
The VI you attached opens with no error. It's executable.

Similar Messages

Cannot Save Document Leading to Serious Error in InDesign

I'm using both InDesign CS3 and CS4 in Mac OS X 10.5.5
We recently got a new printer at work (Xerox 700 Digital Color Press). Since then, I've had major issues saving some of my documents. Immediately after printing a document duplexed, It says this when I try to save: "Cannot save the document. It may be opened by other applications. Close applications and try again. You may also use saveas to save it into a new document." If I cancel and do a save as to another location, InDesign immediately crashes saying a serious error has been detected and must shut down. The same thing happens if I close the document without saving and try to open that same file again. I've tried this with files located on our server as well as my hard drive with the same results.
Fortunately, restarting the computer resolves this problem (although only until I try printing it duplexed again). If I print it without duplexing, It will save just fine. No other applications I use are having this problem. As a temporary solution, I've been printing the job to the hold and then changing the settings on the printer to make the job duplex. I've tried uninstalling and reinstalling the entire creative suite as well as deleting the preferences and other settings, but none of those things have helped.

I managed to find a workaround to this problem. Hopefully this'll be useful for anyone else with this problem until the problem is resolved by Adobe.
After you close the document without saving, rename the file. When you open the file, it will open as a read-only document. Do a "Save As" to another location. You can then move the file you just saved to where it belongs. However, you won't be able to delete the previous file until you restart the computer.

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.

Create new project and serious error occurs...

If I attempt to create a new project at any time during Premiere Pros operation the program gives me a 'serious error' message and does not respond which leads to a crash.
I am running Premiere Pro CS6 on Windows 7 Professional.
Here is the event properties details:
Faulting application name: Adobe Premiere Pro.exe, version: 6.0.0.0, time stamp: 0x4f7177ec
Faulting module name: Premiere.dll, version: 6.0.0.0, time stamp: 0x4f7177e5
Exception code: 0xc0000005
Fault offset: 0x0000000000012836
Faulting process id: 0x1810
Faulting application start time: 0x01cf5a695cfb64c0
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CS6\Adobe Premiere Pro.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CS6\Premiere.dll
Report Id: 1cc11ff4-c65d-11e3-9f91-bc5ff4bc429e
Not sure what other information to give if any.
Any help would be fantastic thanks!

The "serious error" message is far to generic for troubleshooting purposes. Jim posted that link because the crash info that samsandwich provided reports "Exception code: 0xc0000005."
With crashes on launch that start happening after the program has been running successfully, the first thing I'd recommend is to clear the preferences. They sometimes get corrupted such that they keep the program from launching. Here's an article explaining how to clear prefs: http://www.larryjordan.biz/premiere-trash-preferences/

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

Error Message: Sorry, a serious error has occurred that...

This seems to be a common problem, however, I have not found a fix. I am somewhat technologically savvy, but limited! Listed below are my specs and details to the problem.
Software- Premiere Pro (Version 5.03) Recently updated
OS- WIN7 Core 2 Duo CPU E8400 3.00GHz 4.00GB RAM
Footage used- all types
Error message text-
Sorry, a serious error has occurred that requires, Adobe Premiere Pro to shut down. We will attempt to save your project.
The problem-
When attempting to start PP it allows me to start a new project, select setting, and sequences. However, as the program begins to start up the new project the error pops up. The only option is to click ok, which in turn locks up the program.
Also any files that I have previous created also will not open properly.
Also, I have recently lost a drive that contained many of my old PP projects. I've read that some people have this problem when losing a drive that once related to possible PP preferences and scratch disks...once again I am limited on understanding how that all works.
I have restarted, cold boots, warm boots....clean uninstall, clean reinstall of PP and all components, updated chipset, display adaptor is up-to-date (NVIDIA GeForce 9300 GE) ...also I am an administrator of the workstation
**Through my many failed attempts from reading forums I have also at sometimes received a RunTime Error R6025 (pure virtual function call)
I have no 3rd party effects
not using Mecury to my knowledge.?

Has it worked OK in the past? If so, try System Restore.
While your computer might meet Adobe's minimum requirements, it is way underpowered to run Premiere Pro properly.
See here:
http://forums.adobe.com/message/6336879#6336879

Error Message: Sorry, a serious error has occurred that requires Adobe Premier Pro to shut down.

Hi. I'm having another serious problem with CS4 (the version that comes with CS5 when you don't have 64 bit capability. I just finished a project, had saved it, and then had switched over to Adobe Encoder to create a finished flash video (which worked perfectly). I shut down CS4, went home, tried to restart the main project to create a video from the same project (wanted to make an mpeg version as well) and got the following error message:
Sorry, a serious error has occurred that requires Adobe Premier Pro to shut down. We will attempt to save your current project. Then the system shuts down.
Not only can I not open the project I was working on, I cannot open any of my prior projects without receiving the same error.
Does anyone have any idea what may be causing this issue and how to resolve it?
Thanks in advance for any suggestions.
By the way, is everyone else having the same amount of problems with this software? I've never had any software that has had so many problems from the beginning. My opinion of this software and Adobe in general has gone down substantially.

Not enough information for anyone to even make a guess
Work through all of the steps (ideas) listed at http://ppro.wikia.com/wiki/Troubleshooting
If your problem isn't fixed after you follow all of the steps, report back with ALL OF THE DETAILS asked for in the FINALLY section, the questions at the end of the troubleshooting link

A serious error has occurred or how the 7.1 update ruined my life.

Ever since the 7.1 update to Premiere, I've had nothing but problems. The desktop app fails to update for every update, and appears to think it's out of date when it's not and then the icon in the menu bar will be grayed out until I reboot 3-4 times. The "workaround for that seems to be to force quit and uninstall the "previous" version and then download the "new" version from the creative cloud web portal. This wouldn't be that large of an issue, but it happens almost every other day.
Then once I can actually open Premiere, the real fun with errors begins. I have received the "A Serious Error has occurred" screen on 30-40 (not exagerating) delightful occasions in the past couple of weeks, with no real details of what is actually wrong. It usually occurs while trying to fix an issue where my multi-clips aren't showing the audio waveforms in the sequence, but it has happened plenty of other mysterious ways. This is even more complicated, because it's happening on multiple systems and one of them isn't even using the 7.1 update and another is offsite and using different hardware. The same annoying error occurs across them all.
Another super cool "feature" is that Mercury Playback Engine capabilities come and go as they please. Sometimes they work for Premiere or Media Encoder or After Effects, but sometimes they just pick one for that given day and don't let the other apps playback. All of the systems GPU were working just fine in 7.0.1, but now wtf Adobe?
My system specs are varied, but the general idea is this:
Mac Pro systems (4,1-5,1) 2.3GHz - 2.93GHz
16-24GB RAM
Nvidia QuadroFX 4800, Nvidia QuadroFX 4000, Nvidia GeForce 9800
OS X 10.7.4 and 10.7.5
A few of the systems have AJA Kona 3 and Kona 3G
Most of the media is being accessed across 10gigE to a ProMax Platform, and the project files are local on SSD's.
I have the bug report from Apple, so if that helps let me know so I can get that info to someone who cares.

Hi Kevin,
I'm still planning on attempting the 10.8.5 install on one of the affected systems. In the process, I have uncovered a new issue related to the CUDA acceleration not being there at all on a system that used to have it. That particular Mac Pro system only has a GeForce GT120, but the point is that in CS6 and CC, the CUDA was working until this latest update. The other systems have QuadroFX 4000 and 4800 cards, so those seem to be getting CUDA playback, however it is intermittent.
As for the OS X 10.7.4 not allowing me to install 7.1... That is correct. The Creative Cloud Desktop app was failing updating itself (as it still does on every "update") quite a bit, I don't remember any specific messages, but I did see somewhere along the process that I wasn't able to install the Premiere 7.1 update with my 10.7.4. One of the systems here is have a ton of issues with AE, but that's a whole new thread I think. I will attach some of those errors for kicks, but all of these problems occured with the introduction of the virus that is Creative Cloud into our working environment.
I am working with a wide variety of media: R3D, 5D, F55 4K XAVC, Canon C-300, XDCAM EX, FS-100, ProRes. The projects that I've been having the most issues with lately has the Canon C-300 .MXF media mixed with 5D h.264 as a 2 camera multi-cam set up. The other project that was giving me a lot of trouble right when I installed the Premiere 7.1 update was R3D and F55 4K XAVC. Both issues were the "A Serious Error has occurred. Premiere will try and save your project" vague warning. I usually only lost work since the last Autosave 20 minute interval, but sometimes that is a lot of work and when it happens 10 times in one day, that is unacceptable.
Here are some answers to some more of those questions:
What other software are you running?
These are all possible conflicting software (IMO) that are installed:
Final Cut Studio 3
Avid Symphony 6.0.3
Cinema 4D R14
RED CineX
Davinci Resolve
Nuke7
Adobe CS5.5 and CS6 are still installed
Do you have any third-party effects or codecs installed?
Yes. Trapcode Suite, Primatte, lots of scripts in After Effects. Lots of codecs installed from Sony, Avid, RED, Canon, etc.
I think I've answered most of the other questions in this thread, but hopefully that helps. I will update when I'm able to get 10.8.5 installed. I suppose a clean install of 10.7.5 perhaps might have the same chances of fixing this as well.
Here is the Premiere Error:
Here are a series of AE errors, that might need their own thread:

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

Page leads to proxy error sometimes or taking too much time to load

Hi All,
APEX4.0
Web server: Apache 1.3.9 (Oracle 9iAS 10.0.1.2.2)
I am getting the below error at first time when I try to open a page or the page takes 3 to 5 mins to load. From second time on wards, It takes 5 to 8 sec to open as normal. I debugged the page and checked the log. Logs and execution time are looking normal. why the page takes too much time to load at first time or it leads to proxy error?? Is anybody got same experience before??
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET/pls/apex/f.
Reason : Document contains no data
Please guide me to find out and resolve this issue....
Thanks in Advance
Lakshmi

Hi this is what the solution given by your link
A.1.6 Connection Timeouts Through a Stateful Firewall Affect System Performance
Problem
To improve performance the mod_oc4j component in each Oracle HTTP Server process maintains open TCP connections to the AJP port within each OC4J instance it sends requests to.
In situations where a firewall exists between OHS and OC4J, packages sent via AJP are rejected if the connections can be idle for periods in excess of the inactivity timeout of stateful firewalls.
However, the AJP socket is not closed; as long as the socket remains open, the worker thread is tied to it and is never returned to the thread pool. OC4J will continue to create more threads, and will eventually exhaust system resources.
Solution
The OHS TCP connection must be kept "alive" to avoid firewall timeout issues. This can be accomplished using a combination of OC4J configuration parameters and Apache runtime properties.
Set the following parameters in the httpd.conf or mod_oc4j.conf configuration files. Note that the value of Oc4jConnTimeout sets the length of inactivity, in seconds, before the session is considered inactive.
Oc4jUserKeepalive on
Oc4jConnTimeout 12000 (or a similar value)
Also set the following AJP property at OC4J startup to enable OC4J to close AJP sockets in the event that a connection between OHS and OC4J is dropped due to a firewall timeout:
ajp.keepalive=true
For example:
java -Dajp.keepalive=true -jar oc4j.jar
Please tell me where or which file i should put the option
java -Dajp.keepalive=true -jar oc4j.jar ??????/

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.

Another: a serious error has occurred that requires Adobe Premiere Pro to shut down

I know a few people have had the same notification:
sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project
I have tried a whole series of things to fix it and no luck. Here are all the computer stats... does anyone have any ideas???
Premiere Pro
Version number: CS5, with most recent update
Installation language: English
Updates applied: Most recent… installed AFTER problem started
Project/sequence settings… NA
Operating System
Name: Windows 7, 64bt
Update/patch level: Service Pack 1
Installed language: English
Display resolution and color depth. 1920x1080; 32bit color
CPU type and speed Core i7 950
Amount of memory (RAM) 12GB
Video card
Manufacturer: Nvidia
Model: FX3800
Driver version: Latest (installed after errors started)
Number of monitors (displays): in use 2 (with one disabled for testing)
Audio card
Manufacturer Gigabyte Technology 82801J HD Audio Controller
Model
Driver version: 6.1.7601.17514 (latest version)
Each hard drive's capacity and space remaining Disk setup (partitions used, raid configuration, what is where for OS/projects/media/scratch/audio)
C and D, no partitions. D is raided, controlled by hardware controller. All software on C. Media kept on D.
Hardware capture device NA
Manufacturer
Model
Driver version number
Capture software NA
Name
Company
Version
Comprehensive list of third-party plug-ins you installed.
None for Premiere I don’t think. A couple for After Effects. Have been installed for a while with no recent updates.
Exact text of any error messages
sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project
Explain clearly what you want to do, what you are doing and what the result is
Open Premiere to do some work
Be sure to mention if it is something that worked before using the same procedure
Nothing has changed on the PC prior to program failure.
Very importantly: Post details of troubleshooting you have already done to avoid "did that" reponses to questions people ask when trying to help.
Tried:
Reinstalling
Reducing to one screen.
Holding Shift when starting until first screen (New/ Open Existing/ Help)
Holding Ctrl, Shift Alt when starting until first screen (New/ Open Existing/ Help)
Programme crashed regardless of clicking directly on loading icon and opening New or Existing via first load screen, or via clicking directly from a project file.
Removed all fonts installed since last opened.
Restarting.
Updated Graphics Driver.
Updated Premiere

Hi guys; I thought I would share my experience and how I managed to fix this problem. It might help someone.
In my case I kept receiving this message; eventually after re-launching Premiere, I actually paid close attention to the "software loading" information and saw that it got stuck on my installed "Colorista ii" which is a colour grading software.
Now the red bulb came on my head ping!
I recently just upgraded my Mac to the OS X Yosemite & that affected pretty much any non-updated application, which in my case was that and many more of the Red Giant Pacakge; so I searched for the upgrade via Red giant Link, and low and behold I found it and did so. Immediately everything loaded up perfectly fine.. and now can't even do the work, cos I'm so exhausted from an 'almost heartattack'; so going to sleep and commence later in the day I guess..
Now, you might probably want to check if any application on your system needs upgrading to whatever is the operating system on your Mac or PC at this very time. It might help.
Always back-up.
I hope I helped someone :-)
@ToleXElijah
Extreme Studio Manager

Sorry, a serious error has occured

I worked on a project for several hours yesterday. Now it will not open. I tried opening another project from last week. WILL NOT OPEN. In fact, none of my Premiere CC projects will open. They are all corrupt.
Well done Adobe. I'm missing Final Cut Pro more and more everyday. I swear I come across some glitch or a gotcha nearly everyday with the this software.
Can someone please explain why a project(s) would suddenly corrupt???? And why on earth is the this software so unstable?
I'm running on OSX 10.9.2 with the latest update of Premiere CC 7.2.1
This is the message:
"Sorry, a serious error has occured that require Adobe Premiere to shut down. We will attempt to save your current project."
No projects open, no autosave projects work and literally days have been wasted if these can't be opened.

I am on Windows, but have a few saved Mac discussions that may help (or, may not... but free to read)
Mac and Root User http://forums.adobe.com/thread/879931
-and http://forums.adobe.com/thread/940869?tstart=0
Troubleshooting guide for Mac freeze
http://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-mac.html
OSX Crash http://helpx.adobe.com/creative-cloud/kb/ame-premiere-crash-launch-export.html

Export problem "A serious error has occured", or hang, upon export to Encore.

Hello,
I am using adobe Premiere CS3 3.2
I am trying to export my project to a DVD. I've been told that the best way to do this with minimizing quality loss is to export to Encore.
My project has some filters that affect system memory and have locked up the computer numerous times before, like Looks Suite and Noise Remover (on some clips)
when I choose export to Encore, then choose settings, I get the error "A Serious Error has occured...." Then I trried lowering the settings, and I got the window that says "Rendering", at least, but nothing appeared in that window after I left it overnight.
So I have some questions:
- What's the best thing I can do to export my movie onto a DVD with minimum loss of quality?
- Should I export as a video file first? Which is the best quality? Then can I export to Encore?
- Does it help to pre-render my entire project in Premiere first, THEN export to Encore?
I'd appreciate some advice.
Thanks!
EDIT: I just tried to export as a Quicktime Uncompressed video with the regular method (Export-> Movie).. and it gave me the error "Could not compile movie..." then the message "adobe premiere pro is running very low on system memory"
So I am assuming this is a memory issue? Then what should I do??
Also, I want to ask- If I put my entire project with all its files onto an external hard drive, then move them to another computer with adobe premiere pro installed which also has the same filters installed, would I be able to export this way?

I am quite sure it is a memory problem... the computer exported other videos in the past just fine, but its never been used for making a film with a lot of filters and such that run down the memory, and so it gives me the memory errors.
I am not sure what is "Memtest86+"... I would like to try such a program, but in fact this is not my computer... I am using a Workstation at a University and now I have limited time to complete my project (I must figure out a solution by the end of the day on Monday)
Maybe AVI is the best for some... but I have done comparisons beforehand which found .mov to be the best... and I was even told that uncompressed quicktime doesn't lose quality at all (though in fact it seems to just a bit). So if you not completely sure which will be better, I will go with .mov.
So I will try a few things- like exporting only the "special" clips which used a lot of filters on individually as .mov, then reimporting them into the project, then trying to export the whole thing into encore... If that does not work, I will try to export fragments as.mov (because if I try to export too much at one time, it has the memory error->crash).. then create a new project, import the .mov files, and export to Encore.
I only have limited time to solve this problem.. do you all think I am taking the right steps?
Also one key question I have is about the audio.. do you recommend that I export all of the audio into one wav file, and then put that into the new project? Or should I just export the quicktime files, with their audio, into the project and keep it like that?
I appreciate the help, again

A Serious Error Has Occured

Hey guys,
I'm sure this has to exist elsewhere, but I couldn't come up with anything quickly. I've been trying out the Premiere Pro CC trial for a little while now, and have been mostly pleased. I've used nothing but FCP in my career and know it like the back of my hand, but have been hearing such good things about Premiere Pro I decided to try it out and see if I'm ready to make the switch.
Unfortunately, the past few days I haven't been able to get much work done, as I keep getting this "serious error" that requires PP to shut down. I've tried doing a complete re-install to no avail. I've swapped around how much RAM the program is using and am still getting this error. Does anyone have any suggestions? The program is completely up to date, as well. I've attached an image of the error below. At first, it seemed to be happening the most frequently when color correcting, but just now it happened simply moving through my timeline. And again when adding a transition. Seemingly simple tasks.
I'm on a MacBook Pro Retina, late 2012, 2.7GHz Intel Core i7, 16GB RAM, running OS 10.9.5. Haven't upgraded to Yosemite as I've heard FCP will no longer work and the company I work for still relies heavily on it.
Thanks in advance!
Nick

While you may get some help here on the forum, the best way to get a handle on non-specific crashes such as this is to contact Technical Support: Contact Customer Care. Be sure to ask to be put in the Video Queue so that you are assisted by an agent with deep knowledge of the video apps.
If you want to try some troubleshooting on your own first, I'd start by clearing the following, in this order:
preferences, which are in the "Profile-<username>" folder here: Documents\Adobe\Premiere Pro\7.0. With PPro close, rename the Profile-<username> folder. Then launch PPRO. The app will create a fresh copy of the preferences file and other files that record custom settings.
cache files: Macintosh HD ▸ Users ▸ <Username> ▸ Library ▸ Application Support ▸ Adobe ▸ Common. Delete the folders "Media Cache" and "Media Cache Files."
the render preview files. By default, these are saved to the same folder as the project, in a folder named "Adobe Premiere Pro Preview Files"
And if you want to pursue more assistance here, please provide more info, as spelled out here: FAQ: What information should I provide when asking a question on this forum?
If the Crash Reporter dialog comes up afterward, please click the Information link, post the contents to a file on DropBox or the like, and include a link to it.

Modified CRBO lead to serious errors

Similar Messages

Maybe you are looking for