Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

3 points

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

I've sent my MBP i7 mid-2010 for repair with the following frequent and intermittent kernel panic to no avail: panic(cpu 2 caller 0x9cdc8f): NVRM[0/1:0:0]: Read Error 0x00000100: ... to no avail.

I happen to have subscribed to AppleCare for this machine but this did not make any difference. The approved repair center I dealt with just reformatted the HD per Apple's support instructions (twice !) and were unable to reproduce the panic. I called the Apple support folks in Ireland directly with the incident # and got told that there was basically nothing wrong with my machine and that this was bound to be caused by non-Apple software (mind you, the support guy I talked to didn't even know that XCode was an Apple product - sic). I however believe this is very likely due to a faulty NVidia video card on the logic board.

Has this happened to someone else? How did you get resolution? Right now I am stuck with an unreliable machine and seem unable to get it fixed. Any help would be VERY appreciated.

Thank you,

François

FULL DUMP

Interval Since Last Panic Report: 8846 sec

Panics Since Last Report: 1

Anonymous UUID: 46BBCA42-CAD2-4E5E-9720-C4AB2DEBAA74

Thu Jun 9 19:46:32 2011

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

Backtrace (CPU 2), Frame : Return Address (4 potential args on stack)

0x5c41a358 : 0x21b510 (0x5d9514 0x5c41a38c 0x223978 0x0)

0x5c41a3a8 : 0x9cdc8f (0xbe323c 0xc53840 0xbf23cc 0x0)

0x5c41a448 : 0xae85d3 (0x9164404 0x96c3004 0x100 0x0)

0x5c41a498 : 0xadf5cc (0x96c3004 0x100 0x5c41a4c8 0x9bd76c)

0x5c41a4c8 : 0x16af965 (0x96c3004 0x100 0x438004ee 0x0)

0x5c41a608 : 0xb07250 (0x96c3004 0x93b3004 0x0 0x0)

0x5c41a648 : 0x9d6e23 (0x96c3004 0x93b3004 0x0 0x0)

0x5c41a6e8 : 0x9d3502 (0x0 0x9 0x0 0x0)

0x5c41a898 : 0x9d5536 (0x0 0x600d600d 0x702b 0x5c41a8c8)

0x5c41a968 : 0xc987bc (0xc1d00040 0xbfef0033 0xbfef0034 0x857c)

0x5c41a9d8 : 0xca802a (0xbe8da00 0x8514b00 0x5c41aa08 0x0)

0x5c41a9f8 : 0xcccc16 (0x8514b00 0xb 0x5c41aa18 0x224fc5)

0x5c41aa28 : 0xccd431 (0x984f000 0x0 0x5c41aa4c 0x0)

0x5c41aa58 : 0xcad66d (0x984f000 0x7cf51080 0x0 0x5d)

0x5c41aaa8 : 0xc6f6ee (0x46580000 0x0 0x0 0x3)

0x5c41ab18 : 0xc6ee6c (0x46580000 0x0 0x2 0x3)

0x5c41ab48 : 0xc6e254 (0x46580000 0x0 0x18 0x5029e8)

0x5c41ab78 : 0xc73676 (0x46580000 0x1 0x18 0xc75ce5)

0x5c41abb8 : 0x56abea (0x46580000 0x1 0x18 0x5c41abe0)

0x5c41ac38 : 0x56afa4 (0xcf0d70 0x46580000 0x97b6f80 0x2)

0x5c41ac88 : 0x56b88b (0x46580000 0xa 0x5c41acd0 0x0)

0x5c41ada8 : 0x285be0 (0x46580000 0xa 0x97b6f80 0x2)

0x5c41be58 : 0x21d8be (0x97b6f58 0x877b5a0 0x1fda28 0xfd47)

0x5c41be98 : 0x210a3e (0x97b6f00 0x0 0x975ec70 0xc000540)

0x5c41bef8 : 0x216ca1 (0x97b6f00 0x0 0x0 0x0)

0x5c41bf78 : 0x295168 (0x925b728 0x0 0x0 0x0)

