Premiere pro cc and nvidia driver crash... why?

Hi guys
Since my new PC configuration, I've been having difficulties making my graphics card (Gygabyte Geforce GTX 650 Ti) enable the mercury playback engine cuda on premiere pro cc. it works for a few moments or it renders 2 3 minutes of my video and vith video hardware acceleration, but after that the video driver crashes and the rendering process and premiere as well. i have the latest driver from nvidia, but also have tried with drivers as old as 310.70 (released december 2012). i use wi 7 sp1, my cpu is intel's [email protected] and intel z77 chipset with 16GB of ram if this is of any relevance. Any ideas on what's the cause of the problem or how i may fix it? (the same thing also happened with premiere pro cs6)
Thanks for your help !

From Tweakers Page - Balanced Systems
What about the amount of VRAM?
As a rough guide, how much VRAM should be installed on the video card, think along these lines:
For SD material, 1 GB is enough
For HD material, go for 1 - 2 GB
For 3K or 4K, go for 2 - 4 GB
For 5K+, go for 4 - 6 GB
Keep in mind that the requirements can vary significantly, depending on the complexity of the timeline. If it happens that the VRAM is depleted (not enough memory), hardware MPE is automatically turned off rather ungracefully and stays off for the rest of the encoding. If you use two video cards in CC, each card uses its own memory and cannot use the memory on the second card. The encoding process works like this: Frame 1 rendered on card 1, frame 2 rendered on card 2, frame 3 rendered on card 1, etc. If either card runs out of memory, again hardware MPE is turned off. Simply put, two video cards with 1 GB each can not be treated as a single card with 2 GB, so the risk of turning off hardware MPE automatically is bigger with these two cards than with a single card.

Similar Messages

Premiere Pro CC and Nvidia Maximus k5000 and k20

I've tried both nvidia drivers 320.27 and 320.49 and can only get the K5000 for process in Premiere Pro CC, AE CC and Media Encoder CC. In the Maximus Config Utility I have the 5000 set to Dedicated to graphics only tasks, yet the K20 never goes above 0% usage. I'm running Win7 64bit, Premiere CC 7.0.1. Nvidia drivers 320.49.
Im getting better performance from the k5000 through queuing to Media Encoder than I cam from direct export from Premiere. But here's my processes on the GPU when export.
I've tried Using k5000 for "Use for both Graphics and compute tasks" and Tried using ECC on and off for both the k5000 and k20.
I'm stumped how to get my Maximus configuration to work with Adobe CC.

I've delete the CUDA and OpenCL text files with no success of using the K20. I modified the cuda_supported text file to include the k20, and it the premiere timeline used both cards came with an error stating this card is not supported, but worked flawlessly . However, now I can't export a quicktime file. I get a "error compiling movie" error message. I delete the CUDA and Open CL text files and replaced them with the original text files found in the folder, rebooted and now have the Maximus config working in Premier. But still have the error compiling quicktime files.
Thanks for the suggestions for what ever reason, deleting the text file and replacing it with the same file and deleting and reinstalling solved the K20 issue in Premiere.
This also solved AE not seeing the K20.
Thanks again.
Resources for non exporting quicktimes :
http://blogs.adobe.com/aftereffects/2011/02/troubleshooting-quicktime-errors-with-after-ef fects.html

Why is the Nvidia GTX 680 CUDA card supported by Premiere Pro CC, and NOT After Effects CC?

Why is the Nvidia GTX 680 CUDA card supported by Premiere Pro CC, and NOT After Effects CC?

Thanks Todd for all the info. It is much appreciated and very helpful. On a different note, could you possibly direct me to the correct forum to fix this bug? I am suddenly recieving a warning on my System SSD referencing Adobe Exchange. Here is a screen grab to best explain:

Hello, i use premiere pro cc and i would like to uplaod my sequence in speedgrade with direct link but it's not available. I can see the option but it's not clickable, somebody knows why ?

Hello, i use premiere pro cc and i would like to upload my sequence in speedgrade with direct link but it's not available. I can see the option but it's not clickable, somebody knows why ?

Oh i'm not sure they are on same, i downloaded speedgrade this morning and i didn't upgraded premiere so it's maybe this ! thanks i will try it and let you know

