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

How can I identify the source of my kernel panic?

I've got a 5 year old iMac (4 gigs of RAM, 640 Harddrive) running leopard. Recently, I got a kernel panic. I reseached online and I tried some of the methods for fixing it. I get the panic when using the internet (firefox and safari both) but my server is all good. I've deleted almost all 3rd party programs except the neccesities like Office. I've tried the SafeBoot restart and I got no panic, but once I restarted normally, it returned. I'm not savy enough to fiddle with console so I haven't tried any of those methods. I've never experienced any trouble on my iMac before either. I did try switching accounts on my computer and I experienced to kernel panic however tht may have just been luck that it hasn't happened yet. I did the Verbose Startup but I don't know how to interpret that so I was wondering if there is a way of determining how I got the kernel panic so I could look for a cure to that exact problem.

iMac, Mac OS X (10.5.8)

Posted on Nov 29, 2011 9:26 PM

Reply
3 replies

Nov 29, 2011 9:48 PM in response to iMackyD

Hello, open Console & check the system log for the Date/Time of the last KP & restart.


I think you should get Applejack...


http://www.macupdate.com/info.php/id/15667/applejack


After installing, reboot holding down CMD+s, (+s), then when the DOS like prompt shows, type in...


applejack AUTO


Then let it do all 6 of it's things.


At least it'll eliminate some questions if it doesn't fix it.


The 6 things it does are...


Correct any Disk problems.

Repair Permissions.

Clear out Cache Files.

Repair/check several plist files.

Dump the VM files for a fresh start.

Trash old Log files.


First reboot will be slower, sometimes 2 or 3 restarts will be required for full benefit... my guess is files relying upon other files relying upon other files! :-)


Disconnect the USB cable from any Uninterruptible Power Supply so the system doesn't shut down in the middle of the process.


One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for problem in Safe Mode...


PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive


Reboot, test again.


If it only does it in Regular Boot, then it could be some hardware problem like Video card, (Quartz is turned off in Safe Mode), or Airport in 10.4 & below, or 3rd party add-on, Check System Preferences>Accounts>Login Items window to see if it or something relevant is listed.


Check the System Preferences>Other Row, for 3rd party Pref Panes.


Also look in these if they exist, some are invisible...


/private/var/run/StartupItems

/Library/StartupItems

/System/Library/StartupItems

/System/Library/LaunchDaemons

/Library/LaunchDaemons

Nov 30, 2011 5:19 AM in response to iMackyD

Kernel panics are usually caused by a hardware problem – frequently RAM, a USB device or a Firewire device. What external devices do you have connected? When trying to troubleshoot problems, disconnect all external devices except your monitor, keyboard and mouse. Do you experience the same problems?


To eliminate RAM being the problem, Look at this link: Testing RAM @ http://guides.macrumors.com/Testing_RAM Then download & use Memtest & Ramber.


Do you have an Apple Hardware Test disc (the AHT is on the Install/Restore DVD that came with your Mac)? Running the Apple Hardware Test in Loop Mode is an excellent troubleshooting step for finding intermittent hardware problems. It is especially useful when troubleshooting intermittent kernel panics. If Loop Mode is supported by the version of the Apple Hardware Test you are using, you run the Extended Test in Loop Mode by pressing Control-L before starting the test. Looping On should appear in the right window. Then click the Extended Test button.The test will run continuously until a problem is found. If a problem is found, the test will cease to loop, indicating the problem it found. If the test fails, be sure to write down the exact message associated with the failure.In some cases, RAM problems did not show up until nearly 40 loops, so give it a good run.


http://www.thexlab.com/faqs/kernelpanics.htmlResolving Kernel Panics


http://www.macfixit.com/article.php?story=20060911080447777Avoiding and eliminating Kernel panics


http://macosg.com/group/viewtopic.php?t=80012-Step Program to Isolate Freezes and/or Kernel Panics



 Cheers, Tom 😉

How can I identify the source of my kernel panic?

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