mac pro late 2013 freezes with spinning wheel

Just what is connected to the computer at home?

I got very sad by reading your experience with the Mac Pro. Today I wanted to order the 6-core (got a good offer) but after reading this thread and many others with similar display problems (some guy has replaced his MP 5 times!), I decided to discard my order. Thanks to Apple for the bad support around this big problem and the stupid secrecy about further plans with the Mac Pro. This is not customer friendly! 😕

Same problem reported to Mauro, I've contacted also Apple Care at phone, but unfortunately didn't help me.

I'm very frustrated of this situation, and sincerely I don't understand because Apple doesn't do anything for fix this problem that afflict many Pro Users.

I've tried also to reset PRAM, and SMC, but nothing.

I've tried to format Mac, and Re-install clean OS (Yosemite)

In this days I've also notated, cleaning permission this strange thing.

--quote--

Permessi diversi in “private/var/db/GPURestartReporter”; dovrebbero essere drwxr-xr-x , ma sono drwxrwx--- .“private/var/db/GPURestartReporter” riparato

--end quote-

Any suggestion?

Max

I had a similar problem as OP on my Mac Pro (late 2013) except that the problem did not present itself until I updated to Mac OS 10.11.1. On my system, I have a single 4K monitor (Crossover 404K Final) that is connected via a Thunderbolt/Display Port connection. Previously, this monitor worked fine on 10.10.5 and 10.11.0, but soon after updating to 10.11.1, I encountered instability in the monitor with jerkiness and sometimes a lockup. I was able to see in my console error listing that I was getting multiple reports of:

windowserver: surface testing disallowed updates for xx sequential attempts

Normally, I run the 4K display with a scaled display setting to make it easier to read text on my different apps. After some experimentation, I found that if I set for a non-scaled default display, the problem did not seem to occur, but if I set for a scaled display, the problem would re-occur within a couple hours.

I read through a number of other posts here and found the following:

WindowServer crashing in El Capitan

I noticed the post by Alliante said by turning off the Mission Control "Displays have separate spaces" option, he had good results, so I tried doing the same thing and then turning my scaling back on. That was 3 days ago, and so far, have not encountered any other problems. I'm keeping my fingers crossed that the problem will not re-occur now and maybe this trick can help others, so posting here. If I run into other problems later, I will repost here.

Good Luck!

Paul

Well, even though this is the 3rd day without encountering any display problems, I spoke too soon!!! My problem is back. I was viewing some web pages on Safari tonight when the screen jerkiness reoccurred. I then looked at the console log and saw a problem again. See the small section of console error log below with Surface Testing messages:

---

11/1/15 10:02:45.856 PM quicklookd[5104]: Error returned from iconservicesagent: (null)

11/1/15 10:02:45.857 PM iconservicesagent[3403]: -[ISGenerateImageOp generateImageWithCompletion:] Failed to composit image for descriptor <ISBindingImageDescriptor: 0x7f904d006850>.

11/1/15 10:02:45.857 PM quicklookd[5104]: Error returned from iconservicesagent: (null)

11/1/15 10:02:48.142 PM ACCFinderSync[5322]: host connection <NSXPCConnection: 0x7fb008f34c20> connection from pid 4782 invalidated

11/1/15 10:03:44.844 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:03:44.985 PM WindowServer[3178]: Surface test allowed updates after 40 attempts (160 ms)

11/1/15 10:03:45.255 PM WindowServer[3178]: _CGXRemoveWindowFromWindowMovementGroup: window 0x54b is not attached to window 0x54d

11/1/15 10:03:58.387 PM WindowServer[3178]: _CGXRemoveWindowFromWindowMovementGroup: window 0x54b is not attached to window 0x54d

11/1/15 10:04:34.135 PM WindowServer[3178]: _CGXRemoveWindowFromWindowMovementGroup: window 0x54b is not attached to window 0x54d

11/1/15 10:04:34.602 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:04:34.934 PM WindowServer[3178]: Surface test allowed updates after 82 attempts (328 ms)

11/1/15 10:04:35.036 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:04:35.055 PM WindowServer[3178]: Surface test allowed updates after 12 attempts (48 ms)

11/1/15 10:04:35.135 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:04:35.435 PM WindowServer[3178]: Surface test allowed updates after 75 attempts (300 ms)

11/1/15 10:04:35.670 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:04:35.931 PM WindowServer[3178]: Surface test allowed updates after 66 attempts (264 ms)

