Frequent Panic NVRM[0/1:0:0]: Read Error 0x00000100

By the way I hate graphicscards, I have another MacBook Pro 15", this one is from early/mid 2008, guess what: the graphicscard on it broke last week! Internal/external monitor are black, sometimes I get beep responses from keyboard input.

A Small Ray of Hope. (or not)

Sorry if this might look like a rehash to some of you but perhaps its not to others.

I started experiencing the BSOD on Windows 7 (BootCamp), while playing Batman:AA. I did all the Security Updates in Windows 7, then went to search for newer NVidia GT 330M drivers (Windows showed that my drivers prior to update was dated at 1/1/2011). I downloaded the newer drivers from NVidia's site, (released on August 3, 2011) and did a clean install.

I loaded up Batman:AA and ran through the same process when I encountered the BSOD earlier. And the BSOD occurred again ... and then, lo and behold, I had a really nice surprise.

Within a couple of seconds (like 2 to 3 seconds): the game came back, at exactly the same place where it crashed.

This occurred TWO more times!!!

I had read somewhere on this board (I don't think its on this thread however) that Windows 7 somehow detects a problem with the graphics card driver, and resets the driver, and everything just returns to normal. Well I guess this is what happened to me too.

So this raised a question:

What happens when you update NVidia Drivers while loaded into Windows in BootCamp? I mean I know what happens, but how will OSX react to this update? I didn't think I would find any difference. I checked and nope, no difference. Same reproducible BSOD crash in OSX.

I tried to install the latest version of OSX drivers from Nvidia's site but no go (driver filename: Retail_256.02.25f1v1; released June 24, 2011). It says "This computer will not support this NVidia graphics solution".

Maybe, just maybe, its just a driver issue. And maybe if Apple or Nvidia will allow a clean update to the latest drivers provided by NVidia we could solve this problem right now.

Or, to any Apple OS Engineers who might be listening out there, we love your product, but maybe you should take a hint from Windows 7 and perhaps get the OS to reset the video-card's driver instead of crashing with it.

Having the same problem here.

Mid 2010 i7, GeForce GT 330M

Is there any 'true' solution to this yet? Has Apple responded to this yet?

I havn't been able to work properly for the past weeks...

What I'm getting out of all this is:

Get gfxcardstatus. Set it to only use Intel HD Graphics. At least have a working machine & wait for Apple to solve this freakin' crysis.

Also, people that still have their warranty can get a new logic board. What can people (like me) do, that don't have warranty anymore?

Did I get that right so far?

MacBook Pro 15" i7 (mid 2010)

OS X 10.6.7 Snow Leopard

NVIDIA GeForce GT 330M

Same problem, several random occurrences recently. Screen display goes black without warning of a shutdown and computer becomes unresponsive. Log shows similar kernel panic information as reported by other users. I have informed Apple feedback and report logs have been sent.

Curiously, unlike some other users have reported, I cannot reproduce the problem when using the 2nd effects panel in PhotoBooth but I have made it recur repeatedly in Garageband while using the guitar tuning assistant feature - after a minute or so of tuning the screen turns black.

Sat Oct 22 14:57:27 2011

panic(cpu 3 caller 0xffffff7f80aa52e8): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xc0000000 0xffffff80d2f48000 0x0a5480a2, D0, P3/4

Backtrace (CPU 3), Frame : Return Address

0xffffff80b0071fb0 : 0xffffff8000204b99

(repetitive lines deleted here to reduce space)

0xffffff80b0073fa0 : 0xffffff80002e2a14

Kernel Extensions in backtrace (with dependencies):

com.apple.GeForce(6.2.6)@0xffffff7f812fc000->0xffffff7f813befff

dependency: com.apple.NVDAResman(6.2.6)@0xffffff7f80a3c000

dependency: com.apple.iokit.IONDRVSupport(2.2)@0xffffff7f80a2e000

dependency: com.apple.iokit.IOPCIFamily(2.6)@0xffffff7f80604000

dependency: com.apple.iokit.IOGraphicsFamily(2.2)@0xffffff7f80a07000

com.apple.nvidia.nv50hal(6.2.6)@0xffffff7f80d0b000->0xffffff7f8110efff

dependency: com.apple.NVDAResman(6.2.6)@0xffffff7f80a3c000

com.apple.NVDAResman(6.2.6)@0xffffff7f80a3c000->0xffffff7f80d0afff

dependency: com.apple.iokit.IOPCIFamily(2.6)@0xffffff7f80604000

dependency: com.apple.iokit.IONDRVSupport(2.2)@0xffffff7f80a2e000

dependency: com.apple.iokit.IOGraphicsFamily(2.2)@0xffffff7f80a07000

BSD process name corresponding to current thread: WindowServer

I have had this problem only in the last couple of months but have have not added any new software or system upgrades in this time. Still have about 18 months to go under AppleCare warranty so I'm not concerned about cost but it's very disconcerting to have a top of the range Apple computer suddenly and totally disabled in this way.

Hopefully Apple are devoting sufficient engineering resources to resolve this issue asap.

Hello everyone. I, too, have a Mid 2010 MacBook Pro (6,2) i7 with the exact same issue. I've just read through the full thread, and my Nvidia card is the same as the one from the people who posted their info:

Chipset Model:     NVIDIA GeForce GT 330M

Type:     GPU

Bus:     PCIe

PCIe Lane Width:     x16

VRAM (Total):     512 MB

Vendor:     NVIDIA (0x10de)

Device ID:     0x0a29

Revision ID:     0x00a2

ROM Revision:     3560

gMux Version:     1.9.21

I started having this issue after a clean install of Lion (I don't like to upgrade) about a week after it was out. I had had no occurrences before (I had been running SL 10.6.5, 10.6.6, 10.6.7 and 10.6.8 without any problem), but it soon started happening when I installed Lion. Not knowing what the problem was, I reformated the MBP a couple of times with evidently no success. Afterwards, I went back to 10.6.8 (clean install) and had no more problems ever since. About a month later I decided to give Lion a try again, but the black screen issue aroused once again. Then I realized from the panic report that it was an issue with the Nvidia card, and had the idea to use gfxCardStatus to keep it from being used (many other people in this thread have found this workaround as well). That stopped the panics from happening again, albeit being very annoying to have to use the integrated card all the time.

One thing I'm pretty sure hasn't been pointed out in this thread, is that if you force the MBP to use the integrated card only, you can freely boot into any other operating system you have installed (I currently have Windows 7 and Arch Linux) and there's a guaranteed 0% possibility of crash (or at least for me), whereas it is very likely to crash, for instance under Windows 7, if you leave the MBP on dynamic switching. This at least allows you to use the Nvidia card to play games on Windows (that's something, isn't it?). I guess it also means this issue is tied to the Mac's EFI or any other underlaying BIOS-equivalent ****.

Ian

Thank you! You must have understood my message then. So to anyone that didn't:

I didn't say he had posted here I was replying to Bobsterbobs who said that "the developer who made gfxCardStatus could be making a lot of money right now"

Guys N Gals! Its just a difference between "could be making" vs. "would be making".

I meant to say, Cody Krieger, "could be making a lot of money right now" had he put up gfxCardStatus on sale.

He hasn't, and that's just plain Awesome of him.

Yes, Cody has saved many of us from regular crashes as long as you stay in "Integrated Only" mode. While it's not the solution we are all looking for, his solution is much better than the alternative right now. And I seriously doubt he's making a bunch of money. In fact, I would go so far to say that he's made well below minimum wage for the time he's put into this effort. If you notice, Cody has a link to donate on his website so throw him a bone and thank him for allowing your to use your system in a limited fashion while Apple figures out how to solve the problem (and taking their sweet *** time while at it).

Disclaimer: I have no association with Cody, I don't even know him but as a fellow software engineer, I appreciate what he's done. Also, I've read that gfxCardStatus is not solving the problem for everyone but I get a sense that it has for many.

hey there!

Here in Atlanta the genius bar guys where shooting in the dark trying to figure out what is the source of these problems.

I can't tell whether my isssues started after the Lion upgrade but I do remember the first problem I had was that Safari would freeze or stall with the spinning pinwheel going, next problem to show up was that the screen not turning back on after my MBP had been "asleep" for a few hrs/overnight.

After that the who computer started freezing up (with or without the spinning pinwheel). One time this week the system actually gave one of those boxed messages (system failed, please power off and restart).

Well AFTER 2 Applecare calls, 2 fresh reinstalls of Lion, 4 visits to the genius bar, 1 new hard drive, 2 new sticks of RAM (the genius tried to say I might have had some bad third party RAM...I pointed out that the RAM was Apple and had come with the MBP), I am back to square one.

I started having MAJOR crashes again yesterday afternoon and, given that it is the weekend and I am stuck at home anyway, I started my own research on the error messages....That's how I ended up here.

Next I booked 3 genius appointments back-to-back (front guy not happy...what can I say...Fix my computer and I won't have to come back...) and headed back to the genius bar.

The genius bar guy tried to go the "bad-NVIDIA-card" route (we can't replance the card itself, has to send the whole thing in to replace the logics board....), I had read these posts and I knew that the chances of a new logic board fixing the issue were next to slim, so I pointed out that after all that I had put up with and the amount of Apple products I have bought/own it was time for Apple to step up to the plate and replace my system outright.

As expected the genius bar guy tried to dodge my request (he actually went as far as saying that it didn't matter whether I owned a $19 cable or a house full of Apple products...) but I put my foot down and said I wanted to speak to a manager. The manager approved my request, new sytem on order...Now lest hope the new one doesn't have the same issues as the "geniuses" don't have the slightest clue about what is causing these problems....OUCH!!!!

The sore spot in this story is that I was able to do just as much trouble shooting as the Apple genius, if not more and we are supposed to depend on these guys to make our Apple products run smooth...

In short...Keep bugging Apple to look for a solution AND replace your system in the meantime!

Does anyone know whether the Spring 2011 MBP's have the same issues?

ECC

I have been having the same problem and I have a Mid 2010 (bought new Jan 2011) MBP with these specs:

2.4 GHz i5

NVIDIA GeForce GT 330M

4 GB 1067 MHz DDR3

HD: Hitachi HTS725050A9A362: Capacity: 500 GB @7200

(Apple replaced it without solving the problem-I used to have 320 GB @5400)

RAM has also been replaced with brand new factory sealed sticks...

Apple has not figured out the problem yet (and as usual there will NOT be an official problem to resolve until they have a solution they can push out...)

Now that I see all of these problems with i7...I do not feel so lucky about the replacement system they ordered for me! Is anyone having these problem using MBP dating Spring 2011 and after?

Thanks!

I do not have VM or any Windows related crap on my system. I refuse to use any window only software on my machine. If I have to use something that comes widows only, I use it on someone else Windows crapware. 😝

5 panics in last 8 days 😟 Looks like the same issue as everyone else here.

I hope this isn't going to be the same story as the 2008 MBPs with the faulty 8600 GT chips.

panic(cpu 0 caller 0x8350ec97): NVRM[0/1:0:0]: Read Error 0x00000100:

Mac OS version:

10K540

Kernel version:

Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386

System model name: MacBookPro6,2

My post from last page: "have you tried downloading "gfxcardstatus" and setting it to only use Intel HD Graphics as a current workaround? That will spare you a lot of frustration until there's a solution."

Are you really so lazy that you won't even read one page back on the discussion about your very problem?

I had gone days without a blackout, then it happened while I was restoring my iPhone from Backup. I was concerned because the iPhone screen was stuck on the spinning dial, but I reset it and it was working fine. What makes me extremely nervous are the long processes like iOS or Mac OS X updates that require that you do not power off your system while the update is in process. This blackout issue can happen anytime. And for me, using the gfxCardStatus doesn't help. For me, running the integrated Intel card causes more problems than the NVIDIA card.

Understandably, I see why you would say that. Obviously there is something different about my system that causes it to crash with greater frequency while using the integrated card, whereas most everyone in the thread can run that card with no problem. But I still believe my problem is the same problem. The symptoms are the same. My guess is that it is the controller, driver or other firmware. I could be doing something different from other users, although I don't know what, and that is the cause for the difference. Apple is aware of the problem so I am awaiting the fix just as everyone else. Hopefully it will resolve the problem for me and others. I look forward to reporting the results.