We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason. Anyone else got that too with Premiere Pro CC and the new Media encoder? Thanks! bedrijfsfilm Companyfilms

We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason. Anyone else got that too with Premiere Pro CC and the new Media encoder?

We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason
Anyone else got that too with Premiere Pro CC and the new Media encoder?
Lack of detailed info makes your question impossible for anyone to answer you!
eg. ...."Doctor it hurts...anyone else got something that hurts?"

Nvidia Driver Crashed and Recovered

I've been getting errors that say my 258 version nVidia Driver crashed and recovered. It's happened probably five times since I got my new replacement machine.
This time, it managed to corrupt a 3DS max file I was working on for school, so I just lost a bunch of work. I'm really close to just throwing my machine away and spending another $2700 on a Dell or something.
Before I do that though, what could cause a driver to crash like that? I've updated to the version on nVidia's site, since Lenovo's driver is over a year old. Do I need to revert?
Every day I'm more disappointed with the build quality and reliability of something I spent so much money for. I do believe this is the last time I will *ever* purchase anything from this company.

xtsubarublazin wrote:
Before I do that though, what could cause a driver to crash like that? I've updated to the version on nVidia's site, since Lenovo's driver is over a year old. Do I need to revert?
It is not recommended that you use drivers from Nvidia's Website for your system(It may have a customized version) .... didn't you get a warning dialog when you tried to download them?
Cheers and regards,
• » νιנαｿѕαяα∂нι ѕαмανє∂αм ™ « •
●๋•کáŕádhí'ک díáŕý ツ
I am a volunteer here. I don't work for Lenovo

Nvidia driver crashes when fraps is running and a download of a file is done

When I have fraps running in background (but not recording) and I just finish download a file the nvidia driver crashes and restarts. I got the newest nvidia drivers and I am using Windows Vista 32bit

Try doing the update again, but leave all programs off.
Use this if you need it;
'''[http://www.mozilla.org/en-US/firefox/all/ Download Firefox Full Installer For All languages And Systems]''' {web link}

Premiere Pro cc 2014 8.2 crashing

I’ve been working on a documentary with several types of footage/stills. Crashes have become more frequent as I get further into the project. Lately it’s been freezing up to the point where I have to force quit and I’ve also gotten the “Sorry, a serious error has occurred” where it has to restore the file. It's also happening with a new project file which has only one type of footage in it.
My machine’s getting old and I plan on replacing it soon but it still works fine with FCP7, Avid, After Effects, etc. Here are the specs:
2.8 GHz Intel Core 2 Duo
4 GB 1067 MHz DDR3
NVIDIA GeForce 9400M 256 MB
Footage is on an external Glyph drive 2TB
MacBook Pro mid-2009
OSX 10.9.5
Here’s what I’ve tried:
-I made sure my Adobe folder preferences are set to read/write.
-I’ve tried recreating the preference file (ctr+alt+shift) several times while starting the program. This seemed to help the first time I tried it but then it started crashing again and eventually gave me the “Sorry, a serious error has occurred” message again.
-I’ve cleaned the media cache
-The only plugin I have installed is FinalPlug (a compressor) but I haven’t been using it and don’t see that anyone’s listed it as being problematic with PP CC, so I haven’t uninstalled it.
Should I update the video driver? Can anyone advise me on how to do that?
Thanks!

Hi, I have something similar to this happening to me. Does a crash report box also pop up for you? I get one, but it's for Apple, not Adobe. I didn't have my problem until getting a new Mac with Yosemite installed, so it shouldn't be your machine's age.
Part of my error message looks like this:
Crashed Thread:
0 Dispatch queue: com.apple.main-thread
Exception Type:
EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:
KERN_INVALID_ADDRESS at 0x0000000000000000
VM Regions Near 0:
-->
__TEXT
0000000100000000-0000000100003000 [   12K] r-x/rwx SM=COW /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.adobe.AudioSupport.framework    0x0000000103d7f8d0 ML::Device::GetNumberOfPhysicalChannels(unsigned int, bool) + 80

Premier Pro CC and Media Encoder crashing on long file export.

