Adobe Premiere Pro 1.5 CRASHING LIKE HELL!

Ralph Oshiro

Ralph Oshiro

Veteran
Well, I'm about 3:00 minutes of program into my edit, and I'm diddling with some sound FX tracks and moving some video clips around and . . . voila! Premiere crashes if I even look at the timeline funny! Usually, just a single click in the timeline will cause the system to quit and reboot (screens just go black). Can't figure out where it STARTED to crash (like what I did just before this all started). I've saved under new file names, etc. Upon reboot, Premiere says it will "try" to open the "recovered" file, and Windows asks if I want to send an error report to Microsoft. Isn't the Premiere Pro 1.5.1 upgrade just to accomodate the HDV capture capability or are there bug fixes as well?

PC Configuration:

Adobe Premiere Pro 1.5
Windows XP Professional SP2 w/latest updates
3.0 GHz Pentium 4 HT
2GB RAM
10,000 RPM primary SATA HDD (applications)
7,200 RPM 200GB secondary SATA HDD (scratch/video)
 
NBC - Sound like you've got a corrupt file somewhere in the program.
I'd suggest uninstalling PrePro, Reinstall it and go ahead with the 1.5.1 patch before you do anything, then open a NEW project and just add a few clips and play around with it for a few minutes to determine if it's stable. Then go back to your old project and see if the problems persist.
 
Hey NBC, you might have a highly corrupt conformed audio or preview file. Before going through the effort of reinstalling the application, I would just move both the conformed and preview folders to somewhere else. Then restart Premier and start a new project. Import a clip or two from the project that was giving you problems and see what its behavior is like. If it is behaving, then consider opening up the "Auto-Save" folder and see if there is a project backup that was created before you started having problems. If a new project with clean conformed audio and preview files is just as unstable, then I would consider the reinstall suggestion. As for the 1.5.1 patch, I tried it (despite having no use for HDV support) and can't detect any differences as compared to 1.5.

Good luck!
 
..XP SP2 causes brain tumors.. seriously.. it seems to be nothing but trouble for a dedicated editing machine...


if the above doesnt work .. another suggestion would be to try selecting the whole video track by clicking on it over at the very left in the timline.. click outsde where you put the clips. over where it says video 1. then copy it and paste it into a new project.. if your audio is separate.. you can try to do it for audio too.
 
I have the same problem when editing projects with large amounts of still photos. There are some files it does not handle well. Check to see if it crashes in different project. If not then it is something specific to that project. Then check to see what could be unusal in the project that requires too much system resources. Some projects I have to render small amount into movie files and then import back.
 
iamloser said:
..did it work?
Click to expand...
Nope. NOTHING worked. I think WindowsXP was damaged too. I uninstalled/reinstalled Adobe Premiere Pro . . . same problem, and eventually, the application wouldn't load at all. Unable to reinstall WindowsXP. Don't know why. Took PC to repair shop. Bought a new VAIO to complete project.
 
Reinstall Windows XP and all uppdates inkl SP2. Then install Premiere Pro. I have no problem at all on my PC
 
phd said:
Reinstall Windows XP and all uppdates inkl SP2. Then install Premiere Pro. I have no problem at all on my PC
Click to expand...
Yeah, that's what I tried! WindowsXP's install FAILED! It just froze during its DOS-mode "configuration" screen. I told the repair place to wipe the disk clean and reinstall XP/SP2, etc. Since there's no DOS fdisk command anymore, I could never get the machine to format the drive--it froze time and time again before anything was functional. Wouldn't even complete a boot from the CD-ROM. I bought a second machine and installed Premiere on it and NOTHING else. My long term solution is to keep the VAIO as a virgin, Premiere-only machine, and use my other PC for all other applications.
 
You can use fdisk and format from any bootable floppy drive to get a "clean" start (from any version of Windows). Then install the driver for your CD-ROM (if needed) so that you can get to the XP install disc. From that point on out, you should be able to install XP without a problem.

Keeping your NLE on an other wise "virgin" machine is a great idea, we do this at work for all mission critical applications, keeping the machine dedicated and optimized to the task that it will run.
 
I used to have a dedicated virgin machine up until it became a slut! Now instead of just wanting editing, now's she's into music, 3d graphics and video games. What a freak!


Just get a bootable XP cd.:thumbsup:
 
Solution

Solution

One of the main things that causes Premiere Pro to crash and reboot so unexpectedly is an audio conflict. If you're using an external audio device you have to disable on-board audio in the BIOS as Premiere is very sensitive to that. It worked for me on two different computers running Premiere Pro.
 
I'm attempting to edit a 30-minute TV pilot using Premiere Pro. I've edited together about 20 minutes worth of material in one project.

Just got my first crash 15 minutes ago. Now Premiere won't even open the project! It will open other projects, but not the show project. When I attempt to open that file, I get a nasty crash. :crybaby: Any ideas for a fix?

Going forward, my new strategy will be to break up the show into segments...and each of these segments will be edited as separate projects.
 
Sean: there was a similar known problem with premiere 6.0 which sometimes would mess up the project file. there was a very stupid patch around which would fix your files.
try looking on the net for your specific prob. adobe widened the bug and patch section for Ppro.
recently i've found a solution to a problem which nobody could help me with and there was no official assistance about it for a while. this was the 'can't activate the recorder' error when trying capturing, and it was connected to a direct show filter which i had installed.
So you may find a solution online using the error string you get or some like that..
anyway, from that P6.0 experience, i use to make backup copies of the project file from time to time when i work on it.

My definitive solution for crashes (not messed up projects though) is: from a clean installation, make a image of the system hard drive (separated from projects HD) with r-drive image (simple and cheap soptware) and put it somewhere safe (i use another HD).
when your OS get crashes or psychological problems, restore the original clean image. it takes 5 mins.

Andrea
 
Andrea, thanks for your reply. For a while, I thought I was going to lose several days of work!

After much gnashing of teeth, I managed to recover my project from an auto-save file. The previous project file had, for unknown reasons, become corrupt. Thank goodness for auto-save.

I bought an extra hard drive for this project. I will check out R-drive image . . .
 
You must log in or register to reply here.
Back
Top