0x5c41bfc8 : 0x2a149d (0x925b724 0x1 0x10 0x8c71e24)

Kernel Extensions in backtrace (with dependencies):

com.apple.GeForce(6.2.6)@0xc55000->0xd0afff

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

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

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

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

com.apple.nvidia.nv50hal(6.2.6)@0x1579000->0x198dfff

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

com.apple.NVDAResman(6.2.6)@0x967000->0xc54fff

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

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

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

BSD process name corresponding to current thread: WindowServer

Mac OS version:

10J869

Kernel version:

Darwin Kernel Version 10.7.0: Sat Jan 29 15:17:16 PST 2011; root:xnu-1504.9.37~1/RELEASE_I386

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

System uptime in nanoseconds: 668789071497

unloaded kexts:

com.apple.driver.AppleUSBUHCI 4.1.5 (addr 0x141b000, size 0x65536) - last unloaded 138951876487

loaded kexts:

com.apple.driver.AppleHWSensor 1.9.3d0 - last loaded 23159326916

com.apple.filesystems.autofs 2.1.0

com.apple.driver.AGPM 100.12.19

com.apple.driver.AppleMikeyHIDDriver 1.2.0

com.apple.driver.AppleHDA 1.9.9f12

com.apple.driver.AppleUpstreamUserClient 3.5.4

com.apple.driver.AppleMCCSControl 1.0.17

com.apple.driver.AppleMikeyDriver 1.9.9f12

com.apple.driver.AudioAUUC 1.54

com.apple.driver.AppleIntelHDGraphics 6.2.6

com.apple.driver.AppleIntelHDGraphicsFB 6.2.6

com.apple.driver.SMCMotionSensor 3.0.0d4

com.apple.kext.AppleSMCLMU 1.5.0d3

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.AudioIPCDriver 1.1.6

com.apple.driver.AppleIntelNehalemProfile 76

com.apple.driver.ACPI_SMC_PlatformPlugin 4.5.0d5

com.apple.driver.AppleGraphicsControl 2.8.68

com.apple.GeForce 6.2.6

com.apple.driver.AppleLPC 1.4.12

com.apple.driver.AppleUSBTCButtons 200.3.2

com.apple.driver.AppleUSBTCKeyboard 200.3.2

com.apple.driver.AppleIRController 303.8

com.apple.driver.AppleUSBCardReader 2.5.8

com.apple.BootCache 31

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.iokit.SCSITaskUserClient 2.6.5

com.apple.iokit.IOAHCIBlockStorage 1.6.3

com.apple.driver.AppleUSBHub 4.1.7

com.apple.driver.AppleFWOHCI 4.7.1

com.apple.driver.AirPortBrcm43224 427.36.9

com.apple.iokit.AppleBCM5701Ethernet 2.3.9b6

com.apple.driver.AppleEFINVRAM 1.4.0

com.apple.driver.AppleSmartBatteryManager 160.0.0

com.apple.driver.AppleUSBEHCI 4.1.8

com.apple.driver.AppleAHCIPort 2.1.5

com.apple.driver.AppleACPIButtons 1.3.5

com.apple.driver.AppleRTC 1.3.1

com.apple.driver.AppleHPET 1.5

com.apple.driver.AppleSMBIOS 1.6

com.apple.driver.AppleACPIEC 1.3.5

com.apple.driver.AppleAPIC 1.4

com.apple.driver.AppleIntelCPUPowerManagementClient 105.13.0

com.apple.security.sandbox 1

com.apple.security.quarantine 0

com.apple.nke.applicationfirewall 2.1.11

com.apple.driver.AppleIntelCPUPowerManagement 105.13.0

com.apple.driver.DspFuncLib 1.9.9f12

com.apple.driver.AppleProfileReadCounterAction 76

com.apple.driver.AppleProfileTimestampAction 76

com.apple.driver.AppleProfileThreadInfoAction 76

com.apple.driver.AppleProfileRegisterStateAction 76

com.apple.driver.AppleProfileKEventAction 76

com.apple.driver.AppleProfileCallstackAction 76

com.apple.driver.AppleSMBusController 1.0.8d0

