Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Today Mac OS X kernel panicked twice on me. The first time, I got this log. The second time, I got this log.

A few minutes ago, iTunes started sounding blocky, after quitting FireFox everything went back to normal, I am currently using Opera.

These are my system's specs.

EDIT: I ran the apple hardware test and got these results.

Without extended testing:

without extended testing

With extended testing:

with extended testing

share|improve this question
It just works! Except when it doesn't. – hyperslug Oct 1 '09 at 4:37
up vote 1 down vote accepted

Well, there could be quite a few things...

But, here's the top few that might help.

1) Download the Mac OS 10.5.8 Combo-Updater, and run that... 2) Check Virtual Box, and make sure that you have the latest version installed, along with the virtual box tools in your windows session / boot camp.

Let us know what happens.... And try checking your memory as suggested with the other answers...

Try reseting your RAM, and Hard drive. Disconnect all USB & Firewire devices, and if possible try running Tech Tool Pro, in extended hardware tests...

Something is obviously causing a problem... But there doesn't seem to be a obvious reason for it.

What antivirus packages do you have loaded? And do you have Virtual PC installed? Is there any software packages that you have installed or updated recently?

share|improve this answer
I do not have any antivirus programs installed, so far I haven't gotten any kernel panics... – Henri Watson Oct 4 '09 at 4:45

Kernel Panics are nearly always a sign of a hardware issue, most likely one of your memory sticks has developed errors. You can try finding out for sure by either running the Extended Test on the Apple Hardware Test section of your Restore DVD (hold D when you start up and have this disc inserted).

Alternatively you can try using memtest to test your RAM to isolate what stick has gone bad. It's also quite plausible the logic board is having issues instead but your best bet if you can't find out yourself (with the two tests I mentioned) is to take it to your local Apple Authorized Service Provider and have them check it out.

share|improve this answer
Also, even better news, I live in the Dominican Republic, so unlike you guys in the states, it really isn't an option to get it repaired here (WAY too expensive) – Henri Watson Oct 1 '09 at 3:40
If it is a RAM problem, sometimes re-seating the RAM will eliminate the problem. – Richard Hoskins Oct 1 '09 at 4:03
@Henri W: Some of us don't live in the States either. ;-) – Chealion Oct 1 '09 at 4:24
@Chealion: Canada doesn't count, they have Apple owned stores there. ;) – Henri Watson Oct 1 '09 at 4:30

I've seen similar situations (same pmap_flush_tlbs error) with an '07 MacBook Pro (ATI X1600 graphics) from one of our deployed MBPs, and after about 3 or 4 days of wrestling with re-installations, diagnostics, etc, I decided to call Apple and get it replaced.

According to Apple tech, it could be a logic board problem. What you could do is try running diagnostics (hold down 'D' when booting up). However, I strongly recommend you to send it in to Apple - they'll get it replaced pronto.

share|improve this answer
Problem is, I have no warranty because this is a '07 MacBook Pro. – Henri Watson Oct 1 '09 at 3:39
Talk to Apple nicely - explain to them that this is probably a logic board failure and you would like to seek assistance in getting it replaced. – caliban Oct 1 '09 at 3:49
Call them, explain the situation - you will be surprised at how far Apple can go in customer service. – caliban Oct 1 '09 at 3:51

Try turning off Time Machine, and see if the panics cease.

There are a number of known reports of Time Machine causing periodic Kernel panics on some Macs. My wife's MacBook Air had this issue, and a clean install got it running again, but it would eventually re-occur during backups. Becuase the panic doesn't occur on most backups, and the geniuses couldn't reproduce it, they advised her to disable time machine's auto-backups and run it manually every week or two.

Oddly, my machine backs up to the same time machine without incident, but hers continued to have it from time to time even after they replaced her entire motherboard and hard drive (for seemingly unrelated reasons).

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .