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

SpencerHarrison

macrumors newbie
Dec 2, 2017
3
2
No the screensaver is not the problem, but it is probably the best way to replicate the issue. It can take minutes or days but it will crash eventually if you leave Flurry running.

This. Further, it seems to be something the Apple techs are able to set up and recognize. I am totally confident that the machine would freeze just sitting there doing nothing, but when that was the plan, for whatever reason, Apple was never able or willing to get results. Having them do the screensaver was the crack that broke the dam.
 

iigsie

macrumors regular
Nov 17, 2007
141
116
This. Further, it seems to be something the Apple techs are able to set up and recognize. I am totally confident that the machine would freeze just sitting there doing nothing, but when that was the plan, for whatever reason, Apple was never able or willing to get results. Having them do the screensaver was the crack that broke the dam.


In my case they're unwilling to test it any further. I only spoke to the tech yesterday and suggested leaving flurry running but today the same guy called and said they can't replicate the issue and I need to collect. He implied my OS install was bad and that a clean install last week by them must have solved the issue.
 

MarkJames68

macrumors 6502
Sep 24, 2017
394
246
In my case they're unwilling to test it any further. I only spoke to the tech yesterday and suggested leaving flurry running but today the same guy called and said they can't replicate the issue and I need to collect. He implied my OS install was bad and that a clean install last week by them must have solved the issue.
As they said it was solved, I would take it home and immediately video it locking up before you reinstall anything. Then bring it back. Document the times they’ve had it because after a few you can push for a new system.
 

bax2003

Cancelled
Original poster
Dec 25, 2011
947
203
Problem is not the screensaver. I made my D300 do things that you could have fried eggs on it - it did not crash. Problem is, that CAN crash just because it is running - doing nothing but beeing switched on and displaying the desktop.

Still on the most recent version of Sierra they re-introduced the oldest variant of the crash: "freeze and wait until angry user cuts power". I liked the "I will freeze, crash and show you the login screen" a littlt bit more.

I might be repeating older statements: I still cannot understand, why I can run Windows 10 bootcamp all day long, mabye even longer without any interruption, but still do have problems with Mac OS.

...Maybe it was not really "Made for Mac OS" but Windows - who knows.

I have a theory on why High Sierra re-introduced old way of crashing: when your can crashes like that, there is no logged error Console. (named ".crash" or "error") Of course you can search through LOGs and track down the time and forced reboot but is is way less obvious.
 

mikeboss

macrumors 68000
Aug 13, 2009
1,546
862
switzerland
for me, the flurry screensaver really is the diagnostic tool of choice. my old 4-core/D300 machine crashed within 48 hours, every time. the new 6-core/D500 I bought is running flurry for about 10 days now. so far it didn't freeze one single time...
the old machine ran Apple Service Diagnostics and it did not show any errors even though it clearly wasn't a stable system.
 

axantas

macrumors 65816
Jun 29, 2015
1,000
1,407
Home
I have a theory on why High Sierra re-introduced old way of crashing: when your can crashes like that, there is no logged error Console. (named ".crash" or "error") Of course you can search through LOGs and track down the time and forced reboot but is is way less obvious.

Interestingly enough there IS a logged crash. It is again only the graphic frontend which crashes, but does not recover anymore. *sigh*
 

bax2003

Cancelled
Original poster
Dec 25, 2011
947
203
Interestingly enough there IS a logged crash. It is again only the graphic frontend which crashes, but does not recover anymore. *sigh*

There is a logged crash in console ? As gpuRestart or WindowServer crash ?
 

axantas

macrumors 65816
Jun 29, 2015
1,000
1,407
Home
There is a logged crash in console ? As gpuRestart or WindowServer crash ?

just “MacPro crash”. not tge usual window server. Iwas kind of astonished that it did log the crash and just froze

I will have a look at the log again this evening.

EDIT I was wrong:
- Kernel gpu.restart
- WindowServer...crash - 13 sesonds later

then the GUI froze - the machine itself might have been running itself, but i had to power cycle it.
At that time NOTHING at all happened on screen. I was converting a video with HandBrake.
 
Last edited:

GregX

macrumors newbie
Apr 4, 2008
10
0
Summary of Consumer Laws in the United Kingdom
Your consumer rights for goods purchased in the United Kingdom operate alongside, and in addition to, your rights under the Apple One-Year Limited Warranty and the optional AppleCare Protection Plan or AppleCare+.

Under UK consumer law, consumers may choose to have defective goods or goods which do not conform with the contract sale either repaired or replaced free of charge. If a repair or replacement is not possible, would impose a disproportionate burden on the seller, or could not be performed in a reasonable time and without significant inconvenience to the consumer, the consumer may choose either to have the price reduced or to withdraw from the contract by returning the product in exchange for a full refund. A consumer is also entitled to withdraw from the contract by returning the product in exchange for a full refund if the consumer rejects the goods within 30 days or if the product does not conform with the contract after one repair or replacement.. The primary responsibility to provide a remedy is on the seller, which would be Apple if the goods were purchased from the Apple Online Store or an Apple Retail Store. If the goods were purchased from a third party reseller of Apple products, the primary responsibility to provide a remedy will lie with the reseller. For goods purchased in England or Wales, these rights expire six years from delivery of the goods. For goods purchased in Scotland, these rights expire five years from delivery of the goods. A claim under UK consumer law may be made subject to the defect being present at the time of purchase.

