Premiere Pro cc 2014 super buggy

running new mac pro (trash can) fully loaded with newest osx.
here are the bugs i have:
when working in premiere and have a dynamic link to after fx and after fx is open renders basically don't happenwhen you close after fx the renders are fast again...this workflow is terribly painful
in premiere media browser often crashes or doesn't load the contenta reboot of the software normally corrects this
began a project in CC.  client comes back 6 months later and i'm now running cc 2014.  no prob i open old project make a 2014 project version and start working.  come back monday morning and i can not get the timeline to open.  it opens the old timeline, but not the new one.called adobe tech support and very nice knowledgeable rep gets me thru this:
creates new project from scratch and then imports the old project into the new one.
seems to work now, but i am having all the above problems and is NOT a good workflow.
So, I am on the verge of (GAK) going to apple final cut which i left when they created X because it seems to work very well with their new trash can computer which adobe doesn't seem to.  I love the idea of adobe cloud services...huge savings!  but if they don't trouble shoot their products before giving them to us they will lose me that's for sure.
if adobe tech reads this please please please address these most basic issues especially because these are your calling cards...your brand.

1 more bug that i forgot about, but it just happened now.
The play control will stop working on the timeline whether you hit the space bar, the L key or go to the controller in the program viewer and hit play it won't work.  this may be the most embarrassing bug of all.  you can still scrub the timeline, but it won't play.
ok, it just happened again after posting this...this is an edit to the original post above.  it seems to happen most when i leave adobe to do something like use my google chrome browser or other programs like checking email.
ugh!
adobe, please address these bugs quickly or i will be forced to stop using your product.