com.apple.iokit.IOFireWireIP 2.0.3

com.apple.iokit.IOSurface 74.2

com.apple.iokit.IOBluetoothSerialManager 2.4.0f1

com.apple.iokit.IOSerialFamily 10.0.3

com.apple.iokit.IOAudioFamily 1.8.0fc1

com.apple.kext.OSvKernDSPLib 1.3

com.apple.driver.AppleHDAController 1.9.9f12

com.apple.iokit.IOHDAFamily 1.9.9f12

com.apple.iokit.AppleProfileFamily 76

com.apple.driver.AppleSMC 3.1.0d3

com.apple.driver.IOPlatformPluginFamily 4.5.0d5

com.apple.driver.AppleSMBusPCI 1.0.8d0

com.apple.nvidia.nv50hal 6.2.6

com.apple.NVDAResman 6.2.6

com.apple.iokit.IONDRVSupport 2.2

com.apple.iokit.IOGraphicsFamily 2.2

com.apple.driver.BroadcomUSBBluetoothHCIController 2.4.0f1

com.apple.driver.AppleUSBBluetoothHCIController 2.4.0f1

com.apple.iokit.IOBluetoothFamily 2.4.0f1

com.apple.driver.AppleUSBMultitouch 206.6

com.apple.iokit.IOUSBHIDDriver 4.1.5

com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.5

com.apple.iokit.IOUSBMassStorageClass 2.6.5

com.apple.driver.AppleUSBMergeNub 4.1.8

com.apple.driver.AppleUSBComposite 3.9.0

com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.5

com.apple.iokit.IOBDStorageFamily 1.6

com.apple.iokit.IODVDStorageFamily 1.6

com.apple.iokit.IOCDStorageFamily 1.6

com.apple.driver.XsanFilter 402.1

com.apple.iokit.IOAHCISerialATAPI 1.2.5

com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.5

com.apple.iokit.IOUSBUserClient 4.1.5

com.apple.iokit.IOFireWireFamily 4.2.6

com.apple.iokit.IO80211Family 314.1.1

com.apple.iokit.IONetworkingFamily 1.10

com.apple.iokit.IOAHCIFamily 2.0.4

com.apple.driver.AppleEFIRuntime 1.4.0

com.apple.iokit.IOHIDFamily 1.6.5

com.apple.iokit.IOUSBFamily 4.1.8

com.apple.iokit.IOSMBusFamily 1.1

com.apple.kext.AppleMatch 1.0.0d1

com.apple.security.TMSafetyNet 6

com.apple.driver.DiskImages 289

com.apple.iokit.IOStorageFamily 1.6.2

com.apple.driver.AppleACPIPlatform 1.3.5

com.apple.iokit.IOPCIFamily 2.6

com.apple.iokit.IOACPIFamily 1.3.0

Model: MacBookPro6,2, BootROM MBP61.0057.B0C, 2 processors, Intel Core i7, 2.66 GHz, 4 GB, SMC 1.58f16

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

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

Memory Module: global_name

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

Bluetooth: Version 2.4.0f1, 2 service, 12 devices, 1 incoming serial ports

Serial ATA Device: ST9500420ASG, 465.76 GB

Serial ATA Device: MATSHITADVD-R UJ-898

USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfd100000

USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8507, 0xfd110000

USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0xfd120000

USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfa100000

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

USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8218, 0xfa113000

USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403, 0xfa130000

USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0236, 0xfa120000

MacBook Pro, Mac OS X (10.6.7)

Posted on Jun 12, 2011 10:04 AM

760 replies

Feb 22, 2013 4:09 PM in response to alekb

alekb-

the important feature is Disk Utility is ( Repair Disk ). If that gives you problems, they are serious ones.

( Repair Permissions ) always throws error messages, and you can ignore them unless they appear in RED.

palleba

Level 1

0 points

Feb 22, 2013 6:03 PM in response to francois-vda

I have the same problem as everybody else here. I have a MacBook Pro mid 2010. My scree turns suddently black and I have to force the computer to turn of by pressing the start buttten. This happens every 15 min.

