Previous 1 2 Next 19 Replies Latest reply: Apr 28, 2013 1:51 PM by SwankPeRFection
marcel23 Level 1 (0 points)

I recently repaired my 2011 Macbook Pro. The logic board and the harddrive were replaced.
I got it back, upgraded from snow leapord to mountain lion and restored from time machine my mountain lion back up, then immediately updated the software since it was an old back up.


After that I started using it, and it started crashing. The screen glitches (Images below), and restarts. This problem goes away after I reset the PRAM, but then reoccures. It usually occurs when I have more than one application open, it started off while using Chrome. I removed chrome and started using safari and it was okay until I opened iPhoto then it immediately crashed.
Is this a software or a hardware problem? Im thinking of taking it back to Apple but it is a bit far from home.


This is what the screen looks like

MacBook Pro, OS X Mountain Lion (10.8.3)
  • mende1 Level 10 (92,236 points)

    It looks like a display or graphic card problem, so you should take the MacBook to an Apple Store or reseller to get it repaired. All Macs have a 90-day warranty after repairs, so you will have the computer repaired for free

  • marcel23 Level 1 (0 points)

    I thought it would be. Couldn't also be a software issue? It seems like a kernal panic.
    It usually happens when multiple processes are running

  • mende1 Level 10 (92,236 points)

    It's a kernel panic. A kernel panic can be caused by hardware or software, but I need your log to diagnose what your exact problem is

  • Shootist007 Level 6 (16,660 points)

    Are you sure they replaced the logic board with a new one that was checked out as good.


    Never saw any software that would cause those types of screen distortions.

  • marcel23 Level 1 (0 points)

    It happened, restarted itself and this is the report at failure:

    Interval Since Last Panic Report:  21303 sec

    Panics Since Last Report:          1

    Anonymous UUID:                    E0188C01-B862-1D43-DD3A-F3489C5CDA47



    Sun Apr 14 13:10:08 2013

    Panic(CPU 3): Unresponsive processor (this CPU did not acknowledge interrupts) TLB state:0x0

    RAX: 0x000000003e890b58, RBX: 0xffffff8010466800, RCX: 0x0000000000000004, RDX: 0x0000000000000020

    RSP: 0xffffff807e962f00, RBP: 0xffffff807e962f20, RSI: 0x000000403e88f724, RDI: 0xffffff807e955148

    R8:  0xffffff807e8ad078, R9:  0x0000000000000040, R10: 0xffffff7f8561b2d0, R11: 0x0000000100000000

    R12: 0x0000000000000000, R13: 0x0000000000000001, R14: 0x0000000000000000, R15: 0xffffff8010467800

    RFL: 0x0000000000000006, RIP: 0xffffff7f86bb5548, CS:  0x0000000000000008, SS:  0x0000000000000010

    Backtrace (CPU 3), Frame : Return Address

    0xffffff807e962d80 : 0xffffff80044bd721

    0xffffff807e962db0 : 0xffffff80044b74c3

    0xffffff807e962e00 : 0xffffff80044cd80b

    0xffffff807e962f20 : 0xffffff80044ab506

    0xffffff807e962f50 : 0xffffff80044bd75c

    0xffffff807e962f80 : 0xffffff80044b74c3

    0xffffff807e962fd0 : 0xffffff80044cd698

    0xffffff8085003b00 : 0xffffff7f86534e0e

    0xffffff8085003b30 : 0xffffff7f865372ed

    0xffffff8085003b50 : 0xffffff7f84aaa3f3

    0xffffff8085003b70 : 0xffffff7f84aaf750

    0xffffff8085003b90 : 0xffffff7f84ab4b79

    0xffffff8085003bc0 : 0xffffff8004866453

    0xffffff8085003c20 : 0xffffff800486408f

    0xffffff8085003d70 : 0xffffff80044984a1

    0xffffff8085003e80 : 0xffffff8004420aed

    0xffffff8085003eb0 : 0xffffff8004410448

    0xffffff8085003f00 : 0xffffff800441961b

    0xffffff8085003f70 : 0xffffff80044a5dd6

    0xffffff8085003fb0 : 0xffffff80044cdd43

          Kernel Extensions in backtrace:

   [74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7f84aa1000->0xffffff7f84ad8fff

                dependency:[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f84a66000

   [B75BD588-856B-34E5-8B66-7AEAD63B004B]@0xffff ff7f86533000->0xffffff7f86546fff

                dependency:[A35915E8-C1B0-3C0F-81DF-5515BC9002FC]@0xfffff f7f849e6000

                dependency:[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f84a66000

                dependency:[944ED607-EF22-3799-A4D8-C3594C4E2C9B]@0xffffff 7f86100000

                dependency:[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7f84aa1000

          Kernel Extensions in backtrace:

   [BBF44990-49F7-3780-AF55-C2 6B48EDE4C4]@0xffffff7f86bb0000->0xffffff7f86bd8fff



    BSD process name corresponding to current thread: WindowServer



    Mac OS version:




    Kernel version:

    Darwin Kernel Version 12.3.0: Sun Jan  6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64

    Kernel UUID: 3EB7D8A7-C2D3-32EC-80F4-AB37D61492C6

    Kernel slide:     0x0000000004200000

    Kernel text base: 0xffffff8004400000

    System model name: MacBookPro8,2 (Mac-94245A3940C91C80)



    System uptime in nanoseconds: 62065283874

    last loaded kext at 52417535284:          1.9.5d0 (addr 0xffffff7f86bdc000, size 36864)

    loaded kexts:          1.9.5d0          4.1.3f3          1.60          1.0.2d2          100.12.87          3.0          122          2.3.7fc4          4.1.3f3          3.5.10          2.3.7fc4          1.0.0d1          1.6.0          4.1.3f3          8.1.0          2.3.7fc4          8.1.0          170.2.5          7.0.0          3.3.0          1.0.6          3.3.0          1.1.11          3.0.3d1          2.0.3d0          8.1.0          1.0.0          1.0.0          237.1          237.1          237.1          320.15          3.5.5          404          2.3.1          3.0.1          1.0.0d1          1.0.0d1          34          5.5.5          1.4.0          3.6.0b1          614.20.16          4.9.6          2.5.1          5.5.0          5.2.5          1.7          161.0.0          1.7          1.5          1.8          1.9          1.7          1.6          196.0.0          4.0.39          2          196.0.0          10.0.6          1.0          2.2.5          2.3.7fc4          1.8.9fc11          1.6          4.1.3f3          86.0.4          4.1.3f3          30.14          3.3.0          1.0.4          2.3.7          1.0.11d0          1.0.11d0          2.3.7fc4          2.3.7fc4          8.1.0          8.1.0          2.3.7          1.1.8          1.1.8          1.8.9          3.1.4d2          1.0.0          5.3.0d51          1.8.9          1.8.9          1.2.6          237.3          5.2.5          5.5.5          5.2.5          3.5.5          1.7          1.7.1          1.7.1          2.5.1          3.5.5          1.6.3          2.2.6          5.5.5          1.0.2b1          522.4          3.0          4.5.5          2.3.1          5.5.5          1.8.1          1.7          1.1          220.2          1.0.0d1          7          345          1.8          28.21          1.7          2.7.3          1.4          1.0

    panic(cpu 6 caller 0xffffff800449dddb): "TLB invalidation IPI timeout: " "CPU(s) failed to respond to interrupts, unresponsive CPU bitmap: 0x8, NMIPI acks: orig: 0x0, now: 0x1"@/SourceCache/xnu/xnu-2050.22.13/osfmk/x86_64/pmap.c:2337

    Backtrace (CPU 6), Frame : Return Address

    0xffffff8084123aa0 : 0xffffff800441d626

    0xffffff8084123b10 : 0xffffff800449dddb

    0xffffff8084123b90 : 0xffffff80044a25f0

    0xffffff8084123c50 : 0xffffff80044a2e25

    0xffffff8084123ca0 : 0xffffff8004466abc

    0xffffff8084123d90 : 0xffffff800446a990

    0xffffff8084123dc0 : 0xffffff800446548f

    0xffffff8084123df0 : 0xffffff80048011d3

    0xffffff8084123e10 : 0xffffff8004863083

    0xffffff8084123e50 : 0xffffff8004494232

    0xffffff8084123e80 : 0xffffff8004420aed

    0xffffff8084123eb0 : 0xffffff8004410448

    0xffffff8084123f00 : 0xffffff800441961b

    0xffffff8084123f70 : 0xffffff80044a5dd6

    0xffffff8084123fb0 : 0xffffff80044cdd43



    BSD process name corresponding to current thread: airportd

  • marcel23 Level 1 (0 points)

    Is this a CPU issue?

  • clintonfrombirmingham Level 7 (30,000 points)

    Look as if it's a GPU issue, from your kernel panic log.



  • marcel23 Level 1 (0 points)

    That calls for a GPU replacement?
    I'm going to take it back to them.

  • clintonfrombirmingham Level 7 (30,000 points)

    That's exactly what I would suggest...


  • SwankPeRFection Level 4 (1,435 points)

    The new logic board they installed is flaky.  It's either a refurb or one that's just defective.  They will more than likely have to replace it yet again.

  • marcel23 Level 1 (0 points)

    I took it in again, they said it is the graphics and the logic board needs to be replaced again.
    I got it back today, used it for about 20 minutes and the same problem happened! This time, I could still use the screen, it was just split in half and in reverse.
    Any ideas?

  • SwankPeRFection Level 4 (1,435 points)

    Take it back.  It's not fixed until it's fixed.  Get the manager involved this time.  Whomever is working on it, IS NOT fixing the issue.  It's as simple as that.  You contracted them to do a job and they've failed to do it twice now... after 3 times, the lemon law takes affect.  Make sure you state that as well.  They either need to fix your issue correctly this 3rd or final time or they'll be giving you a replacement system at no charge because they cannot fix the current one.  If you encounter resistance, contact Apple corporate relations and file a complaint about this store.  Do not waste your time trying to fix something yourself.  This is why you have warranty or you paid to get the system fixed.  It's their problem, not yours.  Don't stress out over it... just work the system, that's what it's there for.  Don't get stuck with a broken product, this is what they're probably hoping for. (i.e. for you to just go away)

  • marcel23 Level 1 (0 points)

    I like this lemon law, didn't know about it. Thanks!

    I got it repaired out of warranty, they replaced the hard drive and the logic board the first time, the second time they replaced the logic board again free of charge because their replacement products come with a 90 day warranty. Basically if they say that the issue is caused by anything other than the logic board or the hard drive, I have to pay for that. I can't trust them anymore.
    I'm convinced it's a software issue. Are they also responsible for fixing software issues, or is that my problem?

  • SwankPeRFection Level 4 (1,435 points)

    Don't take this the wrong way, because I'm not saying that way, but you are a "dumb user".  All you are concerned with is that you have a working system.  You took it in with a problem, they diagnosed the problem and told you what you should do to fix it and they took your money because it was out of warranty.  The #1 thing Apple stores always want to do is replace the log board because that's all they know.  It's one board that makes up the system if you technically want to look at it that way.  Their thought is... if has to be that... if there's a problem with the roof on the house and we just replace the entire house, that should also fix the roof... right?  Not in the computer world.


    So, that said, what you've got now is a 90 day window in which you have to keep harping that they misdiagnosed your issue #1, misrepaired your system twice now, and you still continue to have a problem.  At this point, you cannot trust what their initial diagnosys was or that any work that they've done to fix it really fixed anything.  You are a simple dumb user (again, just a description, not calling you this) which wants a working system and you've already paid them to fix this one problem for you because that's what they've said they'd do for the fee already paid.  They have failed.  They get one more try and if that doesn't work, they need to do something else to get you going.  Now, the issue with the lemon law thing is... that usually pertains to things under factory warranty.  Yours wasn't under that, but the work that they've done to repair it can still be construde as falling under the new 90 day warranty thing, so technically you could still argue that it would apply to those particular parts in question.


    Do not pay anything else, simply go in, hand it to them and state that it's doing the same thing and you're tired of paying them to fix something they misdiagnosed or haven't properly fixed yet.  Be nice, but firm.  Involve the store manager and inform them that you'll be taking the matter up with Apple corporate relations if they don't do something to resolve your issues.  Simple as that.  Make sure you get names of people you deal with and keep records of all your repair transactions, etc.  You need that paperwork as proof for Apple corp should you need to push it that far.  They may not ask for it, but it doesn't hurt to have it available should they ask for it.  It wouldn't be the first time an Apple store did something to a customer computer out of warranty and didn't document it for them anywhere for Apple to track.


    Good luck.  Again, stop wasting your time trying to fix a problem yourself and running out of your new warranty window... that's what they're hoping will happen.

Previous 1 2 Next