Mac Pro freezes w/Yosemite

Question

Level 1

0 points

Mac Pro freezes w/Yosemite

I'm currently using a Late 2013 Mac Pro, 3.7 GHz Quad-Core Intel Xeon processor with 12 GB 1866 MHz DDR3 memory. Since installing v. 10.10.4 of OS X Yosemite my computer has frozen at least twice a day each day I use it, freezes which always require a hard reboot (Command + Alt + Esc does nothing in this phase).

Typically this problem happens when I play videos or music, but it has also happened with other applications. When it occurs, the screen, mouse, and keyboard becomes unresponsive BUT interestingly enough any sound that was previously playing continues. I've tried re-installing the Yosemite version, verifying and repairing my disc, and removing my external hard drive and non-essential USB connections from the computer, but nothing so far has worked. Any thoughts?

Mac Pro (Late 2013), OS X Yosemite (10.10.4)

Posted on Jul 30, 2015 8:44 PM

Reply

Answer 1

Linc Davis

Level 10

209,649 points

Jul 31, 2015 6:47 AM in response to wtsmith

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. 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.

Reply

Answer 2

CT

Level 7

24,113 points

Jul 31, 2015 6:58 AM in response to wtsmith

TLDR

EtreCheck

Reply

Answer 3

wtsmith Author

Level 1

0 points

Jul 31, 2015 4:34 PM in response to Linc Davis

Requested System Log Queries:

7/31/15 12:35:13.000 AM kernel[0]: USBF: 7022.136 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 2 of Hub at 0x20300000)

7/31/15 12:35:14.000 AM kernel[0]: USBF: 7022.437 The IOUSBFamily was not able to enumerate a device.

7/31/15 12:35:14.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:35:44.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:35:56.820 AM GoogleSoftwareUpdateAgent[569]: 2015-07-31 00:35:56.820 GoogleSoftwareUpdateAgent[569/0xb0219000] [lvl=3] -[KSAgentApp(KeystoneThread) runKeystonesInThreadWithArg:] Failed to connect to system engine.

7/31/15 12:36:00.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:36:03.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:36:09.000 AM kernel[0]: Google Chrome He (map: 0xffffff80320151e0) triggered DYLD shared region unnest for map: 0xffffff80320151e0, region 0x7fff8ce00000->0x7fff8d000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

7/31/15 12:36:16.000 AM kernel[0]: Google Chrome He (map: 0xffffff802d9ee3c0) triggered DYLD shared region unnest for map: 0xffffff802d9ee3c0, region 0x7fff8ce00000->0x7fff8d000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

7/31/15 12:36:17.000 AM kernel[0]: Google Chrome He (map: 0xffffff802bfaf4b0) triggered DYLD shared region unnest for map: 0xffffff802bfaf4b0, region 0x7fff8ce00000->0x7fff8d000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

7/31/15 12:36:19.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:36:25.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:36:25.000 AM kernel[0]: Google Chrome He (map: 0xffffff802efe8c30) triggered DYLD shared region unnest for map: 0xffffff802efe8c30, region 0x7fff8ce00000->0x7fff8d000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

7/31/15 12:36:31.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:36:52.000 AM kernel[0]: [0xffffff803288bc00](1)/(5) Device not responding

7/31/15 12:36:52.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:37:49.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:38:11.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:38:24.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:38:33.000 AM kernel[0]: [0xffffff803d907200](1)/(5) Device not responding

7/31/15 12:38:33.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:38:46.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:38:53.000 AM kernel[0]: Google Chrome He (map: 0xffffff802d9ee3c0) triggered DYLD shared region unnest for map: 0xffffff802d9ee3c0, region 0x7fff8ce00000->0x7fff8d000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

7/31/15 12:39:00.000 AM kernel[0]: USBF: 7248.609 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 2 of Hub at 0x20300000)

7/31/15 12:39:00.000 AM kernel[0]: USBF: 7248.911 The IOUSBFamily was not able to enumerate a device.

7/31/15 12:39:00.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:39:02.812 AM storeassetd[382]: multibyte ASN1 identifiers are not supported.

7/31/15 12:40:06.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:41:14.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:41:29.000 AM kernel[0]: [0xffffff803dc68e00](1)/(5) Device not responding

7/31/15 12:41:29.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:42:03.000 AM kernel[0]: USBF: 7431.754 The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 2 of Hub at 0x20300000)

7/31/15 12:42:03.000 AM kernel[0]: USBF: 7432. 55 The IOUSBFamily was not able to enumerate a device.

7/31/15 12:42:04.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:43:10.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:43:26.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:43:53.000 AM kernel[0]: [0xffffff803dbb9200](1)/(5) Device not responding

7/31/15 12:43:53.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:44:36.000 AM kernel[0]: Google Chrome He (map: 0xffffff80320151e0) triggered DYLD shared region unnest for map: 0xffffff80320151e0, region 0x7fff8ce00000->0x7fff8d000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

7/31/15 12:44:52.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:45:36.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:46:29.000 AM kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0xe8d 0x1887 0x0, 2

7/31/15 12:46:37.000 AM kernel[0]: Sound assertion - 1002:aab0 FIFO error (Stream 0)

7/31/15 12:46:37.530 AM WindowServer[158]: Surface testing disallowed updates for 10 sequential attempts...

7/31/15 12:47:08.000 AM bootlog[0]: BOOT_TIME 1438328828 0

Requested System Diagnostics:

7/30/15 10:37:48.980 PM DumpGPURestart[552]: com.apple.message.domain: com.apple.crashreporter.writereport.gpuRestart

com.apple.message.signature: Kernel

com.apple.message.signature2: UNBUNDLED ||| kernel ((null))

com.apple.message.signature3: UNKNOWN

com.apple.message.result: noop

com.apple.message.summarize: YES

SenderMachUUID: ANONYMOUS

Reply

Answer 4

Linc Davis

Level 10

209,649 points

Jul 31, 2015 5:12 PM in response to wtsmith

The graphics processor is crashing. As far as I know, that only happens as the result of a hardware fault or perhaps a bug in the OS.

Make a "Genius" a ppointment at an Apple Store, or go to another authorized service provider. You may have to leave the machine there for several days.

Back up all data on the internal drive(s) before you hand over your computer to anyone. There are ways to back up a computer that isn't fully functional—ask if you need guidance.

If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.

Keeping your confidential data secure during hardware repair

Apple also recommends that you deauthorize a device in the iTunes Store before having it serviced.

*An SSD doesn't need to be zeroed.

Reply

Answer 5

jbg19086

Level 1

0 points

Oct 17, 2015 6:12 AM in response to wtsmith

I had this same problem with my 2013 Mac Pro. I took it to the genius bar and they replaced a single chip of ram. needless to say that didn't do the trick. What happened when you took yours in? Did you show them the diagnostics that Linc recommended?

Reply

Answer 6

Nov 23, 2015 6:20 PM in response to jbg19086

jbg19086 wrote:

I had this same problem with my 2013 Mac Pro. I took it to the genius bar and they replaced a single chip of ram. needless to say that didn't do the trick. What happened when you took yours in? Did you show them the diagnostics that Linc recommended?

After changing Ram chip, did you solve problem?

Max

Reply