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

Hello everyone !

I rencently expriment the same problem on my MBP 15" mid-2010. I went to an Apple Store to get a solution, and, surprise : nothing ! The first guy told me I have to replace my logic-board and that will cost me 400€ (I don't have Apple Care), so i wanted to leave them my MBP for other test. When they gave it back to me, the Genius say : "We have unmount the computer and clean the dust, there are no problems anymore"...Really ? After 5 min of using, a new black screen ! This Genius was a good joker !

So if I correctly understand all this tread, the only solution is to replace the logic-board, which is not a solution because all the logic-board of mid-2010 potencially have the same problem...

I wonder if it's possible to replace logic-board of mid-2010, by one of later models, but I think the main problem is the connectors which, if i correctly remember, are not excatly the same after 2010 models...

is there a solution ? Because when i bought a computer a 1800€, I prefere when i can use it entirely more than 2 years....

(Excuse my english if it isn't perfect...)

Apple is legally required to replace the logic board and perform any other necessary repairs related to this problem, free of charge,

up to two years after the date of sale - see Apple Bulletin TS4088.

In reality, at least in some cases, they will give you a hard time and delegate costs and inconvenience onto the customer.

Try to pursue it.

Unfortunately in some case the only solution is to sue Apple and the service provider

that refuses to repair it.

In our case, even though Apple advised the local (German) service provider to repair the computer the

service provider refused to. Apple appears to have a bizarre relationship with its 'authorized' service providers,

whereby the 'authorized' service providers can do as they please, even if in complete disregard of Apple's advertised standards and instructions.

Since Apple provides parts exclusively to 'authorized' service providers, warranty and Apple authorized repairs

can become an utter impossibility, rendering the $2000+ Apple computer a useless brick.

Apple will eventually wake from this self destructive and unsustainable path. In the interim, unfortunately, countless customers will bear the costs and inconvenience.

Instead of financing the removal of posts critical of its policies, Apple should proactively listen to us, its customers,

and ensure that its policies and service providers serve the customers' needs, rather than expect

the customer to bear the brunt of its failings.

When I went to the Apple Store, I had already seen the Apple Bulletin TS4088, but the Genius make a test on the MBP, and this tested passed, which significate, according to him, that my MBP is not cover by this warranty extension...

Should I try to go to another Services Center of Apple to get a solution ?

Any 'Genius' should know that even they pass at 12:00 they can fail at 2:00.

The same test produces different results.

So, absolutely get it retested until it fails, which it eventually will (naturally, it wastes everyone's time and resources),

or demand that Apple replace it without it having failed the 'test'.

So long as you get the NVRAM error in the real world it is defective.

The problem is that I don't want to pay 400€ to replace my logic-board if they give me another logic-board of mid-2010, which have the same problem... And the Genius don't want to replace it for free if its test passed, and i pretty sure that even if I could drive the test by myself, they will not accept the results...

So if I correctly understand what you're saying, I have to return to the Apple Store, and insist to have a free replacement ?

The newer production logic boards are OK. And if they replace it with a defective one, you can have that one replaced - naturally, it is precisely this process that wastes everyone's time.

I would go back to the store - replicate the problem. Tell them to run the test multiple times.

It will eventually fail - "they all do" - as confirmed by an authorized provider.

Overall, you have to be waste your time and keep on pressing the issue <edited by host>

Or sell it and buy something else.

Th3pS, you didn't post the error message.

Are you sure it is the exact one it is discussed in this thread ?

If it is, and you show the backlog trace containing the "Panic NVRM[0/1:0:0]: Read Error 0x00000100" and if you can reproduce it at the Genius Bar, then hardware test is likely not required.

If it is another Panic message then the error could come from other issues, even software ones.

here is my log :

Mon May 14 16:15:56 2012

panic(cpu 1 caller 0xffffff7f80958947): NVRM[0/1:0:0]: Read Error 0x00070000: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff809f230000 0x0a5480a2, D0, P3/4

Backtrace (CPU 1), Frame : Return Address

0xffffff807c49b3c0 : 0xffffff8000220792

0xffffff807c49b440 : 0xffffff7f80958947

0xffffff807c49b4d0 : 0xffffff7f80a48aa4

0xffffff807c49b520 : 0xffffff7f80be391d

0xffffff807c49b540 : 0xffffff7f80c59e17

0xffffff807c49b7a0 : 0xffffff7f80c620d0

0xffffff807c49b890 : 0xffffff7f809244ed

0xffffff807c49b930 : 0xffffff7f8093790d

0xffffff807c49b9f0 : 0xffffff7f8095e1a5

0xffffff807c49bbe0 : 0xffffff7f8095e6ed

0xffffff807c49bcc0 : 0xffffff7f817ee542

0xffffff807c49bd40 : 0xffffff7f817ef364

0xffffff807c49bd80 : 0xffffff7f817ecc95

0xffffff807c49bda0 : 0xffffff7f817efc61

0xffffff807c49bde0 : 0xffffff7f817f00d9

0xffffff807c49be00 : 0xffffff7f817ecf04

0xffffff807c49be20 : 0xffffff7f8180436d

0xffffff807c49be40 : 0xffffff7f818044b8

0xffffff807c49bea0 : 0xffffff7f81816560

0xffffff807c49bec0 : 0xffffff7f818169d8

0xffffff807c49bef0 : 0xffffff800063c5b6

0xffffff807c49bf30 : 0xffffff800063b330

0xffffff807c49bf70 : 0xffffff800063b1d4

0xffffff807c49bfb0 : 0xffffff8000820057

Kernel Extensions in backtrace:

com.apple.NVDAResman(7.1.8)[560E1257-BF5E-3B0B-95F0-15033A0D1B97]@0xffffff7f808 f8000->0xffffff7f80bd1fff

dependency: com.apple.iokit.IOPCIFamily(2.6.8)[F63D4ABE-42DA-33EF-BADD-3415B0CB0179]@0xffff ff7f80883000

dependency: com.apple.iokit.IONDRVSupport(2.3.2)[D05CFB53-FB72-3613-8162-2D188DB04738]@0xff ffff7f808e6000

dependency: com.apple.iokit.IOGraphicsFamily(2.3.2)[2D2A4A31-EB4F-3730-BE3A-76C061685FC5]@0 xffffff7f808ae000

com.apple.nvidia.nv50hal(7.1.8)[7596DB8C-AE9D-3C87-B11A-0ED8F940CAF8]@0xffffff7 f80bd2000->0xffffff7f80ef3fff

dependency: com.apple.NVDAResman(7.1.8)[560E1257-BF5E-3B0B-95F0-15033A0D1B97]@0xffffff7f808 f8000

com.apple.GeForce(7.1.8)[00925AF3-22EE-3858-8BD3-06AE57DFCC86]@0xffffff7f817ab0 00->0xffffff7f8186afff

dependency: com.apple.NVDAResman(7.1.8)[560E1257-BF5E-3B0B-95F0-15033A0D1B97]@0xffffff7f808 f8000

dependency: com.apple.iokit.IONDRVSupport(2.3.2)[D05CFB53-FB72-3613-8162-2D188DB04738]@0xff ffff7f808e6000

dependency: com.apple.iokit.IOPCIFamily(2.6.8)[F63D4ABE-42DA-33EF-BADD-3415B0CB0179]@0xffff ff7f80883000

dependency: com.apple.iokit.IOGraphicsFamily(2.3.2)[2D2A4A31-EB4F-3730-BE3A-76C061685FC5]@0 xffffff7f808ae000

BSD process name corresponding to current thread: kernel_task

Clearly the same problem as everyone here... So the Genius i met the first time told me crazy things.... Do you think I have a chance if I try a second time ?

Well, it is almost the same. Everyone who had the issue and had its board replaced has the same identical error with a Panic on reading video RAM at address 0x00000100

As the title of the thread says : Panic NVRM[0/1:0:0]: Read Error 0x00000100

Your error is a Panic on reading NVRAM but the address at fault is not the same one (0x00070000) ...

and it is likely not a detail, but the possible sign of a different issue. And probably that's why the hardware test passed.

Before wasting money you should check a few things :

- check if RAM was upgraded in your computer (it could be an issue)

- check if the system crashes by starting on an external disk Lion fresh install

It may be flaky memory, or just hard disk corruption ... Then :

- talk with a genius and try to understand if the address being different could be due to another error

If it is the same error it normally happens just every few minutes, so it is very easy to show it live

Good luck

F.Y.I. Just bumping your Mac with your foot or something can cause a kernal panic. And, some Geniuses are like actual computer geniuses, so with them, there has to be a complicated answer. I would try a 2nd time if you didn't understand.

That's good. Ok, so the issue is likely to be the same one, or at least anyway related to the same source.

Just to remove any other possibility, can you try to install a fresh copy of Lion on an external hard disk and see if you have kernel panics anyway ?

If you do, then go back to Apple Store (which contry you are in ?) and :

1. show them the backtrace

2. tell them your RAM has not been changed

3. tell them that a fresh install did not fix the issue

4. reproduce the panic in front of they guy (you should be able to do it in a minute or so, just find the right task that triggers the problem every time, there are a few described in the first pages of this thread

When I had mine swapped, the hardware test passed without any problem as it was not capable to detect this issue !

FYI newly produced mid-2010 MBP 15" i7 (this issue is ONLY with mid-2010 MBP 15" with i7 CPU) do not have the bug. So if your board is swapped you will not have the problem again.

Let us know how it goes

Ok, I would try to Install Lion on my external HDD. I'm in France, and when i'll have done all the things you says, i will return to the Apple Store to have a real discussion with this "Genius"

Just to tell you I realize that the log i give you was the only one with the error 0x00070000, all the other are 0x00000100, so it's the same problem.

Thx for your help, i give you some info when i have some news.

I am in Paris, went to the Opera Apple Store and found excellent service there.

If you have 0x00000100 log, show it to the guy.

Now, if you are not covered anymore by Apple Care they may ask you anyway to pay for repair ... try to argument your case and have it done for free.

How come you are reporting this problem just now as it has been happening since more than a year, btw ?

So you recommand me to replace my logic-board ?

In this post,

lpisati wrote:

FYI newly produced mid-2010 MBP 15" i7 (this issue is ONLY with mid-2010 MBP 15" with i7 CPU) do not have the bug. So if your board is swapped you will not have the problem again

You say that this problem is only with MBP with i7 CPU, but I have an i5, and I also have the same crash... Did I misunterstand you ? If there is no risk to have the same problem few months after have paid for a new logic-board, i'm ready to do it... but I prefer to be sure, i'm a student, and I don't have many ressources ! If this doesn't solve the problem...I prefer save my money...

Well, I do not work at Apple, so I can't tell you anything more that what has been written on this thread about one year ago.

By reading all reports by the people that signaled the problem at the time, the forum (not Apple of course) seemed to agree that the issue was affecting mid-2010 MBP 15" with i7 mother board only. If you go back on this thread and read the posts you will realize that. After a while TS4088 was published, and in there they mention mid-2010 MBP 15" (no specific CPU type)

So, at the time we were all inferring issue was ONLY on i7 mother board.

When I went to Apple Store they did take it in for service just by showing Panic messages, by telling them we tried with fresh disk install, and by showing crash live (I think it happened just by opening FaceTime for instance)

The guy told me the issue could have been either motherboard related or RAM related. They actually swapped RAM first, tested it, then swapped motherboard, all in the same service session. Memory could be the culprit because of a timing mismatch in communication between motherbard and RAM.

That's all I know.

As I said before you should try fresh install (don't even install the GFX utility), then go the Apple Store and show them Panic backtrace (0x00000100 one), tell them you tried reinstalling Lion from scratch, and show bug live.