Mac Pro keeps logging out since El Capitan

Upgraded my Mac Pro to El Capitan, all went well. I logged in, then logged into iCloud and that also went well. But then it crashed with a kernel panic, restarted OK.

It now is running OK but after a few minutes it will log me off and back to the password prompt. Very frustrating and not able to work with it in such very short windows of time.


Anybody else seeing this?


Paul.

Mac Pro, OS X El Capitan (10.11)

Posted on Oct 1, 2015 4:29 AM

Reply
393 replies

Oct 6, 2015 4:34 AM in response to LookToWindward

Spoke too soon! I'm a developer and now when I try and compile in XCode 7.0.1, 9 times out of 10 I get the Log Out Crash if on a monitor on one Graphics Card, but if I move that window to a monitor on the other card, then it compiles ok.


I wonder if Apple is actively trying to fix this? It doesn't seem limited to older Mac Pro's, I've seen reports of Brand Mac Book Pro's with the problem and not being able to use a second display on that machine is a real problem.....

Oct 6, 2015 7:18 AM in response to LookToWindward

NVIDIA has published a new update for my card today 6 October. I installed it just now and re-connected my third screen to the second card. After ten minutes my system (early-2009 Mac Pro, 2 x GeForce GT 120 cards, 3 x displays) is still up and running. We shall see.


Edit: 20 minutes still going strong. I have tested it by moving videos across the three screens, opening lots of applications and switching rapidly between them, that sort of thing, and so far all is well.

Oct 6, 2015 7:23 AM in response to Paul Hodson3

Gentlemen,

I include part, of a system log here; it shows that the crash happens in the module "WindowsServer", in thread 0 which handles and uses the graphics drivers. It is interesting that apple uses "Tesla" Graphics drivers - I'm in doubt that the good oulde 120 card is compatible with Tesla drivers. I'm using a Mac Pro early 2009 with two 120 cards and two 23" Apple Displays connected via Displayport.


Process: WindowServer [381]

Path: /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/WindowSe rver

Identifier: WindowServer

Version: 1

Code Type: X86-64 (Native)

Parent Process: launchd [1]

Responsible: WindowServer [381]

User ID: 88



Date/Time: 2015-10-01 20:09:52.907 +0200

OS Version: Mac OS X 10.11 (15A284)

Report Version: 11

Anonymous UUID: 4D007D2A-71CB-A93C-4FF3-23A453AA5FC9





Time Awake Since Boot: 11000 seconds



System Integrity Protection: enabled



Crashed Thread: 0 Dispatch queue: com.apple.main-thread



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: 0x00000002





Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 libsystem_kernel.dylib 0x00007fff9364c0ae __pthread_kill + 10

1 libsystem_pthread.dylib 0x00007fff8d64f500 pthread_kill + 90

2 libsystem_c.dylib 0x00007fff8891037b abort + 129

3 libGPUSupport.dylib 0x00007fff88ba6907 gpusKillClient + 83

4 com.apple.GeForceTeslaGLDriver 0x00001234402f86e0 0x123440000000 + 3114720

5 com.apple.GeForceTeslaGLDriver 0x00001234402f8403 0x123440000000 + 3113987

6 com.apple.CoreGraphics 0x00007fff96e5b640 CGXGLAccelFinish + 89

7 com.apple.CoreGraphics 0x00007fff96db11be CGXReleaseDisplayDeviceSurface + 227

8 com.apple.CoreGraphics 0x00007fff96e1c52e CGXUpdateDisplay + 14915

9 com.apple.CoreGraphics 0x00007fff96e20c6c update_display_callback + 212

10 com.apple.CoreGraphics 0x00007fff96b94806 run_timer_pass + 547

11 com.apple.CoreGraphics 0x00007fff96e0ee16 CGXRunOneServicesPass + 228

12 com.apple.CoreGraphics 0x00007fff96e111b7 CGXServer + 7174

13 WindowServer 0x000000010322ff7e 0x10322f000 + 3966

14 libdyld.dylib 0x00007fff9a3c45ad start + 1

Oct 6, 2015 7:37 AM in response to JCrebbin

i have this problem with a 2009 MacBook Pro; no monitors or special cards involved. The only way to get it to work so far has been to delete ~/Library/Preferences/* via ssh. Then I can login and have a stable desktop; this only lasts for the current boot however; reboot in safe mode then has the same problem, so some incompatible preference gets set causing WindowServer to crash.

Oct 6, 2015 8:19 AM in response to Paul Hodson3

I've had the same problem with a 2009 Mac Pro running 2 original video cards and 2 monitors.

Following the advice to disable separate spaces in Mission Control has stopped the issue for me.

One of my 2 monitors is now dark and not usable, but this is better than the constant return to the log in prompts.


Hope a fix comes sooner rather than later.

Oct 6, 2015 9:14 AM in response to Neliger

Interesting. I've using Firefox and Safari the whole time. Although I've had it crash when doing something in another App (XCode, Mail, Finder, Grab). It usually happens when doing something on a Monitor connected to one Graphics card and then moving to another Graphics Card, e.g. double-clicking a file in a Finder window which opens in a Window on a Monitor on the other Graphics card. I'm not sure if FF was running of every single occasion but the majority of the time is has been running but not the Active App.


Since installing the NVIDIA update WebDriver-346.03.02f01.pkg, the problem still occurs but not so frequently. I then installed the update of today (06Oct15) WebDriver-346.03.02f02 and it seems to now occur more frequently then with f01 but not as frequently as when I use the Mac OS X drivers. However when f02 does crash, after logging on again all the windows start to completely fragment with rectangles of different size appearing all over the place at random and this forces a restart.


I've not tried not using FireFox at all, but I'm not going to use it from now on and see if that makes a difference.


One thing that aggravates the situation is that when it does crash, on restart Mac OS now loads app the apps and windows from the previous crash which on a few occasions has led to it crashing again. Is there any way to turn off this brain-dead feature? Who ever thought it was a good idea to restore state after a crash without at least asking the User if they want to do that needs to be locked up for life.


Cheers

Dave

Oct 6, 2015 1:04 PM in response to Paul Hodson3

I have been following this thread since I upgraded to El Capitan on my Mac Pro as I was experiencing random log outs and display distortions. I run 4 Mac displays on two video cards, an ATI Radeon and the other an Nvidia. I installed the updated Nvidia drivers and the Nvidia Cuda suggested earlier on the thread but none solved the issue for me. I ended up swapping out the Nvidia card for another ATI Radeon card (now running 2 ATI cards) and everything has been running smoothly since then. I have tried to replicate the issue in every possible way that I can think of and so far so good. This may not be a true solution for everyone because not everyone have multiple ATI cards laying around (hoarding) but if you do have some spare ATI cards, give it a go. I will report back if the issue occurs on my current set up.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Mac Pro keeps logging out since El Capitan

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.