OS X Yosemite Keeps Crashing To Log-In Screen

I was always uploading my logs, perhaps this helped them to solve my cause of crashes. It would not make sense to complain now without sending any logs. At least it can be considered verified, that there are multiple reasons. May be they turned on some more sensitive panic mode in hope, they will solve all the problems they had in past and used to just pile up.

WAIT!! every Jrusso01 says worked for me. BUT.. I had no red text to highlight a problem. However I performed his Option 1 anyway (after backing up, of course) and it has worked. No more crashes!

Macbook Air 11" mid 2013 1.7g i7

Let's hope it lasts. For me all the numerous 'fixes' didn't (or only temporary) help. The bottomline is that Apple has to fix this.

Report all issues to Apple and keep the pressure on them. That's in this situation the only thing we can do.

A couple of humble suggestions:

-Always use a test-partition when updating. Monitor the forums. And keep working on your 'old' partition until you're absolutely sure that it is safe to update.

-Make a bootable backup (with SuperDuper or CCC) before you update. Time Machine is nice, but you don't want having to depend on your network/wifi/bluetooth or your keyboard/mouse (not) working. And you can actually continue on the 'old' partition, while testing the new one until you're satisfied.

I'm just glad that I have 10.10.3 only on a test-partition, because it's such a mess. I've never seen anything like this with Apple. Even Lion was better.

Crashes are back on OS X 10.10.4 (14E11f). Twice within 60 minutes after several months. Just closing the lid and opening it after 10-30 minutes. MBA shows black screen with mouse cursor, and when I close lid again after several minutes of waiting I get to login screen. After login, all applications are crashed again. Nothing connected, on wifi. Reported using Feedback Assistant and Bug Reporter both with sysdiagnose.

A lot of ppl have this problem. It is hard to find this thread on the net - my search first took me to lots of other sites. But after multiple searches, finally found this thread, and I am sure lots of others haven't found it yet.

I have a new Retina iMac, i7 4GHz, 295 AMD, 16GB RAM, and just started getting the crashes after running for one week of stability.

The only app I have open is Safari. What I did yesterday that may have started the crashes:

1. Started using Mac Mail. But now that app is not open and still crashing. Does a daemon run in the background anyway, even if app is not open?

2. Turned on screensaver to activate after one hour. Crashes seemed to correspond to this. Screen save now set to "Never" and crashes still occurring.

Running 10.10.3

Don't have other apps installed except firefox and ms office but I am not running any of them -- only Safari is open.

The logs do not show the crash - only show the shutdown with a reference to

nsurlsessiond[923]: SIGTERM received, shutting down.

Above that was some references to iCloud trying to communicate with the remote server. I have shutdown iCloud and testing - will post update on how that went.

I cannot believe an apple developer has not posted a link to a tool we can install to get better logging. Clearly this crash does not leave a fingerprint

(nothing in crash log, and nothing in All system Logs). We need a tool and we need apple jumping in here. Please!!

I tweeted to Apple and got a call from a support rep. Ran a special logging app and sent the files to Apple.

Bottom line, they know this exists and are working on it. I'd expect we hear something soon.

not too soon, I'm afraid... They are requesting those files since, at least, 10.1 via developers support, and maybe earlier versions of OS X

I've had long AppleCare chats with this several times now, but they never get back to me about it.

Apple Mail was "crashing to login" and even sometimes causing system freezes.

It wasn't until I realized it was Apple Mail causing this that I finally stopped using it and switched to Mailplane. Since then not a single system problem like that.

I've started over from scratch any number of times. Apple Mail - while very pretty - and has some nice features when it works - is just hopelessly unreliable. And AppleCare doesn't really help, unfortunately. 😟

I'd love to be able to use a true Mail client instead of a "browser wrap" client, but I can't find a good one yet.

doug

I didn't reinstalled it, no way that I have to do the same that I should do with other less credited OS. !!! 🙂

In my case, I think that it hangs on the login page when I have more users logged in and the computers goes to sleep mode. I have been user a single user for the last 2 days and a program called caffeine to don't let the computer go into sleep mode, and it had not hanged for the last 24 hours !...

It is very disappointing as I want to be able to switch user and let the computer go to sleep ! I'm considering to install Ubuntu in this beautiful hardware.

I was having this similar issue. While in login screen after starting or restarting my Mac I always have the login screen crashed and the Mac restart. What I found was that there was some sort of session stuck because of FileVault turned on.

So I disabled FileVault then logged in again to all accounts. One of those accounts started the process as if it was the first time I was logging in, setting up iCloud and all the first time process we all know. After that I rebooted a couple of times and then re activated FileVault

The issue has gone. Maybe this helps.

I am active on this thread since OS10.10.1, installed 10.10.4 yesterday. In my case (MacBook Air 13", middle of 2013; 1,7 GHz Intel Core i7; 8 GB 1600 MHz DDR3; Intel HD Graphics 5000 1536 MB) the phenomenon (crashing to login screen either while working or during sleep mode) ended after installation of 10.10.3.

Nonetheless, the accompanying problem of fan running at top speed was still there. Fan noise was always a predictor of crashing to login screen within the next hour of operation. When monitoring cpu activity, the culprit appeared to be Apple Mail; it grabbed almost all cpu activity. Quitting Mail quieted down the fan - but not always. A process by the name of

Process: iconservicesd [62]

Path: /System/Library/CoreServices/iconservicesd

Load Address: 0x10ea62000

Identifier: iconservicesd

sometimes took over. I killed it and it didn't behave like this ever since. No prognosis so far if this is just correlation or causal. Hopes are that 10.10.4 cured everything...

Our different experiences are interesting. In your case, 10.10.3 fixed the crashing to login screen problem. In my case, that particular problem began with 10.10.3!

doug

Just had this problem for the first time today. I'm on an iMac 5K i7, 16GB Memory and 2GB AMD Radeon.

It just went off, threw me back to the login screen where I had to put my password in again. I put the password in and all my programs re-loaded.

I was just replying to an SMS via iMessage when it happened, I ran a system diagnostic in system monitor and it says it was WindowServer that caused the crash.

Never had this problem before, had the iMac pretty much since they came out in Late 2014. I'm on OS X Yosemite 10.10.4.

Do you have Filevault?

On Tuesday, July 7, 2015, Apple Support Communities Updates <

Ive got the same problem and has since the beginning of yosemite.Though its weird, because it doesnt happen on a daily basis. It could occure constantly one day then there is nothing for a month. And when its happening im either just being kicked out to the log-in screen or i will experience som graphical glitches and i have to reboot. The graphic problems usually appears when im using vlc, quick time and all the time when im playing games via steam. But as i said, its not all the time either. I could watch ten movies and nothing happens. Then one day i can't get trough ten minutes of one. Its getting really frustrating.

Im running 10.10.4 since yesterday and i guess it got a little bit worse since then. Though its the same problems as always.

This happened yesterday like 5 times combined by getting kicked out to log-in screen another couple of times:(