Mac Pro late 2013 is experiencing frequent crashing.

My late 2013 model Mac Pro has been crashing quite often lately. About once every day, and sometimes more often than that. This has been occurring even when only running Safari (but not limited to just Safari). Basically everything completely locks up, with the exception of the mouse cursor. The only way to fix it, is to force shut down the machine and reboot it. It seems completely random when it occurs, so I really have no idea what could be triggering it. I've run Apple Diagnostics, and it didn't detect any issues.


Mac Pro (Late 2013)

Mac OSX Yosemite 10.10.3

Processor: 3.7 GHz Quad-Core Intel Xeon E5

Memory: 12 GB 1866 MHz DDR3 ECC

Graphics: AMD FirePro D300 2048 MB

1TB Flash Storage (634.71 GB available)

Posted on May 8, 2015 4:16 PM

Reply
3 replies

May 8, 2015 5:54 PM in response to MARl0

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

Step 1

For this step, the title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES All Messages

from the log list on the left. If you don't see that list, select

View Show Log List

from the menu bar at the top of the screen.

In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter "BOOT_TIME" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Select the BOOT_TIME log message that corresponds to the last boot time when you had the problem. Now clear the search box to reveal all messages. Select the ones logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.

If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.

When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Some private information, such as your name, may appear in the log. Anonymize before posting.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Step 2

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION System Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select

View Show Log List

from the menu bar.

There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

When you post the log extract or the crash report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

May 11, 2015 2:10 AM in response to Linc Davis

Hi. I have had the exact same problem for a couple of months but not had a crash for a few days now but when I do I will post the crash reports.


I am wondering if it is a graphics card problem? In the 1st few months I had the mac I had a couple of warning that popped up to the effect of "A Graphics card problem has been detected - performance may be affected". This error has not appeared for a few months now.


The issue I have now (that I have a feeling is related) is that Indesign CC (latest version) is very unresponsive. I get the beachball for 5 seconds after any action - click on text box = beach ball, pan round screen = beachball.


I have tried to boot into 'Apple Diagnostics' by starting up and pressing 'D' but all I get is black screen and working cursor.


Note: I am running dual monitors also:

Apple Thunderbolt Display (27-inch)

Apple Cinema HD Display (23-inch) with apple thunderbolt adapter


Mac Pro (Late 2013)

Mac OSX Yosemite 10.10.3

Processor: 3.7 GHz Quad-Core Intel Xeon E5

Memory: 32 GB 1866 MHz DDR3 ECC

Graphics: AMD FirePro D300 2048 MB

1TB Flash Storage (600 GB available)

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 late 2013 is experiencing frequent crashing.

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