Lazentaters

Q: Kernel Panic - Garageband, Google Chrome

Hey, need some help here. I have a 2011 MacBook Pro with OS X 10.6.8. I recently updated Google Chrome (the only recent change/update on my computer) and my system now freezes when I try to use Google Chrome (screen changes to crazy colored lines and freezes along with peripherals, keyboard, and such). I read about some problems that Chrome has caused with Apple drivers causing the system to freeze, but haven't found any solution to my problem. I've been using Safari as a backup browser, but I'd like to be able to use Chrome again. Also, I opened up Garageband yesterday and the same thing happened. Any ideas? I'm hoping this isn't a hardware issue. Just an FYI, I'm not super technical (which is probably why I bought a Mac in the first place), so hoping you guys/girls who are way smarter than me have some answers. I would really appreciate any help I can get! Thanks in advance!

Mac Pro, Mac OS X (10.6.8)

Posted on Sep 6, 2013 2:36 AM

Close

Q: Kernel Panic - Garageband, Google Chrome

  • All replies
  • Helpful answers

Page 1 Next
  • by pennbank,

    pennbank pennbank Sep 6, 2013 3:47 AM in response to Lazentaters
    Level 4 (1,688 points)
    Sep 6, 2013 3:47 AM in response to Lazentaters

    Take a look at this thread

    https://discussions.apple.com/message/22022697#22022697

     

    although this thread for 2012 Macbooks

    https://discussions.apple.com/message/18767808#18767808

     

    See More like this to the right of the forums.

  • by nbar,

    nbar nbar Sep 6, 2013 3:53 AM in response to Lazentaters
    Level 5 (6,980 points)
    Sep 6, 2013 3:53 AM in response to Lazentaters

    Can you post the log file of the Kernel Panic?

  • by Lazentaters,

    Lazentaters Lazentaters Sep 6, 2013 3:57 AM in response to nbar
    Level 1 (0 points)
    Sep 6, 2013 3:57 AM in response to nbar

    Sorry to be an idiot, but how do I check the log file of the Kernel Panic?

  • by nbar,

    nbar nbar Sep 6, 2013 4:28 AM in response to Lazentaters
    Level 5 (6,980 points)
    Sep 6, 2013 4:28 AM in response to Lazentaters

    No, I should have been specific.

     

    If a kernel panic occurs, information is added to a log file in the folder /Library/Logs/DiagnosticReports

     

    This can be accessed via your Console Application.

     

     

    Mac OS X: How to log a kernel panic

     

    OS X: About kernel panics - Apple - Support

  • by Lazentaters,

    Lazentaters Lazentaters Sep 6, 2013 4:33 AM in response to nbar
    Level 1 (0 points)
    Sep 6, 2013 4:33 AM in response to nbar

    the /Library/Logs/DiagnosticReports folder is empty. Maybe not a kernel panic? I used the term after searching the symptoms of what my computer has been experiencing and it seemed to be the best fit.

  • by nbar,

    nbar nbar Sep 6, 2013 4:39 AM in response to Lazentaters
    Level 5 (6,980 points)
    Sep 6, 2013 4:39 AM in response to Lazentaters

    Okay. Open Console. Is there anything listed:

    Screen Shot 2013-09-06 at 7.37.35 AM.png

  • by nbar,

    nbar nbar Sep 6, 2013 4:42 AM in response to Lazentaters
    Level 5 (6,980 points)
    Sep 6, 2013 4:42 AM in response to Lazentaters

    If not...

     

     

    Based on your symptoms (rereading the OP), open Chrome. Mark the exact time you do so. Let the issue recreate itself. Exit the application. In the console, look under system.log and post the output from the time when this occurred.

  • by Lazentaters,

    Lazentaters Lazentaters Sep 6, 2013 4:53 AM in response to nbar
    Level 1 (0 points)
    Sep 6, 2013 4:53 AM in response to nbar

    Here is a screenshot. Also, when the "kernel panic" occurs, the whole system freezes and I have to power off and reboot, so I can't exit the application and check the log, unless it keeps it and I can check after reboot. Anyway, does the screen shot tell you anything?Screen shot 2013-09-06 at 1.57.49 PM.png

  • by nbar,

    nbar nbar Sep 6, 2013 5:12 AM in response to Lazentaters
    Level 5 (6,980 points)
    Sep 6, 2013 5:12 AM in response to Lazentaters

    No, doesn't really help. This is not a kernel panic, however.

     

    1) Open "activity monitor". Go to the 'memory tab' > see "Page Outs" and "Swap Used."

    2) From the Apple Logo in Finder's menu bar > About this Mac > More info.. > Storage >  "" GB free out of "" GB

     

    Post these in your reply (as text).

     

     

    3) Recreate the issue. The log is kept after reboot. Post the system log from when it occurs.

     

    Do these in order, because 1 won't provide much helpful information after rebooting.

  • by Carolyn Samit,

    Carolyn Samit Carolyn Samit Sep 6, 2013 5:21 AM in response to Lazentaters
    Level 10 (122,650 points)
    Apple Music
    Sep 6, 2013 5:21 AM in response to Lazentaters

    Have you checked the startup disk lately?

     

    Launch Disk Utility located in HD > Applications > Utilities

     

    Select the startup disk on the left then select the First Aid tab.

     

    Click Verify Disk  (not Verify Disk Permisions)

     

    If repairs are necessary, boot from your install disc.

     

    Mac OS X v10.6 Snow Leopard: How to Erase and Install


  • by nbar,

    nbar nbar Sep 6, 2013 5:36 AM in response to Carolyn Samit
    Level 5 (6,980 points)
    Sep 6, 2013 5:36 AM in response to Carolyn Samit

    Yes, good point. Does safe mode only verify disk permissions at boot? I'm forgetting now.

  • by Lazentaters,

    Lazentaters Lazentaters Sep 6, 2013 5:54 AM in response to Carolyn Samit
    Level 1 (0 points)
    Sep 6, 2013 5:54 AM in response to Carolyn Samit

    Everything checked out OK with the Verify Disk. Will try nbar's suggestion next.

  • by Lazentaters,

    Lazentaters Lazentaters Sep 6, 2013 12:34 PM in response to nbar
    Level 1 (0 points)
    Sep 6, 2013 12:34 PM in response to nbar

    Ok, for some reason it took about 6 hours of using Chrome and Garageband to get the same error (system freeze). Here are the results:

     

    1) "Page Outs" and "Swap Used" both read 0 bytes

     

    2) 15.24 GB free out of 499.76

     

    3) The bolded/underlined line is the time right before the error occurred

     

    Sep  6 21:24:33 Matt-Lazenbys-MacBook-Pro com.apple.launchd.peruser.501[98] (com.spotify.webhelper): Throttling respawn: Will start in 10 seconds

    Sep  6 21:24:43 Matt-Lazenbys-MacBook-Pro com.apple.launchd.peruser.501[98] (com.spotify.webhelper[4030]): posix_spawn("/Users/mattlazenby/Library/Application Support/Spotify/SpotifyWebHelper", ...): No such file or directory

    Sep  6 21:24:43 Matt-Lazenbys-MacBook-Pro com.apple.launchd.peruser.501[98] (com.spotify.webhelper[4030]): Exited with exit code: 1

    Sep  6 21:24:43 Matt-Lazenbys-MacBook-Pro com.apple.launchd.peruser.501[98] (com.spotify.webhelper): Throttling respawn: Will start in 10 seconds

    Sep  6 21:24:53 Matt-Lazenbys-MacBook-Pro com.apple.launchd.peruser.501[98] (com.spotify.webhelper[4031]): posix_spawn("/Users/mattlazenby/Library/Application Support/Spotify/SpotifyWebHelper", ...): No such file or directory

    Sep  6 21:24:53 Matt-Lazenbys-MacBook-Pro com.apple.launchd.peruser.501[98] (com.spotify.webhelper[4031]): Exited with exit code: 1

    Sep  6 21:24:53 Matt-Lazenbys-MacBook-Pro com.apple.launchd.peruser.501[98] (com.spotify.webhelper): Throttling respawn: Will start in 10 seconds

    Sep  6 21:25:40 localhost com.apple.launchd[1]: *** launchd[1] has started up. ***

    Sep  6 21:25:47 localhost DirectoryService[15]: Improper shutdown detected

    Sep  6 21:25:54 localhost bootlog[40]: BOOT_TIME: 1378495534 0

    Sep  6 21:25:54 localhost fseventsd[33]: event logs in /.fseventsd out of sync with volume.  destroying old logs. (28986 20 29046)

    Sep  6 21:25:54 localhost fseventsd[33]: log dir: /.fseventsd getting new uuid: B51908A2-578E-4DA8-BFEF-F116D48129B0

  • by nbar,

    nbar nbar Sep 6, 2013 4:41 PM in response to Lazentaters
    Level 5 (6,980 points)
    Sep 6, 2013 4:41 PM in response to Lazentaters

    2) 15.24 GB free out of 499.76

     

     

    You need to free up disk space. You should have at least 10% of your total HDD space free at all times. This will definitely help the slow performance issue.

Page 1 Next