Please forgive the length of this inquiry. But it is complicated and has a lot of variables.
I have an hour long mixed format timeline both Red 3K footage and Black Magic ProRes 1080P footage that I want to make a DVD from and it takes forever and crashes half way through. I have tried doing it every way possible and the only way I was able to get even a partial export was using the "MPEG 2 DVD" export option in Premier CC. It goes fast at first telling me it will take about 2 hours but even though it starts quickly doing about 15 fps it slows down to less than 1 fps and finally just stops and crashes my Cuda Core enabled Macbook Pro Laptop.
I really don't know who to ask about this since there are so many different variables. I never had a problem like this on my MBP with PP6 on a 4K timeline exporting to DVD or Blue Ray or to H-264 or Even Prores. But I wasn't mixing formats either. But on this project the first 20-30 minutes of footage goes through fine in a couple of hours but something seems to be bogging down the system on longer projects. My work around was to break the project up into multiple exports and combining them on the DVD timeline but I can't do this on every project. I thought maybe it was a corrupted clip somewhere in the timeline but when I broke the timeline up into several parts I had no problems.
I did notice a dramatic variance in the time it took to export footage based on the sequence settings. A one minute timeline comprised Red 3K footage and ProRes 1080P footage Here are some sample export results:
From a Red raw 3K timeline 2880x1620 with 1080P Prores footage upscaled 150%)
to .m2v Mpeg 2 720x480 format    1:48 Minutes ***
to .mov Prores 422HQ 1080P                         22 Minutes
to .mov H.264 1080P                    22 Minutes
to .m2v Mpeg 2 1080P                                                22 Minutes
From a 1080P timeline Prores footage at 100% (Red footage downscaled to 67%)
to .m2v Mpeg 2 720x480 format                         13 Minutes
to .mov Prores 422HQ 1080P                             13 Minutes
to .mov H.264 1080P                                                             14 Minutes
to .m2v Mpeg 2 1080P                                                            14 Minutes
Since I am going to DVD, I chose the fastest option Red to m2v Mpeg 2 720x480 format which only took 1:48 per minute. Why? I have no idea. Maybe someone here knows the answer. But again these numbers are for a ONE MINUTE clip when I tried to convert the whole hour timeline to the 720x480.m2v DVD File the Red timeline froze my computer after several hours even though I had set sleep mode to “Never” and turned the display off manually and I had to convert it in multiple chunks. In 20-30 minute chunks it did go fast about 1:48 per minute like the test indicated. But I would like to be able to convert the whole hour and not to have to try to stitch the clips together in my DVD authoring program.
I don’t want to have to avoid using multiple formats on the same timeline or waste time transcoding everything to the same format.
Can anyone give me any suggestions as to why the computer is crashing or bogging down in long exports and what timeline settings I should be using?
I have plenty of room on my Scratch Disk and 8 Gig of RAM and according to my Activity Monitor during the export process have about 800 Meg of System Memory during export but the CPU Usage is 98% and in my Activity Monitor I see under “Process Name” ImporterRedServer flashing up at the top of the list about every second during export.
Why .720x480 mpeg DVD setting is so much faster than all the other export codecs?
And if there are any other settings I can use to get higher speed exports in HD? 14x1 seems a little slow especially since every time it crashes I have to start over.

Hi,
Since a long time I did not encounter the crash of Media encoder with
long file export.
But I take care of a lot of details before the export :
- clean up Media cache and Media Cache Files within PP CS6 and/or CC,
- delete all render files with Preview Files,
- rendering of sequences until the rendering is completed,
- PP CS6 and/or Pp CC opened during export to AME and/or Encore CS6,
I guessed to leave Adobe but this company remains the last with a
serious authoring software (Encore CS 6).
I tested :
- Avid Media Composer, Final Cut Pro X, both are very good software but
no really authoring software for these video editing softs.
Th only way is to "flood" Adobe with "bug reports" and "wish forms"
which are not very easy to use.
And also to call the Adobe support day by day until they send they
escalate the bug.
Le 16/05/2014 16:51, alainmaiki a écrit :
>
      Premier Pro CC and Media Encoder crashing on long file export.
created by alainmaiki <https://forums.adobe.com/people/alainmaiki> in
/Premiere Pro/ - View the full discussion
<https://forums.adobe.com/message/6384665#6384665>

Premiere Pro CC 2014 & Media Encoder Crash when rendering