Similar Messages

  • Premiere Pro CC 2014 crashes when loading project file

    Hi guys, any help on this is much appreciated as I have a job due in 18 hours and I'm in big trouble if I can't fix this.
    I've been editing a project in Adobe Premiere Pro CC 2014 (updated to the latest version) and when I tried to access the same file today it is giving me the error message:
    'Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project.'
    I had saved other version files and they all seem to be working properly so I know it's not my HD that is corrupt. In fact my suspicion is that it has something to do with a blur effect i'm using. The only problem is, I can't even access the file to delete the effect as the project file won't open.
    Information about my computer:
    I am using a Macbook Pro
    OS X version 10.9.4
    2.6 Ghz Intel Core i5
    Memory 16 GB, 1600 MHz DDR3
    Any suggestions/comments would be appreciated.

    Guys I solved my own problem - thought I'd share with you how in case anyone else is having this problem -
    I came across this thread
    Premiere Pro CC error message and crash
    which had the suggestion -
    "Do tou have after effects installed? If yes, please try to import the main sequence into it and then export it as premier pro project from file/export ootion and then try to open that in premiere pro."
    This didn't work for me too but I did try and import my existing project into a new project and copy all the files over. Works fine now.
    I don't know if I will have the same issue again tomorrow so I'm going to render out a super high res video before I close premiere just in case

  • Re-interpreted footage metadata is lost when moving Premiere Pro CC 2014 project file to different computer

    Hi guys,
    I believe this is just a bug in Premiere Pro CC 2014 (and other versions in the past), but I wanted to make sure it was on the PP team's plate for the next update, since it's detrimental to a workflow that include more than one computer or more than one editor on a project.
    My team shoots a lot of footage in slow-motion (for instance, 59.94 for 23.976). Premiere's process to conform this footage is great. Modify -> Interpret Footage -> Assume this frame rate: "23.976".
    Unfortunately, when we move this project file to another system, even if we are using a hard-drive that is synced to have the exact same source media files with the exact same file structure, we lose the footage interpretation metadata. Premiere Pro CC thinks this footage is 59.94 again, and our sequences are in shambles. All clips where the interpretation metadata is lost have "zebra pin stripes" on them wherever they exist in our sequences.
    We have to manually re-interpret the footage, and then sometimes manually re-select in and out points. This is a work-around that enables us to push forward, but it's a barrier that makes collaborative editing extremely challenging and opens up rampant possibility for error. It's hard to locate every clip we need to re-interpret in some of our more complex projects, and even harder to avoid re-interpreting the wrong clips.
    Looking forward to a resolution to this problem.
    Daniel Lichtenberg
    [ad/link removed by moderator]

    Guys I solved my own problem - thought I'd share with you how in case anyone else is having this problem -
    I came across this thread
    Premiere Pro CC error message and crash
    which had the suggestion -
    "Do tou have after effects installed? If yes, please try to import the main sequence into it and then export it as premier pro project from file/export ootion and then try to open that in premiere pro."
    This didn't work for me too but I did try and import my existing project into a new project and copy all the files over. Works fine now.
    I don't know if I will have the same issue again tomorrow so I'm going to render out a super high res video before I close premiere just in case

  • Premiere Pro CC 2014 playback freezing and crashing with new iMac i7

    Using Premiere Pro CC 2014 and having constant playback freezing and software crashes on a brand new iMac i7.
    Here are the specs:
    iMac i7 4.0GHz 5k Retina
    32 GB Ram
    AMD Radeon R9 M295X 4GB graphics card
    512GB Solid State Drive
    I was on chat yesterday with an Adobe tech. Although playback/render settings show the OpenCL option to utilize the AMD graphics card for processing, I was advised to switch to "Software Only" as that card is not supported yet. I had to re-render my 45 minute documentary (which doesn't appear to be any faster than it was on my old 2011 iMac by the way) and it still has the same issues.
    So frustrating? Anyone else experiencing this? Any advice? I hope I didn't just buy this "super machine" in vein.
    Thanks,
    Jason

    Hi All,
    Taking some tips from Kevin Monahan. If you haven't already gone through this list please do so.
    Sign out from Creative Cloud, restart Premiere Pro, then sign in
    Update any GPU drivers
    Trash preferences
    Ensure Adobe preference files are set to read/write
    Delete media cache
    Remove plug-ins
    If you have AMD GPUs, make sure CUDA is not installed
    Repair permissions
    In Sequence Settings > Video Previews, change the codec to one that matches your footage
    Disconnect any third party hardware
    If you have a CUDA GPU, ensure that the Mercury Playback Engine is set to CUDA, not OpenCL
    Disable App Nap
    Reboot
    Best,
    Peter Garaway
    Adobe
    Premiere Pro

  • Premiere Pro CC 2014 freezes frequently and crashes

    Since upgrading from Premiere Pro CC to Premiere Pro CC 2014 my projects crash in regular intervals, which didn't happen before.
    All my settings and presets have been pulled across fine, but suddenly relatively slim projects get stuck during editing, rendering or exporting. The progress bar stops, the preview screen freezes and that's it. I can only radically crash the sucker. I did delete all preview files and it improved marginally... only that the time until it froze took a few minutes longer.
    I'm on 64bit high-end Windows 7 machine and have never had this problem with previous versions of Premiere Pro.
    Very frustrated.

    @bendubb37: I'm not the least bit defensive about complaints regarding the stability and general quality of the program. As a quality engineer on the Premiere Pro development team (not a member of the technical support team), I'm quite familiar with many if not most of the problems--both those that are legitimate bugs in our code and those that result from conflicts with OSes, hardware, codecs, other programs, etc. I genuinely appreciate having customers come to this forum to report issues they're having. Such reports sometimes help us identify bugs that we weren't aware of, and they always help us to prioritize bugs to fix based on which issues are biting the most customers and having the greatest impact on their productivity and satisfaction. And naturally I understand the frustration and anger of customers who are wrestling with one problem or another in the program.
    What I took issue with was cutco's derision of a perfectly valid troubleshooting step recommended by a technical support agent and his assertions that a) "This community is kind of useless" and b) "Adobe is absent." Cutco graciously acknowledged that he had let his frustration get the best of him.
    As to the oft-repeated claim that CC2014 is buggier and less stable than prior versions, I submit that it's a problematic claim to substantiate, at least based on anecdotal personal experience or taking the pulse of this forum & others. There's no question that some customers who enjoyed smooth sailing with an earlier version are experiencing problems with CC2014. But I know for a fact that this release included fixes for a significant number of bugs, including crashers, so many other customers who were having problems with earlier versions are now cruising along without a hitch (or at least without those old, fixed hitches). Alas, those people are not frequenting the forum to sing the praises of CC2014.
    My point here is simply that claims about the relative quality of one release versus others can be a distraction from the more important--and much more concrete--fact: a certain number of customers using CC2014 are having Problem X, which didn't happen in CC7.x. The more we can learn about Problem X--and the more clearly we can differentiate X from Y and Z, which may manifest similarly--the sooner we can nail down the cause.
    Don't get me wrong: there is an objective trajectory of a product's quality. Unfortunately, even when you have a large pool of data in front of you, the trajectory doesn't lend itself to quantification. You can't simply count the number of deferred bugs, for instance, because not all bugs are equal. You can't even go by the number of known crashers because some are extreme edge cases while others lurk in the path of mainstream workflows. That said, for people like me who spend our working lives trying to deliver the highest quality possible, the trajectory our program's quality is a common topic of discussion.

  • New (8/14) Macbook Pro Retina - Premiere Pro CC 2014 spinning beach ball

    Help! Seems my shiny new wiz-bang 4-core Macbook Pro with 16 GB of Ram and a 512 solid state drive works just fine with Adobe Premiere Pro CC 2014 until my project reaches a certain size, then it won't open the project and immediately gives me the deadly spinning beach ball. The only way to exit is to force quit whereupon I get the "Sorry, a serious error has occurred...". Aggravating beyond words.
    Saw one forum comment where it was recommended to update to the 6.0 CUDA driver, but not even sure I have a CUDA driver. Plenty of space left on hard drive. In Premiere Pro preferences under the "Memory Tab" it doesn't seem to matter if it's set to "Optimize rendering for.... Memory or Performance." I've reinstalled the Premiere Pro App twice. Doesn't help.
    Some specs:
    Processor  2.5 GHz Intel Core i7
    Memory  16 GB 1600 MHz DDR3
    Graphics  Intel Iris Pro
    NVIDIA GeForce GT 750M GPU PCie
    Intel Iris Pro GPU Built-in
    8 GB DDR# 1600 MHz (x2) = 16 GB RAM
    350 GB of 499 GB left on drive
    Of the 16 GB of RAM I have 11 available for Premiere Pro and the other 5 GB allocated for other apps.
    Any suggestions would be greatly appreciated.

    >NVIDIA GeForce GT 750M GPU PCie
    >Intel Iris Pro GPU Built-in
    Dual graphics adapters are a bane on civilization!!!
    -http://helpx.adobe.com/premiere-pro/kb/error---preludevideo-play-modules.html
    -http://forums.adobe.com/thread/1001579
    -Use BIOS http://forums.adobe.com/thread/1019004?tstart=0
    -link to why http://forums.adobe.com/message/4685328
    -http://www.anandtech.com/show/4839/mobile-gpu-faceoff-amd-dynamic-switchable-graphics-vs-n vidia-optimus-technology/2
    -Mac Utility for dual adapters http://forums.adobe.com/thread/1017891?tstart=0

  • Adobe Premiere Pro CC 2014 Crashing very often! Please Help!

    Hello,
    I am currently editing my first feature on Adobe Premiere Pro CC 2014 and it is currently up to date.
    I am editing on a iMac 27in, late 2013 brand new computer.
    Processor: 3.5 GHz Intel Core i7
    Memory 32GB 1600 MHz DDR3
    Graphics: NVIDIA GeForce GTX 780M 4096MB
    System: OSX Yosemite V 10.10.1
    The project is located on a 8TB G Drive
    7200 RPM
    High Performance ThunderBolt drive.
    Details of the project:
    I am currently working on a fine cut of 5K Red Footage that is being cut in the RAW.
    I work at 1/2 quality settings and have no lag.
    The timeline includes limited stacked video files and various mp3 audio files.
    The Problem:
    Lately, the program will randomly quit or freeze up 4-5 times during an 5-6 hour edit session.
    Many times it is random, however, it seems to happen often if I accidentally click on the end of a clip on the timeline and it goes to switch into trimming mode. 
    Also, it will randomly go into the "pinwheel of death" out of nowhere followed by "Adobe CC is not responding."
    My project file is just about 15MB now.
    What is causing this reoccurring problem?
    How can I make it happen less?  I have scoured the forums and found similar articles but no helpful solutions.
    I have recently turned auto save on to save every 2 minutes because there have been more than one occasion where I lost A LOT of work because of this issue.
    I am about two weeks out from picture lock delivery and this issue is driving me crazy and loosing me a ton of time.
    Please help or let me know if any more additional information can help solve the issue.
    I have sent in well over 25 error reports already.
    Thanks,
    Thomas.

    I think I may have found the solution...
    I completely removed the Premiere Pro folder under User > Documents > Adobe and so far it seems to have solved the problem.
    I of course backed up my projects and than deleted this folder. So far it seems it worked.
    I'll know for sure in a day or two, but after constantly crashing, Premiere hasn't crashed for the last 4-5 hours of work.
    Goran

  • What is the problem with Adobe Creative Cloud Premiere Pro CC 2014, why it freezes often?

    I Purchased the Adobe Creative Productive Premium Suite CS5 in early 2010 and I was very satisfied with it all this time, I can say that I never had a problem while using any of the Production Premium applications. Few weeks ago, I asked Mr. Philip Bloom about a technical issue regarding the best method to use a 50 FPS clip with a 23.976 FPS project, and I got his kind help but he recommended me too that I should upgrade to the latest Adobe Cloud CC 2014 which has many new features added to the different programs. I took his kind advice and downloaded a trial version of all the Adobe Cloud CC programs which I use for my filmmaking business.
    Today is the 20th day of my trial period and I have 10 days left to take the decision of continuing with CC 2014 or not. The past 20 trial days were not very pleasant. I want you to share with me the following details which I'll list them as bullet points and I would appreciate diagnosing the problem if you can and suggest a solution for it  to re-try the Adobe Cloud CC 2014 for the 10 remaining days with no further problems.
    I used to have the Gigabyte graphics card GTX 470 for about 4 years and it malfunctioned last year and I replaced it with a humble Geoforce GT 610 card, but it worked fine with the Adobe Suite CS5 programs.
    My system configuration is Intel Core I7   950@  3.07GHz , installed memory 12 GB. , Windows 7 Ultimate, 64 bit Service pack 1, 3 hard drives 1TB. each (one of them is dedicated for Adobe asset files and the editing work)
    For the first 2 or 3 days I used mainly the Premiere Pro CC 2014 establishing short projects for a max. of 5 minutes each and it was working normal. But, later, as soon as I started to build a project which reached about 24 minutes of length and I began to edit those before I add more clips to the timeline, unfortunately, the PrPro CC 2014 started to freeze on any of the frames every time I try to edit normally as I used to do with the CS5, so, I had to wait for 2 or 3 minutes every time it freezes, then it works for seconds then freezes again!!  and during the 20 days mentioned above it crashed once.
    The movie files of my project are the Nikon's .Mov files and the editing work which I performed included effects such as Color correction (levels) color correction (fast) color correction (Auto) sharpen effect, and stabilizing effect.
    I installed the Magic Bullets Suite trial version, and the Neat Video trial version, aiming to purchase either the DeNoiser or the Neat Video (but I tried their effects without saving them to the project).
    I used to export parts/ or whole project before finalizing the editing process to be able to monitor on a TV screen (mp4 file format) some of the changes I made in PrPro before being freezed.
    Based on my previous 5 years experience using the CS5 Suite I have a strong trust in Adobe, I never thought the problem was in the PrPro application, but rationally I thought it was the graphic card (GT610), and accordingly I purchased yesterday a new Zotac Geoforce GTX 770 (listed by Adobe as an approved card) and I installed it and checked that it is running fine and I checked the processor temperature which was within the normal level.
    Only today, I began to think that it might be something wrong with the Adobe Cloud CC 2014 ( a bug or something) and as a result of searching on the internet I could see lot of users since 2014 who were having freezes and crashes with the CC and the CC 2014 versions. That was a shock for me, could it be that until Feb. 2015 the same severe problem still occurs???
    Sorry for any inconvenience, looking forward to seeing a solution for that serious problem.

    Hello Ashraf,
    Sorry you didn't get any help on this post. In the future, please contact Adobe Support for 1-1 assistance on issues like this: Contact Customer Care
    Thanks,
    Kevin

  • Multi Cam Flicker Issue - Premiere Pro CC 2014

    Multi Cam Flicker Issue - Premiere Pro CC 2014 can any one help me pls

    Hi,
    This might help :
    Go to File > Project Settings > General and change the Video Renderer to Mercury Playback Engine software only. Click OK and select Delete Previews.
    Thanks,
    Rameez

  • How to work on the same project on two machines at the same time and also exchange progress seamlessly using Adobe Premiere Pro CC 2014?

    We are working on a film project on Adobe Premiere Pro CC 2014. Two editors are working on the same film project (same pproj file ) on two machines. As a result the bin structure and the file structure is exactly the same. We even bought two licenses for the respective machines to make matters simple (at least we thought it would).
    Now when we share a sequence between the two machines, every time we have to import and re-link media. Also each sequence import comes with its own set of files, which are actually already present in the project. Basically the new sequences are looking to re-link the media to the original/ source files only and are completely ignoring the file structure present in the project.
    In all editing softwares, timeline/ sequence sharing is a very common practise when working on multiple machines. Why is it so tedious in CC 2014? Every time we share a sequence between the two machines the media gets doubled and tripled in the project. As a result the project file size is increasing perpetually. Already Premiere CC 2014 is extremely laggy and slow, and this stupid bug is making it more difficult for us to finish our work on time.
    Has anybody ever faced this issue? How do we solve it? We are willing to try out any workflow that you can suggest.

    Concurrently working on the same project it requires a specific implementation in all editing programs like Avid's Unity/ ISIS shared storage. That's what you are simply not considering. none of your issues would be any problem if your projects resided on a commonly accessed server or something like that. Check respective hardware solutions.
    Mylenium

  • Flicker footage in Premiere Pro CC 2014.2. Tested on different computers. When waiting for fixes this bug?

    Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different. Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
    It can occur even in the parts without filters !!! But no all time.
    ver 2014.2 - win 7 - intel i7-4770 - gtx 770 - flicker!
    ver 2014.2 - win 7 - intel i7-4770 - Intel HD Graphics 4600 - flicker!
    ver 2014.2 - win 7 - intel i7-2700K - quadro 2000 - flicker!
    MERCURY PLAYBACK ENGINE work fine! But still flickering in preview and render.
    When waiting for fixes this bug?

    Hi Aleksey,
    Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different.
    Have you tried with the Mercury Playback Engine set to "Software Only?" More info please: FAQ: What information should I provide when asking a question on this forum?
    Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
    Is this a brand new project or one you updated from an earlier version? What kind of footage are you exporting? Which preset are you using?
    When waiting for fixes this bug?
    If I can repeat the case here with the same hardware, GPU, and drivers, that would be easier to fix the bug. Currently, I cannot recreate the bug.  If you or anyone else can provide me with steps to recreate the bug, that would help immensely. It sounds like this will be the difficult thing.
    Thanks,
    Kevin

  • Why does Premiere Pro CC 2014 renders incredibly slow?

    Dear Premiere Pro experts
    I created a movie with Adobe Premiere Pro CC 2014 and I have serious performance issues when it comes to export the movie.
    The first 10% renders pretty fast and takes 1 hour. Then it takes for every additional 1% about 4 hours! (never rendered it to finish so far, 14% max so far)
    Here are some facts that might help to isolate the problem:
    Project:
    Length: 24 minutes in total, splitted into several sequences (up to 4 minutes) and arranged on a "main-sequence"
    Input: Cineform AVI files, 1080p, 59fps (I converted GoPro 3+ footage (3D!) using GoPro Studio to the Cineform format for further processing)
    Desired Output: Same as input, preserving 3D (Render 3D Intermediate)
    Effects used: Warp-Stabilizer (default settings) and Auto-Color (smoothing 1-2 sec) on almost every clip.
    Hardware / Software:
    i7-3770K @3.5 GHZ (Quadcore)
    16 GB RAM
    NVIDIA Geforce GTX 970 (also tried with a ATI Radeon R9 290X)
    Windows 8.1
    SSD for OS and programs, RAID 0 for media files and project, separate drive for rendering output.
    Then I tried to render using AME using the same settings. The whole video rendered in about 14 hours what is acceptable in my case. There problem here is that the 3D gets lost, even if I selected "Render 3D Intermediate". The picture for the left eye is the same as the one for the right eye. This is not happening when I do a direct export. But the direct export get almost stuck at around 10%.
    There is almost no difference in choosing Software-Rendering and GPU. Also, the GPU has almost no load. Premiere Pro uses the CPU for about 45% (total usage 65%) and takes up 5-9 GB of memory (total usage 65%). Disk usage at around 14b/s.
    I think there are two problems. One is that AME renders differently (no 3D) and the other is that the direct export takes way too long.
    Can someone help me with any of these problems?
    Thank you,
    Martin

    I did some additional research and found out, that the slow rendering happens with this combination:
    - Auto-Color using Temporal Smoothing
    - Render 3D Intermediate
    Without rendering the 3D intermediate, Temporal Smoothing is not a problem. And without temporal smoothing, Rendering 3D Intermediate is not a problem.
    Might this be a problem in the codec or in Premiere?

  • After upgrading to Premiere Pro CC 2014, I can't change the render preview location

    Ever since I downloaded Premiere Pro CC 2014, I cannot re-route my render preview files. I have two internal hard drives and I need the files to go to my secondary one. With CC, it did this just fine, but since I've upgraded to 2014, it will not do it. I've set it the same way I did before in Preferences/Media, then set the Media Cache Files and Media Cache Database to the new hard drive.  It's eating all my hard drive space and I cannot render or export a large sequence. Is there a trick to this I'm missing that has changed?

    Thanks Neil! I'm actually wondering how to change where the preview files go. I've attached two screen grabs. Right now my media cache is going to my SATA drive (my smaller of my two internal hard drives and the drive where Premiere Pro is located.) I want to re-route my render files to go to my Macintosh HD drive which is much larger and gives me more breathing room. I could do that before but since I've upgraded to 2014, even though I have it set in preferences, it STILL goes to my SATA drive. So annoying! I'm wondering if I'm doing something wrong or if it's a bug. I'm still running Mountain Lion (getting ready to finally upgrade, I've just been needing to backup my computer), could this be the reason? Any ideas? Thanks so much for the help!

  • ICanon C100 playback issue premiere pro cc 2014

    I am having playback issues in Premiere Pro CC 2014 with footage shot on my Canon C100 (29.97 fps).  It was happening after doing a straight import and creating a sequence using "new item".  Then, after reading some other threads here and elsewhere,  I interpreted the footage so premiere would see it as progressive (no fields) rather than interlaced, but that doe not seem to help.  It is even doing it when I play at 1/4 resolution.  The only solution seems to be to quit and restart and reopen the project.  Then it works temporarily for a little while but not long enough to actually edit.  I have done projects in Premiere with C100 footage in the past and have not experience this level of difficulty.
    My Media Cache is not going to the startup diskc(it is gong to the right place)
    I am on a Mac 2.66 Ghz Quad-Core Intel Xeon
    OS X 10.8.5
    10GB 1066 MHz DDR3
    NVIDIA GeForce GT 120 512 MB
    Please help - very frustrated.  If the solution is to transcode, it sort of kills the value of premiere in many ways.

    Hi,
    This might help :
    Go to File > Project Settings > General and change the Video Renderer to Mercury Playback Engine software only. Click OK and select Delete Previews.
    Thanks,
    Rameez

  • Hard Drive Setup Recommedation - Premiere Pro CC 2014

    Premiere CC on my old Win 7 64bit hard drive had smooth video previews. Premiere CC 2014 on my new Win 8.1 64bit hard drive is choppy and sluggish. Same ATI Mobility Radeon HD 4650 car which uses WDDM v1.1 as the driver. No other driver available.)
    Would love some expert advice how to setup my new configuration to be optimized for Premiere Pro CC 2014, get rid of choppy video.
    Video is not a huge part of our small 2 person business so
    1. I can't justify a large volume expensive SSD
    2. can't justify another 2+ days to reload Windows 8.1 and all my programs on the small SSD I have (might not even fit.)
    Should I leave programs and OS only on the new WD hard drive... put Premiere project and other data files on the old TOS hard drive and use something like the SDD via eSata as the scratch disk?
    Dell Studio 1747 Laptop - 8GB RAM
    1. NEW - INTERNAL WD7500BPKX new hard drive with Windows 8.1 - (Program files only) 7200 RPM, 750GB, 16 MB Buffer, 6GB/s
    2. OLD - INTERNAL TOSHIBA MK 5056GSY old hard drive w/ Windows 7 (can be wiped and only have data files) 7200 RPM, 500GB, 16 MB Buffer, 3GB/s
    3. SPARE - EXTERNAL Lacie d2Next - (partitioned, can be wiped) 5400 RPM, 500GB, 3GB/s eSata
    4. SPARE/DONATED - EXTERNAL (eSata, Firewire, USB) OCZ-Agility3 SSD (can be wiped) ~100GB
    Thanks. These configurations are an art that we can't specialize in due to our staff size, workload and budget.

    Tweakers Page - Disk Setup but start with increasing RAM to at least 16 GB.

Maybe you are looking for