Still getting daily crashes on the NMP. Seem caused by com.apple.photomoments ? Ran the machine in safe mode to repair. Not syncing Photos in iCloud.
Happens usually a few hours into intensive work.
Any thoughts? And thanks in advance.
Mac Pro, OS X Mavericks (10.9.4)
What exactly happens when it crashes?
Mostly while working in Photoshop, beachball crash, can't access any other apps or force quit, have to force shut down/restart.
Here is a bit of the diagnostic logs:
80 Diagnostic reports
81
82 2015-07-28 Mail hang
83 2015-08-10 System Preferences hang
84 2015-08-10 com.apple.preferences.icloud.remoteservice hang
85 2015-08-11 Kernel gpuRestart x2
86 2015-08-20 Mail hang
87 2015-08-21 Finder crash*
88 2015-08-23 com.apple.photomoments crash x5
89 2015-08-24 Finder crash*
90 2015-08-24 com.apple.photomoments crash x11
91 2015-08-25 Finder crash*
92 2015-08-25 com.apple.photomoments crash x4
93 * Code injection
94
95 HID errors: 11
96
97 Kernel log
98
99 Aug 23 14:12:50 SATA WARNING: IDENTIFY DEVICE checksum not implemented.
100 Aug 23 14:12:50 ARPT: 1.515446: BRCM tunables:
101 Aug 23 14:12:50 IO80211AWDLPeerManager::getHtCapabilityIE Unable to get ht capabilities ret ffffffe7
102 Aug 23 14:12:50 IO80211AWDLPeerManager::getVHtCapabilityIE Unable to get vht capabilities ret ffffffe7
103 Aug 23 14:12:53 IOHIDSystem: Seize of AppleMultitouchHIDEventDriver failed.
104 Aug 23 14:12:53 IOHIDSystem: Seize of IOHIDPointing failed.
105 Aug 23 17:39:33 SATA WARNING: IDENTIFY DEVICE checksum not implemented.
106 Aug 23 17:39:33 ARPT: 1.543771: BRCM tunables:
107 Aug 24 11:13:19 SATA WARNING: IDENTIFY DEVICE checksum not implemented.
108 Aug 24 11:13:19 ARPT: 1.485426: BRCM tunables:
109 Aug 24 11:13:19 IO80211AWDLPeerManager::getHtCapabilityIE Unable to get ht capabilities ret ffffffe7
110 Aug 24 11:13:19 IO80211AWDLPeerManager::getVHtCapabilityIE Unable to get vht capabilities ret ffffffe7
111 Aug 24 12:21:58 USBF: 4122.276 AppleUSBHubPort::FatalError - Port 4 of Hub at 0x20400000 reported error 0xe00002c0 while doing getting port status (7)
112 Aug 24 12:21:58 USBF: 4123. 12 AppleUSBHubPort::FatalError - Port 4 of Hub at 0x20400000 reported error 0xe00002c0 while doing getting port status (7)
113 Aug 24 12:21:59 USBF: 4123.575 IOUSBHIDDriver(IOUSBHIDDriver)::RearmInterruptRead returning error 0xe00002c0 (no such device), not issuing any reads to device
114 Aug 24 18:52:02 Limiting closed port RST response from 287 to 250 packets per second
115 Aug 24 21:33:45 Limiting closed port RST response from 271 to 250 packets per second
116 Aug 25 13:06:30 SATA WARNING: IDENTIFY DEVICE checksum not implemented.
117 Aug 25 13:06:30 ARPT: 1.513907: BRCM tunables:
118 Aug 25 13:06:41 bird[252] Unable to quarantine: 93
119 Aug 25 13:06:43 bird[252] Unable to quarantine: 93
120 Aug 25 13:06:43 bird[252] Unable to quarantine: 93
121 Aug 25 16:26:02 SATA WARNING: IDENTIFY DEVICE checksum not implemented.
122 Aug 25 16:26:02 ARPT: 1.572250: BRCM tunables:
123 Aug 25 16:26:04 IO80211AWDLPeerManager::configure Unable to set BSSID ret 52
124
125 System log
126
127 Aug 25 17:58:33 WindowServer: disable_update_timeout: UI updates were forcibly disabled by application "Adobe Photoshop CC 2015" for over 1.00 seconds. Server has re-enabled them.
128 Aug 25 17:59:43 WindowServer: disable_update_timeout: UI updates were forcibly disabled by application "Adobe Photoshop CC 2015" for over 1.00 seconds. Server has re-enabled them.
129 Aug 25 17:59:46 WindowServer: disable_update_timeout: UI updates were forcibly disabled by application "Adobe Photoshop CC 2015" for over 1.00 seconds. Server has re-enabled them.
130 Aug 25 18:00:14 WindowServer: _CGXGetWindowOrderingGroup: Operation on a window 0x95 requiring rights 0x5 by caller Adobe Photoshop CC 2015
131 Aug 25 18:00:25 QuickLookUIHelper: HWJPEG not avaialble on this platform
132 Aug 25 18:05:26 WindowServer: disable_update_timeout: UI updates were forcibly disabled by application "Adobe Photoshop CC 2015" for over 1.00 seconds. Server has re-enabled them.
133 Aug 25 18:05:29 WindowServer: disable_update_timeout: UI updates were forcibly disabled by application "Adobe Photoshop CC 2015" for over 1.00 seconds. Server has re-enabled them.
134 Aug 25 18:06:35 WindowServer: disable_update_timeout: UI updates were forcibly disabled by application "Adobe Photoshop CC 2015" for over 1.00 seconds. Server has re-enabled them.
135 Aug 25 18:06:38 WindowServer: disable_update_timeout: UI updates were forcibly disabled by application "Adobe Photoshop CC 2015" for over 1.00 seconds. Server has re-enabled them.
136 Aug 25 18:07:41 QuickLookUIHelper: HWJPEG not avaialble on this platform
137 Aug 25 18:09:25 WindowServer: disable_update_timeout: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
138 Aug 25 18:09:27 WindowServer: disable_update_timeout: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
139 Aug 25 18:20:57 sharingd: 18:20:57.161 : SDConnectionManager:: XPC connection invalidated
140 Aug 25 18:21:08 sharingd: 18:21:08.217 : SDConnectionManager:: XPC connection invalidated
141 Aug 25 18:21:50 bird: GSLibraryResolveDocumentId(2270); error 16 (Resource busy)
142 Aug 25 18:31:03 airport: Error: Scan failed (82)
143 Aug 25 18:31:03 airport:
144 Aug 25 18:45:32 WindowServer: _CGXGetWindowOrderingGroup: Operation on a window 0x256 requiring rights 0x5 by caller Adobe Photoshop CC 2015
145 Aug 25 19:03:44 WindowServer: _CGXGetWindowOrderingGroup: Operation on a window 0x256 requiring rights 0x5 by caller Adobe Photoshop CC 2015
146 Aug 25 19:24:33 WindowServer: disable_update_timeout: UI updates were forcibly disabled by application "Adobe Photoshop CC 2015" for over 1.00 seconds. Server has re-enabled them.
147 Aug 25 19:24:36 WindowServer: disable_update_timeout: UI updates were forcibly disabled by application "Adobe Photoshop CC 2015" for over 1.00 seconds. Server has re-enabled them.
148 Aug 25 19:26:08 WindowServer: _CGXGetWindowOrderingGroup: Operation on a window 0x22c requiring rights 0x5 by caller Adobe Photoshop CC 2015
149 Aug 25 19:34:32 QuickLookUIHelper: HWJPEG not avaialble on this platform
150 Aug 25 19:34:44 QuickLookUIHelper: HWJPEG not avaialble on this platform
151 Aug 25 19:35:49 WindowServer: disable_update_timeout: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
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.
Part one. Crash at about 4:25pm
8/25/15 4:12:44.757 PM com.apple.iCloudHelper[1763]: objc[1763]: Class FALogging is implemented in both /System/Library/PrivateFrameworks/FamilyCircle.framework/Versions/A/FamilyCircl e and /System/Library/PrivateFrameworks/FamilyNotification.framework/Versions/A/Famil yNotification. One of the two will be used. Which one is undefined.
8/25/15 4:12:44.775 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
8/25/15 4:13:11.838 PM Mail[467]: No worthy mechs found
8/25/15 4:16:04.881 PM CalendarAgent[243]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]
8/25/15 4:17:57.639 PM Mail[467]: No worthy mechs found
8/25/15 4:20:21.121 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
8/25/15 4:22:11.978 PM WindowServer[160]: Surface testing disallowed updates for 10 sequential attempts...
8/25/15 4:24:10.776 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
8/25/15 4:25:02.000 PM kernel[0]: process WindowServer[160] caught causing excessive wakeups. EXC_RESOURCE supressed due to audio playback
Part 2 System Diagnostic Report Kernel Panic, Aug 11th is the most recent:
This is a warranty issue. Either there's a hardware fault or you're triggering a bug.
Ugh. Yes this machine has been buggy since getting it.
I seem to have a similar problem. Have you been able to solve it?
Photomoments causing daily crashes?
