Unexpected and random shutdowns

I just got a new 27 iMac and it has be unexpectedly shuting down a fews times a day on me since I got it and I cant figure out why and nether can apple care, Please Help...
copy from log 8/27/10 11:16:24 PM shutdown[259] SHUTDOWN_TIME: 1282976184 985648
8/28/10 9:30:06 PM shutdown[403] SHUTDOWN_TIME: 1283056206 836431
8/30/10 10:55:31 PM shutdown[582] SHUTDOWN_TIME: 1283234131 795816
9/1/10 2:37:07 PM DirectoryService[11] Improper shutdown detected
9/1/10 2:37:08 PM kernel systemShutdown false
9/1/10 2:37:10 PM kernel Previous Shutdown Cause: -128
9/1/10 3:42:29 PM kernel systemShutdown false
9/1/10 3:42:29 PM DirectoryService[11] Improper shutdown detected
9/1/10 3:42:32 PM kernel Previous Shutdown Cause: -128
9/1/10 8:53:07 PM DirectoryService[11] Improper shutdown detected
9/1/10 8:53:08 PM kernel systemShutdown false
9/1/10 8:53:11 PM kernel Previous Shutdown Cause: 0
9/2/10 12:24:42 PM DirectoryService[11] Improper shutdown detected
9/2/10 12:24:43 PM kernel systemShutdown false
9/2/10 12:24:45 PM kernel Previous Shutdown Cause: -128
9/2/10 2:19:10 PM kernel systemShutdown true
9/2/10 2:19:10 PM kernel systemShutdown true
9/2/10 2:19:14 PM com.apple.loginwindow[45] shutdown: / is busy updating; waiting for lock
9/2/10 2:19:17 PM shutdown[356] reboot by JasonBoyseiMac:
9/2/10 2:19:17 PM shutdown[356] SHUTDOWN_TIME: 1283462357 647192
9/2/10 2:19:37 PM kernel systemShutdown false
9/2/10 2:19:39 PM kernel Previous Shutdown Cause: -128
9/2/10 2:31:05 PM kernel systemShutdown true
9/2/10 2:31:05 PM kernel systemShutdown true
9/2/10 2:31:18 PM com.apple.loginwindow[43] shutdown: / is busy updating; waiting for lock
9/2/10 2:31:21 PM shutdown[255] reboot by JasonBoyseiMac:
9/2/10 2:31:21 PM shutdown[255] SHUTDOWN_TIME: 1283463081 736105
9/2/10 2:31:41 PM kernel systemShutdown false
9/2/10 2:31:43 PM kernel Previous Shutdown Cause: -128
9/2/10 8:52:47 PM DirectoryService[11] Improper shutdown detected
9/2/10 8:52:48 PM kernel systemShutdown false
9/2/10 8:52:50 PM kernel Previous Shutdown Cause: -128
9/2/10 8:53:47 PM shutdown[159] halt by JasonBoyseiMac:
9/2/10 8:53:47 PM shutdown[159] SHUTDOWN_TIME: 1283486027 31227
9/2/10 8:53:47 PM kernel systemShutdown true
9/2/10 8:53:47 PM kernel systemShutdown true
9/2/10 8:57:01 PM kernel systemShutdown false
9/2/10 8:57:03 PM kernel Previous Shutdown Cause: 0
9/2/10 9:16:26 PM DirectoryService[11] Improper shutdown detected
9/2/10 9:16:27 PM kernel systemShutdown false
9/2/10 9:16:30 PM kernel Previous Shutdown Cause: -128
9/2/10 9:37:09 PM DirectoryService[11] Improper shutdown detected
9/2/10 9:37:10 PM kernel systemShutdown false
9/2/10 9:37:12 PM kernel Previous Shutdown Cause: 0
9/2/10 10:13:43 PM DirectoryService[11] Improper shutdown detected
9/2/10 10:13:44 PM kernel systemShutdown false
9/2/10 10:13:46 PM kernel Previous Shutdown Cause: -128
9/2/10 10:24:28 PM DirectoryService[11] Improper shutdown detected
9/2/10 10:24:29 PM kernel systemShutdown false
9/2/10 10:24:31 PM kernel Previous Shutdown Cause: -128
9/3/10 11:37:45 AM DirectoryService[11] Improper shutdown detected
9/3/10 11:37:46 AM kernel systemShutdown false
9/3/10 11:37:48 AM kernel Previous Shutdown Cause: -2
9/3/10 9:58:04 PM DirectoryService[11] Improper shutdown detected
9/3/10 9:58:05 PM kernel systemShutdown false
9/3/10 9:58:08 PM kernel Previous Shutdown Cause: -128
9/3/10 11:29:32 PM DirectoryService[11] Improper shutdown detected
9/3/10 11:29:33 PM kernel systemShutdown false
9/3/10 11:29:36 PM kernel Previous Shutdown Cause: -128
9/3/10 11:29:32 PM DirectoryService[11] Improper shutdown detected
9/3/10 11:29:33 PM kernel systemShutdown false
9/3/10 11:29:36 PM kernel Previous Shutdown Cause: -128
9/4/10 7:43:37 PM shutdown[1786] halt by JasonBoyseiMac:
9/4/10 7:43:37 PM shutdown[1786] SHUTDOWN_TIME: 1283654617 90067
9/4/10 7:43:37 PM kernel systemShutdown true
9/4/10 7:43:37 PM kernel systemShutdown true
9/4/10 7:45:05 PM kernel systemShutdown false
9/4/10 7:45:07 PM kernel Previous Shutdown Cause: 0
9/4/10 7:59:34 PM DirectoryService[11] Improper shutdown detected
9/4/10 7:59:35 PM kernel systemShutdown false
9/4/10 7:59:39 PM kernel Previous Shutdown Cause: -128
9/5/10 10:07:53 AM DirectoryService[11] Improper shutdown detected
9/5/10 10:07:54 AM kernel systemShutdown false
9/5/10 10:07:57 AM kernel Previous Shutdown Cause: -128
9/6/10 1:19:28 PM DirectoryService[11] Improper shutdown detected
9/6/10 1:19:29 PM kernel systemShutdown false
9/6/10 1:19:33 PM kernel Previous Shutdown Cause: -128
9/6/10 1:22:25 PM kernel systemShutdown true
9/6/10 1:22:25 PM shutdown[168] halt by JasonBoyseiMac:
9/6/10 1:22:25 PM shutdown[168] SHUTDOWN_TIME: 1283804545 280047
9/6/10 1:22:26 PM kernel systemShutdown true
9/6/10 1:30:38 PM kernel systemShutdown false
9/6/10 1:30:40 PM kernel Previous Shutdown Cause: 3
9/6/10 1:31:18 PM shutdown[154] halt by JasonBoyseiMac:
9/6/10 1:31:18 PM shutdown[154] SHUTDOWN_TIME: 1283805078 94073
9/6/10 1:31:18 PM kernel systemShutdown true
9/6/10 1:31:18 PM kernel systemShutdown true
9/6/10 1:48:22 PM kernel systemShutdown false
9/6/10 1:48:24 PM kernel Previous Shutdown Cause: 5
9/6/10 2:01:26 PM kernel systemShutdown true
9/6/10 2:01:26 PM kernel systemShutdown true
9/6/10 2:01:43 PM com.apple.loginwindow[48] shutdown: / is busy updating; waiting for lock
9/6/10 2:01:51 PM shutdown[191] reboot by JasonBoyseiMac:
9/6/10 2:01:51 PM shutdown[191] SHUTDOWN_TIME: 1283806911 928184
9/6/10 2:02:13 PM kernel systemShutdown false
9/6/10 2:02:15 PM kernel Previous Shutdown Cause: 5
9/7/10 12:42:31 PM DirectoryService[11] Improper shutdown detected
9/7/10 12:42:33 PM kernel systemShutdown false
9/7/10 12:42:36 PM kernel Previous Shutdown Cause: -128

