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

o_O

macrumors newbie
Dec 25, 2016
2
0
I've been having GPU hangs more frequently, in-fact 15+ within the last day:

Sun Dec 25 11:07:52 2016

Event: GPU Reset
Date/Time: Sun Dec 25 11:07:52 2016
Application:
Path:
Tailspin: /Library/Logs/DiagnosticReports/gpuRestart2016-12-25-110752.tailspin
GPUSubmission Trace ID: 0
OS Version: Mac OS X Version 10.12.1 (Build 16B2657)
Graphics Hardware: AMD FirePro D700
Signature: 0

Report Data:

GPURestartReportStart
------------------------
Hung Channels: DMA0
------------------------
[03] AccelChannel: DMA0
Pending Command from : UnknownCtx
PendingCommandTimestamp: 0x00386124, TotalDWords: 0x00000009, GART Offset=0x000000040b350000, stamp_idx=3, estamp=0x00386124
PendingCommandStart:
PendingCommandEnd
------------------------
[03] DMA0 HWChannel : Enabled, Idle
LastReadTimestamp : 0x00386123
NextSubmitTimestamp : 0x00386125
[DMA0, ts:0x00386124]: semaphore wait[0]: 0xffffff805b411000
HWSemaphore 0xffffff805b411000 Signal Event: [GFX channel[0] TS:0x0f9102dc lastReadTS:0x0f9102dc]
HWSemaphore 0xffffff805b411000 Wait Event : [DMA0 channel[3] TS:0x00386124 lastReadTS:0x00386123]
[DMA0, ts:0x00386124]: semaphore signal: 0xffffff805b461200
HWSemaphore 0xffffff805b461200 Signal Event: [DMA0 channel[3] TS:0x00386124 lastReadTS:0x00386123]
HWSemaphore 0xffffff805b461200 Wait Event : [GFX channel[0] TS:0x0f9102da lastReadTS:0x0f9102dc]
------------------------
[0] PFP_HEADER_DUMP: 0xc0311000 0xc0013900 0xc0044700 0xc0053c00 0xc0034300
[0] ME_HEADER_DUMP : 0xc0013900 0xc0044700 0xc0053c00 0xc0034300 0x00002010
[1] PFP_HEADER_DUMP: 0x9d357be0 0x7e35b9cd 0xe6eaf9f2 0x8f4d1c5f 0x5db2e6e9
[1] ME_HEADER_DUMP : 0xfbbef3f3 0x10f51ab8 0x7fda9fff 0xedff57df 0x87b7b1cf
[2] PFP_HEADER_DUMP: 0xc0013900 0xc0044702 0xc0053c02 0xc0034302 0xc0033702
[2] ME_HEADER_DUMP : 0xc0013900 0xc0044702 0xc0053c02 0xc0034302 0xc0033702
------------------------
SRBM_CNTL : 0x000103ff | CP_ME_CNTL : 0x00000000
SRBM_STATUS: 0x200000c0 | SRBM_STATUS2: 0x00000000
GRBM_STATUS: 0x00003028 | GRBM_STATUS2: 0x00000000
------------------------
GPU HangFlags 0x00000004: AsicHangState 0x00000004, AsicResetRequirement 0x00000002
IndividualEngineHang: 0
NonEngineBlockHang : 0
FenceNotRetired : 1
PerEngineReset : 0
FullAsicReset : 1
HangEngineBitmap : 0x00000000
------------------------
AMDTahitiGraphicsAccelerator PCIe Device: [6:0:0] State: ENABLED
Configuration: deviceBits: 0x50096798, capabilityBits: 0x30840300
TotalVideoRAMBytes: 0x0000000180000000 (6442450944)
------------------------
[00] PM4 Engine : Enabled, Idle
[00] GFX Channel: Enabled, Idle, lastReadTimestamp 0x0f9102dc, nextSubmitTimestamp 0x0f9102dd
[01] C0 Channel: Enabled, Idle, lastReadTimestamp 0x00000000, nextSubmitTimestamp 0x00000001
[02] C1 Channel: Enabled, Idle, lastReadTimestamp 0x00005c2f, nextSubmitTimestamp 0x00005c30
------------------------
[01] SDMA Engine : Enabled, Idle
[03] DMA0 Channel: Enabled, Idle, lastReadTimestamp 0x00386123, nextSubmitTimestamp 0x00386125
------------------------
[02] SDMA Engine : Enabled, Idle
[04] DMA1 Channel: Enabled, Idle, lastReadTimestamp 0x02233964, nextSubmitTimestamp 0x02233965
------------------------
[03] UVD Engine : Disabled, Idle
[05] UVD Channel: Disabled, Idle, lastReadTimestamp 0x00000000, nextSubmitTimestamp 0x00000001
------------------------
[04] SPU Engine : Disabled, Idle
[06] SPU Channel: Disabled, Idle, lastReadTimestamp 0x00000000, nextSubmitTimestamp 0x00000001
------------------------
[05] VCE Engine : Disabled, Idle
[07] VCE Channel: Disabled, Idle, lastReadTimestamp 0x00000000, nextSubmitTimestamp 0x00000001
[08] VCEL Channel: Disabled, Idle, lastReadTimestamp 0x00000000, nextSubmitTimestamp 0x00000001
------------------------


