Apple Intelligence now features Image Playground, Genmoji, Writing Tools enhancements, seamless support for ChatGPT, and visual intelligence.

Apple Intelligence has also begun language expansion with localized English support for Australia, Canada, Ireland, New Zealand, South Africa, and the U.K. Learn more >

You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

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

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

Reply
760 replies

Jul 22, 2011 5:17 PM in response to francois-vda

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...


You have no third-party software capable of causing a kernel panic, so that statement was wrong. This is either a hardware fault or an OS bug.

Jul 19, 2013 1:38 AM in response to francois-vda

I had my Macbook Pro (mid-2010) logic board replaced with Apple about 2 months ago due to the TS4088 after it it was tested and failed the Special Hardware Test.


All seemed fine after it. but recently my macbook started crashing again. However it is not the same as previous when it displays the kernel panic; but instead the screen starts getting fuzzy and then it crashes.


Attached are 2 photo's i took, at different times it has happened.

And a recorded video of it at :http://youtu.be/lH595zzAia4 - where you can see the screen is pixelated and moving statically, but the macbook is unresponsive.


Is this the same problem?


User uploaded file

User uploaded file

Apr 26, 2014 9:13 AM in response to meloman

RE: Mitigation for Failed VST test


If your Mac has been tested and failed the VST Test, it has not broken down from hard use or anything else, but has a Latent Defect that was there from its manufacture.


Reverting to 10.6.8 works because each version of Mac OS X uses the graphics chip a little differently. This is also the reason the problem gets worse with age -- as users upgrade their Mac OS X, it beats on the graphics chip harder and causes the Latent Defect to show up more and more.


On another thread on this subject, several users have suggested two different novel approaches for MacBook Pro 6,2 2010 that have failed the VST test and been refused free repair from Apple:


• One is to have a re-balling service work on the graphics chip on your motherboard, and once the graphics chip is removed, replace it with a new part before re-soldering. This can cost around US$200 complete.


• another is to make a setting change in "/System/Library/Frameworks/ApplicationServices.framework/Frameworks/CoreGraphi cs.framework/Resources/" and change a setting in the "Configurtion.plist" file to force all graphics writes to main store. IF your Mac has FAILED the VST Test, this seems to improve stability.


User uploaded file


GPU Panic - OSX 10.9 Mavericks - Macbook PRO 6,2


.

Aug 2, 2011 12:13 AM in response to jan_cph

hi everyone,

just a quick follow up:

it seems that my kernel panics stopped!

The last couple days i experienced a new strange behaviour of my macbook, when putting it to sleep by closing the lid it would get extremely hot. Putting it to sleep using the shortcut resulted in the screen coming back on after ca. 10 seconds, while the power light would flash very slowly.

I read that a SMC reset would be the frist step to fix that (new, additional) problem.

After the SMC reset everything was fine again, the mac is much cooler now than ever before.

Then i tried with the Nvidia card again, an surprisingly no crashes! - I could run skype (that was a guaranteed crash before), besides a HD video on youtube, and running Google Earth having a second monitor connected (i made a screenshot because i could not believe it myself 😉).



Of course the graphis card is only working properly since yesterday and this doesn't really mean much in this case, but i was hoping that some of you could try the same and share their experience here:

I think it is a combination of the SMC reset and the new drivers I installed coming directly from NVIDIA (i had done SMC resets prior to the installation of the new drivers without any result).

Here is the post that explains how to install NVIDIA's drivers: http://forums.macrumors.com/archive/index.php/t-1145844.html

A second thought I got is: maybe there is a problem with the SMC? After i got my logicboard exchanged i had a period of around a month where everything was fine, and then the problems returned. I found a comment telling the same here: https://discussions.apple.com/thread/2420192?start=1575&tstart=0 (post by Willem-A)


/jan

Aug 7, 2011 5:55 PM in response to ollimuc

News about the problem at Ars Technica:


http://arstechnica.com/apple/news/2011/08/buggy-nvidia-drivers-giving-2010-macbo ok-pro-owners-lion-upgrade-headaches.ars


And a link to a much larger/longer thread about this issue:


https://discussions.apple.com/thread/3191083?start=0&tstart=0


A note from the Ars article:


A commenter noted that Apple Care support technicians have offered another solution which appears to have permanently solved the problem on his machine. Navigate to ~/Library/Preferences/ByHost/, delete any files that contain "windowserver," and reboot the machine. The procedure may need to be repeated if you regularly connect to an external monitor once it is also connected.

