Previous shutdown cause: -62

I'm having the same issue on my MacBook Pro Mid-2010. All symptoms sound 100% the same. I also see shutdown cause as -62. Sometimes when it restarts it presents a kernel panic "press any key" page then begins to restart, but then reboots again, so there's no panic log. I've tried multiple times resetting both PRAM and SMC to no avail. I was using the Yosemite beta, but the problem didn't surface until the last beta before the final release. I have since upgraded to the release version but I'm still having the same problem. Memtest and Apple Hardware Test both brought up no problems. I've also had it restart a couple of times with 3 loud beeps in succession which seems to usually indicate a memory problem. I doubt it really is a memory or memory slot issue, though, because I got a new main logic board and memory less than a year ago from Apple due to a chronic GPU kernel panic brought forth by Mavericks.

I updated to the 10.10.1 beta today and it happened again since then. No fix here.

As of today, I'm still having this very same problem on my MacBook Pro Retina Mid 2012, Yosemite 10.10.2. It occurs once or twice everyday, and it's extremely frustrating :-(

I suspect this is caused by some display driver bug or such. Sigh...

I have the same issue, macbook freezes and I have to shut it down. When it reboots, I get a red screen, then it reboots again several times. Finally I can login. But 5-6 hours later it happens again.

ANY RESPITE ? I've been facing this same issue and its driving me mad ? did a clean install help ? I've tried it and it doesn't help me. Please Reply. Thanks.

I'm experiencing the same issue on a 2010 MB Pro w/ 8GB RAM and 2.66GHz i7. I *think* that it was happening before I upgraded to Yosemite, but not often enough to be concerning. Now it happens once every couple of days.

My symptoms are as follows: I'll be working away on something, then the screen goes black for a few seconds before I hear the disk restart, and then the gray panic screen comes up. There is never a panic log. When I inspect /var/log/system.log, I find

localhost kernel[0]: Previous shutdown cause: -62

I don't see anything especially sinister in the logs leading up to that. Here are a few lines just before where I think it rebooted:

May 2 16:14:45 MacBook-Pro.local SophosSXLD[360]: 20150502 231445.735 P 360 T 2203 ------ 2 - Warning: EARLY TIMEOUT: dns context 0 has 13669 ms before it should time out\n

May 2 16:14:46 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD[47630]): Service could not initialize: Unable to set current working directory. error=2, path=/Applications/SafeConnect.app/Contents/MacOS/: 14D136: xpcproxy + 12761 [1285][E34BADE4-4125-3886-AA5B-08E47BD0E884]: 0x2

May 2 16:14:46 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD): Service only ran for 0 seconds. Pushing respawn out by 2 seconds.

May 2 16:14:48 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD[47631]): Service could not initialize: Unable to set current working directory. error=2, path=/Applications/SafeConnect.app/Contents/MacOS/: 14D136: xpcproxy + 12761 [1285][E34BADE4-4125-3886-AA5B-08E47BD0E884]: 0x2

May 2 16:14:48 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD): Service only ran for 0 seconds. Pushing respawn out by 2 seconds.

May 2 16:14:50 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD[47632]): Service could not initialize: Unable to set current working directory. error=2, path=/Applications/SafeConnect.app/Contents/MacOS/: 14D136: xpcproxy + 12761 [1285][E34BADE4-4125-3886-AA5B-08E47BD0E884]: 0x2

May 2 16:14:50 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD): Service only ran for 0 seconds. Pushing respawn out by 2 seconds.

May 2 16:14:52 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD[47633]): Service could not initialize: Unable to set current working directory. error=2, path=/Applications/SafeConnect.app/Contents/MacOS/: 14D136: xpcproxy + 12761 [1285][E34BADE4-4125-3886-AA5B-08E47BD0E884]: 0x2

May 2 16:14:52 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD): Service only ran for 0 seconds. Pushing respawn out by 2 seconds.

May 2 16:14:54 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD[47634]): Service could not initialize: Unable to set current working directory. error=2, path=/Applications/SafeConnect.app/Contents/MacOS/: 14D136: xpcproxy + 12761 [1285][E34BADE4-4125-3886-AA5B-08E47BD0E884]: 0x2

