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 14, 2012 3:06 AM in response to francois-vda

There is a even larger post in here: https://discussions.apple.com/thread/3191083?start=0&tstart=0

I don't bother to read all the pages in here. All I want to add:

http://support.apple.com/kb/TS4088?viewlocale=en_US&locale=en_US


There is a repair program. It will be valid for two years after purchase so you might need to hurry, unless you have AppleCare. Anyway, most Apple Certified Repair facilities - and even Apple Genius Bars - seem to be unaware of that specific program. That is why you have to be persistent. If you can, try again to reproduce the issue in the store. Maybe you are lucky - i did this once with an iPhone and it immediately triggered the Genius to have a more thorough look and/or believe me. If not: Try again, try different people, try different service providers. They need to run a specific graphics test (that is not the same as the Apple Hardware test that you yourself can run). But this test does not always show the issue. Again, if you insist you may eventually run into someone who will help you.


Clearly, the situation is unacceptable.


In my instance, before i went into the Apple Store, i completely erased my hard disk and started fresh over with a newly downloaded copy of Lion (at that time, it was 10.7.3 and i generated a USB-Stick from the download). I never had a problem ever since.


This means that although i had the same symptoms, my problems were actually software-related and not hardware.


Good luck.

Jul 23, 2012 6:55 AM in response to Nestor Urquiza

Just to add that the issue will not happen if you do not use an extended Display. I had my mothrboard replaced on Feb 2011 for a similar Kernel Panic (look into

https://discussions.apple.com/thread/2712724?answerId=13035539022#13035539022 for Nestor Urquiza to see my report). By that time it was:


Kernel Extensions in backtrace (with dependencies):

com.apple.nvidia.nv50hal(6.2.6)@0x5c084000->0x5c498fff

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

com.apple.NVDAResman(6.2.6)@0x5b91f000->0x5bc0cfff

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

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

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



The error now is:


Kernel Extensions in backtrace (with dependencies):

com.apple.nvidia.nv50hal(6.4.0)@0x15e2000->0x19f6fff

dependency: com.apple.NVDAResman(6.4.0)@0x98f000

com.apple.NVDAResman(6.4.0)@0x98f000->0xc7cfff

dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x949000

dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x982000

dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x960000


I think that Apple has a perfect way to replicate this issue now as I stated above (through Audium)


I will head to the Store for a solution to this problem as soon as I am able to clean up my personal MAC to get transferred my work stuff.

Sep 16, 2012 8:51 PM in response to JustKnowz

My biggest concern is how am I going to leave my mac at the service provider without shelling out $80 when I already did all the leg work of troubleshooting the problem with French Toast, Cody, Allen & everybody else on this community? Should I call Apple Customer Service again with reference to article https://discussions.apple.com/thread/4113257?tstart=0 That would be article TS4088. Suggestions anyone?

Sep 21, 2012 1:25 AM in response to macduncan

Hi macduncan


> I work for 15 years in the IT i never experiance this after a upgrade of software with anny hardware vendor.


So have I and I've seen it on quite a few occasions. As software is updated it will use the hardware differently, make different system calls etc. If a chip has a hardware fault you have two options, release a patch that avoids the fault (if practical) or replace the chip.


> what is apple doing about it?


Replacing the faulty chip (which requires replacement of the whole logic board). It seems that a workaround for Mountain Lion was not possible (unlike 10.6 & 10.7)


> And when you pay 2899 euro for a Macbook Pro and pay for there new software where is the support?


The support is the same place it has always been. At your nearest authorised Apple support centre. It's a well known fault (now that Mountain Lion is gaining wide spread addoption on the mid 2010 15" MBP) with a documented pepair proceedure. http://support.apple.com/kb/TS4088


Apple are very aware of the issue and have a free replacement program in place that all repair centres (should) know about (it's documented in GSX). The verification process is as simple as running AST followed by VST. Once VST has recorded the failure in GSX the replacement can be ordered with the appropriate warranty code.


This is exactly the service and support I expect.

Sep 24, 2012 9:51 AM in response to FrenchToast

I finally got my MBP seen at the Genius Bar and as I was expecting the tests were passing even with the extended monitor. Here is when a consistent test case helps. So I went ahead and open Audium to show the Genius how the graphic card would go off. Here is as a reminder my test case:


https://discussions.apple.com/thread/3114550?answerId=18935520022#18935520022


Remember to use an external monitor plus your MBP Display when running the test case.


Good luck!

-Nestor

Oct 11, 2012 8:43 AM in response to checkyourmirrors

Go back to your Genius, quote http://support.apple.com/kb/TS4088 and ask them to run the test with an external monitor connected. I didn't even make it out of the building before they called me back to say they were replacing the logic board. I have not had one single incident since that time. I haven't changed software or drivers either. It is a problem that started with my mid-2010 15" MBP about July 4 of 2012 and lasted until the end of August when I took it in.

It is important to make sure you tell them to look at TS4088. My Genius didn't know about it. They initially tested without an external monitor attached, called me back in to say it checked out fine. When I pressed them and asked if any test was with an external monitor attached, the answer was no. I requested that recheck and that is when I didn't make it out of the building before it failed the second test.

It is worth well worth the effort because all I was getting before was more and more frustrated. The software based fixes listed here only reduced the frequency, but never eliminated the problem. Get the logic board replaced before it is too late and they charge you for it.

Nov 13, 2012 1:36 PM in response to dmdimon

Lol, obviously dmdimon and I are talking about different faults. The "Frequent Panic NVRM[0/1:0:0]: Read Error 0x00000100" I am talking about is a known hardware fault (see my earlier posts in this thread) and is not related to heat. It is publicly documented here;

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


The way to tell if your machine is affected (as more than one issue can generate this kernel panic) is;

1) Your machine is a MacBook Pro 15-inch, Mid 2010

2) The problem goes away if you disable the nVidia card