Any defect or non-conformity of goods with the contract which becomes apparent within 6 months of delivery are presumed to have existed at the time of delivery. After the expiry of this 6 month period, the burden to prove that the defect or non-conformity of goods with the contract existed on delivery generally shifts to the consumer.


Given that the defect is present and has been since they were built then surely Apple has to fix the issue free of charge. The product is not fit for purpose.

This issue has not started until all warranties have expired and is totally related to Apple messing with Metal or using GPU in later systems.

I will be trying the flurry tests, although after 10 crashes this morning the trashcan Mac is just that and I have had to borrow a laptop before I go crazy.

So for now I may as well test to see if flurry can make it lock up enough and just dump it down in front of Apple support and say I want this faulty product replaced with a model that works, current model, under UK consumer law, this product is not fit for purpose.
 

MarkJames68

macrumors 6502
Sep 24, 2017
394
246
Did some reconfiguration of my system and after setting up again tested flurry with max settings on eGPU. Only let run for 30 minutes but no lockup or strain.

On another note, I did get beachballing when doing the LuxMark Lobby benchmark with both D300s and RX580 eGPU. Then I noticed system was really hot and system fan was near minimum. I then set iStat to the medium fan setting which brought down temps. Running it again passed the benchmark. Didn’t have a failure at any fan speed with just the eGPU.

Which got me thinking - the D300 and D700 run at the highest frequency, while the D500 is comparatively slower. I wonder if there is some sort of thermal issue causing the issues with the D300.
 

iigsie

macrumors regular
Nov 17, 2007
141
116
Officialy, yes. Only D500 and D700.
I think that there were some rare instances with D300 been repaired too.

Yes the repair program only covers D500 and D700 Mac Pro's manufactured between February 8 2015 and April 11 2015. The repair requires replacement of both graphics cards and the interconnect board. The repair program ends in May 2018.

Apple eventually replaced the interconnect board and both graphics cards (card b for the second time) in my D300, though it wasn't easy to get it done - 7 trips to the store and over 12 months of trying. What helped in my case was that I'd been back two times while it was under warranty and I had video footage of the issue.

The level of service you receive depends on the store you visit or whether you have AppleCare. Larger stores and Authorised Resellers that sell lots of Mac Pro's are more likely to fix/replace. Smaller stores tend to strictly follow the guidelines until Engineering get involved and authorise the replacement of both cards and interconnect board.
 
Last edited:

uller6

macrumors 65816
May 14, 2010
1,072
1,777
Well, I've started getting random crashes on my D300 quad core, usually when using Safari with only 1-5 tabs open. Everything except the mouse will lock up and the computer requires a hard restart to recover. The spindump log in console points to a windowserver crash - is my Mac Pro cursed with the dreaded GPA wasting disease?

I'm running 10.13.2 and using a dell 4k display.

Screenshot 2018-01-02 15.08.39.png
 

voyager77

macrumors member
Jun 25, 2012
82
29
Well, I've started getting random crashes on my D300 quad core, usually when using Safari with only 1-5 tabs open. Everything except the mouse will lock up and the computer requires a hard restart to recover. The spindump log in console points to a windowserver crash - is my Mac Pro cursed with the dreaded GPA wasting disease?
View attachment 744918

That sounds very familiar, i'm afraid ...
 

Naimfan

Suspended
Jan 15, 2003
4,669
2,017
Well, I've started getting random crashes on my D300 quad core, usually when using Safari with only 1-5 tabs open. Everything except the mouse will lock up and the computer requires a hard restart to recover. The spindump log in console points to a windowserver crash - is my Mac Pro cursed with the dreaded GPA wasting disease?

I'm running 10.13.2 and using a dell 4k display.

View attachment 744918

Ditto. I'm reconsidering my purchase decision - I have another 2013 MP in the cart, but my first one is headed back to OWC.

Same symptom - random crashes, requiring a hard restart. Console shows numerous GPUrestart errors. Oh well. At least I have a dual-processor 2010 arriving tomorrow . . .
 

SamPotts

macrumors 6502
Sep 25, 2010
278
59
Sydney, Australia
Last week I received my quad core, D300 nMP from OWC - it was rude not too at current sale prices. I upgraded it to 48GB and installed High Sierra and I'm already seeing the odd freeze now and then :( After reading through this thread, I looked in the console for GPU or "WindowServer" related logs but there's nothing in there. I ran the Apple Diagnostics test (held D at boot) and it passed without issue (which seems to be the same for everyone). When I look up my machines build date, it says June 2016 so *shouldn't* be effected. I'll give the original RAM a go but I suspect it's not that.
 

krakman

macrumors 6502
Dec 3, 2009
450
511
Last week I received my quad core, D300 nMP from OWC - it was rude not too at current sale prices. I upgraded it to 48GB and installed High Sierra and I'm already seeing the odd freeze now and then :( After reading through this thread, I looked in the console for GPU or "WindowServer" related logs but there's nothing in there. I ran the Apple Diagnostics test (held D at boot) and it passed without issue (which seems to be the same for everyone). When I look up my machines build date, it says June 2016 so *shouldn't* be effected. I'll give the original RAM a go but I suspect it's not that.

Return it immediately to OWC to avoid the frustration that lies ahead.....!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.