Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

chama98

macrumors 6502
Original poster
Feb 13, 2014
332
159
London
I wonder if anyone out there who is using a mac pro late 2013. I am using a thunderbolt display with my mac pro.

I installed beta 2 and then experienced the graphic issues. I restarted and booted into safe mode then restarted again and the graphic issues disappeared.

Could it be a cache issue?

Thoughts
 

keysofanxiety

macrumors G3
Nov 23, 2011
9,539
25,302
Looks like hardware to be honest. Do you have the D500 or D700? There's an extended repair program for them.
 

chama98

macrumors 6502
Original poster
Feb 13, 2014
332
159
London
Looks like hardware to be honest. Do you have the D500 or D700? There's an extended repair program for them.
No it's not hardware issue is a software issue.

Hardware test came back ok. Both Apple hardware test and other 'professional' hardware tests.
 

keysofanxiety

macrumors G3
Nov 23, 2011
9,539
25,302
No it's not hardware issue is a software issue.

Hardware test came back ok. Both Apple hardware test and other 'professional' hardware tests.

OK, just does very much resemble hardware. Regardless, do you have the D500/700?

Does the issue also occur on 10.11.5?
 

keysofanxiety

macrumors G3
Nov 23, 2011
9,539
25,302
No I have the D300.

I can confirm the error DOES NOT happen in 10.11.5.

Okay, if that's the case it's possibly a driver issue with either Thunderbolt display or D300 on the Sierra build.

You can try the normal PRAM/SMC resets, plus testing through a new administrator user account. If the issue persists, report the bug & roll back to El Cap.
 

chama98

macrumors 6502
Original poster
Feb 13, 2014
332
159
London
Okay, if that's the case it's possibly a driver issue with either Thunderbolt display or D300 on the Sierra build.

You can try the normal PRAM/SMC resets, plus testing through a new administrator user account. If the issue persists, report the bug & roll back to El Cap.
Well funny you should say that. I am doing this now.

However a pram/smc reset is not necessary. It's a cache issue I am sure of it. Because as soon as I rebooted into safe mode the error had gone. To be sure I restarted again normally and everything was back to normal. However I have reported it including the video I took and photos of the issue.

Will wait and see what happens!

Tempted to carry on with testing though.
 

keysofanxiety

macrumors G3
Nov 23, 2011
9,539
25,302
Well funny you should say that. I am doing this now.

However a pram/smc reset is not necessary. It's a cache issue I am sure of it. Because as soon as I rebooted into safe mode the error had gone. To be sure I restarted again normally and everything was back to normal. However I have reported it including the video I took and photos of the issue.

Will wait and see what happens!

Tempted to carry on with testing though.

Have you tried a new user account? And SMC/PRAM doesn't take long at all so it's worth a shot, even if you feel it won't be relevant to the problem you're having.
 

chama98

macrumors 6502
Original poster
Feb 13, 2014
332
159
London
Have you tried a new user account? And SMC/PRAM doesn't take long at all so it's worth a shot, even if you feel it won't be relevant to the problem you're having.


yeah, don't that as well. Didn't make a difference. Its a driver issue
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.