and bonus points if;

3) It only started happening after upgrading to ML (seems that there was a work around in the video drivers for the older versions that couldn't be implemented in ML).


Ta,

Nov 14, 2012 12:52 AM in response to MrSparkle75

MrSparkle75 wrote:


Lol, obviously dmdimon and I are talking about different faults. The "Frequent Panic NVRM[0/1:0:0]: Read Error 0x00000100" I am talking about is a known hardware fault (see my earlier posts in this thread) and is not related to heat. It is publicly documented here;

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


Sadly no.

We're talking about same problem. In Apple support message you pointed to not stated cause of problem.


see yourself:


1) If you'll do a bit deeper search, you'll find that nVidia had problems with thermal dissipation on mentioned GPUs and with packaging quality. there even been clash between Apple & nVidia on that. So this error is thermal-bound.


2) If you'd know nVidia drivers ideology (unified driver architecture) you'd know that equal error report means equal problems independently from hardware since first GeForce chips with UDA drivers, so it is thermal problems on ANY nVidia GPU


3) If you'd watch Apple strategic movement in software development, you'd know that everything goes GPU offloaded - so ML just gives more load to GPU than L, thus - more heat from GPU.


Thus, everyone, who worked under 10.7 happily and got troubles under 10.8 just worked on the edge of GPU thermal stability - and crossed that edge.


Thus, lowering GPU temp will help if GPU not degraded.


To make long story short - there was multiple reports on not exellent quality of GPU-heatsink thermal contact in MBP. So here from my recommendation. Also you can try to spin-up coolers with fan control or something, should help - but worse. Also theoretically you can underclock GPU core/memory - or wait until it'll be done in some drivers version or tweaking utility.

Nov 14, 2012 2:41 AM in response to dmdimon

I respectfully choose to disagree. As Adam Savage would say, "I reject your reality and choose to substitue my own." :)


Firstly the concept that previous OS were "on the thermal edge" is unlikely. The tiny amount of additional 3D load that ML puts on the GPU vs the amount that a 3D game does, would have resulted in Loin systems crashing every time a game was played and couldn't be resolved with a software patch. Also let's not get started on what would happen in hot weather.


Secondly a real thermal issue is unlikely (although not impossible) to behave the same every time. Thermal faults result in random bit swapping so one moment the GPU might try to access a memory location that doesn't exist. The next time it might read the wrong value back for a colour in a texture map resulting in video glitch.


Thirdly, pulling your own machine apart would be a silly thing to do (in terms of voiding your warranty and potentially damaging the machine) when you consider that Apple have a free replacement program for this fault which doesn't even require the owner to have AppleCare on the machine.


What I do agree with is that should you have a heat related issue caused by faulty conduction between the GPU and heatsink, then replacing the thermopaste would likely fix the problem. But I would only do this on a machine that is out of warranty and not covered by a replacement program.


I also agree that Apple have had heat issues with nVidia in the past. http://support.apple.com/kb/TS2377

This fault was actually heat related and would cause random issues. It was easy to trigger just by doing anything that made the GPU work hard enough.


Just my 2c.

