Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: travellerva
travellerva Author
User level: Level 1
29 points

Kernel panic every Sunday evening...

The strangest thing... I had noticed regular kernel panics and auto reboots for some months (10.10.2, then 10.10.4) that seemed to have nothing in common. Examination of the console logs at those times didn't reveal anything in common. There was no kernel panic log in console.app.


I decided to do my own manual log of these panics. It appears they occur on Sunday evenings only - at least recently. Here are the console message logs from the last three occurrences - in all cases, the crash is preceded (or evidenced by) the cursor freezing:


Panic #1:

7/12/15 7:29:30.932 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

7/12/15 7:29:31.036 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

7/12/15 7:29:31.524 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

7/12/15 7:29:33.835 AM com.apple.xpc.launchd[1]: (com.apple.WebKit.Networking.DAFF3DE2-F4DF-40CE-B3fD-3549EBB5DA4D[7587]) Service exited with abnormal code: 1

7/12/15 7:30:49.068 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

7/12/15 7:32:29.000 AM bootlog[0]: BOOT_TIME 1436700749 0

Panic #2 (preceded shorty before by a weekly autoupdate for Microsoft Office):

7/19/15 7:41:52.616 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

7/19/15 7:42:06.350 AM secd[10365]: SecDbRecordChange db <SecDbConnection rw open> changed outside txn

7/19/15 7:42:06.558 AM com.apple.sbd[15564]: SOSCCThisDeviceIsInCircle SOSCCThisDeviceIsInCircle!! 7

7/19/15 7:42:06.606 AM com.apple.sbd[15564]: SOSCCThisDeviceIsInCircle SOSCCThisDeviceIsInCircle!! 8

7/19/15 7:42:06.662 AM com.apple.sbd[15564]: SOSCCThisDeviceIsInCircle SOSCCThisDeviceIsInCircle!! 9

7/19/15 7:44:31.276 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

7/19/15 7:45:35.000 AM bootlog[0]: BOOT_TIME 1437306335 0

Panic #3 (I was playing Spider Solitaire in a Win7 VM under Parallels):

7/26/15 9:33:26.544 PM com.apple.backupd[3491]: Ejected Time Machine network volume.

7/26/15 9:34:24.032 PM WindowServer[161]: _CGXGetWindowOrderingGroup: Operation on a window 0x21a requiring rights 0x5 by caller Windows 7

7/26/15 9:34:24.033 PM WindowServer[161]: _CGXGetWindowOrderingGroup: Operation on a window 0x122 requiring rights 0x5 by caller Executable for Spider Solitaire

7/26/15 9:34:25.636 PM WindowServer[161]: _CGXGetWindowOrderingGroup: Operation on a window 0x122 requiring rights 0x5 by caller Executable for Spider Solitaire

7/26/15 9:34:25.694 PM WindowServer[161]: _CGXGetWindowOrderingGroup: Operation on a window 0x122 requiring rights 0x5 by caller Executable for Spider Solitaire

7/26/15 9:34:27.621 PM WindowServer[161]: _CGXGetWindowOrderingGroup: Operation on a window 0x122 requiring rights 0x5 by caller Executable for Spider Solitaire

7/26/15 9:35:09.424 PM SystemUIServer[252]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc

7/26/15 9:35:09.425 PM com.apple.prefs.backup.remoteservice[1363]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc

7/26/15 9:41:22.000 PM bootlog[0]: BOOT TIME 1437961282 0

Note in all cases there was no console activity prior to the reboot for some time (6 minutes for Panic #3). I mention the weekly Microsoft Office update in the case of Panic #2 because this is the only weekly activity I believe occurs on a Sunday evening. on my system.

There are no kernel panic logs in the console.app for any of these crashes. Although I was running OS X 10.10.4 in a these three cases, earlier crashes - not logged specifically as to date or time by me - occurred under 10.10.2.


Any ideas as to possible causes or how I could capture more information would be much appreciated. Thanks.

OS X Yosemite (10.10.4), Parallels/WinXP/Win7/MS-DOS

Posted on Jul 26, 2015 8:51 PM

Reply
3 replies
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

Jul 27, 2015 10:00 AM in response to travellerva

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

This procedure is a diagnostic test. It makes no changes to your data.

Please triple-click anywhere in the line below on this page to select it:

syslog -k Sender kernel -k Message CSeq 'n Cause: -' | tail | awk '/:/{$4=""; print}' | pbcopy

Copy the selected text to the Clipboard by pressing the key combination command-C.

Launch the built-in Terminal 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. Click Utilities, then Terminal in the icon grid.

Paste into the Terminal window by pressing the key combination command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.

Wait for a new line ending in a dollar sign ($) to appear below what you entered.

The output of the command will be automatically copied to the Clipboard. If the command produced no output, the Clipboard will be empty. Paste into a reply to this message.

The Terminal window doesn't show the output. Please don't copy anything from there.

Reply
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

Jul 27, 2015 6:10 PM in response to travellerva

A negative shutdown code may indicate a hardware problem. The precise meaning of the codes is not publicly documented.

If you haven't already done so, you can try resetting the System Management Controller. Otherwise, or if the reset has no effect, see below.

Make a "Genius" appointment 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

Kernel panic every Sunday evening...

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up