Every time I try and render something out of Premiere Pro CC 2014 it will crash before it completes the render. I have no idea why. I am on a windows 8 machine running the latest version of Premiere Pro CC 2014.Any idea what is going on?
Here is the log from Event Viewer:
Faulting application name: Adobe Premiere Pro.exe, version: 8.0.1.21, time stamp: 0x53c7b17f
Faulting module name: mc_enc_avc.dll, version: 9.8.11.6624, time stamp: 0x536af65d
Exception code: 0xc0000005
Fault offset: 0x00000000000e7f80
Faulting process id: 0x650
Faulting application start time: 0x01cfb99562fe469a
Faulting application path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\mc_enc_avc.dll
Report Id: f30f38a1-2589-11e4-bf2c-bc5ff467c039
Faulting package full name:
Faulting package-relative application ID:
Here is the Report.wer that windows automatically generates: http://pastebin.com/hriEegkJ
I have also tried rendering out of media encoder and I get a crash also (Report.wer: http://pastebin.com/Dpvk6bDb):
Faulting application name: Adobe Media Encoder.exe, version: 8.0.1.48, time stamp: 0x53c99d97
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000002c2cce3d
Faulting process id: 0xcf8
Faulting application start time: 0x01cfb9906060796e
Faulting application path: E:\Program Files\Adobe\Adobe Media Encoder CC 2014\Adobe Media Encoder.exe
Faulting module path: unknown
Report Id: 07096c20-2584-11e4-bf29-a0f3c1153ce7
Faulting package full name:
Faulting package-relative application ID:

More hardware information might help someone give you an idea
-Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
or
http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

Running CS4 Adobe Photoshop/Premiere Pro on a network drive.

I work in IT Management and I ran into a problem with running Photoshop and Premiere Pro on a network drive. When I run the CS4 Premiere Pro I get this message on startup:
Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project.
Photoshop will bring up this message:
This application has failed to start because SPROF32.dll was not found. Re-installing the application may fix this problem.
However, this error can be bypassed and Photoshop will work like normal from then on.
After looking into it our department figured out that the problem the program had was that it was running on a network drive rather than a local drive. When we ran the program on the computer's local drive these errors didn't show up at all and the programs ran flawlessly. After looking at these errors and the overall problem, does anybody know what needs to be done to have these programs run on a Network Drive?

After looking into it our department figured out that the problem the program had was that it was running on a network drive rather than a local drive. When we ran the program on the computer's local drive these errors didn't show up at all and the programs ran flawlessly. After looking at these errors and the overall problem, does anybody know what needs to be done to have these programs run on a Network Drive?
Unfortunately, your first sentence is the answer. Few programs in the Production suite run from a network drive, and need full Administrative log-in.
Good luck,
Hunt

XDCAM HD workflow with Adobe Premiere Pro CC and Macbook Pro

Hi folks,
I have an assignment for a TV production to secure and convert the data (mxf files XDCAM HD 422 1080i 50 / 50 Mbit/sec with 8 audio channels) from Sony XDCAM camcorders (PDW-700) for postproduction.
The producer wants me to convert the mxf files during production to Apple ProRes 422 (HQ) for faster and smooth editing during postproduction.
I'm not sure about the final output yet, but I guess it will be either 720p50 or 1080i 25, since the production will be broadcast and as far as I know this is the standard for HD on German television. It is also not clear which NLE will be used for editing (usually one of the producers edits their projects with FCP, but this time they've got their hands full and are still looking for someone to outsource postproduction.
Unfortunately, my Macbook is getting fixed as we speak, so I can't try things out.
Since this is the first time I'm doing this workflow, could someone please check if I got everything right?
1. Can someone please confirm that I can actually convert the mxf files using AME CC to Apple ProRes 422?
Or do I need to install any other tools/converters for this task? Does MPEG streamclip do the job? Any other freeware?
2. When converting to Apple ProRes422, the producer suggested to deinterlace the footage (1080i 50) to 25p, if 720p or 1080p I have to find out tomorrow since our conversation got interrupted this afternoon.
In my opinion this doesn't make sense, though. First, if output to 1080i 25 it has to stay interlaced anyway. Second, in case the output will be 720p 50 I would edit the footage either natively or in Apple ProRes 422, but leave deinterlacing until the very end when outputting to the final format. This way I could use an advanced deinterlacer, e.g. the one from Magic Bullet Suite, rather than just checking some deinterlace box in the export settings for Apple ProRes 422.
The reason the producer suggested to deinterlace right away when using an intermediate like ProRes was that she and the client got irritated by the jagged lines from the interlaced footage when editing the last project with the same requirements on a progressive display.
3. What would be the best solution to tackle this issue (jagged lines) during editing?
As I said my Mac is getting fixed, so I have no way of trying things out,and I usually edit DSLR footage which is progressive anyway.
But if I remember correctly I can switch my monitor between 1080p and 1080i. This should do the trick, shouldn't it?
4. Can I keep all of the 8 audio tracks when converting to ProRes using AME CC ?
5. Is ProRes422 (HQ) really necessary, or is the regular quality sufficient for this kind of job?
6. Let's assume the whole project would be edited within Adobe Premiere Pro CC and system specs as stated below:
Since Adobe Premiere Pro CC has native support for XDCAM HD is there any advantage of using an intermediate like ProRes at all?
How smooth is native editing with XDCAM HD in Premiere Pro CC? I don't think there will be more than 3-4 video tracks in use...
Thanks for your help!
working with
Adobe Premiere Pro CC and Adobe Media Encoder CC
Apple MacBook Pro
Intel Core i7 Quad Core Prozessor
2.3 GHz and 6MB L3 Cache
16 GB RAM 1600MHz DDR3,
256 GB SSD
Intel HD Graphics 4000 512MB + nVidia GeForce GT 650M with 1 GB GDDR5 RAM

Thanks Jim! I knew there must be a reason xdcam is widely uses for eng aquistion :) I think they used FCP 6 or 7 on their last project... So what about monitoring interlaced footage on a progressive screen? Any advice on that? Is there a converter built in to APP CC that deinterlaces in realtime when monitoring interlaced sources on a progressive screen? And would you agree that deinterlacing source material is best left right before outputting?