The power source ended up being bad after many trouble shooting sessions with apple techs.

Similar Messages

  • Macbook in repair for kernal panics and random shutdowns.....

    It's been exactly one week since I sent in my macbook for random shutdowns. I called today to check on the status and they told me it was on hold because they needed more info from me as they can not replicate the problem. This thing was shutting down on me 3-4 times a day without warning. I gave them all kinds of suggestions, ie: check logic board, power management system, panic logs, etc. Don't these techs know how to troubleshoot? My biggest fear is that they won't find the problem and they'll send my defective Macbook back to me. What are my options then? It was bought for me by a friend in Denver who brought it down to Albuquerque for me (500 miles away) so returning it to a store is not an option. I know other people are having this problem so I know I'm not crazy and delusional. I don't want to be stuck with a defective computer but my 2 week grace period is over. What can I do?
    MacBook   Mac OS X (10.4.5)  

    Here's an update on my repair. It's been 2 weeks and they finally found the problem to be a bad logic board. They said it was on hold for repair to replace the board and didn't specify a return time. I expressed a concern with having a month old computer that has already been in for a major repair. After some polite but concerned dialouge between myself and a product specialist, she offered me a new one. I accepted the offer gladly. She even asked black or white? My original was white. So chalk one up for Apple customer support. They seems like they're out to make things right with their customers. You just have to remain calm and patient.

  • Leopard and Random Shutdown Syndrome

    I've got a 1st gen 1.83 GHz MacBook with RSS. Has upgrading to Leopard solved RSS for anyone?
    Still trying to figure out what's causing it - hardware or software.
    Thanks,
    Matthew

    I should've been more specific. Unfortunately, RSS hasn't "left the building" for me.
    Yes, I've done all updates to EFI Firmware, Battery, SMC, etc. In fact, I've run them all again just to make sure they're there and I get "This computer does not need this update." I'm running 10.4.10. Nothing new shows up when I run "Software Update." That's out.
    The shutdowns only seem to occur when I'm on battery and when surfing graphics-heavy sites on the internet (Youtube or ABC.com with their online shows). However, that's not even a reliable cause; I was doing surfing those sites AND running Parallels while on battery the other day to try to kill it and nada.
    I can't seem to get the RSS to replicate (guess that's why it's called "Random", eh?) so I can narrow down the causes.
    Right now, I'm leaning towards the battery or RAM. I have 2GB of 3rd party RAM installed, and am swapping it out piece by piece with the original Apple RAM.
    It may be the battery, but since I can't get it to replicate with any reliability, that may be hard to prove. My battery IS recognized (no big X in the menubar), ISN'T bulging and lasts a while when I use it. So I doubt I can get a new battery.
    Oh well, just hoping something in Leopard would help. Dammit Jim!
    Thanks,
    Matthew
    ETA: It's a 1st gen Macbook, so it's out of warranty by a few months.
    Message was edited by: noclevername

  • All Open Applications Quitting Unexpectedly and Randomly

    It started last night after I finally allowed App Store to install a bunch of OS X updates that it had wanted to install for quite some time. I'm not 100% sure but I believe one of those updates was for OS X 10.8.4 from 10.8.3 but I may be mistaken and had installed that a bit ago. I do know that among the group of updates was a thunderboldt firmware update, some printer drivers, security updates, etc.
    Anyways, this has to be by far the most frustrating issue I have ever experienced on a machine. Basically, I'll just be working on my computer whether it be in Chrome on one of my many tabs or in Evernote writing a note or in any other app and then bam, out of nowhere every single running up on my machine, even those not shown in the dock and only in the status bar will just vanish and quit, without notice or popups. The only app that remains will be Finder (TotalFinder will be killed) and, very randomly, a few of the status bar apps may survive the mutiny. Whatever I have open and was in the middle of working on will be gone. I can't even begin to explain how downright frustrating this is. It has already happened 3 times in a period of 24 hours and I have absolutely no clue what is going on. Before I ran the updates late last night, I hadn't rebooted my machine for 2-3 weeks and I've most certainly never ever experienced any issues remotely related to this.
    When reviewing the logs in Console around the time of each occurence, there'll be a flood of errors but I cannot identify the root cause of the issue and am left without any leads after hours and hours of searching the web for other users who might be experiencing this exact behavior. Anything I find that might seem related tends to be just one app that's crashing and just isn't quite what I'm experiencing. Might I add that I am not notified, prompted, or anything when the apps close. Literally, one second I have a bunch of apps running and I'm cruising along and the next, nothing but Finder and a few survivors (they probably were able to recover and restart themselves) in the status bar.
    This problem is blowing my mind and it has me about ready to reformat and start from scratch except for the fact that I just don't have the time to set everything back up again right now. I cannot get my work done under these circumstances though.
    Here are some details on my hardware configuration:
    I upgraded my ram to 16gb from a very reputable brand long ago when I first bought the high-resolution late 2011 15" MacBook Pro and have never had issues. I do not believe the hardware has anything to do with this issue anyways...
    500GB Samsung Flash drive with about 70GB free right now. Upgraded that from the stock 500GB 5400 RPM hard drive many months ago and, again, have never had issues until I installed updates last night.
    I'd greatly appreciate any insight or help on this. I am a software developer and have spent over 6 hours trying to find an answer and diagnose this issue already. I am at a complete and utter loss at this point. I've repaired permissions, cleared caches, verified fonts, rebooted multiple times after making some system changes, etc... all to no avail. I am stumped, fooled, dumbfounded, and, quite frankly, REALLY ****** off at this machine right now. Hopefully some genius can come along and save the day here.
    Below is a dump of the Console's logged events from the most recent occurance. Maybe you'll be able to pickup a trail from this information. Please let me know if there's anything else I can provide to possibly help diagnose and fix this.
    Thanks in advance for any guidance you can provide here.
    7/17/13 10:49:25.756 PM WindowServer[80]: CGXDeferSurfaces : Invalid source window 677
    7/17/13 10:49:26.378 PM Finder[544]: Lost connection to NetworkBrowserAgent
    7/17/13 10:49:26.378 PM Finder[544]: Lost connection to NetworkBrowserAgent
    7/17/13 10:49:26.378 PM Finder[544]: Lost connection to NetworkBrowserAgent
    7/17/13 10:49:26.440 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyChildDeath to notificationID=381
    7/17/13 10:49:26.440 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.441 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.475 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.476 PM loginwindow[52]: Connection with distnoted server was invalidated
    7/17/13 10:49:26.477 PM SRFeature[1025]: Connection with distnoted server was invalidated
    7/17/13 10:49:26.477 PM UserEventAgent[185]: Connection with distnoted server was invalidated
    7/17/13 10:49:26.477 PM Dock[194]: Connection with distnoted server was invalidated
    7/17/13 10:49:26.477 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyChildDeath to notificationID=381
    7/17/13 10:49:26.479 PM imagent[213]: ======================================================================
    7/17/13 10:49:26.481 PM imagent[213]: ===== Listener Information ===========================================
    7/17/13 10:49:26.481 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.482 PM imagent[213]: ======================================================================
    7/17/13 10:49:26.000 PM kernel[0]: SRXFrameBufferClient::unPlugMonitor(), Head : 0
    7/17/13 10:49:26.000 PM kernel[0]: SRXFrameBufferClient::unPlugMonitor(), Head : 0
    7/17/13 10:49:26.482 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.497 PM ubd[616]: Connection with distnoted server was invalidated
    7/17/13 10:49:26.498 PM NotificationCenter[209]: Connection with distnoted server was invalidated
    7/17/13 10:49:26.501 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.498 PM imagent[213]: Connection with distnoted server was invalidated
    7/17/13 10:49:26.502 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyChildDeath to notificationID=381
    7/17/13 10:49:26.510 PM com.apple.launchd[1]: (com.apple.XType.FontHelper[639]) Could not terminate job: 3: No such process
    7/17/13 10:49:26.510 PM com.apple.launchd[1]: (com.apple.XType.FontHelper[639]) Using fallback option to terminate job...
    7/17/13 10:49:26.511 PM com.apple.launchd[1]: (com.culturedcode.thingsreminders[1734]) Could not terminate job: 3: No such process
    7/17/13 10:49:26.511 PM com.apple.launchd[1]: (com.culturedcode.thingsreminders[1734]) Using fallback option to terminate job...
    7/17/13 10:49:26.502 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.517 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.517 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.518 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyChildDeath to notificationID=381
    7/17/13 10:49:26.519 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.519 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.519 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.520 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyChildDeath to notificationID=381
    7/17/13 10:49:26.521 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.521 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.521 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.543 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyChildDeath to notificationID=381
    7/17/13 10:49:26.544 PM coreservicesd[28]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=100
    7/17/13 10:49:26.544 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.544 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.544 PM coreservicesd[28]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=289
    7/17/13 10:49:26.544 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.545 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyChildDeath to notificationID=381
    7/17/13 10:49:26.545 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.546 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.546 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.547 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyChildDeath to notificationID=381
    7/17/13 10:49:26.548 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.548 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.548 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.549 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.549 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.549 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.550 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyChildDeath to notificationID=381
    7/17/13 10:49:26.550 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.550 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.551 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.551 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.552 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.552 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.553 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyChildDeath to notificationID=381
    7/17/13 10:49:26.553 PM TotalFinderCrashWatcher[548]: Connection with distnoted server was invalidated
    7/17/13 10:49:26.553 PM ARDAgent[287]: Connection with distnoted server was invalidated
    7/17/13 10:49:26.556 PM com.apple.launchd[1]: (com.apple.dock.extra[310]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.556 PM com.apple.launchd[1]: (com.apple.xpcd.F5010000-0000-0000-0000-000000000000[257]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.542 PM com.apple.launchd.peruser.501[182]: ([0x0-0x51051].com.binaryage.totalfinder.agent[543]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.542 PM com.apple.launchd.peruser.501[182]: ([0x0-0x2b02b].com.freemacsoft.AppCleaner-Helper[275]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.568 PM com.apple.launchd.peruser.501[182]: ([0x0-0x2d02d].com.vmware.fusionStartMenu[277]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.568 PM com.apple.launchd.peruser.501[182]: (com.apple.pboard[200]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.568 PM com.apple.launchd.peruser.501[182]: (net.culater.SIMBL.Agent[222]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.569 PM com.apple.launchd.peruser.501[182]: ([0x0-0x15015].com.avatron.AirDisplayMenuExtra[248]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.569 PM com.apple.launchd.peruser.501[182]: (ws.agile.1PasswordAgent[231]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.570 PM com.apple.launchd.peruser.501[182]: (com.evernote.EvernoteHelper[204]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.571 PM com.apple.launchd.peruser.501[182]: (com.apple.fontd[241]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.571 PM com.apple.launchd.peruser.501[182]: (com.apple.talagent[195]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.571 PM com.apple.launchd.peruser.501[182]: (com.splashtop.streamer.SRServiceAgent[223]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.572 PM com.apple.launchd.peruser.501[182]: (cn.com.zte.usbswapper.plist[221]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.572 PM com.apple.launchd.peruser.501[182]: (com.apple.imklaunchagent[332]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.572 PM com.apple.launchd.peruser.501[182]: (com.apple.printtool.agent[637]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.573 PM com.apple.launchd.peruser.501[182]: (com.Logitech.Control Center.Daemon[225]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.573 PM com.apple.launchd.peruser.501[182]: (com.spotify.webhelper[233]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.574 PM com.apple.launchd.peruser.501[182]: ([0x0-0xf00f].com.codykrieger.gfxCardStatus[245]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.588 PM usernoted[205]: Connection with distnoted server was invalidated
    7/17/13 10:49:26.584 PM com.apple.launchd.peruser.501[182]: ([0x0-0x30030].com.Growl.GrowlHelperApp[284]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.585 PM com.apple.launchd.peruser.501[182]: ([0x0-0x3f03f].jp.co.canon.cijscannerregister[368]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.585 PM com.apple.launchd.peruser.501[182]: (com.apple.pbs[299]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.585 PM com.apple.launchd.peruser.501[182]: (com.apple.LaunchServices.lsboxd[272]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.586 PM com.apple.launchd.peruser.501[182]: (com.apple.NetworkBrowserAgent[266]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.586 PM com.apple.launchd.peruser.501[182]: (com.apple.accountsd[259]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.553 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.595 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.595 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.596 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyChildDeath to notificationID=381
    7/17/13 10:49:26.597 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.597 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.597 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.592 PM com.apple.launchd.peruser.501[182]: (com.apple.coreservices.appleid.authentication[216]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.592 PM com.apple.launchd.peruser.501[182]: (com.apple.AirPortBaseStationAgent[1005]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.592 PM com.apple.launchd.peruser.501[182]: ([0x0-0x19019].com.naotaka.ClipMenu[251]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.613 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyChildDeath to notificationID=381
    7/17/13 10:49:26.613 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.613 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.613 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.612 PM com.apple.launchd.peruser.501[182]: ([0x0-0x21021].com.eidac.smcFanControl2[260]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.613 PM com.apple.launchd.peruser.501[182]: ([0x0-0x61061].com.apple.TextEdit[642]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.613 PM com.apple.launchd.peruser.501[182]: (com.apple.distnoted.xpc.agent[186]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.614 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.614 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.614 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.615 PM com.apple.launchd.peruser.501[182]: ([0x0-0xa30a3].com.hegenberg.BetterTouchTool[1008]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.615 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.615 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.616 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.616 PM coreservicesd[28]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=100
    7/17/13 10:49:26.616 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.616 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.617 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.618 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyChildDeath to notificationID=381
    7/17/13 10:49:26.618 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.618 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.618 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.619 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyChildDeath to notificationID=381
    7/17/13 10:49:26.619 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.619 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.620 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=345
    7/17/13 10:49:26.616 PM com.apple.launchd.peruser.501[182]: ([0x0-0x5f05f].com.hipchat.HipChat[635]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.616 PM com.apple.launchd.peruser.501[182]: ([0x0-0x25025].com.getdropbox.dropbox[267]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.616 PM com.apple.launchd.peruser.501[182]: (com.machangout.glims.agent[224]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.617 PM com.apple.launchd.peruser.501[182]: ([0x0-0x2f02f].com.googlecode.precipitate.agent[281]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.618 PM com.apple.launchd.peruser.501[182]: ([0x0-0x39039].com.apple.AppleSpell[337]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.618 PM com.apple.launchd.peruser.501[182]: ([0x0-0x24024].jp.co.Canon.bj.scan.network.scannerselector2[264]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.618 PM com.apple.launchd.peruser.501[182]: ([0x0-0x12012].com.apple.iTunesHelper[246]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.618 PM com.apple.launchd.peruser.501[182]: ([0x0-0x36036].com.apple.inputmethod.ironwood[333]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.618 PM com.apple.launchd.peruser.501[182]: (com.apple.librariand[644]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.618 PM com.apple.launchd.peruser.501[182]: ([0x0-0x65065].com.apple.iWork.Pages[656]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.618 PM com.apple.launchd.peruser.501[182]: ([0x0-0x60060].com.apple.iChat[640]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.618 PM com.apple.launchd.peruser.501[182]: ([0x0-0x3e03e].com.apple.ImageCaptureExtension2[367]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.618 PM com.apple.launchd.peruser.501[182]: (com.apple.helpd[214]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.618 PM com.apple.launchd.peruser.501[182]: (com.apple.tccd[306]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.618 PM com.apple.launchd.peruser.501[182]: ([0x0-0x20020].com.code42.b42menuextra[258]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.618 PM com.apple.launchd.peruser.501[182]: (com.apple.storeagent[294]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.619 PM com.apple.launchd.peruser.501[182]: ([0x0-0x5d05d].com.evernote.Evernote[628]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.619 PM com.apple.launchd.peruser.501[182]: ([0x0-0x67067].com.google.Chrome[671]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.619 PM com.apple.launchd.peruser.501[182]: ([0x0-0x5a05a].com.culturedcode.things[619]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.619 PM com.apple.launchd.peruser.501[182]: (com.apple.CalendarAgent[217]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.624 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyChildDeath to notificationID=381
    7/17/13 10:49:26.624 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.624 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.623 PM com.apple.launchd.peruser.501[182]: ([0x0-0x1e01e].com.google.GmailNotifier[254]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.624 PM com.apple.launchd.peruser.501[182]: ([0x0-0x27027].com.kapeli.dashExpander[268]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.624 PM com.apple.launchd.peruser.501[182]: (com.apple.photostream-agent[203]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.625 PM com.apple.launchd.peruser.501[182]: (com.apple.Finder[544]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.627 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.627 PM com.apple.launchd.peruser.501[182]: (com.apple.mdworker.shared.04000000-0000-0000-0000-000000000000[1487]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.628 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.630 PM com.apple.launchd.peruser.501[182]: (com.apple.SystemUIServer.agent[196]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.630 PM com.apple.launchd.peruser.501[182]: ([0x0-0x16016].com.coderage.Zooom2[249]) Exited abnormally: User defined signal 1: 30
    7/17/13 10:49:26.631 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.632 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.633 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.633 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.633 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.634 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.634 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.634 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=242
    7/17/13 10:49:26.635 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.636 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.636 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.643 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.644 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.645 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.646 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.648 PM coreservicesd[28]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=100
    7/17/13 10:49:26.649 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.649 PM coreservicesd[28]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=193
    7/17/13 10:49:26.666 PM coreservicesd[28]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=100
    7/17/13 10:49:26.666 PM coreservicesd[28]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=122
    7/17/13 10:49:26.666 PM coreservicesd[28]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=122
    7/17/13 10:49:26.698 PM coreservicesd[28]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=100
    7/17/13 10:49:26.701 PM coreservicesd[28]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=122
    7/17/13 10:49:26.702 PM coreservicesd[28]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=122
    7/17/13 10:49:26.726 PM WindowServer[80]: CGXGetConnectionProperty: Invalid connection 197583
    7/17/13 10:49:26.726 PM WindowServer[80]: CGXGetConnectionProperty: Invalid connection 197583
    7/17/13 10:49:26.729 PM WindowServer[80]: CGXGetConnectionProperty: Invalid connection 197583
    7/17/13 10:49:26.730 PM WindowServer[80]: CGXGetConnectionProperty: Invalid connection 197583
    7/17/13 10:49:26.732 PM WindowServer[80]: CGXGetConnectionProperty: Invalid connection 197583
    7/17/13 10:49:26.746 PM WindowServer[80]: CGXDeferSurfaces : Invalid source window 798
    7/17/13 10:49:26.770 PM WindowServer[80]: dict count after removing entry for window 0x169 is 0
    7/17/13 10:49:26.871 PM distnoted[1759]: # distnote server agent  absolute time: 2974.474728467   civil time: Wed Jul 17 22:49:26 2013   pid: 1759 uid: 501  root: no
    7/17/13 10:49:26.885 PM Mac_SwapperDemon[1749]: Mac_SwapperDemon Version:1.0
    7/17/13 10:49:26.891 PM Mac_SwapperDemon[1749]: Start UI when system start up: 0

    Hey Clinton, thanks for such a speed reply!
    The Console logs sure do seem useless. They definitely haven't helped me track anything down for squat but, as you suspected, I have no kernal panics to pull logs from. I did notice, however, one particular app that was leaving a User Diagnostic Report / crash log at the same time each occurance happened. The reports are for SRServiceAgent, which is part of Splashtop Streamer.app. Maybe these logs might reveal something? If you think so, I can share the output as well. I've looked through them but I must say, they're near giberish to me
    Here's the out from kextstat | grep -v com.apple:
    Index Refs Address            Size       Wired      Name (Version) <Linked Against>
       61    0 0xffffff7f8139a000 0x3000     0x3000     com.rogueamoeba.InstantOn (6.0.2) <5 4 3 1>
      102    1 0xffffff7f81588000 0xa000     0xa000     com.avatron.AVExVideo (1.7) <78 5 4 3>
      118    0 0xffffff7f82492000 0x22000    0x22000    com.rogueamoeba.InstantOnCore (6.0.2) <117 5 4 3 1>
      121    0 0xffffff7f808a0000 0x5000     0x5000     com.Cycling74.driver.Soundflower (1.5.3) <117 5 4 3>
      122    1 0xffffff7f8084a000 0x13000    0x13000    com.splashtop.driver.SRXDisplayCard (1.6) <78 5 4 3>
      129    0 0xffffff7f825ea000 0x5000     0x5000     com.avatron.AVExFramebuffer (1.7) <102 78 5 4 3>
      131    0 0xffffff7f825f4000 0x9000     0x9000     com.splashtop.driver.SRXFrameBufferConnector (1.6) <122 4 3>
      136    3 0xffffff7f82602000 0x42000    0x42000    org.virtualbox.kext.VBoxDrv (4.2.8) <7 5 4 3 1>
      137    0 0xffffff7f82644000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (4.2.8) <136 46 33 7 5 4 3 1>
      139    0 0xffffff7f8264c000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (4.2.8) <136 7 5 4 3 1>
      140    0 0xffffff7f82651000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (4.2.8) <136 5 4 1>
    I'll try giving a reinstall of 10.8.4 via the combo updater a shot and see if that helps. I've been using the machine without another episode for about an hour now but that really doesn't mean anything since I have no frigin idea what's causing this and if anything I may have adjusted would have even fixed it or not. It's kinda an only time will tell thing right now.
    See anything that raises any flags in the output above? The Splashtop kext is for the same app I mentioned above that left a crash log. It's an app that allows me to remote in using my iPhone or iPad but I don't believe I even had it actively running when I whitnessed the lovely disappearing act. Of course, that doesn't mean things weren't still running in the background of course.
    On that note, I ought to wipe VirtualBox. I've been using VMWare instead lately and I've actually already uninstalled the VirtualBox app itself. I'll see if I can find a writeup on how to properly remove its kernel extensions... long shot in terms of a solution to my issue but hey.
    Btw, is it possible to look into exactly what and when system updates were installed? I'd like to confirm whether I actually did install 10.8.4 the first night or if it already had been. At the very least, it would help me isolate some details behind what's causing this cause this certainly didn't happen before those updates I installed the first night.
    Thanks again!

  • Using both Firefox 17 and 18, browser, still freezes unexpectedly and randomly even though have tried almost every suggested fix on mozilla support

    I have tried almost everything in support forum to end the freezing problem, and just when I think the latest thing I have read has solved it, it happens again.
    One page it freezes once in a while is: http://www.nationalpost.com/index.html. Other wise it is random sites that I visit.
    The only thing I havent done is disable the add-ons that I rely on all the time, namely
    ReminderFox, Sage, Email Link, and Flashblock, all up-to-date.
    I currently have four plugins enabled, being: Adobe Acrobat, itunes application detector, Windows media player firefox plugin and Shockwave Flash, all are up-to-date.

    Try to disable hardware acceleration in Firefox.
    *Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
    *https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
    *https://hacks.mozilla.org/2010/09/hardware-acceleration/
    You can also do a check for problems caused by plugins.
    *https://support.mozilla.org/kb/Troubleshooting+plugins
    *https://support.mozilla.org/kb/Safe+Mode
    In Firefox Safe mode these changes are effective:
    *all extensions are disabled
    *the default theme is used (no persona)
    *userChrome.css and userContent.css are ignored
    *the default toolbar layout is used
    *the Javascript JIT compiler is disabled
    *hardware acceleration is disabled
    *plugins are not affected
    *preferences are not affected

  • Problems with New Kernel regarding mouse and random shutdowns etc

    After upgrading to kernel 3.2.1-2, my computer has shutdown a couple times. They "normal" shutdowns as in I will press the shutdown button in my de and computer actually shuts down. Also a couple times when turning my computer off i will have to reboot because my laptop touchpad is not working. going into a tty i do rmmod psmouse and it will say the module is not loaded, loading the module makes no difference. The last few updates I have also had regressions with my wireless. By default arch blocks my wireless and in rc.local I have rfkill unblock all, but this lately does not always work. I have been manually loading the ath9k driver. My laptop is a gateway nv79c, intel i5, onboard graphics, 4 gb of ram. My wireless card is an atheros ar928x. To be clear, the mouse problem and shutting down has started since updating to 3.2.1-2. Yes I know the kernel was just updated today but I have been using my laptop a lot today.
    Last edited by quasifilmie (2012-01-24 03:21:25)

    I seem to have the same problem. The sound would play in some programs, would not in others, and in all of them when I stop playing, it would repeat the last half second endlessly. Could anybody shed some light on this problem?
    in dmesg:
    AC'97 1 does not respond - RESET
    AC'97 1 access is not valid [0xffffffff], removing mixer.
    ali mixer 1 creating error.
    and in errors.log:
    May 13 09:14:22 aconarch ali15x3_smbus 0000:00:06.0: ALI15X3_smb region uninitialized - upgrade BIOS or use force_addr=0xaddr
    May 13 09:14:22 aconarch ali15x3_smbus 0000:00:06.0: ALI15X3 not detected, module not inserted.
    May 13 09:14:22 aconarch AC'97 1 access is not valid [0xffffffff], removing mixer.
    May 13 09:14:22 aconarch ali mixer 1 creating error.
    EDIT: 'lsmod | grep snd'
    snd_seq_oss 29056 0
    snd_seq_midi_event 6528 1 snd_seq_oss
    snd_seq 46800 4 snd_seq_oss,snd_seq_midi_event
    snd_seq_device 6796 2 snd_seq_oss,snd_seq
    snd_pcm_oss 38816 0
    snd_mixer_oss 14336 1 snd_pcm_oss
    snd_ali5451 19212 1
    snd_ac97_codec 95396 1 snd_ali5451
    ac97_bus 2432 1 snd_ac97_codec
    snd_pcm 68484 3 snd_pcm_oss,snd_ali5451,snd_ac97_codec
    snd_timer 19076 2 snd_seq,snd_pcm
    snd 44388 11 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_ali5451,snd_ac97_codec,snd_pcm,snd_timer
    soundcore 6496 1 snd
    snd_page_alloc 7816 1 snd_pcm
    Last edited by bender02 (2007-05-13 15:41:04)

  • Safari causing kernal panics and random shutdowns and overheating.

    My original Inel macbook pro is getting rather sick and I am hoping to hold out for the new 15 inches when they eventually unpdate.
    However Safari is causig all kinds of hangs restarts kernal panics overheating with my machine and yet if I use google chrome for the exact same web sites these same problems are not present.  I much prefer to be able to keep using safari and I realise that I haev not got the most up to date software since Lion is not supported on my machine but it is as up todate as snow leaopard allows.
    I also realise that a more than 5 year old machine is doing very well especially since it is rarely off. It has outlasted 2 timecapsules and countless airport express but the anomyly between 2 browsers is weird. I doubt this has a solution but maybe the odd apple tech who read this might find it a challenge to know why one browser causes heart issues but another doesn't.

    If you're able to boot, 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.
    ☞ If you’re running Mac OS X 10.7 or later, open LaunchPad. Click Utilities, then Console in the page that opens.
    Select the most recent panic log under System Diagnostic Reports. Post the contents — the text, please, not a screenshot. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header and body of the report, if it’s present (it may not be.) Please don't post "shutdownStall" or "hang" reports.
    If you can't boot in the usual way, try a safe boot. The instructions provided by Apple are as follows:
    Be sure your Mac is shut down.
    Press the power button.
    Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
    Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
    During startup, you’ll see a progress bar, and then the login screen, which appears even if you normally log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    Safe mode is slower than normal, and some things won’t work at all.
    Note: If FileVault is enabled under Mac OS X 10.7 or later, you can’t boot in safe mode.

  • 2.5 y/o macbook develops random shutdown?

    Hi,
    my 2.0 ghz core2duo white macbook has done the random shutdown thing 2 nights in a row, and its never happened before. no warning, no prior indication, it just instantly shuts down. I haven't heard of this developing on an older macbook. Both times the computer was under light load, on battery power and had maybe 20% charge left.
    I did see one thread where on old battery may be an alternative cause, so I downloaded the suggested coconutbattery, which tells me my battery has a capacity of 4036 mAH now, as opposed to 5020 when new. I don't know if this is significant but it doesn't seem that 80% of the original battery capacity is too bad.
    Does anyone have experience of this happening, or any helpful info for me?? This is a pain as I was hoping to use my macbook for some live music soon... not too confident of that now.
    thanks, Simon Gregory

    I'm not sure resetting the SMC is good advice, according this article:
    http://support.apple.com/kb/HT1894
    It says only to do it very very specific issues, and random shutdown is not one of them. The article specifically warns against doing it as a troubleshooting measure...

  • My iPhone 5 randomly shutdown and rebooting doesn't seem to work for me, what should I do?

    It also happens when I'm charging my phone, and also the battery percentage doesn't show that correct battery level not unless I turn off and on.. I tried rebooting the phone but it doesn't seem to work for me, random shutdown still happens..

    Will not turn on, will not turn on unless connected to power, or unexpected power off
    Verify that the Sleep/Wake button functions. If it does not function, inspect it for signs of damage. If the button is damaged or is not functioning when pressed, seek service.
    Check if a Liquid Contact Indicator (LCI) is activated or there are signs of corrosion. Learn about LCIsand corrosion.
    Connect the iPhone to the iPhone's USB power adapter and let it charge for at least ten minutes.
    After at least 30 minutes, if:
    The home screen appears: The iPhone should be working. Update to the latest version of iOS if necessary. Continue charging it until it is completely charged and you see this battery icon in the upper-right corner of the screen . Then unplug the phone from power. If it immediately turns off, seek service.
    The low-battery image appears, even after the phone has charged for at least 20 minutes: See "iPhone displays the low-battery image and is unresponsive" symptom in this article.
    Something other than the Home screen or Low Battery image appears, continue with this article for further troubleshooting steps.
    If the iPhone did not turn on, reset it while connected to the iPhone USB power adapter.
    If the display turns on, go to step 4.
    If the display remains black, go to next step.
    Connect the iPhone to a computer and open iTunes. If iTunes recognizes the iPhone and indicates that it is in recovery mode, attempt to restore the iPhone. If the iPhone doesn't appear in iTunes or if you have difficulties in restoring the iPhone, see this article for further assistance.
    If restoring the iPhone resolved the issue, go to step 4. If restoring the iPhone did not solve the issue, seek service.

  • Unexpected  random shutdowns

    I'm experiencing unexpected random shutdowns every few hours on my macbook (listed below). I did a search on the forum and found a firmware update that is supposed to take care of this, but when I try to run it I'm told I don't need it and the update aborts. no other real symptoms other than getting dumped to a black screen and power-off.
    any ideas from the brain trust?

    Do you have all the latest software updates?

  • White Macbook 2006 random shutdown solved removed cpu heatsink and more

    I picked up a cheap macbook from a secondhand retailer for $300 and it regularly shutdown, froze, restarted as well as the grey kernel panic screen completely random no real pattern. I set about trying to solve the problem swapping ram and hard drive with my identical 2006 macbook (which I had similar problems with last year, fixed that one with a new battery connector cable). The ram and hard drive made no difference so I downloaded istat menus to see if any combination of cpu voltage, current and temperature were causing the random shutdowns. It seemed when the temperature reached certain values the computer would shutdown or freeze(around 30 to 50 degrees). I'd read on other forums about faulty cpu temperature diodes so I reapplied heatsink compound to the cpu heatsink and checked all the wiring for shorts but nothing seemed to solve the problem. I was ready to retire the computer and use it for spares for my other macbook when needed but I pulled the keyboard off one more time and tried something completely radical. This fix requires some forward planning and software installation but it has completely solved my Random shutdowns completely.
    for instructions see my next post *Fix for random shutdowns white macbook*

    Ok this is not for the non technical person but it is quite a simple process with the right instructions.
    This first step is very important install the software coolbook($10) and fan control (Free)( not smc fan control). Set up coolbook to operate the cpu at the lowest speed and voltage for both power adapter and battery(1002MHz and .95Volts). Remove the keyboard to access the computer logic board (instructions can be found at iFixit). Remove the four screws and two connectors holding the heatsink to the logicboard and gently lift the heatsink out (very important that you leave the fan screwed in and connected). Close the computer back up if you wish to test just gently connect the keyboard and loosly sit the keyboard back in. Restart and reset the pram immediately. Let the computer boot up and then open system preferences and configure Fan Control to your liking. So far no random shutdowns for over a week (was getting many a day previously.

  • Random shutdowns: my experience, and a suggestion

    I own a BlackBook whose random shutdowns began a couple of weeks ago.
    During my first trip to my local Genius Bar, the guy behind the counter reset the PMU and PRAM, and was unable to reproduce the problem, and sent me on my way.
    The random shutdowns continued.
    During my second trip to the Genius Bar, the guy was able to boot the machine from another drive, and was able to reproduce the problem. The machine was sent to the repair center for servicing. I got it back a few days later.
    Random shutdowns have still occurred, but I find that if I reset the PRAM as the machine is booting, and wait for at least three startup chimes before letting go of the key combination (control-option-P-R), the machine seems to stabilize and not shut down on its own, at least so far.
    Before repair, the machine was also exhibiting the "vertical colored lines at startup" problem. Before that, it needed a replacement power adapter and a replacement battery (the battery was refusing to take a charge or even be recognized by the computer).
    Various theories for the cause or causes of the problem with random shutdowns have been suggested -- along with a number of magic-bullet solutions from different sources. My guess is that even Apple isn't sure what's causing the issue, and there's certainly no foolproof solution that the user can apply. We'll just have to wait and see what comes of the investigations.
    Despite these problems, I still love the BlackBook and think it's perhaps the most beautifully designed computer ever made. I assume that once these growing pains subside, Apple will have a total winner on its hands.
    MacBook (black) 13"   Mac OS X (10.4.7)  

    I have a whitebook bought in June, shutdowns started about 6 weeks after I got it. Did the whole tech support line thing several times resetting various things etc. No change. Sent it in for repair with a strong encouragement that it would only take 48 hours. It is now 10 days later and repair is still on hold. Sent in several "why is this dragging on" and got nice automatic reponse saying they would respond in a day or two. No real responses yet. Called today the helpful tech said they would check and see what was holding things up and let me know when I called back in 48 hours. Assured me I would not be without my Macbook more than a week longer. Have missed work and have a presentation on Friday that I will have to do without it. Had I known it would take this long I would have taken my chance that it would not shut down mid stream in the presentation. I am very disapointed with Apple at this point. Have been a long time user and own stock etc. This is the worse customer service I have gotten on a computer problem, personal or business. Apple needs to realize they have a batch of lemons on their hands and bite the bullet and replace them. I am not encouraged to hear others are getting their books back repaired only to find the problem on going.

  • Random shutdown issues, battery, and overheating.

    Hi,
    About two weeks ago, I've experienced random shutdowns on my MacBook Pro (Bought it on October).
    I am not sure if all this problem was about battery issues. First I've charged it for the first time and only lasted 1 hour. then I recalibrated it and now it last 2 hours and a bit more.
    Now, apart from having battery issue, I've experienced random shutdowns from my laptop. I had installed all the available updates for my laptop.
    Reading all the posted topics about heat, shutdowns and batteries, maybe my problem is just overheating.
    So I've installed the fan control, adjusted the speed to 3500 rpm and worked fine.
    But one thing came to my mind:
    Is it safe for the fans to actually force the speed all time? if so, their cycle life could be shorter?.
    On either case, what if the MBP actually has a defective factory error and if I still be using it, it could completely "melt from the inside"?
    Does the battery itself has something to do with the overheating itself?
    Maybe I should call for a laptop replacement as well.
    Any suggestions?

    Your Mac will very likely last as long as you own it or otherwise choose to upgrade. The heat issues posted here are not entirely valid. With that said, you might want to verify that your battery isn’t on the recall list by viewing the link provided below.
    Excerpt:
    "The affected batteries have model number A1175 and a 12-digit serial number that ends with U7SA, U7SB or U7SC. To view the model and serial numbers located on the bottom of the battery, you must remove the battery from the computer. The battery serial number is located above the barcode. See photos below. Only batteries within the noted serial number ranges need to be exchanged."
    https://support.apple.com/macbookpro15/batteryexchange/
    Regards,
     MBP-15"/2.16/2GB RAM/7200/W8612...   Mac OS X (10.4.8)   G4 Tower (OS 9/10), Dell 620 WorkStation (XP Pro), Gateway P4 (XP Home)

  • Random Shutdown and Mooing

    I'm curious. Of those who have MacBooks that exhibit the random shutdown syndrome, how many also have the "mooing" fans? And how many shutdowns have occured to people who don't have a fan that moos?
    My fan mooed and only turned on once at full throttle since I purchased my MacBook, and it started shutting down after about six weeks. I wonder if the problem involves the failure of the fan to cool the logic board (or some other part of the computer), which at some point fails due to the high head.
    For now, my MacBook again works perfectly, but I wonder what will happen in six weeks' time, since I still have the moo.

    I have bought a white MacBook at the Farmer's Market Apple Store in L.A. about a month and a half ago. Since last Sunday, it has been randomly shutting down on me.
    It has happened both when the computer was cool (just turned on) and when the computer was hot (not alarmingly hot, though). It has happened with the computer plugged in and with the computer not plugged in. It has happened before the computer has gone to sleep and after the computer has awaken from sleep, never with any overwhelming workload.
    It seems pretty random to me and, even though I almost never hear the fans, the temperature seems to have nothing to do with it.
    For the past two days, the only way I had to turn it on and not get a shutdown a few seconds later, was to press the on/off button for ten seconds, until the light started blinking fast and it emitted an alien beep before turning on. Even so, it usually shut down after the first time it went to sleep.
    Now that I am back in Brazil, where I live, the Apple phone service tells me they can't offer me any support (even though I bought it less than two months ago), 'cause you only get phone support for three months in the country where you bought the computer. This after two days of getting nothing but a busy signal from both numbers listed for Brazil in the AppleCare Service and Support Guide.
    Granted I haven't bought AppleCare, but this is a major defect and I am appalled that they aren't dealing with this in a more forthcoming way, especially since I am still fully covered by warranty.
    I have entered Brazil legally with my laptop, and for a simple lack of assistance and options, I have left it at an Apple Store in Rio for hardware tests. Unfortunately, my computer started up just fine in front of the tech support guy today, for the first time in nearly three days. Let's hope they can replicate the defect and SOLVE IT, godwilling.
    But I've looked at many forums and found reports of people having to get their logic boards replaced two or three times, isn't Apple at least acknowledging that there is a problem here?

  • Random Shutdown and Previous shutdown cause: -x2

    Hi,
    I had twice "random shutdown" for now. My MacBook is about 4 month old and It happend with about 3 weeks between them.
    I tried stress testing it with 'yes >/dev/null' heating it up and cooling it down several times but I could not reproduce the Problem. However, looking at older system.log files, I found the "Previous shutdown cause: -82" lines in there. My question: Some MBs seem to report -72, others -82 as the shutdown cause known as random shutdown but what actually is the difference? Is it possible to guess the time it will take to get it repaired depending on the shutdown cause (which obviously describe two different conditions)?
    Thanks a lot in advance and sorry for my somewhat clumsy english;-)
    Peter

    I don't know where you are in Austria, but I took my RSD macbook to mcshark in Vienna, and they repaired it, replaced the case, and returned it to me in one day. That was last Friday and it's been working great since. They knew all about the heat sink problem, didn't even ask for my user name or password, left my hard drive completely intact - they were absolutely super.
    If you are anywhere near Vienna, call McShark and make an appointment - they'll repair it quickly for sure.

Maybe you are looking for