11/1/15 10:04:36.002 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:04:36.217 PM WindowServer[3178]: Surface test allowed updates after 56 attempts (224 ms)

11/1/15 10:04:37.331 PM WindowServer[3178]: _CGXRemoveWindowFromWindowMovementGroup: window 0x54b is not attached to window 0x54d

11/1/15 10:04:37.552 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:04:37.664 PM WindowServer[3178]: Surface test allowed updates after 33 attempts (132 ms)

11/1/15 10:04:38.137 PM WindowServer[3178]: _CGXRemoveWindowFromWindowMovementGroup: window 0x54b is not attached to window 0x54d

11/1/15 10:04:38.419 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:04:38.443 PM WindowServer[3178]: Surface test allowed updates after 14 attempts (56 ms)

11/1/15 10:04:38.503 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:04:38.948 PM WindowServer[3178]: Surface test allowed updates after 107 attempts (428 ms)

11/1/15 10:04:40.354 PM WindowServer[3178]: _CGXRemoveWindowFromWindowMovementGroup: window 0x54b is not attached to window 0x54d

11/1/15 10:04:44.155 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:04:44.475 PM WindowServer[3178]: Surface test allowed updates after 79 attempts (316 ms)

11/1/15 10:04:45.324 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:04:45.479 PM WindowServer[3178]: Surface test allowed updates after 42 attempts (168 ms)

11/1/15 10:04:48.172 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:04:48.502 PM WindowServer[3178]: Surface test allowed updates after 82 attempts (328 ms)

11/1/15 10:04:57.526 PM Console[5323]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable

11/1/15 10:04:57.784 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:04:58.042 PM WindowServer[3178]: Surface test allowed updates after 65 attempts (260 ms)

11/1/15 10:04:58.167 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:04:58.545 PM WindowServer[3178]: Surface test allowed updates after 91 attempts (364 ms)

11/1/15 10:05:25.813 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:05:25.841 PM WindowServer[3178]: Surface test allowed updates after 15 attempts (60 ms)

11/1/15 10:05:25.899 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:05:26.010 PM WindowServer[3178]: Surface test allowed updates after 33 attempts (132 ms)

11/1/15 10:05:26.080 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:05:26.194 PM WindowServer[3178]: Surface test allowed updates after 34 attempts (136 ms)

11/1/15 10:05:26.195 PM WindowServer[3178]: _CGXRemoveWindowFromWindowMovementGroup: window 0x54b is not attached to window 0x54d

11/1/15 10:05:26.248 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:05:26.702 PM WindowServer[3178]: Surface test allowed updates after 108 attempts (432 ms)

11/1/15 10:05:43.648 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:05:43.789 PM WindowServer[3178]: Surface test allowed updates after 40 attempts (160 ms)

11/1/15 10:05:43.999 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:05:44.158 PM WindowServer[3178]: Surface test allowed updates after 44 attempts (176 ms)

11/1/15 10:05:51.722 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:05:51.838 PM WindowServer[3178]: Surface test allowed updates after 34 attempts (136 ms)

11/1/15 10:05:51.906 PM WindowServer[3178]: Surface testing disallowed updates for 10 sequential attempts...

11/1/15 10:05:52.343 PM WindowServer[3178]: Surface test allowed updates after 105 attempts (420 ms)

11/1/15 10:06:01.861 PM WindowServer[3178]: MPServiceForDisplayDevice: Invalid device alias (0)

11/1/15 10:06:01.861 PM WindowServer[3178]: Display 0x13c235f5: GL mask 0x20; bounds (0, 0)[3200 x 1800], 138 modes available

Main, Active, on-line, enabled, boot, OpenGL-accel, Vendor e4f, Model 8e1, S/N db0, Unit 5, Rotation 0

UUID 0xbb2cc9937ac04ddd455dbce4db0ac314, ColorSpace { 148653395 }

11/1/15 10:06:01.861 PM WindowServer[3178]: GLCompositor: GL renderer id 0x01021c02, GL mask 0x0000007f, accelerator 0x0000247f, unit 0, caps QEX|MIPMAP, vram 2048 MB

texture max 16384, viewport max {16384, 16384}, extensions NPOT|GLSL|FLOAT

11/1/15 10:06:01.861 PM WindowServer[3178]: Display 0x003f0042: GL mask 0x40; bounds (4224, 0)[1 x 1], 2 modes available

off-line, enabled, OpenGL-accel, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 6, Rotation 0