Premiere Pro CS6 and Media Encoder CS6 Color shift on export

Hello,
I am working on an early 2008 Mac Pro with 2 X 3.2 GHz Quad Core Intel Xeon Processors 32 GB of RAM a NVIDIA GeForce 8800 GT 512 MB Graphics Card and I am running OS X 10.8.2.
I have the updated Version of Adobe Premiere Pro CS6 and Media Encoder CS6 through the awesome Subscription program that Adobe has started.
My footage is shot with the Canon 1D Mark IV shot 1920X1080 at 24 FPS
I am importing the camera files and then exporting them after I cut them up in to Quicktime Pro Res 422 HQ files
With the technical explination out of the way here is my problem. I have color right from the camera files that I like. and with out doing any thing to change the color I export the footage and get a dramatic color shift. The exported file looks desaturated and slightly green.
I have tried using Media Encoder CS6 to export my footage and that has the same result.
I started my career as a photographic retoucher and use photoshop and light room constantly so I am pretty confident that i know color. I also calibrate my Lacie 526 and Lacie 324i montiors monthly as well as have a sensor that will slightly shift the profile depending on the time of day.
I have attached three screen shots that show the color shift exactly. Now what I need is a solution. What I am not seeing is color settings for Premiere. I am totally open to any suggestions on what I might be doing incorrectly.
Ben

Benjamin Peterson wrote:
I started my career as a photographic retoucher and use photoshop and light room constantly so I am pretty confident that i know color. I also calibrate my Lacie 526 and Lacie 324i montiors monthly as well as have a sensor that will slightly shift the profile depending on the time of day.
I've been doing this for a few years now, and have come to some conclusions. Basically, the difference between still photography and video is like the difference between playing the trumpet and the sax. What you bring to the sax from playing trumpet is your ability to read music, what you know about composition, blending while playint with others, ect. But playing trumpet tells you nothing about how to physically play a sax. So it is with still photography and video.
For starters, your carefully calibrated computer monitor is just that, a computer monitor. It doesn't display the correct working space for video. What you need for WYSIWYG in video is a monitor that can show you the Rec.709 working space. Rec.709 has a different gamut, a different gamma, probably a different white point (D65), different phosphor colors, etc., etc., etc. Enought differences that it's difficult to make a computer monitor that can successfully display Rec.709. Yet there are a couple of computer monitors that can do this (a few Eizos, one HP). The vast majority of people doing serious color correction work in video use a production monitor for just this reason.
But a production monitor isn't enough. You also have to make sure that the signals you're sending the production monitor are correct. There's a sub-industry making signal converters for signals from NLE video cards (usually RGB based) -> signals for production monitors (usually YUV based).
That said, it is certainly possible to get a very good match between your NLE suite and a DVD / BD as displayed on an HDTV. But it's not as simple or easy as a calibrtated computer monitor for still photography use.
This is probably part of your problem. But Quicktime is probably the root of it. Quicktime is, well, I guess the polite way of saying it is that Quicktime is problematic. It gives all kinds of problems. Most people have abandoned it. You should too.

