Macbook Pro mid 2010 constantly freezing

Discussion in 'Mac Basics and Help' started by hirumaui, Sep 24, 2013.

  1. hirumaui, Sep 24, 2013
    Last edited: Sep 24, 2013

    hirumaui macrumors newbie

    Joined:
    Sep 24, 2013
    #1
    Aloha , I recently installed a new logic board and SSD in this used machine. Now I am getting multiple daily freezes . System using 150% + processor.
    Could it be my slow satellite connection? (com.apple.com errors)

    Could it be that I have the updated to Mt Lion OS on the 2nd Original HD ?(I boot from SSD in optical drive bay)

    So many console errors.. Don't know where to start.

    Could my Chinese - repaired logic board be funky? My SSD?

    It crashes less often when not connected to internet

    Running Firefox 24 as primary browser and latest Chrome when I need to down load a Vimeo video.
    Please help...Mahalo.

    Model Name: MacBook Pro
    Model Identifier: MacBookPro7,1
    Processor Name: Intel Core 2 Duo
    Processor Speed: 2.4 GHz
    Number of Processors: 1
    Total Number of Cores: 2
    L2 Cache: 3 MB
    Memory: 4 GB
    Bus Speed: 1.07 GHz
    Boot ROM Version: MBP71.0039.B0E
    SMC Version (system): 1.62f7
    Serial Number (system): WQ029PGWATM
    Hardware UUID: 982555AE-20CF-512C-85DE-87CA1589C9EC
    Sudden Motion Sensor:
    State: Enabled


    38 Google Chrome Framework 0x007a6e10 ChromeMain + 7611184
    39 Google Chrome Framework 0x007bcab1 ChromeMain + 7700433
    40 Google Chrome Framework 0x001de6e1 ChromeMain + 1547265
    41 Google Chrome Framework 0x02b52090 ChromeMain + 45012400
    42 Google Chrome Framework 0x02b52b63 ChromeMain + 45015171
    43 Google Chrome Framework 0x02b4ea01 ChromeMain + 44998433
    44 Google Chrome Framework 0x00686083 ChromeMain + 6428067
    45 Google Chrome Framework 0x00686baf ChromeMain + 6430927
    46 Google Chrome Framework 0x00685e60 ChromeMain + 6427520
    47 Google Chrome Framework 0x00064b09 ChromeMain + 41
    48 Google Chrome 0x0005ef78 main + 24
    49 Google Chrome 0x0005ef55 Google Chrome + 3925
    )
    9/24/13 4:49:54.000 AM kernel[0]: IOHIDSystem cursor update overdue. Resending.
    9/24/13 4:50:03.000 AM kernel[0]: IOHIDSystem cursor update overdue. Resending.
    9/24/13 4:50:06.293 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 4:50:06.584 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 1.30 seconds (server forcibly re-enabled them after 1.00 seconds)
    9/24/13 4:51:48.460 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 4:51:48.796 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 1.36 seconds (server forcibly re-enabled them after 1.02 seconds)
    9/24/13 4:52:11.149 AM com.apple.time[166]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
    9/24/13 4:53:39.603 AM Dock[182]: find_shared_window: WID 216
    9/24/13 4:53:39.604 AM Dock[182]: CGSGetWindowTags: Invalid window 0xd8
    9/24/13 4:53:39.614 AM Dock[182]: find_shared_window: WID 215
    9/24/13 4:53:39.614 AM Dock[182]: CGSGetWindowTags: Invalid window 0xd7
    9/24/13 4:53:39.619 AM Dock[182]: find_shared_window: WID 214
    9/24/13 4:53:39.619 AM Dock[182]: CGSGetWindowTags: Invalid window 0xd6
    9/24/13 4:53:41.397 AM Dock[182]: find_shared_window: WID 231
    9/24/13 4:53:41.397 AM Dock[182]: CGSGetWindowTags: Invalid window 0xe7
    9/24/13 4:53:41.401 AM Dock[182]: find_shared_window: WID 230
    9/24/13 4:53:41.404 AM Dock[182]: CGSGetWindowTags: Invalid window 0xe6
    9/24/13 4:53:41.405 AM Dock[182]: find_shared_window: WID 229
    9/24/13 4:53:41.405 AM Dock[182]: CGSGetWindowTags: Invalid window 0xe5
    9/24/13 4:53:46.382 AM Dock[182]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
    9/24/13 4:53:50.167 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 4:53:52.268 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Console" after 3.11 seconds (server forcibly re-enabled them after 1.01 seconds)
    9/24/13 4:56:00.891 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 4:56:02.086 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 2.20 seconds (server forcibly re-enabled them after 1.01 seconds)
    9/24/13 4:56:03.833 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 4:56:04.227 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 1.40 seconds (server forcibly re-enabled them after 1.01 seconds)
    9/24/13 4:56:06.115 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 4:56:06.146 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 1.19 seconds (server forcibly re-enabled them after 1.16 seconds)
    9/24/13 4:56:07.192 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 4:56:07.333 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 1.17 seconds (server forcibly re-enabled them after 1.00 seconds)
    9/24/13 4:56:10.574 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 4:56:11.481 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Console" after 1.91 seconds (server forcibly re-enabled them after 1.00 seconds)
    9/24/13 4:56:16.404 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 4:56:17.387 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 1.98 seconds (server forcibly re-enabled them after 1.00 seconds)
    9/24/13 4:56:18.430 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 4:56:18.584 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 1.17 seconds (server forcibly re-enabled them after 1.02 seconds)
    9/24/13 4:56:40.410 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 4:56:41.795 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 2.42 seconds (server forcibly re-enabled them after 1.04 seconds)
    9/24/13 4:56:44.564 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 4:56:44.564 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 4:56:45.262 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Console" after 1.73 seconds (server forcibly re-enabled them after 1.02 seconds)
    9/24/13 4:56:45.673 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 2.12 seconds (server forcibly re-enabled them after 1.01 seconds)
    9/24/13 4:56:55.129 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 4:56:58.386 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 4.27 seconds (server forcibly re-enabled them after 1.01 seconds)
    9/24/13 4:57:00.761 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 4:57:01.336 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Console" after 1.59 seconds (server forcibly re-enabled them after 1.01 seconds)
    9/24/13 5:01:16.466 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 5:01:16.881 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 1.42 seconds (server forcibly re-enabled them after 1.01 seconds)
    9/24/13 5:01:21.262 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 5:01:21.606 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 1.41 seconds (server forcibly re-enabled them after 1.06 seconds)
    9/24/13 5:01:22.707 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 5:01:25.434 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 3.73 seconds (server forcibly re-enabled them after 1.00 seconds)
    9/24/13 5:01:27.389 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 5:01:28.825 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 5:01:28.856 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 2.48 seconds (server forcibly re-enabled them after 1.01 seconds)
    9/24/13 5:01:29.704 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Console" after 1.89 seconds (server forcibly re-enabled them after 1.01 seconds)
    9/24/13 5:01:30.810 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 5:01:31.552 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Console" after 1.79 seconds (server forcibly re-enabled them after 1.05 seconds)
    9/24/13 5:01:33.383 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 5:01:34.706 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 2.32 seconds (server forcibly re-enabled them after 1.00 seconds)
    9/24/13 5:01:39.127 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 5:01:40.007 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 1.88 seconds (server forcibly re-enabled them after 1.00 seconds)
    9/24/13 5:01:40.953 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 5:01:41.957 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Console" after 2.02 seconds (server forcibly re-enabled them after 1.01 seconds)
    9/24/13 5:01:43.614 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 5:01:43.740 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 1.22 seconds (server forcibly re-enabled them after 1.10 seconds)
    9/24/13 5:01:45.650 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 5:01:45.658 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Console" after 1.22 seconds (server forcibly re-enabled them after 1.21 seconds)
    9/24/13 5:01:49.039 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 5:01:49.301 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 5:01:49.710 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 1.67 seconds (server forcibly re-enabled them after 1.00 seconds)
    9/24/13 5:01:50.328 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Console" after 2.05 seconds (server forcibly re-enabled them after 1.02 seconds)
    9/24/13 5:01:54.136 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 5:01:54.225 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Console" after 1.09 seconds (server forcibly re-enabled them after 1.00 seconds)
    9/24/13 5:01:56.374 AM WindowServer[88]: CGXDisableUpdate: UI updates were forcibly disabled by application "Mail" for over 1.00 seconds. Server has re-enabled them.
    9/24/13 5:01:56.550 AM WindowServer[88]: reenable_update_for_connection: UI updates were finally reenabled by application "Mail" after 1.19 seconds (server forcibly re-enabled them after 1.01 seconds)
    9/24/13 5:02:05.169 AM lsboxd[218]: @AE relay 4755524c:4755524c
    9/24/13 5:02:07.518 AM lsboxd[218]: @AE relay 4755524c:4755524c
    9/24/13 5:05:26.281 AM Google Chrome Helper EH[326]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 3. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
    9/24/13 5:05:26.286 AM Google Chrome Helper EH[326]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 3. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
     
  2. r0k macrumors 68040

    r0k

    Joined:
    Mar 3, 2008
    Location:
    Detroit
    #2
    I put an SSD in my 2008 Macbook and it worked fine for about a day. Then it started having longer and longer freezes. I took it to the Apple store and they booted it over the network to one of their OS images. It ran fine. It wasn't my hardware, it was either my OS install or my SSD. I took out the SSD, went back to my previous drive and returned the SSD to the store.

    The reason I mention this in your thread is I had repeating errors, more than once a second, showing up in my console logs. I can't remember at the moment what they were but I do think they were different than yours. A simple test would be to plug in a different HDD to usb and boot from it. If there are no problems then you can suspect either 1) your OS or 2) your SSD.

    This is why I always recommend booting from an external drive for days or weeks before opening your Mac to put it inside. You can always set the default boot device by holding option when you boot. You can boot from an SSD connected via an SATA to USB cable for weeks until you really convince yourself everything is alright. Then and only then should you reach for your phillips and torx screwdrivers.
     

Share This Page