francois-vda

Q: 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

Close

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

  • All replies
  • Helpful answers

first Previous Page 39 of 51 last Next
  • by dmdimon,

    dmdimon dmdimon Nov 13, 2012 1:16 PM in response to totalmajor
    Level 3 (840 points)
    Nov 13, 2012 1:16 PM in response to totalmajor

    Can we get something going for this??

    yes.

    Go iFixit for your model, disassemble it up to heatpipes/heatsynk dismount, wipe thermopaste from GPU, CPU and heatsinks, add small amount of good thermopaste, assemble carefully and tight.

     

    90% that problem will go.

    99.5% that problem will go for users who get this errors only after update to ML.

  • by MrSparkle75,

    MrSparkle75 MrSparkle75 Nov 13, 2012 1:36 PM in response to dmdimon
    Level 1 (5 points)
    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,

  • by dmdimon,

    dmdimon dmdimon Nov 14, 2012 12:52 AM in response to MrSparkle75
    Level 3 (840 points)
    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.

  • by MrSparkle75,

    MrSparkle75 MrSparkle75 Nov 14, 2012 2:41 AM in response to dmdimon
    Level 1 (5 points)
    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.

  • by dmdimon,

    dmdimon dmdimon Nov 14, 2012 3:41 AM in response to MrSparkle75
    Level 3 (840 points)
    Nov 14, 2012 3:41 AM in response to MrSparkle75

    lets try to find some consensus )

    sorry for my english level, I'll try as I can. So:

    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.

    well, how cooling works? thing is simple. you have some heating element, some heat dissipation element and some heat transfer element (frome heater to dissipator). For example - heater - GPU, transfer - thermopaste, dissipator - thermotube. Or heater - thermotube, dissipator - air cooled radiator, transfer - zone of contact between tube and radiator. Hope I give you idea.

    So there are some temperature steps on each transfer element, as heat can be transferred with some speed and there are such characteristic as thermal resistance for that.

    Now going to problem - if we have high thermal resistance between GPU and thermotubes we get high thermal step between GPU and cooling system, say 5-10 C more than it should be. (if you take a look at overclockers forums you'll find that it goes 5-15 C). So Mac adaptive cooling system should run coolers say 5-10% faster at same weather and load level to compensate that enormous thermopaste layer.

    Here we go with system almost on edge - it will work ok at cold and probably overheat at warm weather and full load. Looks like situation you described.

     

    BUT. It will be so if cooling system will use only and exactly on-die thermosensor. In real life it is not so - lots of sensors are involved and all of them exept one (on die) lies to us due to high thermal resistance between GPU and thermotube. And our well-balanced and precalculated (for normal T-resist) adaptive cooling with all cooler control algorithms and coefficients go offsync with reality and undercool GPU at ANY weather. So our GPU will in reality be (not so) slightly overheated all time. I'd say up to 5-7 C

     

    Here we are exactly 3-5 C lower than edge now - at least for Intel CPU difference between safety shutdown and 100% load is like =< 10 C. And we are almost on edge for ANY weather - as our fooled cooling system drives us there.

     

    Now we go for more sophisticated thing.

     

    All modern GPUs have asyncronous independently floating speeds for subblocks. It is done to conserve power/lover heat dissipation. Every block in GPU tries to run at lowest possible speed, just enough to fulfill current task. If that is not enough - speed goes up for that block.

     

    Take a look at modern GPU bottleneck analysis and you'll see that most heavy working part in GPU in almost any situation is memory controller. So if we add a bit of memory-intensive things (ML offloaded parts) to GPU we easily can flop memory controller at given GPU speed thus enforcing it to go higher.

     

    And if we have only memory-intensive tasks with low load on other blocks - we have HOT memory controller and cold everything else. And median temperature will be not so high, and cooling system will try not so hard to cool it down.

     

    Got the idea? We have already fooled cooling system (undercooling), and we fool it again due to spot heating and low median temperature. Here we immediately get memory controller overheated and what ? read error. What else can you expect?

     

    For this error in condition of normal cooling we should overheat mem controller for say 10 C, so if we already have 5-7 C gap on cooling it lowers to 3-5 C, i.e. we have 2x - 3x less thermal reserve.

     

    And now we go to time factor. For GPU run faster we need some nanoseconds, for cooling system run faster we need seconds. see the gap? and we have 2x-3x lovered reserve to survive that gap.

     

    This is living on the edge. And to flop over that edge +5-10% specific GPU-memory operations easily can be enough.

  • by dmdimon,

    dmdimon dmdimon Nov 14, 2012 3:47 AM in response to MrSparkle75
    Level 3 (840 points)
    Nov 14, 2012 3:47 AM in response to MrSparkle75

    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.

    Fully agree with you on that. But question was - what we can do?

  • by fndtomas,

    fndtomas fndtomas Nov 14, 2012 10:24 AM in response to dmdimon
    Level 1 (0 points)
    Nov 14, 2012 10:24 AM in response to dmdimon

    Hi folks,

     

    I have following this discussion for quite some time. I had the same "panic problem" as described and, after months of "coming and go", it was finally solved.

     

    Yesterday I got my computer from the repair center. The solution ?

     

    Answer: Logic board replacement.

     

    This is the only way to fix the machine, no way. Insist on TS4088.

     

    Good luck.

  • by alekb,

    alekb alekb Nov 23, 2012 5:19 AM in response to fndtomas
    Level 1 (5 points)
    Nov 23, 2012 5:19 AM in response to fndtomas

    Hello fndtomas,

    can you say me how much does your repair cost you and where are you, please?

     

    Please! if someone fixed this issue with Apple Service under this plan:

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

    or anything else please, post a note about it here,

     

    thanks

  • by fndtomas,

    fndtomas fndtomas Nov 23, 2012 6:18 AM in response to alekb
    Level 1 (0 points)
    Nov 23, 2012 6:18 AM in response to alekb

    Hi alekb,

     

    I got it the logicboard replaced for free in Frankfurt/DE. It took quite long time talking with all the hierarchy of genius, repair center and apple care.

     

    First of all: This problem doesn’t seems to be localized. Several people are reporting the same issue ... since jul/2011.

     

    Most Important thing: NEVER follow any advise which tells you to do stupid things with your hardware such as open it, put thermic pasta, change disk, memory and etc...

     

    Good luck for you.

     

    <Edited By Host>

  • by apple242,

    apple242 apple242 Nov 23, 2012 6:33 AM in response to fndtomas
    Level 1 (0 points)
    Nov 23, 2012 6:33 AM in response to fndtomas

    Unfortunately Apple Germany is a different matter than Apple USA and most other Apple countries.

     

    Save your time, money and health and go another EU country and resolve the problem ASAP.

  • by fndtomas,

    fndtomas fndtomas Nov 23, 2012 6:45 AM in response to apple242
    Level 1 (0 points)
    Nov 23, 2012 6:45 AM in response to apple242

    1. I love this country .

    2. The problem is the business model not the algorithm .

    3. My suggestions is constructive.

    4. Only understand who can...

     

    <Edited By Host>

  • by apple242,

    apple242 apple242 Nov 23, 2012 6:55 AM in response to fndtomas
    Level 1 (0 points)
    Nov 23, 2012 6:55 AM in response to fndtomas

    As I said, if you want to save time and money go to France or Holland and repair it without the unprofessional and inferior service from Apple Germany.

     

    I know what I'm talking about. We spent in excess of 6 months trying to resolve it.

    And that was with Apple USA all over them.

     

    They hadn't even heard of TS4088 when the rest of the world was already doing these repairs for a year.


    Go to France or Holland where the service is as polite and competent as in the USA.

    There is absolutely no need to indulge the unprofessionalism of Apple Germany.

  • by apple242,

    apple242 apple242 Nov 23, 2012 7:03 AM in response to fndtomas
    Level 1 (0 points)
    Nov 23, 2012 7:03 AM in response to fndtomas

    fndtomas - I wasn't criticising you. Nevertheless your last post is emblematic. 

     

    For those interested in actually repairing their laptop instead of debating endlessly with Apple Germany,

    better service is available just across the border.

     

    There's no excuse for wasting 6 months with Apple Germany.

  • by fndtomas,

    fndtomas fndtomas Nov 23, 2012 7:05 AM in response to apple242
    Level 1 (0 points)
    Nov 23, 2012 7:05 AM in response to apple242

    You have your own opinions that are not congruents with mine.

     

    Thanks for the last emails. You could very well be a genius.

  • by apple242,

    apple242 apple242 Nov 23, 2012 7:11 AM in response to fndtomas
    Level 1 (0 points)
    Nov 23, 2012 7:11 AM in response to fndtomas

    It is not important whether our opinions are congruent.

     

    You yourself have mentioned the absurd amount of time required to resolve the problem with Apple Germany.

     

    It's completely unnecessary.

     

    Across the border, one receives more polite and competent service,

    and what requires 6+ months in Germany is resolved in 1 week.

     

    What is important is that people get their laptops repaired ASAP,

    not learn and comply with the German way of doing things.

first Previous Page 39 of 51 last Next