Sun Dec 25 11:08:32 2016

Event: GPU Reset
Date/Time: Sun Dec 25 11:08:32 2016
Application:
Path:
Tailspin: /Library/Logs/DiagnosticReports/gpuRestart2016-12-25-110832.tailspin
GPUSubmission Trace ID: 0
OS Version: Mac OS X Version 10.12.1 (Build 16B2657)
Graphics Hardware: AMD FirePro D700
Signature: 2e

Report Data:

GPURestartReportStart
------------------------
Hung Channels: GFX DMA0
------------------------
[03] AccelChannel: DMA0
Pending Command from : UnknownCtx
PendingCommandTimestamp: 0x00386127, TotalDWords: 0x00000009, GART Offset=0x0000000429950000, stamp_idx=3, estamp=0x00386127
PendingCommandStart:
PendingCommandEnd
------------------------
[03] DMA0 HWChannel : Enabled, NotIdle
LastReadTimestamp : 0x00386126
NextSubmitTimestamp : 0x00386167
[DMA0, ts:0x00386127]: No semaphore wait
[DMA0, ts:0x00386127]: semaphore signal: 0xffffff805b461f80
HWSemaphore 0xffffff805b461f80 Signal Event: [DMA0 channel[3] TS:0x00386165 lastReadTS:0x00386126]
HWSemaphore 0xffffff805b461f80 Wait Event : [GFX channel[0] TS:0x0f910301 lastReadTS:0x0f9102fd]
------------------------
[0] PFP_HEADER_DUMP: 0xc0066900 0xc0066900 0xc0066900 0xc0066900 0xc0066900
[0] ME_HEADER_DUMP : 0xc0034300 0xc0005200 0xc0004600 0xc0012d00 0xc0002f00
[1] PFP_HEADER_DUMP: 0x9d357be0 0x7e35b9cd 0xe6eaf9f2 0x8f4d1c5f 0x5db2e6e9
[1] ME_HEADER_DUMP : 0xfbbef3f3 0x10f51ab8 0x7fda9fff 0xedff57df 0x87b7b1cf
[2] PFP_HEADER_DUMP: 0xc0013900 0xc0044702 0xc0053c02 0xc0034302 0xc0033702
[2] ME_HEADER_DUMP : 0xc0013900 0xc0044702 0xc0053c02 0xc0034302 0xc0033702
------------------------
SRBM_CNTL : 0x000003ff | CP_ME_CNTL : 0x00000000
SRBM_STATUS: 0x200000c0 | SRBM_STATUS2: 0x00000020
GRBM_STATUS: 0xb7523028 | GRBM_STATUS2: 0x00000000
[sh,se]=[0,0] spiDebugBusy 0x0003c000: [LS,HS,ES]=[0,0,0] [GS,VS,PS0,PS1]=[0,0,0,0] [CS0,CS1,CS2]=[0,0,0]
[sh,se]=[0,1] spiDebugBusy 0x0003c000: [LS,HS,ES]=[0,0,0] [GS,VS,PS0,PS1]=[0,0,0,0] [CS0,CS1,CS2]=[0,0,0]
[sh,se]=[1,0] spiDebugBusy 0x00000000: [LS,HS,ES]=[0,0,0] [GS,VS,PS0,PS1]=[0,0,0,0] [CS0,CS1,CS2]=[0,0,0]
[sh,se]=[1,1] spiDebugBusy 0x00000000: [LS,HS,ES]=[0,0,0] [GS,VS,PS0,PS1]=[0,0,0,0] [CS0,CS1,CS2]=[0,0,0]
------------------------
GPU HangFlags 0x00000007: AsicHangState 0x00000007, AsicResetRequirement 0x00000002
IndividualEngineHang: 1
NonEngineBlockHang : 1
FenceNotRetired : 1
PerEngineReset : 0
FullAsicReset : 1
HangEngineBitmap : 0x0000002e
Hung Engines Detected by Cail: GRAPHICS COMPUTE0 COMPUTE1 DRMDMA/SDMA
------------------------
AMDTahitiGraphicsAccelerator PCIe Device: [6:0:0] State: ENABLED
Configuration: deviceBits: 0x50096798, capabilityBits: 0x30840300
TotalVideoRAMBytes: 0x0000000180000000 (6442450944)
------------------------
[00] PM4 Engine : Enabled, NotIdle
[00] GFX Channel: Enabled, NotIdle, lastReadTimestamp 0x0f9102fd, nextSubmitTimestamp 0x0f910399
[01] C0 Channel: Enabled, Idle, lastReadTimestamp 0x00000000, nextSubmitTimestamp 0x00000001
[02] C1 Channel: Enabled, Idle, lastReadTimestamp 0x00005c2f, nextSubmitTimestamp 0x00005c30
------------------------
[01] SDMA Engine : Enabled, NotIdle
[03] DMA0 Channel: Enabled, NotIdle, lastReadTimestamp 0x00386126, nextSubmitTimestamp 0x00386167
------------------------
[02] SDMA Engine : Enabled, Idle
[04] DMA1 Channel: Enabled, Idle, lastReadTimestamp 0x02233b2a, nextSubmitTimestamp 0x02233b2b
------------------------
[03] UVD Engine : Disabled, Idle
[05] UVD Channel: Disabled, Idle, lastReadTimestamp 0x00000000, nextSubmitTimestamp 0x00000001
------------------------
[04] SPU Engine : Disabled, Idle
[06] SPU Channel: Disabled, Idle, lastReadTimestamp 0x00000000, nextSubmitTimestamp 0x00000001
------------------------
[05] VCE Engine : Disabled, Idle
[07] VCE Channel: Disabled, Idle, lastReadTimestamp 0x00000000, nextSubmitTimestamp 0x00000001
[08] VCEL Channel: Disabled, Idle, lastReadTimestamp 0x00000000, nextSubmitTimestamp 0x00000001
------------------------


