how to determine cause of kernel panics - and what to do?

dividenddividend
Posted:
in Genius Bar edited January 2014
I haven't had a kernel panic since December last year; now I have had two in less than 24 hours doing no particular thing. Is it time for me to re-install the entire system and all programmes?



I cannot find a cause for these kernel-panics at all; I haven't installed any new software, I am not doing any special stuff (last kernel panic occured when I closed a Word-window). Any tips?



thanx

Comments

  • Reply 1 of 6
    rick1138rick1138 Posts: 938member
    [quote]



    (last kernel panic occured when I closed a Word-window).



    <hr></blockquote>



    There is your clue,Microsoft is the spawn of Satan and must be exorcised from your machine.
  • Reply 2 of 6
    kelibkelib Posts: 740member
    [quote]Originally posted by Rick1138:

    <strong>



    There is your clue,Microsoft is the spawn of Satan and must be exorcised from your machine.</strong><hr></blockquote> I had a couple of panics within a short period of time without any MS product installed. Hell Apple must be 'the spawn of Satan' so I better erase all Apple SW from my puter or what??? Don't blame MS for Apple's inferiority. I opted for reformat and 'Write to zero' and it's been stable ever since
  • Reply 3 of 6
    neutrino23neutrino23 Posts: 1,562member
    One of the biggest puzzles is why two computers side by side running the same software will behave differently; one running stably and the other crashing. <img src="graemlins/hmmm.gif" border="0" alt="[Hmmm]" />



    Before reinstalling everything I would do some basic maintenance.

    -Boot from the install CD and run the disk checker (forgot the correct name, sort of like disk first aid).

    -Boot OS 9 and rebuild the desktop (recommended to me by Apple tech support at MWSF to help with OS X problems, maybe it affects Classic).

    -Zap the PRAM.

    -Get MacJanitor from Version Tracker and use it to invoke OS X's housekeeping scripts.



    OS X is organized such that the programs can never invade the OS' memory space. However, drivers share space with the OS. Therefore, if you have installed any drivers, ever, for your printer or some other device it would be a good precaution to reinstall them. A faulty application file would only cause the app to crash. A faulty driver file could, in theory, cause a kernel panic.



    I also wouldn't rule out power supply problems. Are you sure the AC power is OK? The power cord isn't loose? It only takes a small glitch in the power to screw up the computer. Measure the AC power (carefully, get someone to help if you are not familiar with this). Is it within spec or is it marginal? Maybe your computer needs a UPS.



    You should keep a log of system crashes so you have some real data to go by. If none of the above helps then you could try a complete reinstall.
  • Reply 4 of 6
    chucksterchuckster Posts: 56member
    dividend,



    See my thread in the Genius Bar "Netinfo, MS office, and kernel panics"



    These computers NEVER have a kernel panic unless someone runs an Office App.
  • Reply 5 of 6
    neutrino23neutrino23 Posts: 1,562member
    [quote]Originally posted by chuckster:

    <strong>dividend,



    See my thread in the Genius Bar "Netinfo, MS office, and kernel panics"



    These computers NEVER have a kernel panic unless someone runs an Office App.</strong><hr></blockquote>



    Anecdotally, I would agree. The one computer that I know that has had several KPs is the one running office. But why should that be? Does ms install some kind of driver that then gives it access to the OS? I thought that the OS was protected from the applications doing anything bad.
  • Reply 6 of 6
    zozo Posts: 3,117member
    I've had MS stuff present during all the KPs Ive had that I can recall.



    I've gotten a lot of probs solved by resetting PRAM

    Don't let it do it once... try keeping it down for 3 consecutive resets. Keep the keys pressed until you hear the 4th startup chime.



    You may also want to check for faulty memory dimms. Either not seated well or what not.
Sign In or Register to comment.