Premiere Pro CC 2014.2 often crashes (Windows)

Hi...i'm on windows 8.1 and using premiere pro cc 2014.2.... there have been bugs and really need help as this problem has affected my workflow and i even can't get a solution of this.....
1. There are times my files will be offline and have to reconnect them one by one....and sometimes i have to restart the software or computer to reconnect them back....there are also times when i reconnect them and get a "files are corrupted" error but they can be opened in redcine x...
2. I also get error when trying to reconnect audio files stating a "header error....
3. If i mark in and out and try to copy paste from one sequence to another, the computer will not respond and freeze....
I'm using a asus g750jm, i7 2.4ghz, with 24gb of ram.....
The sequence that i use to edit these red raw files are just 1024x540....
Need serious help here...thank you...

Hi Nazim,
You´re not alone! It looks like the whole world of Mac users crashes when inside Premiere Pro CC 2014.
I´ve tried back peddling to early version (8.0) same problem.
So this is for Kevin (who probably will tell me to stay with the Mac-probelm-users-thread):
Here is my latest crash report (out of hundred):
Process:               Adobe Premiere Pro CC 2014 [717]
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.0 (8.0.0)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Adobe Premiere Pro CC 2014 [717]
User ID:               501
Date/Time:             2015-04-03 14:55:56.729 +0900
OS Version:            Mac OS X 10.10.2 (14C1514)
Report Version:        11
Anonymous UUID:        3C4BE865-15A1-83C0-2A8F-247384EECB0D
Time Awake Since Boot: 19000 seconds
Crashed Thread:        0 Dispatch queue: com.apple.main-thread
Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x00000000000000c0
VM Regions Near 0xc0:
-->
    __TEXT                 0000000100000000-0000000100003000 [   12K] r-x/rwx SM=COW /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.CoreText             0x00007fff8c98db95 TLine::~TLine() + 243