Sun Dec 25 11:07:52 2016

Event: GPU Reset
Date/Time: Sun Dec 25 11:07:52 2016
Application: WindowServer
Path:
Tailspin: /Library/Logs/DiagnosticReports/gpuRestart2016-12-25-110752.tailspin
GPUSubmission Trace ID: 0
OS Version: Mac OS X Version 10.12.1 (Build 16B2657)
Graphics Hardware: AMD FirePro D700
Signature: e

Report Data:

GPURestartReportStart
------------------------
Hung Channels: GFX
------------------------
[00] AccelChannel: GFX
Pending Command from : GLCtx
PendingCommandTimestamp: 0x0f9101a6, TotalDWords: 0x00000280, GART Offset=0x00000004572d4d80, stamp_idx=0, estamp=0x0f9101a6
PendingCommandStart:
PendingCommandEnd
------------------------
[00] GFX HWChannel : Enabled, NotIdle
LastReadTimestamp : 0x0f9101a5
NextSubmitTimestamp : 0x0f9102dd
[GFX, ts:0x0f9101a6]: No semaphore wait
[GFX, ts:0x0f9101a6]: semaphore signal: 0xffffff805b3f15c0
HWSemaphore 0xffffff805b3f15c0 Signal Event: [GFX channel[0] TS:0x0f9102dc lastReadTS:0x0f9101a5]
------------------------
[0] PFP_HEADER_DUMP: 0xc0016900 0xc0016900 0xc0016900 0xc0016900 0xc0016900
[0] ME_HEADER_DUMP : 0xc0034300 0xc0004600 0xc0016900 0xc0016900 0xc0026900
[1] PFP_HEADER_DUMP: 0x9d357be0 0x7e35b9cd 0xe6eaf9f2 0x8f4d1c5f 0x5db2e6e9
[1] ME_HEADER_DUMP : 0xfbbef3f3 0x10f51ab8 0x7fda9fff 0xedff57df 0x87b7b1cf
[2] PFP_HEADER_DUMP: 0xc0013900 0xc0044702 0xc0053c02 0xc0034302 0xc0033702
[2] ME_HEADER_DUMP : 0xc0034302 0xc0033702 0xc0004602 0xc0031502 0xc0017602
------------------------
SRBM_CNTL : 0x000003ff | CP_ME_CNTL : 0x00000000
SRBM_STATUS: 0x200000c0 | SRBM_STATUS2: 0x00000000
GRBM_STATUS: 0xb3523028 | GRBM_STATUS2: 0x00000000
[sh,se]=[0,0] spiDebugBusy 0x0003f010: [LS,HS,ES]=[0,0,0] [GS,VS,PS0,PS1]=[0,1,0,0] [CS0,CS1,CS2]=[0,0,0]
[sh,se]=[0,1] spiDebugBusy 0x0003f010: [LS,HS,ES]=[0,0,0] [GS,VS,PS0,PS1]=[0,1,0,0] [CS0,CS1,CS2]=[0,0,0]
[sh,se]=[1,0] spiDebugBusy 0x00000000: [LS,HS,ES]=[0,0,0] [GS,VS,PS0,PS1]=[0,0,0,0] [CS0,CS1,CS2]=[0,0,0]
[sh,se]=[1,1] spiDebugBusy 0x00000000: [LS,HS,ES]=[0,0,0] [GS,VS,PS0,PS1]=[0,0,0,0] [CS0,CS1,CS2]=[0,0,0]
------------------------
GPU HangFlags 0x00000007: AsicHangState 0x00000007, AsicResetRequirement 0x00000002
IndividualEngineHang: 1
NonEngineBlockHang : 1
FenceNotRetired : 1
PerEngineReset : 0
FullAsicReset : 1
HangEngineBitmap : 0x0000000e
Hung Engines Detected by Cail: GRAPHICS COMPUTE0 COMPUTE1
------------------------
AMDTahitiGraphicsAccelerator PCIe Device: [6:0:0] State: ENABLED
Configuration: deviceBits: 0x50096798, capabilityBits: 0x30840300
TotalVideoRAMBytes: 0x0000000180000000 (6442450944)
------------------------
[00] PM4 Engine : Enabled, NotIdle
[00] GFX Channel: Enabled, NotIdle, lastReadTimestamp 0x0f9101a5, nextSubmitTimestamp 0x0f9102dd
[01] C0 Channel: Enabled, Idle, lastReadTimestamp 0x00000000, nextSubmitTimestamp 0x00000001
[02] C1 Channel: Enabled, Idle, lastReadTimestamp 0x00005c2c, nextSubmitTimestamp 0x00005c30
------------------------
[01] SDMA Engine : Enabled, Idle
[03] DMA0 Channel: Enabled, Idle, lastReadTimestamp 0x00386123, nextSubmitTimestamp 0x00386125
------------------------
[02] SDMA Engine : Enabled, Idle
[04] DMA1 Channel: Enabled, Idle, lastReadTimestamp 0x02233964, nextSubmitTimestamp 0x02233965
------------------------
[03] UVD Engine : Disabled, Idle
[05] UVD Channel: Disabled, Idle, lastReadTimestamp 0x00000000, nextSubmitTimestamp 0x00000001
------------------------
[04] SPU Engine : Disabled, Idle
[06] SPU Channel: Disabled, Idle, lastReadTimestamp 0x00000000, nextSubmitTimestamp 0x00000001
------------------------
[05] VCE Engine : Disabled, Idle
[07] VCE Channel: Disabled, Idle, lastReadTimestamp 0x00000000, nextSubmitTimestamp 0x00000001
[08] VCEL Channel: Disabled, Idle, lastReadTimestamp 0x00000000, nextSubmitTimestamp 0x00000001
------------------------
 