Note that the user Library folder is hidden by default on Lion. You can get to it by holding down the Option key in the Finder's Go menu, use the Go To Folder command and paste in the full path, or use Terminal to make your ~/Library folder permanently visible.


...


I did not find the offending files on my machine. I'm not sure why they are generated or where they come from. I usually keep my MBP attached to a Cinema Display permanantly to get my work done. I definitely need that extra real estate.


Message was edited by: honkzilla

Aug 22, 2011 5:53 AM in response to francois-vda

This is what I sent to Mr. Jobs, and I hope each and everyone of you would do likewise:


Subject: 2010 MBP i7 Faulty Logic Board


Dear Mr. Jobs,


Apparently you are a very busy person, but I hope you would pay attention to my plead. I've been tolerating this infamous Panic NVRM problem (see https://discussions.apple.com/thread/3114550?start=105&tstart=0) for some time now, but I can no longer put up with it since the recent upgrade to Lion. I'm getting it even just doing a simple "Mission Control!"


As seen in the thread, many people resorted to replacing the logic board to get rid of the problem, but apparently the machine must be under warranty or Apple Care to get it for free. I bought Apple products not only because it's cool, but because I trust the people and the products at Apple, like I trust a certain brand of automobiles because of the brand reputation, in addition to how easy it helps me pick up chicks.


Now imagine that there is a faulty brake on my Japanese-brand (starts with a "T") eco-friendly car (no, you don't really pick up gals in one of these :P), am I supposed to pay for the replacement even if the warranty expires? There is a thing called "Recall" in the Auto industry (and other consumer products of course) due to faulty parts, and one would expect that the same practice applies to Apple products, but the Geniuses at Apple Store are certainly telling us otherwise.


I think it is only reasonable to expect a defect product (or a part) to be replaced free of charge, just like I would for some software applications I wrote and put into production in the financial institution I work in. I wouldn't tell the Business Unit that it's a new change requirement and charge them for the fix, would I?


Therefore, I sincerely hope that there will be a recall program for all MBP (or any other Mac machine for that matter) with the faulty logic board free of charge. I will be sending this plead to you weekly, and then daily, until I hear some good news from the Geniuses. You can treat it as a spam, but I will manually send this every time and encourage other people to do the same.


Yours Sincerely,


Alan

Oct 22, 2011 11:52 AM in response to Everandever

Thanks, I've installed gfxCardStatus and it does indeed provide a workaround. The reproducible black screen kernel panic with guitar tuning in Garageband does not occur when Integrated Only is selected. If Discrete Only is selected, sure enough the same panic in Garageband guitar tuning occurs - NVRM[0/1:0:0]: Read Error 0x00000100.


Seems this is not the first time Apple has had problems with NVIDIA hardware, there were display issues with 15" and 17" MBPs equipped with the NVIDIA GeForce 8600M GT graphics processors sold 3 to 4 years ago. http://support.apple.com/kb/ts2377


I have read the Apple KB posting on this current issue and realise they are aware of it (http://support.apple.com/kb/TS4086) - one can only hope that a fix is coming SOON!


Regardless I can't help but feel that Apple's relentless PR about meteoric sales figures for iOS mobile devices and the accumulation of $75 billion worth of cash and security assets starts to wear a bit thin when hardware as fundamentally basic as an MBP's graphic display does not function correctly.


Is Apple not paying sufficient attention to production/component quality control?

Oct 24, 2011 9:06 AM in response to neldyn

Thank you very much for that report neldyn. Yes, I have the backlit keyboard symptom as well!


I have been (and I presume so have others) been on the lookout for the dollar amounts Apple is throwing around to get this issue fixed. The amounts you mentioned in your post is really very informative. Thank you once again.


Makes one wonder how they come up with these numbers. Cupertino is very aware of this problem of course. Its so very evil of them to actually know that a software fix is in the works while simultaneously offering a costly hardware fix, which, as some people have reported on this thread and elsewhere, is a very hit-or-miss proposition.

Oct 24, 2011 3:22 PM in response to wibrandy

wibrandy wrote:


Well, for those that have not gotten their logic board replaced, there might be a resolution:


http://support.apple.com/kb/TS4088


It showed up in Software Update today. Would be curious how it works for everyone


Finally Apple fixed it. This resolved the problem for me. Fingers crossed, but my previous methods of instantly crashing no longer work.


I'm pretty amazed it took this long to fix. My computer has hardly been usable since I upgraded to Lion back in July.


Hopefully this is over for good and I can get back to work.

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

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.