Previous 1 192 193 194 195 196 Next 2,929 Replies Latest reply: Sep 3, 2014 6:33 PM by TiTi SS Go to original post Branched to a new discussion.
  • CraigJr88 Level 1 Level 1

    Not sure if i should have replied to the original poster or the latest....


    Anyways I was given a 2006 Macbook Pro 17inch C2D to wipe, reinstall OS and sell. It only has 2GB of RAM so at first I wanted to give Snow Leopard a run and see how it ran. I ran it for 3 days installing things, running programs and just random web browsing and so on with no problems.

    So I then wipe and do a clean install of Lion which went fine no problems, then I started installing a few apps and I have only been running the MBP after the install for about 30minutes and right after Firefox installed I went to launch it and BAM! BLACK SCREEN!

    So I'm going to check a few things and see if it happens again, if it does happen again and I can't see any reason why - I'm going to wipe reinstall Snow Leopard and install all the same apps again and see if it happens.


    My friend did tell me that it would randomly black screen like that and she was on Lion but the battery was no good also. So I don't know if that had anything to do with it - but figured I'd throw that tidbit in there.


    After I install SnowLeopard and run it for quite a while - I'll post back what happens. I know it may not be a solution since some APPS refuse to run on Snow Leopard (which is why I decided to just upgrade to Lion), also I might see if I can upgrade it too the 3gb of RAM, right now it only has the 2GB and only supports up to 3GB Usable.

    **Apple does seem to have a problem with some Macbook Pro's and Video Card Driver's since Lion moving forward. I personally own a 2010 15" MacBookPro i7 2.66GHz 8GB Ram 512MB Nvidia and when I upgraded to Lion I wasn't getting the black screen like this - but I was getting panic errors almost right at login and the only fix was to uncheck the Video Switching feature. Have not had the problem since Upgrading to Mt.Lion - but just figured I'd add that as well!

  • KostNalu Level 1 Level 1

    Who tried OS X Mavericks Dev Preview on problematic macbooks with NVIDIA GPU and kernel panics on Lion and Mountain Lion?

  • Grégory Cuffel Level 1 Level 1

    Had test Mavericks.


    Don't no know. But I had previously several problems with my MBP6.2 under lion. I had fixed them with gfxcardstatus.

    And then, don't know why, they had gone. So I could use Mountain Lion without gfxcardstatus for a year.

    But It was before Maverick. The glitches and freezes are back. Since DP4. May be that this is a coincidence or it is the devil.


    I've reinstall, lion, mountain lion, even snow leopard. No way...


    So I cannot recommand to install mavericks.

  • paulohco Level 1 Level 1

    I've been facing that heck of "BSOD" for about 2 months. The problem is: I bought my MacBook Pro 15" on April 2010, and now it is August 2013, so... more than 3 years have passed, which is obvious, according both to Murphy's laws and to some companies that Care (less and less) for its costumers. The OSX that shipped with my Mac was Snow Leopard, which I unfortunately replaced by MacOSX Cat (oops, Lion). Question is:


    1- Is it worthy downgrading to Snow Leopard? Will that get any better? (I mean, will it happen less frequently at least?)

    2- Do you think there is any "tolerance" on the period of 3 years? Would I be eligible for the free replacement of the board today?

    3- How much does it cost in US to replace the Logic Board?


    I had a iBook (PowerPC) once, I miss those times when Apple was still a good company. After Intel came in, it seems to me that the "expensive but good" Apple is getting more and more like the Microsoft, full of bugs, crashes, and so on.

  • paulohco Level 1 Level 1

    Besides that, what is also annoying is that Apple did not contact me about this possible issue. I had to experience it for myself while using the MacBook Pro for a long time. This is not a proper way of doing a recall...

  • warbster Level 1 Level 1

    Worth a visit to your local apple store. I have had my logic board replaced free of charge, twice, because of this issue and both times out of warranty. THere was no general recall for this problem but they are aware of it and even lengthened the period to cover replacing logic boards on affected machines. Good luck.

  • Vicx Level 1 Level 1



    I think the problem is not present under SL (I never experienced it before Lion).


    You can try to explain that you have installed Lion only after the 3 years so you couldn't find the problem before ?


    The price (in euros) was 300-400 € if I remember...



    Hope that helps ;-) And sorry for my English


  • paulohco Level 1 Level 1

    Today I went to an Authorized Service Provider, the guy ran all the tests, including the VST, and guess what? It PASSED !!!!  Now I'm clueless, but I swear I saw the BSOD (I feel like I'm saying "I saw the White Walkers!"). I don't know if I should be happy or if I should be sad, because at this point I don't know what is happening anymore... I guess Lion is the one to blame, or maybe some application I have installed in the last 6 months is the culprit. I'll keep an eye on the panic error, hoping that it won't come back. If it should happen again maybe I will install the MacOSX from scratch and reinstall applications one by one, without using Time Machine backup...

    Any tips are very welcome...








    ---- The BSOD ----


    Interval Since Last Panic Report:  151865 sec

    Panics Since Last Report:          9

    Anonymous UUID:                    61B2F669-0330-4E18-9ABE-1551DFA3D8D9


    Tue Aug 27 11:51:40 2013

    panic(cpu 0 caller 0xffffff7f80a6b007): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff809fab9000 0x0a5480a2, D0, P3/4

    Backtrace (CPU 0), Frame : Return Address

    0xffffff807c2d3280 : 0xffffff8000220792

    0xffffff807c2d3300 : 0xffffff7f80a6b007

    0xffffff807c2d3390 : 0xffffff7f80b63b83

    0xffffff807c2d33f0 : 0xffffff7f80b63bf7

    0xffffff807c2d3460 : 0xffffff7f80e65855

    0xffffff807c2d35a0 : 0xffffff7f80b87ddd

    0xffffff807c2d35d0 : 0xffffff7f80a74d6a

    0xffffff807c2d3680 : 0xffffff7f80a7043c

    0xffffff807c2d3870 : 0xffffff7f80a71f6e

    0xffffff807c2d3950 : 0xffffff7f81e9864e

    0xffffff807c2d3990 : 0xffffff7f81eaf3d8

    0xffffff807c2d39b0 : 0xffffff7f81ecd3a2

    0xffffff807c2d39f0 : 0xffffff7f81ecd643

    0xffffff807c2d3a30 : 0xffffff7f81eb3329

    0xffffff807c2d3a80 : 0xffffff7f81e6770b

    0xffffff807c2d3b10 : 0xffffff7f81e65a09

    0xffffff807c2d3b40 : 0xffffff7f81e6c221

    0xffffff807c2d3b70 : 0xffffff800065645d

    0xffffff807c2d3be0 : 0xffffff80006567fc

    0xffffff807c2d3c40 : 0xffffff8000656fbb

    0xffffff807c2d3d80 : 0xffffff80002a3f08

    0xffffff807c2d3e80 : 0xffffff8000223096

    0xffffff807c2d3eb0 : 0xffffff80002148a9

    0xffffff807c2d3f10 : 0xffffff800021bbd8

    0xffffff807c2d3f70 : 0xffffff80002aef10

    0xffffff807c2d3fb0 : 0xffffff80002daec3

          Kernel Extensions in backtrace:

   [97284661-2629-379E-B86B-D388618E8C30]@0xffffff7f80a 04000->0xffffff7f80cfffff

                dependency:[5C23D598-58B2-3204-BC03-BC3C0F00BD32]@0xffffff 7f8081d000

                dependency:[7C8672C4-8B0D-3CCF-A79A-23C62E90F895]@0xff ffff7f809f2000

                dependency:[D0A1F6BD-E66E-3DD8-9913-A3AB8746F422]@0 xffffff7f809b9000

   [38ACBB3D-4E3C-3883-9A4B-67F15592905F]@0xffffff7 f80d00000->0xffffff7f81022fff

                dependency:[97284661-2629-379E-B86B-D388618E8C30]@0xffffff7f80a 04000

                dependency:[5C23D598-58B2-3204-BC03-BC3C0F00BD32]@0xffffff 7f8081d000

   [7E1D7726-416F-3716-ACCB-E1E276E35002]@0xffffff7f81e4f0 00->0xffffff7f81f11fff

                dependency:[97284661-2629-379E-B86B-D388618E8C30]@0xffffff7f80a 04000

                dependency:[7C8672C4-8B0D-3CCF-A79A-23C62E90F895]@0xff ffff7f809f2000

                dependency:[5C23D598-58B2-3204-BC03-BC3C0F00BD32]@0xffffff 7f8081d000

                dependency:[D0A1F6BD-E66E-3DD8-9913-A3AB8746F422]@0 xffffff7f809b9000


    BSD process name corresponding to current thread: WindowServer


    Mac OS version:



    Kernel version:

    Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64

    Kernel UUID: FF3BB088-60A4-349C-92EA-CA649C698CE5

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


    System uptime in nanoseconds: 10275793296410

    last loaded kext at 53967211548: org.virtualbox.kext.VBoxNetAdp    3.2.0 (addr 0xffffff7f816a8000, size 12288)

    last unloaded kext at 179208064078:    5.1.0 (addr 0xffffff7f81767000, size 65536)

    loaded kexts:

    org.virtualbox.kext.VBoxNetAdp    3.2.0

    org.virtualbox.kext.VBoxNetFlt    3.2.0

    org.virtualbox.kext.VBoxUSB    3.2.0

    org.virtualbox.kext.VBoxDrv    3.2.0    1.9.5d0    1.59    122    2.2.5a5    2.2.5a5    100.12.75    3.5.9    3.0.2d6    3.0    5.0.0d8    1.0.0d1    2.0.1d2    4.0.8f17    7.0.0    1.2.3    3.1.33    5.0.0d8    3.1.33    1.6.0    1.0.33    7.3.2    7.3.2    7.3.2    227.6    4.0.8f17    3.0.6    227.6    312    1.0.0d1    1.0.0d1    33    3.2.1    404    2.0.3    2.1.0    5.1.0    4.9.0    3.2.4b8    561.7.22    1.6.1    161.0.0    2.3.1    5.1.0    1.5    1.5    1.7    1.9    1.5    1.6    195.0.0    3.2.30    1.4    8    195.0.0    2.2.5a5    1.0    80.0.2    2.2.5    1.0.10d0    10.0.5    1.8.6fc18    1.3    3.1.3d10    5.0.0d8    3.1.33    2.2.5a5    2.2.5a5    5.1.1d6    1.0.4    1.0.10d0    7.3.2    7.3.2    2.3.4    2.3.4    4.0.8f17    4.0.8f17    3.0.3    230.5    5.0.0    5.1.0    5.0.0    3.2.1    1.7    1.7.1    1.7.1    3.2.1    3.2.1    5.0.0    4.4.8    1.0.1b1    420.3    2.1    2.0.8    5.1.0    1.6.1    1.7.1    1.1    177.11    1.0.0d1    331.7    1.7.2    28.18    1.5    2.7    1.4

    Model: MacBookPro6,2, BootROM MBP61.0057.B0F, 2 processors, Intel Core i5, 2.53 GHz, 4 GB, SMC 1.58f17

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

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

    Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53463235363634485A2D3147314631

    Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53463235363634485A2D3147314631

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

    Bluetooth: Version 4.0.8f17, 2 service, 11 devices, 1 incoming serial ports

    Network Service: Ethernet Adaptor (en2), Ethernet, en2

    Network Service: AirPort, AirPort, en1

    Serial ATA Device: ST9500420ASG, 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: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0237, 0xfa120000 / 4

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

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

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

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

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

  • Vicx Level 1 Level 1


    The first time I went to the Apple Store, all the test passed. The second time, I had replaced my SSD by the original HDD and the test failed after about 2sec. Maybe the test did not work the first time because it couldn't identify my Mac as it should because of the modified hardware (the new SSD).

    If you modified yours, you should try to remove all your modifications and go back to the Apple Store to check your Mac.


    Hope that could help you ;-)

    And as usual, sorry for my English


  • paulohco Level 1 Level 1

    Hi Vicx,


    in my case, I haven't replaced anything, my MacBook Pro is  original. I only had it customized, before ordering it, on Apple Store.

    About 2 days ago I restored the backup from TimeMachine, and so far so good, no BSOD. But I'm not so confident yet, I have to wait some more time before saying that the problem is gone...





  • kvad Level 1 Level 1

    Did anyone else have success getting Apple to fix this problem on their 17-inch Macbook Pro (mid 2010)?

    We just got a reply back from the service shop - only solution was to replace the logic board, but as it was not a 15-inch we'd have to cover the cost ourselves (at a rather obscene price).

  • Bikul Level 1 Level 1



    Yes, they changed the logicboard of my 17-inch MacBook Pro (mid 2010) TWICE !


  • kvad Level 1 Level 1

    Thanks for the info and the extensive post Bikul - good to hear there at least is a chance!

    I do wonder how I can convince them to fix it though, as they seem to be sticking with the official line, that only the 15-inch'er will be fixed.

  • Bikul Level 1 Level 1

    As you can read in my post, Bootcamp, Windows 7 and changing Resolution there with the NVDIA-Panel did DESTROY the LogicBoard. I was under the 2 years warranty at that time. I think for you it might be too late now. But you could ask Apple if they would exchange by goodwill. The Logicboard of the 15 and 17 inch models is the same.

  • gen_ Level 2 Level 2

    Bikul wrote:


    As you can read in my post, Bootcamp, Windows 7 and changing Resolution there with the NVDIA-Panel did DESTROY the LogicBoard. I was under the 2 years warranty at that time. I think for you it might be too late now. But you could ask Apple if they would exchange by goodwill. The Logicboard of the 15 and 17 inch models is the same.

    Categorically impossible.


    It is categorically impossible for a resolution change in BootCamp to do any more damage to your Mac than it is for one in OS X to do so. If the problem is hardware based, they would HAVE to recall. If it is software based, then it would be a Nvidia problem, and much like th Flash issue, Apple wuld love nothing more than to place the blame. It would not have gone unnoticed for any period of time anyway, especially considering that all the hardware this pertains to exists in the Windows world, so the drivers saw a lot more real world testing on Windows before they released the Mac.