Previous 1 143 144 145 146 147 Next 2,929 Replies Latest reply: Sep 3, 2014 6:33 PM by TiTi SS Go to original post Branched to a new discussion.
  • Smartie777 Level 1 (0 points)

    When I went to the Genius Bar they had a new diagnostic test specificly for our problem and the test failed with the words: swap MLB. So from my point of you, nobody needs to convince them.

  • Anastasis Level 1 (0 points)

    Picking up my MacBook Pro from the Apple store today after a logic board replacement. Hoping this resolves everything!

  • Ian Kelleigh Level 1 (140 points)

    After a full week of use after the new logic board replacement (post video update), I have not had one single BSOD or crash of any kind. Lion and Boot Camp run perfectly.

  • Dugby Level 1 (0 points)

    This is about the third BSOD  since I did all the up dates.  Does this look like it need a logic board replacement?


    nterval Since Last Panic Report:  226167 sec

    Panics Since Last Report:          1

    Anonymous UUID:                    350C16BD-B70C-4BAF-95E1-9FEB6CD0A899


    Mon Nov  7 19:52:43 2011

    panic(cpu 0 caller 0xffffff7f809f100b): NVRM[0/1:0:0]: Read Error 0x0061002c: CFG 0x0a2910de 0x00100406 0xc0000000, BAR0 0xc0000000 0xffffff8115e10000 0x0a5480a2, D0, P3/4

    Backtrace (CPU 0), Frame : Return Address

    0xffffff8115a4bc80 : 0xffffff8000220702

    0xffffff8115a4bd00 : 0xffffff7f809f100b

    0xffffff8115a4bd90 : 0xffffff7f80ae1120

    0xffffff8115a4bde0 : 0xffffff7f80ce4500

    0xffffff8115a4be00 : 0xffffff7f80aa9d5f

    0xffffff8115a4be20 : 0xffffff7f80b520c6

    0xffffff8115a4be90 : 0xffffff7f809ddeda

    0xffffff8115a4bf40 : 0xffffff7f80997b42

    0xffffff8115a4bf70 : 0xffffff800023db2c

    0xffffff8115a4bfb0 : 0xffffff8000820057

          Kernel Extensions in backtrace:

   [71EBC846-807C-386D-8D01-E144A87FAC0F]@0xffffff7f809 90000->0xffffff7f80c69fff

                dependency:[6D54F06A-46B7-37FC-AF22-DE68DC18A1A3]@0xffff ff7f80862000

                dependency:[6517D9A6-58F5-3CFC-B021-C882306150D5]@0xff ffff7f8097e000

                dependency:[55FF26D3-292D-3B4B-8AB7-1D25C8B4313B]@0 xffffff7f80946000

   [A44D0B74-5A18-34D5-842C-4E280365F55F]@0xffffff7 f80c6a000->0xffffff7f80f8bfff

                dependency:[71EBC846-807C-386D-8D01-E144A87FAC0F]@0xffffff7f809 90000


    BSD process name corresponding to current thread: kernel_task


    Mac OS version:



    Kernel version:

    Darwin Kernel Version 11.2.0: Tue Aug  9 20:54:00 PDT 2011; root:xnu-1699.24.8~1/RELEASE_X86_64

    Kernel UUID: 59275DFA-10C0-30B3-9E26-F7B5DFB1A432

    System model name: MacBookPro6,2 (Mac-F22586C8)


    System uptime in nanoseconds: 59669170119024

    last loaded kext at 59628184979092:          1.0.0d22 (addr 0xffffff7f8083e000, size 36864)

    last unloaded kext at 58989203152626:          1.0.0d22 (addr 0xffffff7f8083e000, size 36864)

    loaded kexts:

    com.Cycling74.driver.Soundflower          1.5.1          1.7.0          1.9.4d0          3.0          122          1.59          2.1.3f7          2.1.3f7          100.12.42          1.0.0d1          7.0.0          1.2.1          3.0.1d2          2.0.1d2          4.7.5d4          1.5.3          3.0.16          7.1.4          3.5.9          1.0.26          7.1.4          7.1.4          225.2          3.0.1          225.2          312          1.0.0d1          1.0.0d1          33          3.0.1          2.0.1          4.5.0          4.8.9          512.20.18          3.0.8b2          1.5.0          161.0.0          2.2.0          4.5.0          1.4          1.4          1.6          1.7          1.4          1.5          167.0.0          3.2.30          1          167.0.0          1.0.0d22          1.0          2.1.3f7          1.0.10d0          80.0          4.0.1f4          10.0.5          1.8.3fc11          1.3          3.0.16          2.2.4          2.1.3f7          2.1.3f7          3.1.1d8          4.7.5d4          1.0.10d0          3.0.16          1.0.3          7.1.4          7.1.4          2.3.2          2.3.2          4.0.1f4          4.0.1f4          4.0.1f4          227.1          3.0.1          3.0.0          4.4.5          4.5.3          3.9.0          3.0.1          1.6          1.7          1.7          403          2.0.1          3.0.1          4.5.3          4.4.5          411.1          1.0.0d5          2.0          2.0.7          4.5.3          1.5.0          1.7.1          1.1          165.3          1.0.0d1          7          331          1.7          28.18          1.4          2.6.7          1.4

    Model: MacBookPro6,2, BootROM MBP61.0057.B0C, 2 processors, Intel Core i7, 2.66 GHz, 8 GB, SMC 1.58f16

    Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 512 MB

    Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB

    Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353237334248312D4346382020

    Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353237334248312D4346382020

    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (

    Bluetooth: Version 4.0.1f4, 2 service, 18 devices, 1 incoming serial ports

    Network Service: AirPort, AirPort, en1

    Serial ATA Device: Hitachi HTS725050A9A362, 500.11 GB

    Serial ATA Device: MATSHITADVD-R   UJ-898

    USB Device: hub_device, 0x0424  (SMSC), 0x2514, 0xfa100000 / 2

    USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfa130000 / 5

    USB Device: BRCM2070 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0xfa110000 / 4

    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8218, 0xfa113000 / 6

    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0236, 0xfa120000 / 3

    USB Device: hub_device, 0x0424  (SMSC), 0x2514, 0xfd100000 / 2

    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 4

    USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0xfd110000 / 3

  • Anastasis Level 1 (0 points)

    @dugby Yes.


    And for the record. I picked up my MacBook Pro with a fresh logic board and have had three kernel panics in less than an hour. Nuking and paving with an install of Lion, not from backup...... again.


    If I get one more it is going back.

  • Dugby Level 1 (0 points)

    Thank you I will be taking it in to the Spokane Apple Store when I get home.

  • Michael Moy2 Level 1 (5 points)

    What was the replacement board part number?


    BTW, NVRM is the crash signature for this problem.

  • nevillev Level 1 (5 points)

    For what it's worth it's now been 2 weeks since I once again upgraded from SL to Lion (10.7.2) and installed the Apple  MacBook Pro Video Update 1.0.


    So far, touch wood, my 2010 Macbook Prol has been stable.


    This may still not mean the issue is really gone, since my freeze ups were some time apart - and clearly the problem still exists for a number of people - but maybe this udpate does fix it for a certain set of machines.

  • FunkyDrug Level 1 (0 points)

    Went to see the Genius Bar yesterday with Apple Phone support case number. I was out of warranty but patiently explained everything to the genius and the relation to KB article TS4088 and extended 2 year support, he did not run any test then but he has kept my mid-2010 mbp saying that they will run the diagnostic and will let me know the path forward. Even though he did not commit to the logic board replacement yet, the work order he created for me did include logic board (661-6362) worth 487.50$ and my amount due is 0$.


    Can anyone tell if this is indeed the new part number for the logic boards? I certainly hope they decide to replace my logic board with this new one and that fixes the issue for good. Will keep you posted.



  • kspes Level 1 (0 points)

    I've noticed that the bsod issue is much less frequent when your battery is 100% charged and the charger is connected. when I'm on the battery or on a charger and the battery is charging, it's bsoding every half an hour tops.


    anyone else experiencing something similar?

  • ulanbator Level 1 (0 points)

    I can confirm that this one is a 100% reproducable case for me even after installing the Video Update.

    But it worked only 1. if I was on battery and 2. gfx was assigned to discrete, because with an automatic switch it always stayed on integrated and thus produced no BSOD.


    With this argument I will go to the the Mac Store which is opening here next month.


    karlfromdeathvalley wrote:


    Hey guys I think I found a way to reproduce the BSOD even after the new update.

    I tried it three times in a row and it always worked.. so maybe you wanna try it too:

    - Dowload XCode from the AppStore (if you don't have it already installed)

    - Start a new Project or open up the TextEdit Example (/Developer/Examples/TextEdit)

    - Select a .m or .h file in the outliner.

    - Click into the editor window and do a three finger swipe up and a three finger swipe downwards..

    - Stare at a black screen...



    -When I tried it for the third time I had to do the swiping a bit more often to make it crash.. but it crased after the fourth swipe I think.

    - Normally XCode should switch to the corresponding .h or .m file after the gesture. I have already mission controll on that gesture so maybe it has something to do with this..

  • JMUAndy Level 1 (0 points)

    Another victim of the BSOD issue here...


    Here's my experience with the problem. I was an idiot and accidentally spilled a drink on my less than 1 year old Mid 2010 15" MacBook Pro... since it was my fault obviously, I had to pay the hefty cost to replace the logic board.


    I got the MacBook Pro back from repair work with a logic board replacement, and immediately upgraded to Lion. The BSOD issues started immediately. I rode out the issue for 2 months hoping for a software update that fixed the problem - I experienced approximately 5-10 BSOD's a day depending on what I was doing. Aperture, iMovie, iPhoto, PhotoBooth, and MS Powerpoint / Word all lead to crashes.


    Finally, I took the MacBook into the Apple Store and explained the situation, along with Apple's guidance they posted online. They ran a very slow diagnostic, and finally acknowledged that the logic board would need replaced. I was more or less told that their fix for this is to swap out the logic board for a replacement. When asked if the problem persisted, I was told they'd repeat the process until they found one that worked. It seems that this batch of logic boards produced during that period of time is hit or miss - some work, some don't. Since they refurb many of the units, you have to hope that when they replace it, you don't get another dud.


    Luckily, my Apple Store had one in stock, and the replacement was done in less than 24 hours. I was super excited and went down to pick it up the following morning. I got home, gave it some testing and did not encounter a single BSOD from all the normal applications that caused the problem previously. It appears the new logic board solved my problem..... until....I went to log into my email account. The P key didn't work. Nor did the Caps Lock. After doing a quick search online, there is a trend among people that have had logic boards replaced, and specifically, the "P" key not working. Bizarre.


    Of course, I'm livid at this point, and made my third trip to the Geniur Bar in 3 days. They assumed some of the wires inside the computer weren't plugged in correctly, and thought they'd be able to have the problem solved by later that day. I received a call later that evening, that I was correct - another bunk logic board. They ordered a replacement.


    Just picked up the MBP from the Genius Bar. I've had about enough of logic boards, and skinny jeans/thick rimmed glasses sporting Apple employees. When I get home to test the MBP, it had better be fixed. If not, I'm storming in and demanding a brand new MacBook with a newer model logic board, end of discussion.


    (For reference, I am still under Warranty and have not been charged for any of these replacements).

  • pikzel Level 1 (0 points)

    The video update solved my problem in OS X, but I still have it Windows. I can't sit around for months again waiting for another update. I've had it with Apple. This is it. I'm switching back to PC again.

  • Ian Kelleigh Level 1 (140 points)

    pikzel wrote:


    The video update solved my problem in OS X, but I still have it Windows. I can't sit around for months again waiting for another update. I've had it with Apple. This is it. I'm switching back to PC again.


    Why can't you get the mobo replaced? It seems to be the 100% fix.