dubrovnik incorporated
Level 1 (4 points)
Notebooks

Q: Exciting Kernel Panic Adventures!

So I have a 17-inch Late 2011 MacBook Pro. Last week I upgraded my memory, the existing manufacturer-installed sticks being in need of replacement. I got the new sticks from Crucial, if that means anything. (I can't afford the $700+ memory sticks offered from the Apple website so)

 

I installed the memory a few days ago, and because of a lack of time ran only the basic hardware test before restarting. Everything worked fine. My computer ran no problem, could read and write files which seem to be still valid, could use most of the installed memory with no issues, etc. But having just come off some memory that was starting to go bad I am absolutely terrified of memory errors, so as soon as I got the chance to shut down (last night) I ran the extended hardware test. That showed everything as being fine, but as soon as I rebooted, well...

 

Basically as soon as Chrome re-opened my screen started to take me on a magical mystery tour of screen tearing, blue screens, black screens, white screens, grey screens, the normal screen but with horizontal lines across it, the normal screen but with the left side displaced over to the right side, etc. Finally a kernel panic indicated itself and I rebooted. The first few times, pretty much as soon as applications started to open automatically the same thing would happen (though usually without the kernel panic, instead I just held down the power button to hard-reboot or whatever that's called).

 

I initially assumed it was the logic board as for some reason those always fail in MBPs (in 12 years I've gone through at least six of them), but as far as I can tell, kernel panics are a common outcome of bad memory and the memory was the only thing I'd changed recently. Following vague tips on the apple site and/or vague memories of past computer problems I rebooted in safe mode, where it didn't even get to the login screen before kernel-panicking again, and then tried again (which worked—for a short time—then split-screen effect listed above became permanent and required another reboot). Finally I thought I'd do the hardware test again in both basic and extended mode; both tests indicated no errors. Upon rebooting it seemed things were back to normal, and I was successfully able to make a backup via time machine, but... no. Not back to normal actually. (I've had two kernel panics while trying to write this message, good thing it auto-saves!)

 

Now I'm the first to admit that I'm pretty much the worst possible person at using my hands to do things. I have spatial issues, am pretty ADHD, my hands shake a lot when trying to do delicate things and I'm basically useless. So it's entirely possible I installed the memory incorrectly and it just took a while for the computer to notice. I also don't own a screwdriver in whatever incredibly tiny size Apple makes their laptop case screws (installed the memory in a friend's place, they're out of the country now)

 

So I'm not really sure what the best course of action would be (apart from buying one of those screwdrivers, which I will do once shops are open tomorrow):

- assume the memory is incorrectly installed rather than defective and try to install it better, or switch the positions of the two sticks, or whatever

- assume the memory sticks are defective and, as soon as possible, take them out, put the original (also not very good but at least the kernel didn't panic every five minutes) back, request a replacement or refund from Crucial

- could the problem be in only one of the memory sticks? if so, how do I figure out which one?

- could the problem be in something else? if so, how do I figure out what?

- is my computer itself dying? if so, where can I get a replacement late 2011 17-inch MBP? >_>

 

I'm attaching two crash reports, the first of which showed up after I rebooted following the second hardware test (corresponding to the panic in safe mode), the second of which is from a panic that occurred while I was writing this message.

 

https://www.dropbox.com/s/wz3pu2jg01sl5lq/crash%20report.txt?dl=0

https://www.dropbox.com/s/9mip8py9tknwqh2/crash%20report%202.txt?dl=0

 

(Also possibly worth noting that my machine's temperature was 65-70º C after restarting, which is unusually high, but setting the fans to 5500rpm has brought it down to normal idle temperatures of 50ºish)

MacBook Pro, Mac OS X (10.7.5)

Posted on Jan 31, 2016 9:54 PM

Close
dubrovnik incorporated

Q: Exciting Kernel Panic Adventures!

  • All replies
  • Helpful answers

  • by dubrovnik incorporated,

    dubrovnik incorporated dubrovnik incorporated Jan 31, 2016 10:17 PM in response to dubrovnik incorporated
    Level 1 (4 points)
    Notebooks
    Jan 31, 2016 10:17 PM in response to dubrovnik incorporated

    There's no way to edit posts? Hmm. [Edit: I can edit this post. But not the OP. ]

     

    One other potentially important bit of information. Prior to installing the new memory, the process kernel_task used up 300-350 MB of real memory at startup (more over time as more threads were added or whatever).

     

    Right now, immediately upon starting up, it's using 700-900 MB of real memory and the number climbs a lot more quickly. I don't know if that's just a function of having more physical memory available and therefore the kernel processes being allowed to expand to fill available space. I don't think so.

     

    (Mac OS X 10.7.5)

  • by dubrovnik incorporated,

    dubrovnik incorporated dubrovnik incorporated Feb 3, 2016 12:23 AM in response to dubrovnik incorporated
    Level 1 (4 points)
    Notebooks
    Feb 3, 2016 12:23 AM in response to dubrovnik incorporated

    any help?

  • by K Shaffer,Helpful

    K Shaffer K Shaffer Feb 3, 2016 10:25 PM in response to dubrovnik incorporated
    Level 6 (14,350 points)
    Desktops
    Feb 3, 2016 10:25 PM in response to dubrovnik incorporated

    One of the basic troubleshooting measures, as you've mentioned, is to replace the memory

    chips with the originals and see if that resolves the kernel panic frequency or if other codes

    appear to imply memory alone and not CPU.

     

    If the original RAM were installed, and the computer taken to an Apple Store genius (by

    appointment) to have it checked over, perhaps with a diagnostic tool they'd have, to see

    if the logic board, or cables to the drives, or if other hardware is the cause of the KP's.

     

    • OS X: About kernel panics - Apple Support

    • Mac OS X: How to log a kernel panic - Apple Support

     

    {Note some links to information further down, that may be helpful in perspective; or to

    consider troubleshooting; however to restore the original RAM chips and then contact

    an Apple Store with Genius staff for an appointment (or an Authorized Apple Service

    Provider, an independent reseller service center) to have deep diagnostics performed.

     

     

    Also if there is excess heat, there may be a need for someone to inspect the thermal

    cooling, heat-sink, and the logic board. If used in dusty environs, to chase out dust a

    few times a year.

     

    • MacBookPro 17-inch Unibody Repair guide - iFixit.com:

    https://www.ifixit.com/Device/MacBook_Pro_17%22_Unibody

     

    Some of those models of MacBook Pro with dual graphics, had issues and some errors

    or causes of odd visual effects were due to one of the graphic processors acting up. Not

    sure if that kind of activity resulted in some user experience with kernel panic, or what

    kind of evidence that may create in system logs (console) or if any crash logs appeared.

     

    Curiosity insists that I ask about the identity of your MacBook Pro as verification of the

    computer may help other readers in understanding the issue... as it relates to hardware.

    Kernel Panics can also relate to hardware issues, non-compatible software, or damage.

     

    • Resolving Kernel Panics, archival:

    http://www.thexlab.com/faqs/kernelpanics.html

     

    • Technical Note TN2063: Understanding and Debugging Kernal Panics:

    https://developer.apple.com/library/mac/technotes/tn2063/_index.html

     

    Because the Graphics in the model you have does share a portion of Standard RAM

    memory chip capacity with the rest of the computer, that is where quality memory chips

    of the correct specification can make subtle important difference in function....

     

    Memory from Crucial may be OK, but may not be the exact ones for your MacBook/Pro.

    OWC has been a trusted vendor of tested Mac-centric replacement and upgrade parts.

    • MacBook Pro 17" Late 2011 - View Memory Options - macsales OWC

     

    MacBook Pro (17-inch, Late 2011)

     

    Introduced    October 2011

    Discontinued    June 2012

    Model Identifier    MacBookPro8,3

    Model Number    A1297

    EMC    2564

    Order Number    MD311LL/A

     

    Processor    Intel Core i7 (2760QM, or 2860QM) ("Sandy Bridge")

    Processor Speed    2.4 or 2.5 GHz

    Architecture    64-bit

    Number of Cores    4

    Cache    6 MB (2.4 GHz) or 8 MB (2.5 GHz) shared L3 cache

    System Bus    Intel Direct Media Interface (DMI) at 5 GT/

     

    Graphics Card    AMD Radeon HD 6770M and Intel HD 3000 Graphics

    Graphics Memory    1 GB (6770M) GDDR5 and 384 MB (HD Graphics) DDR3 shared with main memory.

     

    {Specification details courtesy of http://mactracker.ca and MacTracker application}

     

    Assuming this MacBook Pro EFI Firmware Update 2.7 was done; from 2012.

    • MacBook Pro EFI Firmware Update 2.7

     

    Everymac.com details both builds of your MacBookPro8.3 model identifier:

     

    • MacBook Pro "Core i7" 2.4 17" Late 2011 2.4 GHz Core i7 (I7-2760QM)

    • MacBook Pro "Core i7" 2.5 17" Late 2011 2.5 GHz Core i7 (I7-2860QM)


    Did you try to use the Apple Hardware Test for a basic diagnostic in your MacBook/Pro?

    • Using Apple Hardware Test - Apple Support - this may be on original DVD install media

     

    After installing the RAM upgrade, did you try an SMC reset or perhaps NVRAM reset?

    • Resetting the System Management Controller (SMC) on your Mac - Apple Support

    • How to Reset NVRAM on your Mac - Apple Support

     

    These would relate to Troubleshooting; as would a Safe mode startup...

    • Try safe mode if your Mac doesn't finish starting up - Apple Support

     

    You should have the basic tools to open the back of the computer, to access

    the memory chips and hard drive, also to check other hardware, cables, etc.

     

    Sorry to not have a shortcut method to resolve this issue; it will require troubleshooting

    and other related hands-on diagnostic effort to determine the cause(s) of this problem.

     

    In any event...

    Good luck & happy computing!

  • by OGELTHORPE,Helpful

    OGELTHORPE OGELTHORPE Feb 3, 2016 10:25 PM in response to dubrovnik incorporated
    Level 9 (52,323 points)
    Mac OS X
    Feb 3, 2016 10:25 PM in response to dubrovnik incorporated

    These are possible software candidates that may be causing the kernel panics.  Disengage/delete them and see if the panics stop.  Then add them one at a time to find the 'offender'.

     

    Screen Shot 2016-02-03 at 6.29.12 AM.png

    Ciao.

  • by dubrovnik incorporated,

    dubrovnik incorporated dubrovnik incorporated Feb 3, 2016 10:18 PM in response to K Shaffer
    Level 1 (4 points)
    Notebooks
    Feb 3, 2016 10:18 PM in response to K Shaffer

    @ K Shaffer

    Ok, so what's been happening:

     

    Over the last few days I've been basically unable to reproduce the kernel panics or screen going crazy. However, at one point when I was trying to do something (download a large file from the internet) the computer froze, I hard-rebooted, and on the reboot it never reached the login screen (instead stalling on a grey screen and then hard-shutdowning itself, somehow). On subsequent reboot it worked fine.

     

    I've just reset the PRAM, no problems yet. Don't know why I didn't think to do that before, lol. In between the last reboot and now I've been running the machine at fairly high capacity. The one thing I've noticed is again about the memory—my impression was always that given a certain amount of time, inactive memory will revert to being free. For me, that never happened, or only in minimal amounts; before I shut down to do the PRAM reset, I had 10.31 GB of inactive memory and less than 100 MB of free, and it had swapped a little bit, about 29 MB.

     

    (Just to digress about swap for a sec, that was the biggest problem with the old memory—it would regularly run up 30-40 GB of swap even when I wasn't doing anything much. I was told it was because I needed more physical RAM, but the problem had only been occurring for about a year or so, and I got my laptop in 2012. So there's that. I know 29 MB isn't much, but I believe—not know, mind—that you shouldn't have any swap used if you have enough RAM.)

     

    That and kernel_task is still overusing memory. Currently 709MB just after restarting (nothing running except chrome, activity monitor, skype & dropbox) but it's been over 1GB at times. I haven't updated my operating system at all, just the memory; this is the exact same kernel that was previously using only 300-500MB on average. I don't know what's wrong, though. The OS seems to be working fine, at least since the panics stopped.

     

    My system specs (I assume that's what you meant by identity?) are as you list—the Intel HD Graphics 3000 is 512 MB not 384, though. Processor is the 2.4 GHz one. Memory is 16GB (two 8GB cards). HD capacity 750GB, split into 625GB for OSX (170GB free) and 125GB for Windows 7 (45GB free). I don't know what other information would be useful?

     

    Yes I used the Apple Hardware Test twice (startup and pressing D—I don't have my original install disk) as detailed in the original report. Results negative.

     

    There is no Apple Store in my country; there's a service provider not far though. But before bringing it in I kind of want to replicate the problem to make sure that they can do so as well; otherwise I'll get a bill for nothing (applecare having already expired, of course).

     

    Regarding excess heat I've just been setting the fans to 5500 with SMC Fan Control whenever I feel I'm about to do something cpu-intensive. So far, no issues, except that they're noisy >_>

     

    @ Oglethorpe

    Thanks! I'll try getting rid of those and see if it helps. I obviously don't need Virtual Box anymore since I have a windows partition, and no idea where the others could be from.

  • by K Shaffer,

    K Shaffer K Shaffer Feb 4, 2016 1:48 AM in response to dubrovnik incorporated
    Level 6 (14,350 points)
    Desktops
    Feb 4, 2016 1:48 AM in response to dubrovnik incorporated

    If the main hard drive were upgraded to another brand or type that does Not

    have the sensor built-in, Fans would run fast most or all the time; even cold.

     

    The cure for the fans issue was the fan control app. An adapter exists for those

    who upgrade or replaced a HDD with a new one, or with an SSD that has no

    sensor port that an original hard drive would have. Depending on the model,

    the actual fix would be easier if you were to locate the original type drive if you

    had to replace one. Or of the same series with the correct Sensor. You could

    see the macsales.com site for their drive sensor that attaches external on HDD.

     

    Not sure about the rest of your post; the time here is almost 1AM Thurs and it

    really is 'past my bedtime' so to speak. Perhaps another will see your reply &

    offer advice based on the situation you have more closely detailed.

     

    The kernel panic issue, as it relates to hardware and or software, could have a

    bearing on changes in configuration in either area or both. This is where effort

    to troubleshoot may be time consuming.

     

    Sorry to not be much help...!