UUID 0xffffffffffffffffffffffffffffffff

11/1/15 10:06:01.861 PM WindowServer[3178]: GLCompositor: GL renderer id 0x01021c02, GL mask 0x0000007f, accelerator 0x0000247f, unit 0, caps QEX|MIPMAP, vram 2048 MB

texture max 16384, viewport max {16384, 16384}, extensions NPOT|GLSL|FLOAT

11/1/15 10:06:01.861 PM WindowServer[3178]: Display 0x003f0043: GL mask 0x80; bounds (4225, 0)[1 x 1], 1 modes available

---

Once I turned off Display Scaling in Display control panel, the problem went away. I then immediately turned scaling back on and now not seeing any problems. So I guess if problem only occurs every 2-3 days, I can do what I just did tonight to clear up. Hopefully, this problem will be corrected in 10.11.2 update. 😟

Will let you know here if any new revelations.

Thx.

Paul

I have a Mac Pro late 2013 with a Dell UP2414Q 4k Monitor and I am having the spinning wheel problem from the very beginning two years ago until today, several software updates didn't change anything. I'm pretty ****** about it in the meantime!

Are you guys having this problem also with non-4k monitors?

Hi There,

I have the same problem with 3 early 2013 Mac Pro's from a batch of 12 ordered. I have the quad core version with D300 video cards.

I am also trying for months to solve this randomly freezes. It is the GUI which freezes and I can move the move but without response.

I can ssh to the machine and do anything I want without problems, also do a reboot.

After contacting the Genius bar and first try to repair Apple replaced the MLB, but it didn't help still the machine will freeze.

The problem can be reproduced by setting the Power Options to never sleep and start the flurry screensaver and let it run, my Mac Pro's are freezing within a timespan from 20 mins to 2 days.

I think there is a problem with the Graphics cards, because only the GUI is freezing but the system will react without problems using the terminal.

But this said in our case the problem wasn't noticed until Keynote forced us the install OSX 10.10

I hope Apple will finally admit there is problem with the Early 2013 Mac Pro and find a solution for it. Until now the Apple test tools can't find anything yet.

I wonder what we users are supposed to do about this issue? Apple isn't responding at all ...

Anyone with contacts to media? I could try to bring the story to heise.de ... a german IT-magazine.

It would be helpful if anyone could tell it to an english magazine as well!

Hi,

I confirm that I have the same problem again I've tried also to format, reset PRAM, Safe mode, reinstall OS X but.. nothing.

I tried also to check the console, when problem appears.

I confirm that It's always the same task...

19/11/15 16:24:47,186 WindowServer[158]: Surface testing disallowed updates for 10 sequential attempts...

Note : Following you suggestion, I tried today to contact a famous forum about Apple in Italy for try to making the problem at attention of Apple.

'What you are supposed to do about it' is ignore the general problem, and press your individual case using Apple's existing solutions for yourself alone.

Present yourself and your failing equipment at an appointment at the genius bar, and if the problem is not solved during your visit, continue to press them until it is escalated and solved. Do not walk away from a 'no fault found' visit when you can reproduce a problem in all-Apple software. Insist that they swap parts until the problem is fixed, or refer your case to Engineering. Ask that the store manager be involved.

If you have access to National Account Tech Support, Education Tech Support, or Developer Tech Support, you should also press your case with them.

Using your energy to pursue a lawsuit will make some lawyers very rich, and will not move you any closer to a solution. You want Apple to apply Engineering resources to solve this problem, not Legal resources to defend itself.

http://forums.macrumors.com/threads/mac-pro-late-2013-gpu-driver-issues.1860297/ page-25

Leo laporte in the tech guy on 14 nov- episode 1237 around 1:26 was replying to a caller and said the new mac pros are lemons. He said the he has 2 new mac pros and the spinning beach balls happens to him as well. His theory is that it has to do with the usb.

This machine took too much of my productivity time. Im at the last stage of grief, acceptance. They reply to my bug report at the start of the year and said its a duplicate of another. Apple also called me to diagnose the machine. And then nothing. Ive given up and just saving regularly and restarting. Working in aftereffects and cinema4d is really frustrating because of the crashes.

Bottom line is that this machine is beautiful to look at and verging on unusable. Its really disappointing, once the workhorse of apple machines, is now just a poorly engineered piece of sculpture. Its an unreliable computer, it is what it is. Apple may not be keen or unable to fix it. Who knows, they are not acknowledging the problem