Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Mac Pro (Late 2013) GPU (Driver) Issues
- Thread starter bax2003
- Start date
- Sort by reaction score
10.10.4 gpurestart crash. Hulu with flash, fullscreen. nope, 10.10.4 did not solve it for me. Granted, the time between crashes are further apart, but still.. The pattern for me is video,flash,fullscreen. My flash is on lastest update. This newmacpro is the most unreliable computer ever and the cliche that apple is style over substance is gonna stick if they dont sort this out soon.
Well I'm back in business for now, which is great. Everything is a lot smoother than I had been used to. Also this machine is "a lot" quieter than the last one which was replaced. The fan on that machine was noticeably louder than any of the other 3 nMp's I've used - don't know if that means anything but just observing. Managed to get a few hours work in so far with Final Cut Pro X without any issues - only time will tell - just hope that this issue can be solved generally rather than fighting isolated cases
After the simple refresh rate change from 60 to 50Hz. I finally got a smoothly running system here. There were only two complete hangs in Yosemite with a spinning (not frozen) beachball. I am also stressing the MacPro concerning temperatures - at constantly 30 degrees celsius ambient-temperature. (you know, summer...)
The old crashes are gone for now.
@flyingfoxuk: Interesting changes in your case. No particular noise here even with a fan actually spinning at higher speed.
@wiaderko: little misunderstanding - i just wanted to stress the Mac to see, what happens.
Concerning these messages like
- WindowServer ... : Surface testing disallowed updates for ... sequential attempts.. -
forget about them. Identical messages running GPU-Test on my brandnew MacBookPro 2015 with an i7. This is Yosemite general. Same for the hickups in the furmark-graphics - the MacBook does the same - just much much worse
The old crashes are gone for now.
@flyingfoxuk: Interesting changes in your case. No particular noise here even with a fan actually spinning at higher speed.
@wiaderko: little misunderstanding - i just wanted to stress the Mac to see, what happens.
Concerning these messages like
- WindowServer ... : Surface testing disallowed updates for ... sequential attempts.. -
forget about them. Identical messages running GPU-Test on my brandnew MacBookPro 2015 with an i7. This is Yosemite general. Same for the hickups in the furmark-graphics - the MacBook does the same - just much much worse
Last edited:
My exchange with Apple over my bugreport on nMP suspend=>panic issue seems to have come to a standstill; for last two months (dunno what really triggered it, it was post 10.10.3, but not by much; no other major software updates) my nMP started panicking more and more frequently when resuming from long suspend. I provided them with the panic logs, but they wanted coredumps, which seem insanely slow to produce + I am not sure I want to leak e.g. encryption keys and whatever may be in the memory at the time anyway. So I guess next time, morale of the story is simply not to buy Apple but build hackintosh.. sigh.
I am pretty sure this is a bug in the ATI driver, triggered by combination of HDMI projector + 2 very different 4k displays; especially the Dell 4k one has actually some bugs and does not always recognize signal _at all_ post-resume and requires power cycling. Given the stacktrace, I would have imagined fixing it would be possible, but apparently not.
I am pretty sure this is a bug in the ATI driver, triggered by combination of HDMI projector + 2 very different 4k displays; especially the Dell 4k one has actually some bugs and does not always recognize signal _at all_ post-resume and requires power cycling. Given the stacktrace, I would have imagined fixing it would be possible, but apparently not.
No problems so far - running smooth. The real test will come when I start rendering 3D animation in the next couple of weeks. I did have a 17" Macbook Pro die 2 days after this one arrived though!
No flash - I don't even use this machine for internet at all. Just one monitor connected by Apple Thunderbolt to DVI-D adapter - same configuration as with 2 previous machines. In the middle of a massive job right now so not pushing anything too hard. Curiously I think it was flash that killed my Macbook Pro - I don't install it anymore!
I had the same problem running Yosemite on my Mac Pro 6,1 6 cores 32GB RAM D300s. At first, I tried a lot of things with no success. Then I upgraded to El Capitan beta and it seemed to work fine there for a while although Ozone 6 didn't work and it kept disconnecting my USB audio interface.
So at the end, I tried installing Mavericks 10.9.5. Haven't had this issue ever since.
So at the end, I tried installing Mavericks 10.9.5. Haven't had this issue ever since.
One more interesting thing to add to the list:
I had one more hang (everything frozen, mouse cursor still alive) recently. Out of pure curiosity i hooked up my old monitor via hdmi. You would not believe it: The Mac did not crash at all. It was still running via hdmi, showing the frozen desktop on the TB monitor. Although there were some glitches in the picture, it was still usable as if nothing happened.
I am more and more conviced that this is purely a driver problem that only affects TB.
I had one more hang (everything frozen, mouse cursor still alive) recently. Out of pure curiosity i hooked up my old monitor via hdmi. You would not believe it: The Mac did not crash at all. It was still running via hdmi, showing the frozen desktop on the TB monitor. Although there were some glitches in the picture, it was still usable as if nothing happened.
I am more and more conviced that this is purely a driver problem that only affects TB.
Just the fact that after freeze almost every mac replies via ssh tells that this is usually software (Windows Server) and driver problem.
Nevertheless, this is very useful discovery. This could help someone to save some work in progress.
r
Oh yes please do! I wonder whether you get a usable but partly flickering hdmi-picture as well. Could be caused by wrong timings do to "hotplugging" - interfering with settings stored in the PRAM or the crashed TB.
Last edited:
I'm very curious about that too. And to see if I just run HDMI and get rid of any TB displays altogether (until El Cap comes out anyway), and see if we can see results there.
...or just run our TB display connected via hdmi *cough* - just came to my mind.
They usually do have both connectors.Powercycling the monitor usually works for me. I did not notice a problem with the os before yosemite. I just hope people with this problem files a bug report or a tech news site picks this story up.
I filed an extensive bug-report and was told that "this is not normal", have the nMP checked at Apple and the report was closed.
...just using that Mac right now running Windows - with no problems.
No lockups yet running new display via HDMI. Will report back over the next few days. (Before this was getting 2 to 4 a day.)
I have got that request about more logs as well. Regarding the final answer, it now appears just like some kind of automated reply...