angopop

macrumors newbie
Dec 4, 2016
3
0
Update...

I left my Mac Pro with the Apple store a week before Christmas, that was the third time leaving it there. On the second trip they were supposed to wipe the drive and run diagnostics, and when I got it back they had not wiped so I brought it back so they could wipe and run those diagnostics.

I got the Mac Pro back yesterday, they told me they had wiped it, reinstalled the OS and ran it nonstop with no issues. I get it home and found that they had installed Sierra on it, after I had repeatedly told them to leave it on El Capitan (as I don't know yet whether all my software will work on Sierra without making purchases, etc...)

Does anyone know if I can install El Capitan on a machine with Sierra? I've heard that you can only install newer Mac OS, not older versions?

Anyway, that probably means that the week of diagnostics that they did was on Sierra and not El Capitan.

That's the second time they did not do what they told me they were going to do, wasting more of my time....
 

bax2003

Cancelled
Original poster
Dec 25, 2011
947
203
Update...

I left my Mac Pro with the Apple store a week before Christmas, that was the third time leaving it there. On the second trip they were supposed to wipe the drive and run diagnostics, and when I got it back they had not wiped so I brought it back so they could wipe and run those diagnostics.

I got the Mac Pro back yesterday, they told me they had wiped it, reinstalled the OS and ran it nonstop with no issues. I get it home and found that they had installed Sierra on it, after I had repeatedly told them to leave it on El Capitan (as I don't know yet whether all my software will work on Sierra without making purchases, etc...)

Does anyone know if I can install El Capitan on a machine with Sierra? I've heard that you can only install newer Mac OS, not older versions?

Anyway, that probably means that the week of diagnostics that they did was on Sierra and not El Capitan.

That's the second time they did not do what they told me they were going to do, wasting more of my time....

You can install any supported Mac OS on any Mac in any order. Go to App Store and download a copy of El Capitan and create bootable USB drive with this terminal command:

sudo /Applications/Install\ OS\ X\ El Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB_NAME --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction

Replace USB_NAME with your actual USB drive name and be sure to format it before this command as GUID (Partition Map) and Mac OS Extended Journaled (File System).

When terminal command is finished, boot from that USB, erase Macintosh HD and Install El Capitan on that erased disk.
 

canhaz

macrumors 6502
Jan 17, 2012
310
145
In addition to the beach balls and GPU resets. A new related issued has emerged.

1/1/17 3:43:22.000 PM kernel[0]: stalling for detach from AMDPitcairnGraphicsAccelerator

No beachballs with this error. But GUI will become unresponsive for a few seconds. Then it recovers.
 

bax2003

Cancelled
Original poster
Dec 25, 2011
947
203
Reached limit od 10 files per message....
:D
 

Attachments

  • Kernel_2017-01-03-160840_Mac-Pro.gpuRestart.zip
    5.7 KB · Views: 177
  • WindowServer_2017-01-03-160534_Mac-Pro.crash.zip
    14 KB · Views: 143
  • WindowServer_2017-01-03-160857_Mac-Pro.crash.zip
    14.1 KB · Views: 213

axantas

macrumors 65816
Jun 29, 2015
1,000
1,407
Home
Since the update to 12.2 - 10 days ago now - i am running a shockingly stable MacPro. The crashes are gone. There are a "WindowServer_Mac-Pro.wakeups_resource" events logged, but that's it. No repair, no changes of whatever kind. Did they do some BIOS-Updates with 12.2 as well? in 12.1. i did have these nasty crashes - getting logged out as reported here. In Bootcamp/Windows 10 there are occasional graphics-driver crashes, but there are no more "notifications" on screen "...became unresponsive and was recovered". No changes in Windows-setup as well.
I am just a bit confused...

EDIT 26/01
12.2.1 still no crashes.
 
Last edited:

o_O

macrumors newbie
Dec 25, 2016
2
0
My system has increasingly become quite unstable and almost unusable; It seems almost everything hangs now, including Finder with regularity. I guess that I'm going to have to backup all my data and take it into Apple, as it's starting to get aggravating. Hanging is not the only issue either, as applications such as Final Cut Pro X are crashing often:

Crashed Thread: 124 Dispatch queue: _NSCGSWindowLocallyRenderedLayerSurfaceRenderingQueue

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called

Application Specific Signatures:
Graphics kernel error: 0xfffffffc
Ugh!...
 
Last edited:

bax2003

Cancelled
Original poster
Dec 25, 2011
947
203
Great fun....
 

Attachments

  • Kernel_2017-01-11-202452_Mac-Pro.gpuRestart.zip
    5.9 KB · Views: 167
  • Kernel_2017-01-11-202512_Mac-Pro.gpuRestart.zip
    5.6 KB · Views: 153
  • Kernel_2017-01-11-202513_Mac-Pro.gpuRestart.zip
    5.8 KB · Views: 177

Artificial

macrumors newbie
Jan 3, 2017
6
1
Hi everyone - I am new so apologies for any mistakes that might occur.

I wanted to see how everyone is getting on with this issue. I have a Mac Pro and like the initial poster had, I also had the same. My machine firstly had one card changed, than back it went for another card to be changed, then back again for the motherboard. After this, the machine still hung. It was eventually changed. I now, for the last few months, have a new replaced Mac Pro.

Since I first got the new replacement, there is a glitch that appears across the screen upon loading of the OS; only for a second or so before it continues to boot up. This I was told is an OS software problem: I am on sierra now and so I let that problem go for now. My latest problems is the hibernation of my mac will not awake the monitor, and at times, the monitor will flash as it tries to connect - think rave at midnight. It completely glitches, across the whole screen until I pull out the monitor and plug it back in. The computer works fine once I plug the monitor back in. Sometimes the monitor will just hibernate and not wake up, also without the manic effect flashing across the screen, and when I unplug the monitor, it will be fine.

I have added this part about the second replacement machine as I wonder if this all relates to the initial post. With my old machine that had the hung GPU, to regain control of the machine, I would have to pull out the monitor and then gain control to reboot. There seems to be a strange resemblance here in some respects with the GPU problem as I have to unplug the monitor to regain the monitor just as I did with the GPU.

I hope this is helpful.
 
Last edited:

bax2003

Cancelled
Original poster
Dec 25, 2011
947
203
Crashed while looping Flurry screensaver
 

Attachments

  • WindowServer_2017-01-14-000928_Mac-Pro.crash.zip
    14.1 KB · Views: 148
  • WindowServer_2017-01-18-175513_Mac-Pro.crash.zip
    14 KB · Views: 137
Last edited:

Infrared

macrumors 68000
Mar 28, 2007
1,715
65
Latest OS update supposedly fixes some sort of freezing issue.

As for me, I've not updated since the early GM version I had back in September and not one freeze since then.
 

bax2003

Cancelled
Original poster
Dec 25, 2011
947
203
10.12.3 helped a lot o_O
 

Attachments

  • WindowServer_2017-01-26-214422_Mac-Pro.crash.zip
    14 KB · Views: 169
  • Screen Shot 2017-01-26 at 22.04.01.png
    Screen Shot 2017-01-26 at 22.04.01.png
    116.8 KB · Views: 509

Idolum

macrumors member
Jun 10, 2016
91
43
Whenever a new OS X version is released I don't even check the features anymore but simply check this forum to see if the crashes are addressed. I am still on Mavericks without a single crash. Everything else is secondary. The last professional Mac I owned that I had to reboot was this bad boy:
Screen Shot 2017-01-26 at 10.13.11 PM.png
 

bax2003

Cancelled
Original poster
Dec 25, 2011
947
203
This is crazy, machine is very unstable doing nothing ! Flurry screensaver crashes WindowServer almost every day.
 

Attachments

  • WindowServer_2017-01-26-214422_Mac-Pro.crash.zip
    14 KB · Views: 199

iigsie

macrumors regular
Nov 17, 2007
141
116
I've had the windowserver error and gpu panics. I originally took to Applestore while still under warranty. They wanted to replace the GPU's but this was blocked by someone higher up. They ended up replacing the little ribbon cables, which did appear to stop the issue for a few months, strangely just until the warranty expired. They also insisted on wiping my computer.

It started happening again mid december last year, so I did some testing.

As others have said, the issue does not appear under Mavericks. Later versions have the issue, until 10.12.2, which so far (1 month) has not had a single gpu/windowserver issue. I've been able to put to sleep every night and it always wakes up.

So it seems like there can be several issues to the fault on D300 computers.
 

bax2003

Cancelled
Original poster
Dec 25, 2011
947
203
MP is going for a service "meeting" :(:confused:

I'll keep you posted....
 

Attachments

  • WindowServer_2017-01-27-203416_Mac-Pro.crash.zip
    14.1 KB · Views: 176
  • WindowServer_2017-01-28-204044_Mac-Pro.crash.zip
    14 KB · Views: 176
  • WindowServer_2017-01-29-221837_Mac-Pro.crash.zip
    14 KB · Views: 170
  • WindowServer_2017-01-30-061437_Mac-Pro.crash.zip
    14 KB · Views: 178

iigsie

macrumors regular
Nov 17, 2007
141
116
The
MP is going for a service "meeting" :(:confused:

I'll keep you posted....


The only logical conclusion is that there are multiple issues here.

I had the windowserver and GPU panic issues really bad - more than once a day. They told me the replaced the ribbon cables, which fixed the issue for about 6 months, then it came back until I updated to 10.2.2.

So some people have bad D300's, some people have bad ribbon cables and for the others it appears to be a driver issue.
 

teohyc

macrumors 6502a
May 24, 2007
551
474
My Mac Pro has be in and out of servicing for several times. Apple insisted on wanting to reproduced the problem and while my Mac Pro was at the service centre, it worked fine. Now my Mac Pro is back with me, I've had 2 freezes and 1 auto-restart.

Here's what I think.

Mac OS does not work well on this Mac Pro. It could be a hardware problem, but I doubt so, but since I'm not an engineer I can't confirm.

Even though my Mac Pro is still under warranty, I've given up ever getting a perfectly working Mac Pro already. Whenever it has freezes now, I will just force restart. Whether or not I send it in for repairs, the end result is the same.

There's no other way to put it except to say that this is a flawed product. What a shame.
 

bax2003

Cancelled
Original poster
Dec 25, 2011
947
203
I had a few situations in Windows (8.1 Pro) where Driver Stopped Responding....excatly what WindowServer LOG files reports....driver stoped responding for more than 10s.

I can˙t believe that this cannot be fixed because there are a lot of MP6.1s which work 100% stable.

My MP is still at Apple Authorised Provider. They called me to say that Apple send them all possible tests they ever run, and MP passed all of them with no problems at all. Now, because I sent them computer with tons of evidence, even with video clips where MP froze live with "About This Mac" dialog is open, they want to analyse this even further.
They can˙t escape the fact that there is something wrong.

Fortunately that MP is not my primary machine and I˙ll give them as much time as they need to fix it.
 

teohyc

macrumors 6502a
May 24, 2007
551
474
My MP is still at Apple Authorised Provider. They called me to say that Apple send them all possible tests they ever run, and MP passed all of them with no problems at all. Now, because I sent them computer with tons of evidence, even with video clips where MP froze live with "About This Mac" dialog is open, they want to analyse this even further.
They can˙t escape the fact that there is something wrong.

That's exactly the same situation I am in.

Just because their engineers cannot reproduce the problem does not mean there is no problem. It just means the engineers can't reproduce the problem.

Anyway, this is a flawed product. It has been years and they still can't fix it so I doubt they will be able to do anything going forward except to test and do further tests and waste their customer's time.
 

bax2003

Cancelled
Original poster
Dec 25, 2011
947
203
That's exactly the same situation I am in.

Just because their engineers cannot reproduce the problem does not mean there is no problem. It just means the engineers can't reproduce the problem.

Anyway, this is a flawed product. It has been years and they still can't fix it so I doubt they will be able to do anything going forward except to test and do further tests and waste their customer's time.

There is a flaw and now is too late do to any corrections, only thing they can do is what they are actually doing - replacing parts.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.