Graphics problem after Yosemite upgrade

[Jose Miguel jimenez]

100% related to CUDA in my experience. After reading this thread I uninstalled CUDA (which is almost a challenge to achieve!) and haven’t had any issue in the last 24hrs at least. Before uninstalling CUDA I was getting the weird screen patters, PPro crashing all the time, Kernel panics on a permanent basis – Macbook Pro crashing and restarting… and (this is a weird one, to me at least) using my Wacom Intuos would mess up with the Macbook’s trackpad – as in, it would get unresponsive: not right clicking with 2 fingers, not popping up the hidden Dock even when draggin the cursor to the bottom of the screen, etc. Since uninstalling CUDA it hasn’t happened again…???

I just joined Creative Cow to thank you for this thread. I was in agony! So: thanks!

[Gregory David]

Great that out experience is shortening other editors path to being able to work. I encourage anybody who has had these issues, has removed CUDA from their system and is now problem free, to post their experience. We need this sorted out. I wan’t the speed the CUDA gives me!

[Jose Miguel jimenez]

Hi,

Anyone have any new experiences/ updates on this?

I don’t know if this is connected but just in case: if I verify my permissions I always get this

User differs on “private/var/db/displaypolicyd”; should be 0; user is 244.
Group differs on “private/var/db/displaypolicyd”; should be 0; group is 244.

I obviously repair them and I suppose then it;s all ok, but only until a restart. Every time I verify permissions after restarting i get that message. Again dunno if it;s connected but…

[Kevin Balling]

I have been getting this same problem intermittently with Premiere Pro CC. I am on a late 2012 iMAC,
3.4 GHz Intel Core i7
Memory 16 GB 1600 MHz DDR3
NVIDIA GeForce GTX 675MX 1024 MB

I am on Mountain Lion, so it is not an isolated Yosemite problem. I use OpenCL, not CUDA because I found many other unrelated problems CUDA, so I uninstalled it. The new Premiere CC update installed CUDA as part of the update. I tried it. Same problem. The problem usually presents itself when Premiere Pro is dealing with Text plus effects, or doing something that is a bit complicated. A long export sometimes causes it, and always when the export has clips with Red Giant Denoiser. Sometimes the system freezes and I need to shut down. Other times I just close out of Premiere. The glitches remain on the screen even after I close out of Premiere Pro and will dissipate if i just let the computer sit for awhile or restart.

Kevin Balling
Tin Roof Video
http://www.tinroofvideo.com

[Craig Ricker]

Have 3 Mac Pro’s at work, upgraded them all to yosemite just before the Christmas break. Come back to work, and we are all experiencing constant freezing and crashing of our Mac Pro’s, which causes a complete freeze, followed by a restart, and a pop up saying ‘Graphics problem detected’.

Most often happens when were using the GPU in premiere pro, or during a render/export from either after effects or premiere.

I have glitches on my screen all the time as well, especially when using hot spaces.

There is clearly some serious bug in yosemite in regards to GPU.

Very painful, and seriously considering now restoring the Mac’s back to snow leopard, where we were completely glitch free, and I could boast the reliability of our Mac’s….

Mac Pro 2.4Ghz 8 core, 24GB RAM, GTX 670

[Paul Jones]

Over 2 months later and people are still complaining about this…including myself.
Clearly nothing is being done about this!

[Craig Ricker]

Not sure about you guys. But the problem has now cleared, since Apple released 10.10.2 combined with the latest cuda driver 6.5.46

I no longer have any crashes or graphics glitching and its been this way now for over 2 weeks.

Hope the rest of you have as much luck

Mac Pro 2.4Ghz 8 core, 24GB RAM, GTX 670

[Nabil Majid]

I use to have the same problem, but I’ve download manual the CUDA 6.5.46 and fix the problem, thanks god!!!

[Paul Jones]

Sadly mine is still the same even after all the updates

[Peter Garaway]

Hi Guys,

There is another thread discussing this issue here.

In case you haven’t seen it I wanted to share it with you in hopes that there will be some helpful information.

Best,

Peter Garaway
Adobe
Premiere Pro