1   com.apple.CoreFoundation       0x00007fff9105ca9e CFRelease + 526
2   com.apple.HIToolbox           0x00007fff8d5a0944 TCoreTextLineInfo::~TCoreTextLineInfo() + 34
3   com.apple.HIToolbox           0x00007fff8d5a0913 TLayoutInfo::Clear() + 51
4   com.apple.HIToolbox           0x00007fff8d5a078f TCoreTextEngine::Invalidate() + 49
5   com.apple.HIToolbox           0x00007fff8d59d0a8 TCoreTextEngine::Init(void const*, THIThemeTextInfo const*) + 92
6   com.apple.HIToolbox           0x00007fff8d59cf00 TThemeTextCache::Create(void const*, THIThemeTextInfo const*) + 460
7   com.apple.HIToolbox           0x00007fff8d59c8bf DataEngine::GetTextDimensions(void const*, double, HIThemeTextInfo*, double*, double*, double*) + 259
8   com.apple.HIToolbox           0x00007fff8d59c785 HIThemeGetTextDimensions + 185
9   com.apple.HIToolbox           0x00007fff8d5e124e HIStandardMenuView::MeasureItemTextWidth(__CFString const*, TextLayout*, __CTFont const*) + 122
10 com.apple.HIToolbox           0x00007fff8d5e0a3f HIStandardMenuView::GetItemWidth(float, TextLayout*, unsigned char*) + 719
11 com.apple.HIToolbox           0x00007fff8d5dde02 HIStandardMenuView::GetOptimalSizeSelf(CGSize*, float*) + 878
12 com.apple.HIToolbox           0x00007fff8d5dda1c HIView::SendGetOptimalBounds(CGRect*, float*, CGSize*) + 416
13 com.apple.HIToolbox           0x00007fff8d5dd84f HIView::GetOptimalSize(CGSize*, float*, CGSize*) + 45
14 com.apple.HIToolbox           0x00007fff8d5dd755 HandleCalculateMenuSize(OpaqueEventRef*) + 154
15 com.apple.HIToolbox           0x00007fff8d58213a MenuData::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 358
16 com.apple.HIToolbox           0x00007fff8d58098c DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1260
17 com.apple.HIToolbox           0x00007fff8d57fdce SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 386
18 com.apple.HIToolbox           0x00007fff8d57fc42 SendEventToEventTargetWithOptions + 43
19 com.apple.HIToolbox           0x00007fff8d5dd4e4 _CalcMenuSizeOnDevice(MenuData*, unsigned short, unsigned int, CGRect const*, unsigned int) + 763
20 com.apple.HIToolbox           0x00007fff8d5e1bad GetInitialMenuRect(MenuSelectData*, MenuData*, unsigned char, Point, unsigned short, Rect*, unsigned int*, CGPoint*) + 261
21 com.apple.HIToolbox           0x00007fff8d5f6f32 GetCurrentMenuRect(MenuSelectData*, unsigned int*, CGPoint*) + 110
22 com.apple.HIToolbox           0x00007fff8d605890 DrawTheMenu(MenuSelectData*, __CFArray**, unsigned char, unsigned char*) + 582
23 com.apple.HIToolbox           0x00007fff8d60548c MenuChanged(MenuSelectData*, unsigned char, unsigned char) + 356
24 com.apple.HIToolbox           0x00007fff8d5f1e36 TrackMenuCommon(MenuSelectData&, unsigned char*) + 1211
25 com.apple.HIToolbox           0x00007fff8d604fb1 MenuSelectCore(MenuData*, Point, double, unsigned int, OpaqueMenuRef**, unsigned short*) + 510
26 com.apple.HIToolbox           0x00007fff8d604c5e _HandleMenuSelection2 + 446
27 com.apple.AppKit               0x00007fff9191b8be _NSHandleCarbonMenuEvent + 277
28 com.apple.AppKit               0x00007fff917b72f0 _DPSNextEvent + 1843
29 com.apple.AppKit               0x00007fff917b6730 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 194
30 com.apple.AppKit               0x00007fff917aa593 -[NSApplication run] + 594
31 com.adobe.Frontend.framework   0x00000001000c948d FE::MacApplication::RunSelf() + 45
32 com.adobe.Frontend.framework   0x0000000100047cca FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 4058
33 com.adobe.Frontend.framework   0x00000001000cad44 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
34 com.adobe.Frontend.framework   0x00000001000d1f25 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
35 com.adobe.AdobePremierePro     0x00000001000018ac main + 508
36 com.adobe.AdobePremierePro     0x00000001000016a4 start + 52

Adobe Premiere Pro.exe and Dynamiclinkmanager.exe *32 not stopping after closing PP CS6.03

PP 6.03 will not restart after closing program. When I try to re-start nothing happens when clicking on the PP6 icon. Looked in task manager and found that Adobe Premiere Pro.exe and Dynamiclinkmanager.exe *32 are not stopping after closing program. Once I manually stop the processes PP will restart as normal. This is on Win 7 Sp1, HP Elitebook 8760W Matrox MXO2 LE. Also Audio meters are not active during capture, can't change clip name during capture.

Hello Elcuad, and Canino video,
Please verify the following steps and report back your findings:
- uninstall the currently installed MXO2 effects and drivers
- go to control panel - user accounts - and locate the account you are using, then drop down the UAC level all the way, ok and reboot
- download our 7.02 driver with Internet Explorer, followed by our effects
- after the files are downloaded, right click each file, go to properties, and confirm they are not blocked, if they are click the unblock button
- reinstall the Matrox driver, again, the one we just downloaded, followed by the effects, reboot
- go to start, all programs and locate the premiere icon, hold shift and ctrl keys down, and launch this particular icon, keeping the keys down until the application opens up
- please build a new project and try it out

Premiere pro cc and nvidia driver crash... why?

Similar Messages

Maybe you are looking for