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

Hi All,

Hmm. I have question, perhaps someone can help me.

Does changing the logic board entail changing the hard-drive?

In other words, Is the hard-drive completely separate from the logic board in such a way that you can just switch out the logic board with the hard drive still in place, and you can just start up where you left off?

The main reason for my question is because I do a lot of work in Windows (BootCamped) and having to get back everything to the way it is now, before changing the logic board, is going to be a royal pain.

Any comments? Thanks!

Hi bobsterbobs,

The logic board and HDD are different components and replacing one does not require replacing the other. Of course good practice is to backup all your data before sending it off for repair just in case something goes wrong.

I'm having the random kernel panics as well - especially after waking up from sleep.

I took it to an apple store and asked them about the logic board issue / special test. The guy said that the test is now integrated in the 10.8 test suite that you can run when rebooting. He ran the tests and it didn't show anything weird. So he said - reinstall your OS and it's probably some 3rd part software....

Anybody got the same response?

Hi bodacious_sd,

"The guy said that the test is now integrated in the 10.8 test suite that you can run when rebooting."
To my knowledge 'the guy' is wrong. The test has not been included in the inbuilt test suite. According to the official internal Apple technical documentation, VST is the correct and only way to detect the fault. If they are not sure then remind them to reread the OP555 document, which is the official test and repair proceedure.
There is no reason for them to refuse to run VST as it is a quick and easy test.

Keep in mind that it is possible your fault is not related, in which case the VST will pass.

If you don't have any luck with the guy' then just go to a different Authorised Apple Repair Centre and hopefully they will follow proceedure.

Thanks! I dropped it off at the apple store and they said they were going to do a "full ASD TESTING" and called me back today that they couldn't find any issues.

Does "full ASD TESTING" include the VST test?

Hi bodacious_sd,

AST - Apple Service Toolkit is a quick set of test that run in their own environment and is intended to find quick and obvious hardware faults. Eg, faulty temp sensors, fans that don't spin, etc.

ASD - Apple Service Diagnostic is a fairly comprehensive test that is run through a cutdown OSX. It includes many of the AST tests but also runs software to stress the hardware in an attempt to elicit faults. It has a harder time finding faults because the hardware is abstracted from the software by the OS but it can do things that AST can't because it has a full OS.

VST - Video Service Toolkit is available as a test that can be launched from the home screen in AST but only on machines that meet the requirement (15" Mid 2010 MBP) and only after the normal set of AST tests have been run and the machine rebooted. I expect that what is happening is that when AST runs on the machine for the first time, after performing the test, it uploads the results to Apple. Apple know know that this machine is eligible to have the fault so when AST is loaded for the second time on the same machine, it is told to present the VST option.

It's a convoluted process but it works and only takes about 10min.

AST is loaded via netboot and is updated regularly so it can include new code to find new faults easily. ASD is released at the same time as a new lineup of hardware and is never updated. So if a new fault is found for a given system then ASD can never be updated to know about it.

So in answer to your question, no they did not run the correct test so they would not have found the fault.

Remind them to read OP555 which they have access to via GSX and then they can follow the official Apple service guidelines to find the fault.

Good luck, let us know how you get on.

Is there a technical reason why this is limited to the 15" models? I had the same problem with my 17" 2.66 GHz i7 mid-2010 MBP with GT 330M. I started getting the same NVRM: Read Error kernel panics and gray 'computer needs to restart' screens after about six months of use, running Snow Leopard. Finally one morning it turned off abruptly without warning and wouldn't turn back on or show any signs of life. I had to pay out of pocket for the logic board replacement six months out of warranty. That was in May, and now since September it's been hanging on the graphics card switch intermittently again - going from discrete to integrated graphics smashes the screen into one half of the display horizontally and distorts everything to a green color. This is the first I've seen of T

^ sorry about the truncation! Anyway I'm newly aware of TS4088 and wonder if it would be appropriate to ask for my 17" (with the same 2.66 i7 and 330M GPU) to be inspected under this pronouncement. The 90 day repair warranty was up in August so I'd otherwise be looking at a second out-of-pocket logic board replacement.

I've actually already bought another 17" just out of concern for general stability, but having already reduced the former to a $3,000 doorstop after less than two years of use has not been a fulfilling conclusion.

What do you think? Are these GPU issues categorically distinct for 15 & 17" MBPs with the same CPUs, GPUs & chipsets? I'm not otherwise sure why they would make explicit that only 15" models qualify for this service; hopefully it's not simply a result of underrepresentation of 17" owners.

I got it back from the store after explaining them what I wanted them to do. The short answer was (via telephone when they called me that it's ready) - yes we did everything, though it didn't sound like a technical person, so not sure if they did run the test procedure or not.

I got it back and the kernel panics are still happening, so I started the disabling various pieces of software.

My current suspect is the Twitter client. After not running it for a while the panics almost went away (at least they substantially lessened - maybe once every 3-5 days now), but they're not completely gone yet.

My computer has been having this issue for quite some time now. It is a Mid 2010 MBP 15". I took the computer in a few months back and Apple said it was the hard drive causing it. They replaced the drive, and I re-installed everything from scratch. The HD replacement did solve some other minor issues (either that or the rebuild did); however, it was crashing just as much with the noted panic's in this thread. So, I started to do some research and found this article. I took the laptop back to the Apple Store on 12/26 and got it back 12/29. I referecend this thread and asked them to do the VST. They actually could not get the VST to run while I was there. But, I gave them a very detailed description of the problem and obviously referenced the fact that the HD replacement didn't resolve the issue. The Apple genius said they would replace the mobo. Upon reciept of the computer on the 29th, Apple verified that they did find that the mobo was messed up. I also have not had a single panic since getting it back. So, we'll see how it goes, but it is lookign good so far.

My advice to anyone is to just stay persistent and bring as much data as you can. Make sure to leave the crash logs on your computer and ensure that they look at them while you are there. I was even able to get the computer to belly-up while there, so that helped greatly. Good luck!

I m getting this same error? how did u guys fixed? My MBP is mid 2010 15'.

i m tired of frequent reboots. Almost 5 to 6 reboots a day. Please help.

And i m out of warranty.

Interval Since Last Panic Report: 89016 sec

Panics Since Last Report: 17

Anonymous UUID: 507DA918-7189-DC2A-6860-FD62C7E38858

Sun Jan 6 22:09:10 2013

panic(cpu 2 caller 0xffffff7f887a8b25): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff811ba9c000 0x0a5480a2, D0, P2/4

Backtrace (CPU 2), Frame : Return Address

0xffffff80f847b7e0 : 0xffffff800801d626

0xffffff80f847b850 : 0xffffff7f887a8b25

0xffffff80f847b8e0 : 0xffffff7f888a24b3

0xffffff80f847b940 : 0xffffff7f888a2527

0xffffff80f847b9b0 : 0xffffff7f88bb7853

0xffffff80f847baf0 : 0xffffff7f888c8659

0xffffff80f847bb20 : 0xffffff7f887b28da

0xffffff80f847bbd0 : 0xffffff7f887adfac

0xffffff80f847bdc0 : 0xffffff7f887af9ba

0xffffff80f847bea0 : 0xffffff7f887431c4

0xffffff80f847bef0 : 0xffffff7f8a25171f

0xffffff80f847bf40 : 0xffffff7f8a2508e7

0xffffff80f847bf60 : 0xffffff800803dcde

0xffffff80f847bfb0 : 0xffffff80080b26b7

Kernel Extensions in backtrace:

com.apple.NVDAResman(8.0)[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f88741 000->0xffffff7f88a43fff

dependency: com.apple.iokit.IOPCIFamily(2.7.2)[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffff ff7f886af000

dependency: com.apple.iokit.IONDRVSupport(2.3.5)[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xff ffff7f8872d000

dependency: com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7f886ea000

com.apple.nvidia.nv50hal(8.0)[9F3D09B5-3158-3D9E-BDA3-E71576AAD3B7]@0xffffff7f8 8a51000->0xffffff7f88d73fff

dependency: com.apple.NVDAResman(8.0.0)[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f887 41000

dependency: com.apple.iokit.IOPCIFamily(2.7.2)[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffff ff7f886af000

com.apple.driver.AGPM(100.12.69)[FBC949AC-F94D-39CD-96A0-C6F121EA7546]@0xffffff 7f8a24f000->0xffffff7f8a25efff

dependency: com.apple.iokit.IOPCIFamily(2.7.2)[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffff ff7f886af000

dependency: com.apple.driver.IOPlatformPluginFamily(5.2.0d16)[41B414E9-EC1E-3724-A158-14FD4 8712B0C]@0xffffff7f891ec000

dependency: com.apple.iokit.IONDRVSupport(2.3.5)[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xff ffff7f8872d000

dependency: com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7f886ea000

BSD process name corresponding to current thread: kernel_task

Mac OS version:

12C60

Kernel version:

Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64

Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333

Kernel slide: 0x0000000007e00000

Kernel text base: 0xffffff8008000000

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

System uptime in nanoseconds: 15594338813149

last loaded kext at 5752909201335: com.apple.driver.AppleUSBTCKeyEventDriver 235.4 (addr 0xffffff7f8a391000, size 12288)

last unloaded kext at 5923170639380: com.apple.driver.AppleUSBCDC 4.1.22 (addr 0xffffff7f8a38c000, size 12288)

loaded kexts:

com.apple.filesystems.smbfs 1.8

com.apple.driver.AppleHWSensor 1.9.5d0

com.apple.driver.AudioAUUC 1.60

com.apple.filesystems.autofs 3.0

com.apple.iokit.IOBluetoothSerialManager 4.0.9f33

com.apple.driver.AGPM 100.12.69

com.apple.driver.AppleHDA 2.3.1f2

com.apple.driver.AppleMikeyHIDDriver 122

com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport 4.0.9f33

com.apple.iokit.IOUserEthernet 1.0.0d1

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.ApplePolicyControl 3.2.11

com.apple.driver.AppleIntelHDGraphics 8.0.0

com.apple.driver.AppleIntelHDGraphicsFB 8.0.0

com.apple.driver.AppleUpstreamUserClient 3.5.10

com.apple.driver.AppleMCCSControl 1.0.33

com.apple.GeForce 8.0.0

com.apple.driver.AppleMikeyDriver 2.3.1f2

com.apple.driver.AppleSMCPDRC 1.0.0

com.apple.driver.AppleSMCLMU 2.0.2d0

com.apple.driver.AppleLPC 1.6.0

com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0

com.apple.driver.AppleMuxControl 3.2.11

com.apple.driver.SMCMotionSensor 3.0.2d6

com.apple.driver.AppleUSBTCButtons 235.4

com.apple.driver.AppleUSBTCKeyboard 235.4

com.apple.driver.AppleUSBCardReader 3.1.0

com.apple.driver.AppleIRController 320.15

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless

finally 15 days after I left my macbook in the service (in Mexico), they replaced the logic board, since that, I'm not longer experincing the kernel panics again! but was really deficult to get it repair, because no Apple test detected the problem, neither the VST, all seems to be "ok", so they keep the mac in order to reproduce the error, and they did it more than once.

The problem now is my hard drive, since this kernel panics started (like 1 month ago) I had to repaired frecuently throw the disk utility partition, and now I think got worst, I'm suspecting all this seriously damage my HD.

Does anyone is having troubles with the HD since this issue???

And one more thing...

now my microphone is not working since I take it back from the service...

hope everyone can fix their macbooks!

alekb I frequently had to repair volume and repair permissions after crashes to get it to boot again. I have replaced my 750GB hard drive. I was able to get the drive in Mexico by buying a 750GB Seagate external USB drive for 900 pesos at Office Max and removing the drive from the case.

What did it cost to replace the logic board in Mexico?

Hi Spritrig,

i took it to apple, they replacing my logic board.

yes previously i was using intel graphic card to save myself from reboots. Really happy that they fixing it for free, else i would have too sell my house to get it fixed 😀

I have a MacBookPro 15" brand new Dec-2012. This NVRM[0/1:0:0] problem kills me every week or so. Brand new machine and it'll run maybe a week before crashing.

Took to Apple store. They ran the tests, couldn't find anything wrong, re-imaged it. Just crashed again.

This time, I've set "Computer Sleep" to Never. Maybe there's something about the sleep that's triggering it. So far, every time I've seen this issue, it's after I've been away from the laptop for a while.

Before the re-image, I had gfxCardStatus running and set to the discrete NVIDIA. (I need the graphics performance for my work.) Still crashed.

Maybe the sleep is tickling something.