>both crash at the same point
What are you editing, and have you done a frame by frame look to see if there is a problem at that "same point" in the timeline?
I am importing .MTS files from a JVC camcorder. I didn't have this problem with CS5.5 but in all fairness, I built a new machine and did a fresh install with Windows for CS6.
I have not done a frame by frame look. Not sure how to do that. But I do not believe it is the video. I have created new projects using different video clips from previous projects that I was able to do with CS5.5. I have also created projects using standard mpg and avi files. However the end result is the same, when trying to export using H.264 youtube presets or the HD presets, it crashes.
What's the error message?
I solved what might be a similar problem last evening by lowering the speed of my i7-3055K (nominal 3.9GHz) to 4.2GHz from 4.5GHz.
My symptoms were similar: new PC build (10 days old); crashing or blue screens about 1 minute into a 3 minute Premiere export or AME render, Win7 Pro. The system had previously been very stable. At first I suspected an H264 codec problem or an iTunes/Quicktime incompatibility but when an AVI render using the NTSC DV Widescreen preset crashed it broadened my search for solutions. Mercury GPU render on/off did not fix the crash problem.
The render last evening was probably the first time that my new CPU was seriously stressed. Lowering the CPU speed was the quick solution. Overclocking sites/forums probably have tips on stress tests, memory tests, voltage tweaking, etc but as long as the system is stable I'll probably be satisified with the slower CPU solution.
The CPU cooling is the Intel stock fan. 32GB of Corsair memory is running at its rated PC1600. CPU and memory voltages are the defaults, i.e., no tweaking. Intel DZ77RE-75K motherboard. EVGA GTX680 FTW+ 4GB at its defaults, i.e., no overclocking/tweaking. 1000 watt power supply , which is probably overkill but it's what I had lying around (I have an almost identical setup (GTX460 rather than GTX680) which runs fine at 4.2GHz with a 700-watt PSU -- but I've never stressed that 2nd PC with an Premiere/AE/AME render).
Thanks everyone for the quick responses, your advice is most appreciated.
Ed_Elliott, good advice on the overcloaking idea. It didn't even occur to me. Good news is that it worked. Not sure why but it gives me something else to research. I ran several of the projects that previously failed and they all worked in both Adobe Premiere and AME. I was clocking at 3.7 and normal is 3.4. I lowered it to 3.2 and it worked so I will now try to set it up at normal.
I know this is not the right forum for this but any ideas on why overclocking would affect this?
Thanks again Jon, Jim, and Ed.
>any ideas on why overclocking would affect this?
Heat... an overheating CPU will cause problems, up to and including a computer that just stops when a sensor in the CPU tells the power supply to shut down
You need a REALLY good CPU cooler to overclock, as well as LOTS of case fans to push room air into the case and out the back
This is NOT with an overclocked system, but the i7 3770 computer I built for my wife in November has 2 optional case fans (front & side) and her temps are CPU 84F & Drives 77F & ATI card 91F and that is with using a stock Intel CPU cooler
Encoding makes the CPU run hotter anyway, and overclocking just adds to that
I'm still running with my slower CPU settings but have learned that higher CPU utilization can be obtained by disabling parking of the CPU cores. During renders the CPU utilization has moved from roughly 50%-65% with parking enabled to 70%-95% with parking disabled. And Resource Monitor now indicates that the CPU is operating at 118% of max speed (I think that means 118% of 4.2 GHz but my understanding of the technical aspects is superficial.). Regardless of the numbers, renders are faster and the system is stable.
To disable parking use ParkControl from http://bitsum.com/about_cpu_core_parking.php . ParkControl does not do an install so I've pinned ParkControl to the taskbar. My current practice is to disable parking before rendering then enable parking when I don't plan on rendering soon. Despite the warning which pops up the first time ParkControl is run I haven't encountered any issues.