Slashdot Mirror

← Back to Stories (view on slashdot.org)

2011 MacBook Pros Confirmed To Crash Under Load

Posted by timothy on from the switch-to-multifinder dept.

sammcj writes "2011 MacBook crashing under heavy load?... you are not alone. While trying to figure out what was wrong with my fancy new MacBook I soon realized that the issue is very widespread."

9 of 501 comments (clear)

  1. Re:Well of course by philj · · Score: 5, Informative

    Having read the linked thread, it looks like it's an ATI graphics card driver problem. You can still ssh into a machine that has "crashed under load".

  2. Re:Well of course by Dunbal · · Score: 4, Informative

    You don't get a sandy bridge i7 in a Mac for 1000 pounds, either. Your point?

    --
    Seven puppies were harmed during the making of this post.
  3. It is caused by by toxygen01 · · Score: 5, Informative

    iStat menu (most probably).

    for those tl;dr:
    most of the users report that after uninstalling istat menu pro (and it's "fan control" set to on by default) the problem goes away...

    keep panicking...

    1. Re:It is caused by by sk19842 · · Score: 4, Informative

      iStat isn't necessary to cause the problem. Most people seem to be able to reproduce the issue by opening Photo Booth and trying to install/compile Boost from MacPorts (per these directions). FWIW, following these directions just crashed my 2011 15" MBP.

      It seems to be an ATI graphics card issue, because some people report that they can get a stable machine by setting their graphics to integrated only with gfxCardStatus.

    2. Re:It is caused by by sammcj · · Score: 3, Informative

      That's no true so don't spread uninformed rubbish. There are a pile of people having the problem who have never installed istat pro or any other fan controller.

  4. Software Related by amiga3D · · Score: 4, Informative

    According to the thread this is software related. Removing smcfancontrol seems to be fixing the problem. I have to wonder how that got out the door.

  5. Re:Well of course by beelsebob · · Score: 3, Informative
    1. The CPU you chose is significantly slower than the sandy bridge i5 in the MacBook – they may have the same name (in that they're both i5s), but they're completely different archituctures – what you're doing is like comparing a CoreDuo to a Core2Duo. Anyway, with that in mind, lets use the highest end CPU the vostro can have –the i5 560m, which is still slower than the MacBook Pro's
    2. The graphics card is massively slower – this is one area where sandy bridge made an enormous improvement. You can equip the vostro with a GT310m, which is still slower than the HD 3000 in the MacBook Pro (it's roughly as fast as a GT320m).
    3. The battery life on the vostro is about 3 hours -litterally half that of the MacBook Pro

    With that in mind, and the fact that the dell now costs £999 and is still slower, and still has less battery, no, you've not come close.

  6. Re:Well of course by Anonymous Coward · · Score: 3, Informative

    MacBook Pro 17-inch
    Intel "Sandy Bridge" Core i7 2.2GHz
    4GB DDR3 SDRAM
    AMD Radeon HD 6750M 1 GB GDDR5
    17" 1920x1200 16:10 aspect LED backlit display
    750GB SATA hard drive @ 5400 RPM
    DVD burner
    Illuminated keyboard
    ----
    $2500

    vs

    ASUS G Series G73SW
    Intel "Sandy Bridge" Core i7 2.0GHz
    8GB DDR3 SDRAM
    NVIDIA GeForce GTX 460M 1.5GB GDDR5
    17.3" 1920x1080 16:9 aspect LED backlit, 120Hz 3D display w/3D glasses
    1TB (500GB SATA hard drive with Hybrid SSD x2) @ 7200 RPM
    Blu-Ray burner
    Illuminated keyboard
    ----
    $2000


    Superior hardware in bold.

  7. It's not exactly crashing by Anonymous Coward · · Score: 3, Informative

    This happened to select 2010 models as well - the problem is that the video card overheats and tries to switch back to integrated and the machine barfs all over that. (If you use a laptop cooling pad, this tends not to happen, although there are still some non-heat-related "hangs" in switching between integrated and discrete graphics). If you have ssh enabled, you can indeed see that the machine hasn't crashed, it just isn't drawing to the display (because the display is now connected to the other video card, but something - OpenCL, CoreGraphics, whatnot - didn't get the memo to write to a different display).

    If you can make your machine do this reliably, you can take it to an Apple store, show it to them (being able to ssh helps), and they will replace the machine for you. You may of course get another machine with the same problem, but you also might not...so you have the option of rolling the dice on a new machine until someone comes up with a software fix. (You can also go into the Energy Saver control panel and force the discrete graphics to be used all the time, at the expense of your battery life, which tends to resolve the problem).