Feb 22, 2013 7:44 PM in response to palleba

Not every Kernel Panic is the same. Some posters on this thread have different problems. If you have the panic-reason listed in the title, you should go to the genius Bar with this article printed out on paper in your hand:

TS4088- MacBook Pro (15-inch, Mid 2010): Intermittent black screen or loss of video

To determine if you have this same kernel panic, use this article:

Mac OS X: How to log a kernel panic

If yours is NOT:

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

then cut and paste one here for Readers to look at and help determine the cause, or start a new thread all your own with a catchy title and paste it there.

alekb

Level 1

19 points

Feb 23, 2013 7:49 AM in response to Grant Bennet-Alder

Hi! yes this is the problem, There is an error in RED so it says for me to repair it from the "Recovery Partition" so I reset my mac and press ALT, by the disk utility form the other partition I repair the disk, and then restart. Now when I run the test there is no more errors, there is a GREEN text about that, fine. But in a week o less, happens again and again, even the system feels slower.

So, I would like to know if other people is having this problem? because all started with the mountain lion installation, and the kernel panics too, after changing the logic board no more kernel panics but the HD seems to be damage because of this.

thanks!

Feb 23, 2013 8:07 AM in response to alekb

If you need to ( Repair Disk ) frequently, that could be an indication that your Hard drive is having Hardware problems. This sometimes leads to the drive dying suddenly.

If you do not have good backups, make a good backup immediately.

alekb

Level 1

19 points

Feb 23, 2013 8:29 AM in response to Grant Bennet-Alder

thanks for your replay! yes there is a hardware problem, I'm not going to loose my info because I have backups, so if my mac "exploites now" that's not a big problem jajaja!

Today I picked it form the service, and they told my about other cases when ML damage HDs (hardware because of overheating), so they want to change the HD for a new one and install the system "garantee" by them themselves, for a considerable amount of money. So it doesn't seems to be fair, why Apple sell their system online if, even following all instructions carefully, this has to be made by technicians to be "garantee". I'm not stupid! I installed all kind of OS in my life, without breaking a single pice of hardware, so now is not only the price of the OS, you also have to pay for the installation of the OS to be "garantee", and in my case for a new HD and the installation of the HD... ah and diagnostics too, that's ridiculous!

but I can't forgot the mac was a failed one, and all problems stared with the update form SL to ML, the Kernel Panics, and HD problems too, just annoying this new ML (don't even say it's complete name! shhh)

bye!

alekb

Level 1

19 points

Feb 23, 2013 8:34 AM in response to alekb

And the strangest thing this technichian said to me: that I can keep the HD for store information without problem, but not to run the OS, so is really damage? am I that paranoid? jajaja

Feb 23, 2013 8:58 AM in response to alekb

If your car gets a flat tire, buying a new car will DEFINITELY fix the problem. Guaranteed!

--------

My approach would be to make a second backup, then erase the drive and security erase, Zero all data.

This operation erases Everything AND tells the drive controller to substitute spare blocks (that it has in reserve) for any blocks found bad after Zeroing. The process take a few hours, but if it completes without errors, your drive has 100 percent good blocks again.

Another alternative is to just keep using it, and buy a drive to replace the one inside your Mac when it fails. If you buy an external enclosure as well, you could install a new copy of Mac OS X on it and be ready if the old one fails.

dmdimon

Level 3

856 points

Mar 7, 2013 1:22 AM in response to Grant Bennet-Alder

Grant Bennet-Alder wrote:

My approach would be to make a second backup, then erase the drive and security erase, Zero all data.

This operation erases Everything AND tells the drive controller to substitute spare blocks (that it has in reserve) for any blocks found bad after Zeroing. The process take a few hours, but if it completes without errors, your drive has 100 percent good blocks again.

Basically I'm with you on this, but there are some nuances.

1) Special zones of drive will not be affected by this method. Like partition tables and so on. They will benefit just from HD internal bad blocks remapping methods - and here comes 2:

2) on lowest level block substitution list have limited length - so if there are too much bad blocks - they just can't be substituted with good ones

