You've had luck with this one The support article says,
About MacBook Pro Video Update 1.0
This update addresses an issue where MacBook Pro (15-inch Mid 2010) computers may intermittently freeze or stop displaying video.
I wonder if this problem is wider than just the MBP's 15" Mid 2010 units? I haven't read all this thread - it's way too long - however what I have read points mostly to the Mid 2010, 15" and 17" units.
Maybe you should start a separate thread for the model you have to see if you can find anyone else in a similar situation.
I just found this article via another thread, may be of interest as it explains the nature of the fix.
Apple issues update to address MacBook Pro black-screen bug
I have continued to test with my MBP 15", mid 2010 unit after installing the update. I'm sorry to report that, while there are less crashes, it still crashes. Only once so far (but once too many as far as I am concerned) when simply scrolling through log files.
I'm taking mine along for the free out of warranty service mentioned in the support article.
I installed the update yesterday and I thought the problem had been resolved, but today during a presentation of work and opening a webpage with Safari, the system freezes again. I had to force shutdown. Opening the page again the system does not froze. In my case, everytime the freezing comes randomly.
Perhaps the problem on my computer is otherwise.
Unsolved problem !
Black Screen continues especially when using the Mission Control.
Tue Oct 25 10:05:39 2011
panic(cpu 1 caller 0xffffff7f8094e00b): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xc0000000 0xffffff80a0598000 0x0a5480a2, D0, P3/4
Backtrace (CPU 1), Frame : Return Address
0xffffff80a38dbb10 : 0xffffff8000220702
0xffffff80a38dbb90 : 0xffffff7f8094e00b
0xffffff80a38dbc20 : 0xffffff7f80a3e120
0xffffff80a38dbc70 : 0xffffff7f80a3e1e0
0xffffff80a38dbcd0 : 0xffffff7f80cea749
0xffffff80a38dbe10 : 0xffffff7f80a5d269
0xffffff80a38dbe40 : 0xffffff7f8095796e
0xffffff80a38dbef0 : 0xffffff8000639966
0xffffff80a38dbf30 : 0xffffff80006386e0
0xffffff80a38dbf70 : 0xffffff8000638584
0xffffff80a38dbfb0 : 0xffffff8000820057
Kernel Extensions in backtrace:
dependency: com.apple.iokit.IOPCIFamily(2.6.7)[6D54F06A-46B7-37FC-AF22-DE68DC18A1A3]@0xffff ff7f80878000
dependency: com.apple.iokit.IONDRVSupport(2.3.2)[6517D9A6-58F5-3CFC-B021-C882306150D5]@0xff ffff7f808db000
dependency: com.apple.iokit.IOGraphicsFamily(2.3.2)[55FF26D3-292D-3B4B-8AB7-1D25C8B4313B]@0 xffffff7f808a3000
dependency: com.apple.NVDAResman(7.1.4)[71EBC846-807C-386D-8D01-E144A87FAC0F]@0xffffff7f808 ed000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
We must try and send emails, call to Apple, saying it did not work!
Enjoy the facebook page related to the problem. Maybe just once they solve this problem
I have MacBook pro 15 mid2010. I got BSOD the day lion came out and installed. Since then I kept on getting it until I installed gfxcardstatu have integrated only active I stopped getting the BSOD.
I downloaded the new video card update and this is what I did:
- Before I installed it I uninstalled the gfxcardstatu
- installed the new update and restarted it.
- I noticed some changes in the gray apple on white screen.
- computer started normal and things were fine. I got too excited I guess because right after 20 mins. Just because I was switching between my desktops on my Mac I got the BSOD again! Dammit! Your update did not fix anything!!!
I just hope they are not leaving this issue and moving on thinking it solved it. And categorize people like me are just complaining are not part of the same problem. AGAIN I REPEAT: I have MacBook pro 15 mid2010. I got BSOD the day lion came out and installed.
I also suspect FileVault2 is causing this on a 2011 MBP 13 with Crucial M4 SSD. I did a reinstall and for almost two weeks the system was dead solid without FileVault activated. After activating FileVault, at least one kernel panic ("you need to restart your computer" black screen) per day. The logs don't point consistently to one offender and seem random which makes it hard to debug. I'm pretty sure it's FileVault though I don't know exactly what.
With all due respect and sympathy for those who are still experiencing the BSODs, call Apple Support or take your machines into your local Apple Store if you live near one.
It's clear from the knowledgebase article that Apple believes they have identified and solved this issue. They go on to state that if the provided software update doesn't fix it, you need to take your machine in to Apple for repair, and they're even extending you to 2 full years of coverage from purchase date.
It's fine to post to this thread to say the software didn't work for you, but I don't think it's productive anymore to say "Apple please fix this." They don't read this thread. They consider the matter resolved via the KB article. If you continue to have problems, contact Apple. For a few of us (maybe the majority, I don't know) the software worked and we are checking out of this thread (I'm unsubscribing after this post).
I can report success with the update so far. My machine is the 'target' machine (mid-2010 MB 15" i7). I've been using for a number of hours now without a crash; previously I would have experienced multiple crashes by this time.
I'm logging off of the e-mail notifications...
Good luck to the rest of you!