Skip navigation

Kernel Panic - Help wanted please!

3412 Views 11 Replies Latest reply: Feb 10, 2013 8:25 AM by WZZZ RSS
nnaattiiee Calculating status...
Currently Being Moderated
Feb 1, 2013 3:23 PM

Really need someones help on finding what is the problem with my little Macbook...

I have had no problems whatsoever over the past year, until I loaded it up on the other morning and the dreaded kernel panic screen popped up.

I was hoping it was a software problem but even after erasing the hard drive, reinstalling the system and updating, it's not solved. The crash report is below, any help on deciphering it will be greatly appreciated! Also I can boot up fine in safe mode...



panic (cpu 0 caller 0x563ebd) : "Unable to find driver for this platform :

\ "ACPI \ ". \ n"@/ SourceCache / xnu / xnu - 1504.15.3 / iokit / kernel / IOPlatformExpert.cpp : 1387

Debugger called : <panic>

Backtrace (cpu 0) , Frame : Return Address (4 potential args on stack)

0x79f93da8 : 0x21b837 (0x5dd7fc 0x79f93ddc 0x223ce1 0x0)

0x79f93df8 : 0x563ebd (0x5e71ac 0xb916500 0x79f93e28 0xb97f640)

0x79f93e18 : 0x543f60 (0xb978d00 0xb978d80 0x1 0x506b76)

0x79f93e78 : 0x542137 (0xb978d80 0xb978d00 0xb97f680 0x50aa3e)

0x79f93f28 : 0x5426e9 (0xb978d80 0xb97f740 0x8 0xffffffff)

0x79f93f78 : 0x5443d5 (0xb978d80 0x0 0x79f93fac 0x1)

0x79f93fc8 :0x2a179c (0xb9165c0 0x0 0x56803fe9 0xad007fd2)


BSD process name corresponding to current thread : Unknown


Mac OS version : Not yet set


Kernel version : Darwin Kernel Version 10.8.0 Tue Jun 7 16.33.36 pm


System uptime in nanoseconds : 239533251

MacBook, Mac OS X (10.6.8)
  • ds store Level 7 Level 7 (30,305 points)
    Currently Being Moderated
    Feb 1, 2013 4:31 PM (in response to nnaattiiee)

    All I can suggest is try a hardware check


    Instructions: Apple: Hardware Test



    ..Step by Step to fix your Mac

  • ds store Level 7 Level 7 (30,305 points)
    Currently Being Moderated
    Feb 3, 2013 7:00 AM (in response to nnaattiiee)

    Take the machine in to the closest Apple Store and they will evaluate it.


    You can call Apple to get a replacement boot disk.

  • WZZZ Level 6 Level 6 (11,875 points)
    Currently Being Moderated
    Feb 5, 2013 10:11 AM (in response to nnaattiiee)

    If you reinstalled any third party applications after doing the erase and install, these might be causing the KPs. A reinstall in that case won't prove it isn't software related.


    If you don't have the Snow Leopard Install DVD, how did you reinstall? You reinstalled 10.8?


    Is there more to the panic log than that? If so, can you post the full log.


    You appear to be running 10.8, why then do you want to install Snow Leopard?


    What replacement discs is Apple sending? As replacements, they would be sending the grey machine specific discs that originally came with the computer.

  • WZZZ Level 6 Level 6 (11,875 points)
    Currently Being Moderated
    Feb 5, 2013 12:05 PM (in response to nnaattiiee)

    Might try reseating the RAM. RAM is a likely culprit with KPs. You can trust a positive, but the Hardware Test isn't a very reliable diagnostic for negatives. You could run it a few times in extended.

  • WZZZ Level 6 Level 6 (11,875 points)
    Currently Being Moderated
    Feb 5, 2013 1:25 PM (in response to nnaattiiee)

    Just that the Hardware Test isn't really great at finding errors, which is to say it isn't great at diagnosing. So if it comes back empty handed (a negative), that doesn't mean nothing is wrong. But if it reports an error (a positive) it can be trusted.


    If you can boot the computer and get on the Internet to download memtest, it would run a better check on the RAM than the AHT. But even there, as RAM errors are known to be elusive and random, it might take a fair number of loops to find anything.


    So, in case you can:


    To test the memory, get memtest and run it in single user mode, where it will test as much memory as possible, more than with the OS loaded.


    You can get memtest + directions from the link below. However, ignore running it from Terminal. Instead, boot into SU Mode, CMD-S at the startup chime. (Best to startup from a full shutdown.)


    At the prompt, simply type /usr/bin/memtest all 3 -L (From this link It will be installed in /usr/bin/) Then hit return. This will run three loops of memtest and create a log in Console in Utilties. The log may also appear in the Hard Drive Folder (Macintosh HD, unless you have renamed it), which is either on your Desktop or in the sidebar of a Finder window.


    If you want to run memtest longer, which may be advisable, since RAM errors can be very elusive, you can change the number of loops it runs by changing the number. For example, to run 8 loops you would enter /usr/bin/memtest all 8 -L.


    If you want to quit the test at any time, just hit control-c


    When finished, you can just type in "reboot" and hit return.



    Direct link for the download.





    Here is an Apple article that shows how to get at the RAM on a MacBook



    Message was edited by: WZZZ

  • WZZZ Level 6 Level 6 (11,875 points)
    Currently Being Moderated
    Feb 10, 2013 8:25 AM (in response to nnaattiiee)

    It's not that the other 6GB is responsible for the KPs--and I'm kind of confused about this myself, and will have to do some more research as to how to get memtest to test all the RAM. (I believe memtest was developed before RAM capacities became so large.)


    On all other systems, memtest executes in 32-bit mode with a maximum testable limit of 2 GB.


    It might be that it tests incrementally more of the RAM on subsequent passes. But don't really know. I will have to look into this.


    It does sound like you need to bring the MB in for a proper, professional diagnosis.


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.