Mar 7, 2013 7:45 AM in response to dmdimon

dmdimon-

There are a finite number of spares. At some point, the drive may indeed run out. If this occurs, the message back from erase disk will be "Initialization Failed!"

Also, if more than 10 blocks are substituted in one pass, you may get "Initialization failed!" Whether you decide to run another pass is a delicate judgement call.

Google has found (over an enormous sample of their drives) that most drives that develop more than one Bad Block that is spared out but the drive is left in service will be determined to be "BAD" (Bad enough to warrant replacement) within six months.

This brings up the possibility that a drive running out of spares is becoming inherently unreliable, and should either be moved to light duty service (second backup drive) or retired to a long life of propping open doors.

Mar 14, 2013 12:31 PM in response to nicksmacalret

Thought I give an update on this from my experience

After visiting the Apple Store twice with no solution and panics pretty much every day, I went for a third time, prepared with all the printouts (again) and got the logicboard issue diagnosed within 5 minutes (first running the Apple System Test then the Apple Video Test). Big red "FAILED" with "replace MLB". They ordered a replacement and got it fixed and no panics so far...

I talked to the store manager about the whole experience and he pretty much said that the Geniuses have their protocol (and standard test suite) that they have to follow. Even if I bring them printouts and pointers to support and repair articles they tend to ignore me, since they don't trust any of the information out there (not quite his words, but that's how it came across). With my 3rd appointment, the first genius that looked at it pretty much ignored me too and started the default suite of tests - luckily another genius was standing next to him and said "those are the 2010 MBP - you have to run the VST on it", which the 2nd guy did when the 1st one stepped out. So the only conclusion that I took away was - let them run their system tests and diagnostics suite and talk to you about reinstalling MacOS and blame it on your software. At the end, show printouts of the KB article and reference the OP procedure that was mentioned and ask them to run AST and then VST. This produced the error message. For this error it's a rather fast test (5min), so checking the computer in to run tests in the back won't help (at least in my case, since they didn't run the appropriate tests anyway, despite claiming they did). If that doesn't get anywhere, finish up with the genius and talk to the manager about it. For me 3/4 didn't know anything about this issue, wouldn't run the required tests and wouldn't be convinced to do otherwise by me - only another genius that knew about it was able to get it solved.

Mar 15, 2013 7:39 AM in response to francois-vda

I've been having this issue for a couple of months now, with my MBP spontaneously going into panic and rebooting sometimes multiple times a day. Took it to the Apple store where it was diagnosed with a bad video card, however, in my case this repair was going to cost me $900 due to the fact that I'd replaced the HDD on my own earlier. So I decided to live with it.

At any rate, I just installed gfxCardStatus, and set it up to force everything to use the integrated GPU only. So far, this is working GREAT. In the past, working with iPhoto for more than about 5 minutes would almost always cause a panic, but that seems to have ben cleaned up. Fantastic!

I'm not sure with the limitations are of using integrated GPU only, but so far, I'm certainly happy to live with them!

I would be intersting to know if there is a lower level way to shut down the NVidia GPU, perhaps through BIOS switch, but in the meantime, gfxCardStatus seems to be working.

dmdimon

Level 3

856 points

Mar 15, 2013 7:48 AM in response to i_am_Halloran

i_am_Halloran wrote:

I'm not sure with the limitations are of using integrated GPU only, but so far, I'm certainly happy to live with them!

Unwise. like instead repairing car you switched off 4 cylinders of 6 total and it no more gives you strange sounds during drive.

Mar 15, 2013 7:52 AM in response to dmdimon

Close; but no ciger. More like it no more gives you fatal explosions during drive... to put the wisdom into perspective.

dmdimon

Level 3

856 points

Mar 15, 2013 8:17 AM in response to i_am_Halloran

let me say it other way - you paid for dedicated GPU, you paid for dedicated pricey GDDR5 videoram, that investment intended to pay back with exellent OpenCL performance. For example now your computer will not qualify for CaptureOne OpenCL acceleration, for Adobe CS6 GPU acceleration, etc, etc.

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