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

What do you think is the source of the graphics issues on Mac Pro (Late 2013) ?

  • Hardware

    Votes: 69 53.1%
  • Software

    Votes: 28 21.5%
  • Hardware & Software

    Votes: 32 24.6%
  • Other

    Votes: 1 0.8%

  • Total voters
    130

iigsie

macrumors regular
Nov 17, 2007
141
116
6 months since apple replaced the circular board (logic board/interconnect board) and I haven't had a crash or error appear in the log. It's also running the same image of 10.12.6 that it was running when it was crashing.

it really does look like in my case it was hardware. I'ver not had a single issue since they reluctantly replaced that part
 

swithdrawn

macrumors member
Apr 28, 2018
40
20
Have you checked on console, in the system log, the last process before the KP?

I haven't checked console in awhile since I never saw anything relevant. Next crash I will.

I am now on Mojave 10.14 beta 2 and will report any crashes...

**EDIT**

Crash 20 seconds after posting. Nothing of relevance in log, just:

Jun 19 22:00:21 Stephens-Pro com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit

Also did not get an error report dialog after rebooting with the Defrost app.
 
Last edited:

jjack78

macrumors newbie
Jun 17, 2018
3
1
Paris
Positive, this is a cut and paste of my plist <!--<string>Aqua</string>--> as of 2 minutes ago.
And for reference, had another kernel panic about 3 hours after the one I posted about. Was just scrolling through Facebook, went to edit a post and bang, everything frozen except the mouse.

I looked at my plist file and this line has disappeared (because this is a comment ?).

**EDIT**
Please ignore.
 
Last edited:

boli

macrumors newbie
Aug 6, 2010
19
8
I did just now, after my nMP panicked again (first time since my previous post on Monday, when it panicked twice).

My feeling is that it won't help, as those log messages seem more like a symptom of the problem – other things also go nuts during the freeze/before the panic. I'd love to be wrong on this though. ;)

My nMP just panicked again, despite doing this change on June 11. :(
 

bax2003

Cancelled
Original poster
Dec 25, 2011
947
203
I have sold all of my nMPs. The End.

It is a good idea, nice form factor, quite powerful and quiet, but it just does not work properly.

Of course, I´ll still be around when I can to give some ideas and maybe help someone.
I would really like that Apple come out with some solution or at least, workaround.
 

R3k

macrumors 68000
Sep 7, 2011
1,522
1,504
Sep 7, 2011
I haven't checked console in awhile since I never saw anything relevant. Next crash I will.

I am now on Mojave 10.14 beta 2 and will report any crashes...

**EDIT**

Crash 20 seconds after posting. Nothing of relevance in log, just:

Jun 19 22:00:21 Stephens-Pro com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit

Also did not get an error report dialog after rebooting with the Defrost app.

Do you think the crash has anything to do with "displayModeDidChange" or just a general crash?
 

letsbefrank56

macrumors newbie
Apr 4, 2018
6
6
I have sold all of my nMPs. The End.

It is a good idea, nice form factor, quite powerful and quiet, but it just does not work properly.

Of course, I´ll still be around when I can to give some ideas and maybe help someone.
I would really like that Apple come out with some solution or at least, workaround.

Did you only have D300s in your nMPs or did you also have issues with ones that had D500 and D700s ?
 

bax2003

Cancelled
Original poster
Dec 25, 2011
947
203
Did you only have D300s in your nMPs or did you also have issues with ones that had D500 and D700s ?

1st QC with D300s, reported problems, lost many days waiting for service, serviced, both cards replaced - problem not solved, got rid of it

2nd QC with D300s, reported problem, both cards replaced - the same problem, got 6c replacement

6c with D500s, freeze (with spinning wheel) every 10 days and these new kernel panics every 2 days, got rid of it

To summarize: 4 pairs of D300s and 1 pair of D500s. D500s more or less the same problem, but occurred less often then on D300s.
 
  • Like
Reactions: OverZealous

letsbefrank56

macrumors newbie
Apr 4, 2018
6
6
1st QC with D300s, reported problems, lost many days waiting for service, serviced, both cards replaced - problem not solved, got rid of it

2nd QC with D300s, reported problem, both cards replaced - the same problem, got 6c replacement

6c with D500s, freeze (with spinning wheel) every 10 days and these new kernel panics every 2 days, got rid of it

To summarize: 4 pairs of D300s and 1 pair of D500s. D500s more or less the same problem, but occurred less often then on D300s.

That's too bad. I may be getting my nMP D300 replaced through AppleCare and I am worried that the replacement (most probably a 6 Core D500) will have the same freezing issues. Thanks for your info.
 

Martyimac

macrumors 68020
Aug 19, 2009
2,460
1,695
S. AZ.
I am, at this point, absolutely convinced that there is something deep inside the actual D300 card which is at fault. I used all the replacement parts I could from my nMP 4 core/D300 to get my 6c/D500 back up and running, with the exception of the CPU and the GPU's. My D500 machine is running flawlessly again just like it did for the last 4+ years until I gave it a bath, unintentionally of course. :( I even used the upper logic board from the newer D300 machine and no freezes. I think the only "fix" is to replace the boards and of course that is way to expensive.
Good luck all.
 

R3k

macrumors 68000
Sep 7, 2011
1,522
1,504
Sep 7, 2011
I’ve been involved with 4 different Mac nMac Pro systems. First 2 D500’s are great and still working fine today. The third had crazy graphic freezes and reboots, screwed up images on screen, etc. I feel this is the issue Apple is fixing for free. I returned it. Later got a D300 system and one year after that the "displaymodedidchange" error started popping up.

I feel the D500 and D700 hardware graphic problems and the displaymodidchange panics are two separate issues.
 
  • Like
Reactions: Martyimac

boli

macrumors newbie
Aug 6, 2010
19
8
I feel the D500 and D700 hardware graphic problems and the displaymodidchange panics are two separate issues.

Maybe. I'm currently trying to get my D300s nMP serviced, and only just now noticed that the repair program is for D500s and D700s only. I'm in contact with a friend who's an Apple authorized technician at a third party shop to see what gives.

If he can't/won't repair it I'll go to Apple directly (who replaced my D300 June 2014 MP in December 2016 with a brand new one, as a summary from my first post).
 

krakman

macrumors 6502
Dec 3, 2009
450
511
Installed Mojave beta this morning onto a spare drive to see see if improved anything......have had 4 freezes so far.......:mad:
 

bax2003

Cancelled
Original poster
Dec 25, 2011
947
203
Installed Mojave beta this morning onto a spare drive to see see if improved anything......have had 4 freezes so far.......:mad:

Software does not have anything to do with this. Apple can change reports or try to hide the problem by auto restarting the driver but that does hide the fact that hardware is the culprit.

Mavericks (with least issues as least graphically intensive nMP OS) to Mohave - it is clear that we must stop hoping that software can solve this.
 
  • Like
Reactions: Martyimac

swithdrawn

macrumors member
Apr 28, 2018
40
20
Do you think the crash has anything to do with "displayModeDidChange" or just a general crash?

It's the same displaymodedidchange panic.

Software does not have anything to do with this. Apple can change reports or try to hide the problem by auto restarting the driver but that does hide the fact that hardware is the culprit.

Mavericks (with least issues as least graphically intensive nMP OS) to Mohave - it is clear that we must stop hoping that software can solve this.

It's obviously a h/w issue but the whole system doesn't have to crap the bed. Windows just restarts the GPU driver as others have mentioned, and you move on. This can certainly be mitigated with software, but it's a long shot for Apple to do anything.

Trying 10.13.6 beta 4 but am not expecting anything.
 
  • Like
Reactions: R3k

AidenShaw

macrumors P6
Feb 8, 2003
18,667
4,677
The Peninsula
Software does not have anything to do with this. Apple can change reports or try to hide the problem by auto restarting the driver but that does hide the fact that hardware is the culprit.
Windows just restarts the GPU driver as others have mentioned, and you move on.
Software can hide hardware problems, and has been for decades.

Apple is simply lazy (or simply no longer cares about Apple OSX).
 

bax2003

Cancelled
Original poster
Dec 25, 2011
947
203
Aren't there reports that it's only a minor glitch when running Windows on the MP6,1?

That would be proof that Apple *could* mask it - if they cared to.

Those "Display driver stopped responding and has recovered" glitches could be caused be already crappy AMD drivers or hardware itself, or maybe both. Either way, I am not specialist in drivers so I cannot prove that if something is done on Windows that could also be done on OS X, especially because in OS X Window Server crashes and you don´t have something like that in Windows environment. "Display driver stopped responding and has recovered" glitches could happen in Windows with perfectly healthy hardware.

My conclusion, Apple is aware that software is not the problem here, because when customer reports an issue, they replace GPU-A, then GPU-B, PSU, GPU cables, I/O panel and finally Logic Board - by using system of elimination it is clear to me that they are not even sure what to do.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.