May 2 16:14:54 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD): Service only ran for 0 seconds. Pushing respawn out by 2 seconds.

May 2 16:14:56 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD[47635]): Service could not initialize: Unable to set current working directory. error=2, path=/Applications/SafeConnect.app/Contents/MacOS/: 14D136: xpcproxy + 12761 [1285][E34BADE4-4125-3886-AA5B-08E47BD0E884]: 0x2

May 2 16:14:56 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD): Service only ran for 0 seconds. Pushing respawn out by 2 seconds.

May 2 16:14:58 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD[47636]): Service could not initialize: Unable to set current working directory. error=2, path=/Applications/SafeConnect.app/Contents/MacOS/: 14D136: xpcproxy + 12761 [1285][E34BADE4-4125-3886-AA5B-08E47BD0E884]: 0x2

May 2 16:14:58 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD): Service only ran for 0 seconds. Pushing respawn out by 2 seconds.

May 2 16:15:00 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD[47637]): Service could not initialize: Unable to set current working directory. error=2, path=/Applications/SafeConnect.app/Contents/MacOS/: 14D136: xpcproxy + 12761 [1285][E34BADE4-4125-3886-AA5B-08E47BD0E884]: 0x2

May 2 16:15:00 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD): Service only ran for 0 seconds. Pushing respawn out by 2 seconds.

May 2 16:15:02 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD[47638]): Service could not initialize: Unable to set current working directory. error=2, path=/Applications/SafeConnect.app/Contents/MacOS/: 14D136: xpcproxy + 12761 [1285][E34BADE4-4125-3886-AA5B-08E47BD0E884]: 0x2

May 2 16:15:02 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD): Service only ran for 0 seconds. Pushing respawn out by 2 seconds.

May 2 16:15:04 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD[47639]): Service could not initialize: Unable to set current working directory. error=2, path=/Applications/SafeConnect.app/Contents/MacOS/: 14D136: xpcproxy + 12761 [1285][E34BADE4-4125-3886-AA5B-08E47BD0E884]: 0x2

May 2 16:15:04 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD): Service only ran for 0 seconds. Pushing respawn out by 2 seconds.

May 2 16:15:06 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD[47640]): Service could not initialize: Unable to set current working directory. error=2, path=/Applications/SafeConnect.app/Contents/MacOS/: 14D136: xpcproxy + 12761 [1285][E34BADE4-4125-3886-AA5B-08E47BD0E884]: 0x2

May 2 16:15:06 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD): Service only ran for 0 seconds. Pushing respawn out by 2 seconds.

May 2 16:15:08 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD[47641]): Service could not initialize: Unable to set current working directory. error=2, path=/Applications/SafeConnect.app/Contents/MacOS/: 14D136: xpcproxy + 12761 [1285][E34BADE4-4125-3886-AA5B-08E47BD0E884]: 0x2

May 2 16:15:08 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD): Service only ran for 0 seconds. Pushing respawn out by 2 seconds.

May 2 16:15:10 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD[47642]): Service could not initialize: Unable to set current working directory. error=2, path=/Applications/SafeConnect.app/Contents/MacOS/: 14D136: xpcproxy + 12761 [1285][E34BADE4-4125-3886-AA5B-08E47BD0E884]: 0x2

May 2 16:15:10 MacBook-Pro com.apple.xpc.launchd[1] (scManagerD): Service only ran for 0 seconds. Pushing respawn out by 2 seconds.

May 2 16:15:56 localhost bootlog[0]: BOOT_TIME 1430608556 0

Hope that someone figures this out soon.

Hey nimbl,

Any solution yet ?

Anyone found any solution to this?

If this indicates:

MacBook-Pro.local SophosSXLD[360]:

... that you are running Sophos anti-Virus, that is exactly the cause of the problem. Remove that junk (which can't find anything that will hurt your Mac) and you problems will be over.

I have basically the same issue with my Macbook Pro Mid 2010, 2.4 intel core duo, 8gb ddr3, NVIDIA GeForce 32M 256mb and I'm still running Mac OS Lion 10.7.5. This just started about 6 months ago. I would have to guess it's a hardware issue.