Nov 23, 2012 2:13 PM in response to alekb

alekb - Read bulletin TS4088.


http://support.apple.com/kb/TS4088?viewlocale=en_US&locale=en_US



Apple repairs this defect free of charge up to 3 years from the date of sale.

It doesn't matter if it's out of warranty.


Print the bulletin and take it to an Apple store or Authorized repair.

They're obligated to repair it free of charge. The repair entails replacing the logic board.

Jan 1, 2013 7:16 PM in response to francois-vda

I am getting the black screen when I plug in the external monitor on my 15" Early 2011 MBP with AMD 6075M GPU. 😟 Reboot starts with red striped screen followed by black screen with backlight on.


This has been an absolute nightmare, stopping my work for a month so far. Restoring my data from backup is a waste of time because the computer crashes and frequently corrupts the hard drive (even with new hard drive). See photos on my thread. (Black screen wasn't interesting to photograph.) I rarely get a panic notice.

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

So I have an Early 2011 MBP manufactured in Feb 2011. This is in the last month of the April 2010 to February 2011 manufacture period. However mine is an Early 2011 rather than Mid 2010 MBP. By manufacture date I should be covered. What about the Mid 2010 vs. Early 2011 designation? Seems kind of ambiguous.
http://support.apple.com/kb/TS4088

Jan 7, 2013 12:33 PM in response to vitaminme

Vitamineme, I got mine to stop crashing reverting to Snow Leopard and by setting:


System Preferences --> Energy Saver & uncheck "Automatic graphics switching".


My computer reliably crashed by using iPhoto in either Snow Leopard or Mountain Lion (ML, or by plugging in the external monitor on Montain Lion. I belive turning off the graphics switching will work on ML as well. It hasn't crashed for 5 days, and I was having crashes multiple times a day before.


This will get my work going again. After I go to the USA, I will follow Apple's remedy instrtuctions. http://support.apple.com/kb/TS4088

Jan 28, 2013 1:55 PM in response to jamespaulley

Hi jamespaulley, linuxlizard, bmccarthy2hp, vitaminme,


You will find the ansers to all your questions in the thread if you just go back and read...


In short;


jamespaulley - yes, ask them to run VST which will show the error (read back through the thread for detailed instructions on how to do that). Then remind them to read OP555 which has the details on how they can request the replacement logic board even if it is out of warranty.


linuxlizard - you have a different fault the one discussed in this thread is only for the 15" mid 2010. Good luck.


bmccarthy2hp - if the machine is not a 15" mid 2010 then it won't be covered and it will have to still be under warranty or the Mac repair agents will charge you to fix it. If it is then it is covered for 3 (or maybe 4) years from the purchase date irrelevant of the warranty status (assuming you haven't dropped it and left a big dent in the case).


vitaminme - as mentioned numerous times, the fact it is out of warranty is irrelevant. Quote surrort article http://support.apple.com/kb/TS4088, repair process OP555 and AST/VST to get the job done. Unfortunately there are still repair agents that have not come across this issue and may give you friction. If they follow the process of running AST then VST and reading OP555 then it will become clear to them.


Good luck.

Jan 28, 2013 3:32 PM in response to MrSparkle75

Thankyou for reminding participants to look back into the history of this thread, MrSparkle75.


All - You'll find from my previous post at https://discussions.apple.com/thread/3114550?answerId=19233354022#19233354022 that 17" Mid-2010 MacBookPros will exhibit this problem and others and will have their logic board replaced for $free if you are as persistent as I was.


The Genius at our local Apple store would not authorise an out-of-warranty logic board replacement given TS4088 and a demonstable graphics and logic board panic complying with the 15" symptom list. They directed me through Apple Care to local Apple Technical Support people who liased with Apple Engineering (USA) throughout the thorough diagnosis of this problem. They even re-engineered a custom testing and reporting tool for this purpose. I was also lucky that the native extended hardware test exibited a clear error, albeit on the second pass, not the first.


So my advice to you all is to be persistent, keep all of your evidence (symptoms, panics, hardware test results) and be prepared to escalate your issue past the Apple Genius, through Apple Care to the genuine technical support people that understand and will have empathy with your issue.


Finally, be prepared for an extensive round of negotiation as the 3-year moratorium on this matter to replace the logic board for $free is very close to expiry, so act quickly now!. My resolution took many months, but I finally won and our 17" MacBookPro has not exibited any problem since, so the latest Lion OS and all the apps that demonstrated the problem have been updated and have operated prefectly for 8 months now.

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.