Premiere Pro CC 2014 with NVIDIA system freezes (Win7x64)

It appears after perhaps the last update Premiere Pro CC 2014 started freezing during editing. It appears to happen mostly with 4K material and using the Ultra key and alpha blending but may also occur with 4K titles. The sequences are 23.976 1080p, with mixed footage from the Sony A7S (50 Mbps XAVC-S/H.264) and GH4 (4K 100 Mbps H.264). There are also frequent crashes with GPUFoundation.dll (Mercury + CUDA). No freezing with software only rendering. I tried a variety of drivers when using a Quadro 5000 with no change in freeze behavior. I tried a new GTX 770 (clean driver install) and the freeze behavior and GPUFoundation.dll crashes are the same, however now even the mouse freezes. With the Quadro 5000, the entire Windows GUI would freeze (become inactive), however the mouse would still move. Thus, it appears there are issues with both NVidia drivers and Premiere Pro CUDA code path on Windows (app errors shouldn't be able to lock up the entire GUI). GPU Meter shows low GPU and GPU memory utilization during the freezes. The freezes typically occur when switching between clips during playback or scrubbing (more often with fast scrubbing). As a developer, it feels like some kind of semaphore lock / race condition, since during the freezes CPU, GPU, and memory utilization are very low. Additional hardware info: 2010 MacPro 12-Core, 24GB RAM running Win7x64 (with latest updates). Side note: PPro used to hang in memory on exit, but stopped after a recent Microsoft forced update (PPro now crashes sometimes on exit but no longer hangs in memory (used to have to kill it after exiting every time)). Has this been reported before? (A7S XAVC & GH4 4K footage is relatively new)

This crash occurred when dragging Black Video with Noise and other effects on top of alpha composited layers (+3 layers). CUDA turned the rendered area black, so I switched to OpenCL. This crash happened a few minutes later. While this would appear to be an Nvidia driver error (OpenCL), perhaps the developers can investigate. The system is very stable except when doing complex operations in PPro (and only PPro crashes). A tried and true Quadro 5000 crashed in the same way (totally different hardware and drivers).
The full debug info wouldn't post, edited shorter:
     Application Specific Signatures:
     Graphics hardware encountered an error and was reset: 0x0000001f
Process:         Adobe Premiere Pro CC 2014 [380]
Path:            /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
Identifier:      com.adobe.AdobePremierePro
Version:         8.0.1 (8.0.1)
Code Type:       X86-64 (Native)
Parent Process: launchd [191]
Responsible:     Adobe Premiere Pro CC 2014 [380]
User ID:         501
Date/Time:       2014-10-01 03:13:25.803 -0700
OS Version:      Mac OS X 10.9.5 (13F34)
Report Version: 11
Anonymous UUID: 3E030FD4-F38F-857C-3EB9-85D10E36AB49
Crashed Thread: 11 Dispatch queue: opencl_runtime
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
abort() called
Application Specific Signatures:
Graphics hardware encountered an error and was reset: 0x0000001f
Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib         0x00007fff8bcbfa1a mach_msg_trap + 10
1   libsystem_kernel.dylib         0x00007fff8bcbed18 mach_msg + 64
2   com.apple.CoreFoundation       0x00007fff8bb10f15 __CFRunLoopServiceMachPort + 181
3   com.apple.CoreFoundation       0x00007fff8bb10539 __CFRunLoopRun + 1161
4   com.apple.CoreFoundation       0x00007fff8bb0fe75 CFRunLoopRunSpecific + 309
5   com.apple.HIToolbox           0x00007fff8d375a0d RunCurrentEventLoopInMode + 226
6   com.apple.HIToolbox           0x00007fff8d3757b7 ReceiveNextEventCommon + 479
7   com.apple.HIToolbox           0x00007fff8d3755bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
8   com.apple.AppKit               0x00007fff86c7424e _DPSNextEvent + 1434
9   com.apple.AppKit               0x00007fff86c7389b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
10 com.apple.AppKit               0x00007fff86c6799c -[NSApplication run] + 553
11 com.adobe.Frontend.framework   0x00000001000ca38d FE::MacApplication::RunSelf() + 45
12 com.adobe.Frontend.framework   0x000000010004898a FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 4058
13 com.adobe.Frontend.framework   0x00000001000cbc44 FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 276
14 com.adobe.Frontend.framework   0x00000001000d2e25 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
15 com.adobe.AdobePremierePro     0x00000001000018ac main + 508
16 com.adobe.AdobePremierePro     0x00000001000016a4 start + 52
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib         0x00007fff8bcc4662 kevent64 + 10
1   libdispatch.dylib             0x00007fff8a0c2421 _dispatch_mgr_invoke + 239
2   libdispatch.dylib             0x00007fff8a0c2136 _dispatch_mgr_thread + 52
Thread 2:
0   libsystem_kernel.dylib         0x00007fff8bcc464a kevent + 10
1   com.adobe.dvatransport.framework 0x0000000100e294fc boost::asio::detail::kqueue_reactor::run(bool, boost::asio::detail::op_queue<boost::asio::detail::task_io_service_operation>&) + 236
2   com.adobe.dvatransport.framework 0x0000000100e291a7 boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock<boost:: asio::detail::posix_mutex>&, boost::asio::detail::task_io_service_thread_info&, boost::system::error_code const&) + 375
3   com.adobe.dvatransport.framework 0x0000000100e28d18 boost::asio::detail::task_io_service::run(boost::system::error_code&) + 552
4   com.adobe.dvatransport.framework 0x0000000100e18157 SkyConnectionEnv::MainLoop() + 167
5   com.adobe.dvatransport.framework 0x0000000100e17c09 SkyConnectionEnv::StaticThreadFunc(SkyConnectionEnv*) + 9
6   com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
7   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
8   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
9   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 3:
0   libsystem_kernel.dylib         0x00007fff8bcc3716 __psynch_cvwait + 10
1   libsystem_pthread.dylib       0x00007fff8c0d0c3b _pthread_cond_wait + 727
2   com.adobe.dvacore.framework   0x000000010036a0ab boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock<boost:: asio::detail::posix_mutex>&, boost::asio::detail::task_io_service_thread_info&, boost::system::error_code const&) + 139
3   com.adobe.dvacore.framework   0x0000000100369e18 boost::asio::detail::task_io_service::run(boost::system::error_code&) + 552
4   com.adobe.dvacore.framework   0x0000000100369bda boost::asio::detail::posix_thread::func<boost::asio::detail::resolver_service_base::work_ io_service_runner>::run() + 42
5   com.adobe.dvatransport.framework 0x0000000100e29bb3 boost_asio_detail_posix_thread_function + 19
6   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
7   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
8   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 4:
0   libsystem_kernel.dylib         0x00007fff8bcc3716 __psynch_cvwait + 10
1   libsystem_pthread.dylib       0x00007fff8c0d0c3b _pthread_cond_wait + 727
2   com.apple.CoreServices.CarbonCore 0x00007fff824bc800 TSWaitOnCondition + 108
3   com.apple.CoreServices.CarbonCore 0x00007fff824bc9ff TSWaitOnConditionTimedRelative + 172
4   com.apple.CoreServices.CarbonCore 0x00007fff8248d145 MPWaitOnQueue + 192
5   com.adobe.dvacore.framework   0x00000001003a359d dvacore::threads::ThreadSafeDelayQueue::PopWithTimeout(std::auto_ptr<dvacore::threads::Al locatedFunctionT<boost::function<void ()> > >&, int) + 141
6   com.adobe.dvacore.framework   0x00000001003a1500 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 160
7   com.adobe.dvacore.framework   0x00000001003919ac boost::function0<void>::operator()() const + 28
8   com.adobe.dvacore.framework   0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
9   com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
10 libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
11 libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
12 libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 5:
0   libsystem_kernel.dylib         0x00007fff8bcc3716 __psynch_cvwait + 10
1   libsystem_pthread.dylib       0x00007fff8c0d0c3b _pthread_cond_wait + 727
2   com.adobe.GPUFoundation.framework 0x000000010941b8d6 void boost::condition_variable_any::wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&) + 70
3   com.adobe.GPUFoundation.framework 0x0000000109419705 GF::Device::AcquireExclusiveAccess() + 117
4   com.adobe.PlayerMediaCore.framework 0x0000000129518684 AdobePlayer::PlayerDisplay::UpdateWindow() + 372
5   com.adobe.PlayerMediaCore.framework 0x000000012952b2a5 AdobePlayer::PlayerMain::OnUpdate() + 21
6   com.adobe.PlayerMediaCore.framework 0x0000000129530501 PrPlayModule<AdobePlayer::PlayerMain>::PlayEntry(int, pmStdParms*, void*, void*) + 241
7   com.adobe.PlayerMediaCore.framework 0x0000000129530390 xPlayEntry + 16
8   com.adobe.PlayerHost.framework 0x00000001057238c4 ML::CallPlayerModuleGuarded(int (*)(int, pmStdParms*, void*, void*), int, pmStdParms*, void*, void*, int*, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 276
9   com.adobe.PlayerHost.framework 0x0000000105721669 ML::PlayerModule::CallPlugin(int, void*, void*) + 153
10 com.adobe.PlayerHost.framework 0x0000000105745c36 ML::VideoPlayer::CallPlayModuleSelector_Update() + 86
11 com.adobe.PlayerHost.framework 0x000000010573421d ML::VideoPlayer::ForceDisplayRedraw(ML::PlayerOutputQuality) + 205
12 com.adobe.PlayerHost.framework 0x0000000105728a34 ML::PlayModuleThreadQueue::ExecuteDeferredCall(ASL::ObjectPtr<ML::DeferredCallBase, ASL::AtomicValue>) + 340
13 com.adobe.PlayerHost.framework 0x0000000105727935 ML::PlayModuleThreadQueue::ServiceQueue() + 293
14 com.adobe.dvacore.framework   0x00000001003a159e dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 318
15 com.adobe.dvacore.framework   0x00000001003919ac boost::function0<void>::operator()() const + 28
16 com.adobe.dvacore.framework   0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
17 com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
18 libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
19 libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
20 libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 6:
0   libsystem_kernel.dylib         0x00007fff8bcc3716 __psynch_cvwait + 10
1   libsystem_pthread.dylib       0x00007fff8c0d0c77 _pthread_cond_wait + 787
2   com.apple.CoreServices.CarbonCore 0x00007fff824bc9e7 TSWaitOnConditionTimedRelative + 148
3   com.apple.CoreServices.CarbonCore 0x00007fff8248d145 MPWaitOnQueue + 192
4   com.adobe.dvacore.framework   0x00000001003a359d dvacore::threads::ThreadSafeDelayQueue::PopWithTimeout(std::auto_ptr<dvacore::threads::Al locatedFunctionT<boost::function<void ()> > >&, int) + 141
5   com.adobe.dvacore.framework   0x00000001003a1500 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 160
6   com.adobe.dvacore.framework   0x00000001003919ac boost::function0<void>::operator()() const + 28
7   com.adobe.dvacore.framework   0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
8   com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
9   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
10 libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
11 libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 7:
0   libsystem_kernel.dylib         0x00007fff8bcbfa1a mach_msg_trap + 10
1   libsystem_kernel.dylib         0x00007fff8bcbed18 mach_msg + 64
2   libcuda_334.01.03_mercury.dylib 0x00000001223f85a2 cuosEventWait + 210
3   libcuda_334.01.03_mercury.dylib 0x000000012233e922 intHandlerMain + 114
4   libcuda_334.01.03_mercury.dylib 0x00000001223f9479 cuosPosixThreadStartFunc(void*) + 41
5   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
6   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
7   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 8:
0   libsystem_kernel.dylib         0x00007fff8bcbfa1a mach_msg_trap + 10
1   libsystem_kernel.dylib         0x00007fff8bcbed18 mach_msg + 64
2   libclh.dylib                   0x000000011ae0fe19 0x11a800000 + 6356505
3   libclh.dylib                   0x000000011a8c5df2 0x11a800000 + 810482
4   libclh.dylib                   0x000000011ae10c69 0x11a800000 + 6360169
5   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
6   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
7   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 9:
0   libsystem_kernel.dylib         0x00007fff8bcbfa1a mach_msg_trap + 10
1   libsystem_kernel.dylib         0x00007fff8bcbed18 mach_msg + 64
2   libclh.dylib                   0x000000011ae0fe19 0x11a800000 + 6356505
3   libclh.dylib                   0x000000011a8c5df2 0x11a800000 + 810482
4   libclh.dylib                   0x000000011ae10c69 0x11a800000 + 6360169
5   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
6   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
7   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 10:
0   libsystem_kernel.dylib         0x00007fff8bcbfa1a mach_msg_trap + 10
1   libsystem_kernel.dylib         0x00007fff8bcbed18 mach_msg + 64
2   libclh.dylib                   0x000000011ae0fe19 0x11a800000 + 6356505
3   libclh.dylib                   0x000000011a8c5df2 0x11a800000 + 810482
4   libclh.dylib                   0x000000011ae10c69 0x11a800000 + 6360169
5   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
6   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
7   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 11 Crashed:: Dispatch queue: opencl_runtime
0   libsystem_kernel.dylib         0x00007fff8bcc3866 __pthread_kill + 10
1   libsystem_pthread.dylib       0x00007fff8c0cf35c pthread_kill + 92
2   libsystem_c.dylib             0x00007fff8c131bba __abort + 145
3   libsystem_c.dylib             0x00007fff8c131b29 abort + 140
4   libGPUSupportMercury.dylib     0x00007fff89db41ca gpusKillClient + 111
5   libGPUSupportMercury.dylib     0x00007fff89db4b51 gpusQueueSubmitDataBuffers + 155
6   libclh.dylib                   0x000000011a90ee26 0x11a800000 + 1109542
7   libclh.dylib                   0x000000011a8b104a 0x11a800000 + 725066
8   libclh.dylib                   0x000000011a8b10a1 0x11a800000 + 725153
9   libclh.dylib                   0x000000011a8b4394 0x11a800000 + 738196
10 libclh.dylib                   0x000000011a910425 clhCtxSynchronize + 21
11 com.nvidia.web.GeForceGLDriverWeb 0x00001234402e627d gldFinishQueue + 234
12 com.apple.opencl               0x00007fff87917abe 0x7fff87911000 + 27326
13 com.apple.opencl               0x00007fff87931123 0x7fff87911000 + 131363
14 com.apple.opencl               0x00007fff8793414a 0x7fff87911000 + 143690
15 libdispatch.dylib             0x00007fff8a0c028d _dispatch_client_callout + 8
16 libdispatch.dylib             0x00007fff8a0c6a18 _dispatch_barrier_sync_f_slow + 460
17 com.apple.opencl               0x00007fff87933faa 0x7fff87911000 + 143274
18 com.apple.opencl               0x00007fff8792a202 clEnqueueMapBuffer + 631
19 com.adobe.RendererGPU.framework 0x0000000111714245 GF::ScopedRecordedHostMemory::Map() const + 133
20 com.adobe.RendererGPU.framework 0x00000001117685ea RendererGPU::PointwiseFilterHostNode::ApplyConcatenatedPointwiseFilters(ASL::InterfaceRef <MF::IVideoFrame, MF::IVideoFrame> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame> const&, boost::shared_ptr<RenderResults> const&, std::vector<RendererGPU::PointwiseFilter, std::allocator<RendererGPU::PointwiseFilter> > const&) + 826
21 com.adobe.RendererGPU.framework 0x0000000111767daf RendererGPU::PointwiseFilterHostNode::Process(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&) + 831
22 com.adobe.RendererGPU.framework 0x000000011171d2b8 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 1448
23 com.adobe.RendererGPU.framework 0x00000001117ad03c RenderNodeBase::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 76
24 com.adobe.RendererGPU.framework 0x000000011171d094 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 900
25 com.adobe.RendererGPU.framework 0x00000001117ad03c RenderNodeBase::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 76
26 com.adobe.RendererGPU.framework 0x000000011171d094 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 900
27 com.adobe.RendererGPU.framework 0x00000001117ad03c RenderNodeBase::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 76
28 com.adobe.RendererGPU.framework 0x000000011171d094 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 900
29 com.adobe.RendererGPU.framework 0x00000001117194d5 RendererGPU::CompositorNode::Process(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&) + 1413
30 com.adobe.RendererGPU.framework 0x000000011171d2b8 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 1448
31 com.adobe.RendererGPU.framework 0x000000011170f36f RendererGPU::(anonymous namespace)::RendererGPU::ProduceFrame(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, std::string*, ASL::ParamRect<int>) + 1279
32 com.adobe.PlayerMediaCore.framework 0x0000000129535bf0 AdobePlayer::RenderRequest::ProduceFrame(ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, RenderParams const&, std::string*, ASL::ParamRect<int>) + 96
33 com.adobe.PlayerMediaCore.framework 0x000000012951cefd AdobePlayer::PlayerDisplay::PresentRenderRequestImpl(boost::shared_ptr<AdobePlayer::Rende rRequest> const&) + 1901
34 com.adobe.PlayerMediaCore.framework 0x00000001295204db AdobePlayer::PlayerDisplay::PresentLastCompletedRenderRequestImpl() + 267
35 com.adobe.dvacore.framework   0x00000001003a159e dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 318
36 com.adobe.dvacore.framework   0x00000001003919ac boost::function0<void>::operator()() const + 28
37 com.adobe.dvacore.framework   0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
38 com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
39 libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
40 libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
41 libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
External Modification Summary:
Calls made by other processes targeting this process:
    task_for_pid: 319
    thread_create: 0
    thread_set_state: 0
Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
Calls made by all processes on this machine:
    task_for_pid: 56776
    thread_create: 1
    thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=679.6M resident=223.0M(33%) swapped_out_or_unallocated=456.6M(67%)
Writable regions: Total=19.5G written=15.6G(80%) resident=14.2G(73%) swapped_out=3.0G(16%) unallocated=5.3G(27%)
REGION TYPE                      VIRTUAL
===========                      =======
ATS (font support)                 32.0M
ATS (font support) (reserved)         8K        reserved VM address space (unallocated)
CG backing stores                  23.8M
CG image                            584K
CG raster data                       48K
CG shared images                    204K
CoreImage                             8K
Foundation                            4K
IOKit                              78.3M
IOKit (reserved)                    268K        reserved VM address space (unallocated)
Image IO                           1032K
Kernel Alloc Once                     8K
MALLOC                              1.5G
MALLOC (admin)                       32K
MALLOC_LARGE (reserved)             512K        reserved VM address space (unallocated)
Memory Tag 241                      128K
Memory Tag 242                       12K
Memory Tag 249                      192K
Memory Tag 251                       24K
OpenCL                              1.0G
OpenGL GLSL                        1664K
STACK GUARD                        56.8M
Stack                             113.7M
VM_ALLOCATE                        52.6G
VM_ALLOCATE (reserved)             30.4M        reserved VM address space (unallocated)
__DATA                             71.6M
__IMAGE                             528K
__LINKEDIT                        225.7M
__NV_CUDA                           456K
__TEXT                            453.8M
__UNICODE                           544K
mapped file                        84.0M
shared memory                        68K
===========                      =======
TOTAL                              56.3G
TOTAL, minus reserved VM space     56.3G
Model: MacPro5,1, BootROM MP51.007F.B03, 12 processors, 6-Core Intel Xeon, 2.93 GHz, 24 GB, SMC 1.39f11
Graphics: NVIDIA GeForce GTX 770, NVIDIA GeForce GTX 770, PCIe, 2048 MB
Memory Module: DIMM 1, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 2, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 3, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 5, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 6, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 7, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.7f3 14616, 3 services, 15 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
PCI Card: NVIDIA GeForce GTX 770, Display Controller, Slot-1
PCI Card: pci1095,3132, SATA Controller, Slot-2
PCI Card: NVIDIA GeForce GTX 770, NVDA,Parent, Slot-1
PCI Card: pci1b73,1100, USB eXtensible Host Controller, Slot-4
Serial ATA Device: HL-DT-ST DVD-RW GH61N
Serial ATA Device: WDC WD1001FALS-41Y6A0, 1 TB
Serial ATA Device: OWC Mercury Extreme Pro SSD, 240.06 GB
Serial ATA Device: OWC Mercury Extreme Pro SSD, 240.06 GB
Serial ATA Device: WDC WD4001FAEX-00MJRA0, 4 TB
USB Device: Scarlett 2i2 USB
USB Device: Keyboard Hub
USB Device: USB-PS/2 Optical Mouse
USB Device: Apple Keyboard
USB Device: My Passport 0741
USB Device: My Passport 0820
USB Device: USB3.0 Media Reader
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Logitech RumblePad 2 USB
USB Device: Mobile Keys 49
FireWire Device: built-in_hub, Up to 800 Mb/sec
Thunderbolt Bus:

Similar Messages

How does premiere pro CC work with nvidia GT 630M (2GB) vega???!

how does premiere pro CC work with nvidia GT 630M (2GB) vega????!

That will work. I would just not expect major performance with a heavier load on playback.
Eric
ADK

Adobe Premiere Pro CC 2014.2 (8.2) freezes up constantly on Mac OS X Yosemite

After the latest update (no idea which one but the latest update) Premiere Pro cc just keeps freezing up constantly. There's no indication what brings it up but after different periods of time I just get the apple wheel and the entire program freezes up. I force quit and get the "sorry, a serious problem has occured", blabla. Sometimes it's in the middle of cutting a clip, sometimes it's while trimming. There isn't a single indication what causes it. At first I thought it was only because of using a multicam clip, but that's not the case anymore. I tried reducing memory to other apps, deleting preview files, deleting autosaves, turning off autosave altogether, deleting Adobe Premiere 8.0 preference file, changing permissions, basically everything in this post: Re: Adobe Premiere Pro CC keeps crashing... (Which now also seems totally neglected by Adobe).
Believe me, there's hardly a thing I haven't tried.
It's getting REALLY frustrating now and it's time something is done about this. Yes I know, "don't just say it's frustrating, explain the problem", but that fase has passed now. I'm paying for this product and it needs to work like it should.
Also I know I'm not the only one who's having these problems.
My specs are:
OS X Yosemite 10.10.1
MacBook Pro (Retina, Mid 2012)
2,3 GHz Intel Core i7
16 GB 1600 MHz DDR3
NVIDIA GeForce GT 650M 1024 MB

Hi JJ,
JJ Millen wrote:
It is not about the past times you may or may not have participated, but about the latest message from rob654 and my last messages in that thread (which are clearly not about Windows).
One great reason to get a Mac only version of the post. It is never a good idea to post on a Windows post with Mac problems. And when threads get so long and unruly, the team can't focus on the actual issue so it doesn't get the attention it needs.
Now that we have that sorted out...
JJ Millen wrote:
I checked that and it says 8.2.0. (65) build.
Thanks for the verification. You are running Premiere Pro CC 2014.2 (8.2). It helps to have that absolutely clear.
JJ Millen wrote:
Here are all the checkpoints mentioned in that thread, applicable to my project:
- Version 8.2.0;
- My Creative Cloud says Premiere Pro is up-to-date;
- Operating system is OS X Yosemite version 10.10.1 (14B25);
Very well, did things operate any differently on Mac OS X 10.9.x? Or did you have the same problem?
JJ Millen wrote:
Type: MPEG Movie
File Size: 4,0 GB
Image Size: 1920 x 1080
Frame Rate: 25,00
Source Audio Format: 48000 Hz - 16 bit - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Total Duration: 00:12:35:16
Pixel Aspect Ratio: 1,0;
So is this H.264? What is the camera that you are working with? DSLR?
JJ Millen wrote:
- I do not get any error messages, except for the "Sorry, a serious problem has occurred"-message after I have to force quit my Premiere because of the freeze;
What kind of drives are the media files stored on?
Are the permissions set correctly (as Read/Write) for the Mac HD and your media drives?
Are the permissions set correctly for all the Adobe folders as I outlined in my blog?
JJ Millen wrote:
- The problem mostly occurs when cutting a clip with the razor tool, regardless of the kind of clip;
When you import clips, are you using File > Import, or are you importing via the Media Browser?
JJ Millen wrote:
- Yes this has worked before, the problems started either after creating a submix (which I've deleted, without result) and/or after updating to a newer version of Premiere CC;
Definitely do not update Premiere Pro or OS X when in the middle of a project. Wait until it's complete. If you did either or both of these things, you can cause your project to become corrupt. After your current project is wrapped, test with a brand new project.
JJ Millen wrote:
- The only software I run actively besides Premiere is Apple's Mail program, Safari and/or Chrome, sometimes Wire, sometimes Spotify;
- I currently have no third-part effects or codecs installed in Premiere;
- I installed the latest CUDA Mac Driver, version 6.5.37 (release date 01/14/2015);
- The problem just happens while working in my sequence, not in any final output. I don't know what is meant by "previews", but I have the yellow bar indicator in my sequence, if that's info you need.
I have heard of others having issues with OS X 10.10 and NVIDIA GPUs. My advice is to consider downgrading your OS if you continue to have issues. I believe I have avoided a lot of trouble by sticking to OS X 10.8.5.
Previews AKA the Media Cache are your "render files." They can become corrupt, so it's a good idea to trash them when troubleshooting. You can locate them via your Preferences > Media. Click the Browse button.
JJ Millen wrote:
Okay I went through that menu (which I'm not eager to do, I prefer direct contact) and came across the CUDA setting inside the project settings. I've now enabled the "Mercury Playback Engine GPU Acceleration (CUDA)", which might help.
So were you set to "Mercury Playback Engine Software Only" or "Mercury Playback Engine GPU Acceleration (OpenCL)" prior to changing it to "Mercury Playback Engine GPU Acceleration (CUDA)?
JJ Millen wrote:
Testing with a brand new project is not an option. I have a deadline for my current project and it's impossible to start from scratch. What I did try is start a new project and importing the existing one, which didn't help so far.
I was just wondering if you experienced the same issues in a new project. Any project you update to a new version is suspect, in my opinion. In the future, try to avoid doing that. If your current project is corrupt, I could see why you are having certain issues.
For what it's worth, we had another user that exhibited similar issues until they started with a brand new Premiere Pro CC 2014.2 (8.2) file.
Since importing your 8.1 file to a new 8.2 project isn't working, make sure to triple check permissions on all the Adobe folders I laid out in my blog post: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)
It's the #1 reason Mac users experience freezing and crashing. The other one I'd look at is that NVIDIA drivers are not working well with Yosemite. Finally, if you update a project across versions, it can become corrupt. Not much you can do about that except start a new project ASAP.
Thanks,
Kevin

Performance Issue Premiere Pro CC 2014 with Late 2013 Mac Pro

Hi all!
Im working Premiere Pro CC 2014 on a Late 2013 Mac Pro 6 core D700s and 32GB RAM on OSX 10.9.4
After the 2014 update i have experience some drop frames and hangs with a new 1080p timeline project.
And it later results in software hang and crashing . even after a quit (force quit) and re-poen, it seems to happen again and again.
Even after a system reboot seems to be fine at first, but it still crashes on the project.
Tired to render the timeline and still the same. Also tried to delete rendered file and play right with timeline with yellow bar, same.
Even drop the preview playback to 1/2 and still..
files are mixed 1080p footage from Canon 5d3, 60D, T2i.
I have 3 layers (interview video with different angles) and a title layer (hard subtitle)
had some light color correction with fast color corrector and a sharpening on the 5d3 layer.
Ive work with the CC premiere pro before with mac pro and everything is fine and never hand an issue.
All my memory setting are set for performance and i have open GL on my D700s
Im not sure if this a software issue or someone my hardware is not working right?!
Thanks in advance!

I am having the same issues.
Im working on a late 2012 iMac, 3.4 GHz Intel Core i7. 32 Gb ram, NVIDIA GeForce GTX 680MX, OS X 10.9.4.
I'm editing RED footage, about 3 TB worth for this project from a Promise Pegasus drive.
The software really slows down when using the TYPE tool and also when scrubbing through footage.
When I attempt to quite the software and restart, the interface goes away but the app is still running but says "not responding" when I attempt to force quit.
If you've figured it out since then Id love to know what works.
Thanks!
G

Premiere pro cc 2014 crashing my system

I have a new Mac book pro (2014) 16 gbs ram.. everything is upgraded to max. downloaded the new premiere pro CC 2014. and it's crashing my system every time.
it takes about 4 mins. with the spinning ball. Then all the processes and plugins load in. Then it says "premiere pro couldn't find any capable video play modules. Please update your video display drivers
and start again" WHICH IS FREAKING IMPOSSIBLE SINCE I AM ON A MAC BOOK PRO. So sick and tired of companies not working out glitches in this crap. Could someone please help. I am so
angry and frustrated here.
Sean

Somewhat figured it out and extremely frustrated.
I created another new user with administrative privileges. When i did this i got AE CC 2014 and Premiere Pro CC 2014 working. However, they will not work in my regular main account which has
administrative priviledges. On the phone with ADOBE they told me that it was a permissions issue and that it was Apple's Problem. Which I CALL B.S.!!!
I tried to repair permissions in disk utility knowing full well that it wouldn't fix the issue. How on earth would apple know what the permissions errors in folders or files are for Adobe products!!
I was very angry and upset with the Adobe technical support for this issue.
On the new mac pro i am using i was able to create the new administrator account and erase the old administrator account since i have 0 documents or old data that i have on it other than programs.
However, on my mac pro. I have well over 15 years of data on it including 100 GB of music, etc... that i simply can't just erase away. Not too interested in working on 2 different accounts either.
Not sure what to do now and i am extremely frustrated.

Premiere Pro CC 2014 (8.1.0) freezes while scrubbing timeline

Using a Mac Mini (late 2012 model), running Mavericks 10.9.5
Processor: 2.6 GHz Intel Quad Core i7
Memory: 16 GB
Graphics: Intel HD Graphics 4000 1024MB
I am also using a 2TB Fantom G-Force Megadisk external HD to store all my media. It is connected via a Firewire 800 cable
I've been having a lot of trouble with Premiere Pro CC 2014. While scrubbing through a project, a frame will all of a sudden freeze in the program monitor. I have my processors displayed on my menu bar and I've noticed that whenever I run into lag time or freezing the 8 processors won't all be firing, usually just one is actually working at that time. I am also only running one program at a time as to not tie up my processor.
All of my source files are usually AVCHD. Most of my work is under 10 minutes long, so they are just short corporate videos not feature length movies. I understand that editing native files can really slow your processors so with my latest project I consolidated and transcoded in the Project Manager to Apple ProRes in order to test that. Even with that I'm still having the exact same problem.
These are some other steps I've taken to correct this:
I've contacted Adobe several times and they told me that the Graphics Card is known to have problems and to contact Apple. I contacted Apple and they said there are no known problems with that Graphics Card it sounds like a software issue. I ran a disk permissions test and uninstalled and reinstalled the software. Same problems. Nothing has worked.
I've trashed my preferences as well
Really it seems that both Adobe and Apple are pointing the finger at each other. All I want to do is edit my videos without having to restart Premiere Pro every 10 minutes.

This seems to be an issue for me A LOT too. I can't keep Premiere open for more than 2 minutes at a time right now. The Customer Service rep from India did a "Team View" on my computer before and after 45 minutes finally fixed the issue. But I can't seem to get a hold of customer support right now. I hope you and I both find a solution soon. Good luck!

Premiere pro CC 2014 with Aja Kona playback issue

After last Premiere pro update, have big problem with aja kona Lhi playback. After 5 sec of playback video and audio freezes. After 5-10 sec it start playing but very badly. Video strobing and audio jumping. then it freezes again. When i turn off Aja playback all fine. I have done all settings correctly following instructions. Audio output in preferences other than Aja and etc.
I have this problem on both computers with OSX Maveric and Aja Kona cards.

After last Premiere pro update, have big problem with aja kona Lhi playback. After 5 sec of playback video and audio freezes. After 5-10 sec it start playing but very badly. Video strobing and audio jumping. then it freezes again. When i turn off Aja playback all fine. I have done all settings correctly following instructions. Audio output in preferences other than Aja and etc.
I have this problem on both computers with OSX Maveric and Aja Kona cards.

Premiere Pro CS3 Issue with nVidia 182.50 GeForce Driver?

I recently updated the driver for the GeForce 8800GTS on my other editing workstation because it would sometimes BSOD when preparing to standby with a fault in the nvidia minidriver being reported. I updated to the current version as of today, 182.50 from nVidia's own web site.
After the driver update, I could swear I am seeing more frequent lockups of Premiere when jumping from clip to clip on a timeline of many clips. I can jump maybe half a dozen times and then Premiere will stop responding. Task Manager reports Monitor.exe 'not responding' and a few seconds later, Premiere.exe stops responding and I have to kill the app and start over. I can get it to hang within 20 seconds by just paging down through a few clips on the timeline now. The problem has existed prior, but usually after flipping though several dozen clips, not just a half dozen.
Is anyone noticing problems with more frequent lockups with the 182.50 driver?
SYSTEM CONFIG
Gigabyte GA-P35-DQ6
XFX PVT80GTHF9 GeForce 8800GTS 640MB
Intel Core 2 Quad Q6600
Mushkin Hp2-6400 Ddr2 4gb Kit
4 Western Digital Caviar HD 500G|WD 7K 16M SATA2 WD5000AAKS
SILVERSTONE TEMJIN SST-TJ06S-W Silver Aluminum
Seasonic S12 Energy Plus SS- 650HT Power Supply
LG GGW-H20L Blu-ray Burner
HP LP3065 30" LCD Display
Turtle Beach Montego DDL 7.1 Dolby Digital
Pioneer DVR-112D
NEC Beige 1.44MB 3.5" Floppy Drive Model FD1231H
ZALMAN 9700 LED 110mm 2 Ball CPU Cooler
Contour Shuttle-Pro

Hi Mark I'm running the 182.50 no problem now! I was having problems moving clips as the timeline would double in size and distort and not run correctly. The way I solved it was to to tick "disable display scaling on high DPI settings" in the compatibility section of the Premiere CS3 properties (right click on the icon for CS3 and then choose properties) this may help because with a 30" screen you're sure to have a high DPI setting. Terry

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

Premiere Pro cc 2014 not find any capable video play modules

French version :
bonjour j'ai installer première pro cc 2014 avec les dernières mise à jour en date je ne parviens pas à le démarrer j'ai essayer toute les solution en commencant par desinstaller propement les drivers de ma carte graphique avec l'outil de netoyage fournit par amd, réinstaller première pro cc 2014, j'ai même vérifier la configuration du bios. rien n'y fait j'ai toujours cette erreur "Premiere Pro could not find any capable video play modules"
carte graphique: sapphire radeon hd 6950
carte mère : asus p5ql pro
English version :
hello I install premiere pro cc 2014 with the latest update in time I can not start I tried all the solution starting with propement uninstall the drivers for my graphics card with the tool cleaning provided by amd reinstall premiere pro cc 2014, I even checked the bios configuration. nothing happens I always have this error "Premiere Pro could not find Any video can play modules"
graphics card: sapphire radeon hd 6950
Motherboard: Asus P5QL pro
report error :
Nom du journal :Application
Source :       Windows Error Reporting
Date :         13/11/2014 10:02:21
ID de l’événement :1001
Catégorie de la tâche :Aucun
Niveau :       Information
Mots clés :    Classique
Utilisateur : N/A
Ordinateur :   Mixta
Description :
Récipient d’erreurs 85962806217, type 4
Nom d’événement : APPCRASH
Réponse : Non disponible
ID de CAB : 0
Signature du problème :
P1 : Adobe Premiere Pro.exe
P2 : 8.1.0.81
P3 : 5426694c
P4 : dvaui.dll
P5 : 8.1.0.81
P6 : 54263f06
P7 : c0000005
P8 : 0000000000187a68
P9 :
P10 :
Fichiers joints :
C:\Users\Mixta971\AppData\Local\Temp\WER28FC.tmp.WERInternalMetadata.xml
Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Adobe Premiere P_a9de66cfad22891274ed6b2ad373c3cc8e66213_fea0d0c4_18cc8331
Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : b8897a65-6b13-11e4-be97-90e6ba56758e
Statut du rapport : 0
Récipient avec hachage : 0556574ab858e5348b9b17772269773f
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-11-13T09:02:21.000000000Z" />
    <EventRecordID>35631</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Mixta</Computer>
    <Security />
</System>
<EventData>
    <Data>85962806217</Data>
    <Data>4</Data>
    <Data>APPCRASH</Data>
    <Data>Non disponible</Data>
    <Data>0</Data>
    <Data>Adobe Premiere Pro.exe</Data>
    <Data>8.1.0.81</Data>
    <Data>5426694c</Data>
    <Data>dvaui.dll</Data>
    <Data>8.1.0.81</Data>
    <Data>54263f06</Data>
    <Data>c0000005</Data>
    <Data>0000000000187a68</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
C:\Users\Mixta971\AppData\Local\Temp\WER28FC.tmp.WERInternalMetadata.xml</Data>
    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Adobe Premiere P_a9de66cfad22891274ed6b2ad373c3cc8e66213_fea0d0c4_18cc8331</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>b8897a65-6b13-11e4-be97-90e6ba56758e</Data>
    <Data>0</Data>
    <Data>0556574ab858e5348b9b17772269773f</Data>
</EventData>

Hi Delarey,
Please go to the following location and rename the folder to old_folder name
User/user library/Application Support and rename Adobe folder
User/user library/Preferences and rename the Adobe folder
Then go to Documents folder and Go to Adobe/Premiere pro/8.0 and rename 8.0 folder
Make sure that you are in user library if you are not sure check the link below.
Access hidden user library files | Mac OS 10.7 and later
Regards,
Vinay

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

Macbook Pro 2.6ghz i7 2013 system freeze when using Premiere/AME CC 2014

I have a Macbook Pro i7 2.6ghz form late 2013 and I have been experiencing some serious problems with my system freezing while using Premiere Pro and whilst rendering from AME.
I am running the latest version of CC (8.1) on OSX 10.9.5.
GFX card: NVIDIA GeForce GT 750M 2048 MB
RAM: 16 GB 1600 MHz DDR3
I have CUDA enabled, I need the performance boost so rendering previews of the CPU is not much of a option for me.
I have experienced this problem since I started running Premiere on my laptop (3 months ago). If I am doing any GPU hungry processes within Premiere or AME the system will freeze, when it freezes nothing will respond and the screen stays frozen, I have to do a manual shut down.
I went as far as replacing the whole laptop with Apple as they put it down to a faulty GFX card, the new one has the same problem which leads me to think that the problem is with how Premiere and AME work with the new Macbook Pro's.
These crashes happen up to three times a day if I'm doing a full day of editing and I have to make sure I don't push the system to hard to avoid it, the crashes don't tend to happen when I am editing 5D footage but they are quite frequent when editing 4k GH4 footage. I am working off multiple hard drives with valuable data which are put at risk when the system crashes. I normally work on a 6 core Mac Pro but next week I'll be pushing my laptop pretty hard with a full week of editing and I'd love to avoid these crashes.
If more info and specs are needed to identify the problem, I'll be happy to provide them.
Cheers, Moja.
ps.
My system just crashed twice today, once while writing this message, I had a project open in Premiere but I wasn't even editing, its currently 30 degrees in Melbourne, one of the hottest days of the year yet, which leads me to believe that the heat is contributing to the GFX card or CPU overloading.

mojareeves1 wrote:
I forgot to add that I have also updated to the latest nvidia card driver.
My music seems to keep playing when the crash occurs which suggests the hard drive and other components are still running fine, its just the GFX card that is crashing.
The GFX card may be a red herring if it still crashes in software mode and with the internal card. The fact that you have music playing, however, may be a clue. Programs that can access your audio hardware (like Soundflower) at the same time as Pr have been known to conflict and cause crashes. Turn off any background audio processes. Check your system audio settings, as well as Pr's audio and audio hardware settings. If you can, change the source of Pr's Desktop Audio in Preferences>Audio Hardware. Try changing the ASIO settings.
The next (and most painful) step would be to work your way meticulously through this document:
Troubleshoot system errors, freezes | Mac OS 10.x | Adobe software
The "Re-create Adobe application preferences" step often helps a lot.
Cheers,
Jeff

Adobe Premiere Pro CC 2014 compatible with Nvidia 970 GTX?

Good afternoon.
I'm an owner of a GIGABYTE Nvidia 660 GTX Ti OC 2GB. The card is detected by Adobe Premiere Pro CC 2014 (Even though,i think,it said that it's not listed or something but will work under my own risk..Is there a way to check if it's certified/supported via my own program and NOT the typical "This is the list of supported GPUs"?)
Anyways,i was thinking of buying one of the new 970GTX cards to game on better,but also to make full advantage of it's properties to do much more faster encoding/exporting (you know,create a H.264 MP4 720p@29,97FPS file) than my actual 660GTX card with Adobe Premiere Pro CC 2014.
The thing is,any owner of such card (GIGABYTE,MSI,doesn't matter) have tried to launch Adobe Premiere Pro CC 2014 and export stuff by using the GPU's full potential to make everything faster?.. Because i have this fear of "Getting the newest n greatest Nvidia card so far and in the end see/notice it'll not work with Premiere Pro CC 2014"
....Can somebody please help me with this big fear of mine,please?
Thanks in advance
DV

Locked... duplicate discussion... see GTX 970 and Premiere Pro

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 keeps freezing when loading projects from Premiere Pro CC

Hi everyone,
I'm reporting this issue in case someone else would have the same problem.
I just downloaded the 2014 version of Premiere Pro CC, and when I'm loading a project from Premiere Pro CC into CC2014 I have the software freezing and being unable to even play the loaded sequences. It seems that dynamic link is having trouble linking the CC and the CC2014 version of Premiere Pro.
Until now the only solution I found was to kill the process of the software and start it again, after 8 times I got my sequence loaded alright, then sometimes it is freezing again, killing process, starting software again, and so on. Does anyone has the same problem ?
I'm running a Windows 7 Ultimate PC with 12Go RAM dedicated only to Premiere Pro.
Cheers,
Vincent

Hi Vincent,
I feel your pain, you are not alone. Here are my machine specs and my very frustrating situation, if anyone has any idea as to how I should move forward, I would really appreciate the input/advice...
iMac - 27" Late 2013
Processor 3.4 GHz Intel Core i5
Memory 12 GB 1067 MHz DDR3
Graphics NVIDIA GeForce GTX 780M 4096 MB
Software OS X 10.9.4 (13E28)
I'm having similar issues that began when I installed Premiere Pro CC 2014, and actually got worse with the latest update/release. The majority of my projects worked fine at first, but the update last week ended that quickly. I did what I know I never should do and updated Adobe CC while completing a project on a deadline. I thought some of the fixes would help me complete the project sooner. Needless to say, the deadline has passed, my client is pissed enough to not pay me or hire me again and I'm stuck with an almost-there version that I can't export correctly because of this software. This is my problem, not Adobe's, but I didn't expect such a detrimental update to halt my operation.
After doing some research, I found that some plugins could be the cause of some specific editing issues, mainly due to incorrect or inaccessible folders - who knows if its Dynamic Link, CC apps or 2014 apps. I concluded that my issue at the time was a plugin permissions issue on the Adobe "Preference" Folder, so I reset the permissions on the folder so that CC and 2014 apps would be able to access its contents without any problems. This was the wrong decision. For some reason, resetting this folders permissions also effected the main HDD, it's Kernel Text files and their respective permission. I could not boot my machine, just got the Apple and spinning wheel until I had to power down. I ended up on the phone with 3 different AppleCare reps who helped me at least be able to turn the machine back on and access my desktop/files, apps, etc. Outside of this, no one could offer anything other than "Uninstall the problematic application, reboot, reinstall, etc..." or "Backup your files and reimage the HDD." When I mentioned the recent CUDA driver update for my graphics card (NVIDIA GeForce GTX 780M 4096 MB now running CUDA Driver Version: 6.0.51), it was like they had never heard of graphics cards being used in their machines.
Resetting permissions on Adobe Preference Folder...
This is what I read would get the CC and 2014 apps communicating correctly so that they could utilize my plugins. There is a problem, I believe, in that their are TOO MANY locations where Adobe folders/components live. There are 3 "Preferences" folders that I found, and I don't know which effects what process, but the folder I changed permissions on clearly effects the operation of all of the CC & 2014 apps I had installed, as well as my HDD. Kernel Extensions and the entire system.
Based on my perceived effects of the Preference folder, I needed to uninstall everything, run the Adobe CC Cleaner Tool, download/install just the 2014 releases and see if that resolved the issue. I'm not downloading CC apps, the 2014 releases should run fine on their own. I've yet to confirm this with Adobe, as what I've read has simply said to install the new release next to the CC apps, rather than on top of, as traditional update releases work. Anyway, one by one, I reinstalled the 14 apps that I use on a regular basis on a "clean" machine with no trace of previous Adobe apps.
After reinstalling (without any plugins), I was at least able to open Premiere Pro from the Application folder and work for a few minutes before both Program and Source monitors froze and had to force quit the app. If I try to open the Project File by double clicking it in the Finder, SpeedGrade opens up instead of Premiere Pro - never seen that before. I also had to force quit to end that process and reopen in Premiere instead of SpeedGrade.
So back to Premiere, if I do have success in opening a project in the right application, Premiere freezes - if not immediately, eventually it will just stop responding. The video clips, sequence segments and UI freeze, but the audio will keep playing until I force quit. When I force quit, Premiere Pro doesn't close entirely. The UI closes, but the process still runs. I've even force quit from Finder, force quit again from the Dock, Shut Down the machine, restarted and Premiere Pro will still be open, but "Not Responding", so I force quit again and open the project. Just now, I opened PP, made minor edits to a sequence, sent it to Media Encoder, exported, but the video I tested exported without audio. I force quite PP twice just before that and it is still running now, but again, it is "not responding".
Ultimately, none of this works, nor have my attempts at resolving these many issues. One thing I know is that there is something VERY WRONG with either the latest release/update to 2014 apps, the Preference folder or the permissions that were changed.
As I mentioned previously, and what I think is a major oversight by someone at Adobe, is that for some reason the permission changes to ONE Adobe folder also effected my entire system and Macintosh HD. Some Kernel Extension files went missing, which is never good and should not happen when resetting folder permissions, so I believe my issues are far greater than the faulty Adobe CC 2014 applications, and is the cause of many of my problems right now. If I can't get things sorted soon, I'm going to reimage my HDD and start from scratch. As much as I would like to avoid this, I really have no choice if I want to get back to work and not lose clients over inexplicable technology issues.
If I find a solution, I will repost, but I think Adobe has to make some serious fixes on this release before anything is resolved entirely. I pay them monthly and rely on their software and platform to work without issue, which is foolish - I know, but I've used CC since it was introduced and it has work well enough until now.
Is there anyone at Adobe that can offer some advice??

Premiere Pro CC 2014 with NVIDIA system freezes (Win7x64)

Similar Messages

Maybe you are looking for