I've been struggling for weeks trying to troubleshoot and narrow down my encoding nightmare on my own and I have finally succumbed to getting the forum's or Adobe's Help.
Rendering a Premiere Pro CC project with via Export Media > Queue to AME in H.264 causes the encode to randomly fail on multiple projects.
I find it quite amazing that this error happens as I surely am not the only one rendering ProRes to H.264 on a new Macbook Pro!
Output preview starts to flicker then encoding stops randomly, preview window turns to a black screen or simply stalls while the Elapsed Time keeps rolling, PProheadless crashes in Console, encoding sometimes resumes after several minutes post the crash (but sometimes not) however the final output in such case is garbled before/after the crash. Computer is useable. All other software shutdown. Not using computer during encode. Can reproduce virtually every time.
Early 2013 Retina Macbook Pro
Processor 2.8 GHz Intel Core i7
Memory 16 GB 1600 MHz DDR3
Graphics NVIDIA GeForce GT 650M 1024 MB
Premiere 7.0.1 (105)
Adobe Media Encoder 22.214.171.124 (64bit)
Creative Cloud Latest Updates
Cuda 5.5.25 (latest)
GPU Driver: 8.12.47 310.40.00.05f01
OS X 10.8.4 (latest)
ProRes 4:2:2 or AVCHD sources
No nested sequences
Video track with image over whole sequence
Video track with text over whole sequence
Sometimes video track with adjustment layer
Standard disolve effects between cuts
4 effects used: denoiser for audio, luma corrector and twice Fast Color Corrector
No third party plugins installed nor used
Sequence is set to Maximum Bit Depth / Max Render Quality / Linear Color
Use Previews off
Encode is set to Maximum Render Quality and always H.264 2pass VBR.
Errors in console:
8/27/13 12:38:01.144 AM PProHeadless: [CL_INVALID_OPERATION] : OpenCL Error : Failed to retrieve device information! Invalid enumerated value!
This is seen at multiple times while starting Premiere (no crash) and while starting the encodes and usually after/during the crash.
Process: PProHeadless 
Path: /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents/PProHeadless.app/Contents/MacOS/PProHeadless
Version: 7.0.1 (126.96.36.199)
Code Type: X86-64 (Native)
Parent Process: dynamiclinkmanager 
User ID: 501
Date/Time: 2013-08-26 21:12:21.878 +0200
OS Version: Mac OS X 10.8.4 (12E55)
Report Version: 10
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGSEGV)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Full Crash report:
Attempts to solve the issue:
Tried encoding without external montior
Tried encoding with source on internal HDD, output internal HDD, source exterbak RAID, output internal HDD
Tried encoding with AME while Premiere is open in the background and without it opened in the background
Uninstalled other software that could mess with the graphics: Colormunki, Parallels.
Software mode is fine on all attempts in AME however encoding takes 2-3x longer. On a $3000 laptop it's not really great.
Encoding directly via Export Media > Export without Queuing to Adobe Media Encoder seems to work fine. I have not tried this too many times because I need to render multiple outputs and doing it without AME means a lot of 'sitting and waiting' to click Export for the next format. This is not an option.
Tried deleting the Media Cache
Completely reinstalled OS X 10.8.4 from scratch with no other software running and tried to export. Same problem.
Performed Apple hardward test. No problems.
I'm planning on installing Bootcamp so I can test the problem in the Windows version and I could pinpoint it to a hardware problem rather than a software problem.
Problem happens with CUDA and Open CL modes although in Open CL mode, the whole computer tends to freeze intead of just 'stalling'.
Editing and playback inside Premiere is OK! Even encoding out of Premiere is OK directly but not useful for me as I need to render each project to 5 different H.264 formats.
I hope you guys or Adobe's Support can find a solution to this problem because I'm really stuck between a rock and a hard place.
I've submitted a bug report but their reply is not very comforting:
but their bug report says "Due to the volume of submissions we receive, responses to inquiries are generally not possible. However, we may contact you if we need clarification on your submission." Nice.