kernel panic, looks GPU related

I've been getting kernel panics over the last couple days. I think they are GPU related and seem to happen when I am changing from one window to another (ex switching from Mail to Chrome, or switching tabs on Chrome).


Here is the latest report:




Interval Since Last Panic Report: 17 sec

Panics Since Last Report: 1

Anonymous UUID: 7151FACD-C0BE-0C18-817F-B7ED928EF95D



Wed Jun 12 13:43:47 2013

panic(cpu 0 caller 0xffffff7f8d052f1a): "GPU Panic: [<None>] 5 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff810c4e1000 0x0a5480a2, D0, P3/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.4.5/src/AppleM uxControl/kext/GPUPanic.cpp:127

Backtrace (CPU 0), Frame : Return Address

0xffffff80fb28b710 : 0xffffff800ae1d626

0xffffff80fb28b780 : 0xffffff7f8d052f1a

0xffffff80fb28b850 : 0xffffff7f8b6cbf1e

0xffffff80fb28b910 : 0xffffff7f8b7a012d

0xffffff80fb28b950 : 0xffffff7f8b7a018e

0xffffff80fb28b9c0 : 0xffffff7f8ba66ed0

0xffffff80fb28baf0 : 0xffffff7f8b7c8a75

0xffffff80fb28bb10 : 0xffffff7f8b6d2d50

0xffffff80fb28bbc0 : 0xffffff7f8b6d07d0

0xffffff80fb28bdc0 : 0xffffff7f8b6d1845

0xffffff80fb28bea0 : 0xffffff7f8b66d0a4

0xffffff80fb28bef0 : 0xffffff7f8d0160df

0xffffff80fb28bf40 : 0xffffff7f8d0151e7

0xffffff80fb28bf60 : 0xffffff800ae3e25e

0xffffff80fb28bfb0 : 0xffffff800aeb3137

Kernel Extensions in backtrace:

com.apple.driver.AppleMuxControl(3.4.5)[49FEF732-D7A3-327B-A7AA-6AC5A6E3DCFF]@0 xffffff7f8d045000->0xffffff7f8d057fff

dependency: com.apple.driver.AppleBacklightExpert(1.0.4)[1D0BB11E-7D71-34CF-ACC3-57DF01CADA 08]@0xffffff7f8d040000

dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f8b46a000

dependency: com.apple.driver.AppleGraphicsControl(3.4.5)[4A2C8548-7EF1-38A9-8817-E8CB34B8DC A6]@0xffffff7f8d02c000

dependency: com.apple.iokit.IOACPIFamily(1.4)[A35915E8-C1B0-3C0F-81DF-5515BC9002FC]@0xfffff f7f8b433000

dependency: com.apple.iokit.IONDRVSupport(2.3.7)[6C8CFC18-75F0-3DEF-86C7-CEB2C1FD6BB1]@0xff ffff7f8b656000

dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7f8b613000

com.apple.NVDAResman(8.1.2)[96AE69DE-8A37-39D0-B2D3-D8446A6AA670]@0xffffff7f8b6 6a000->0xffffff7f8b90ffff

dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f8b46a000

dependency: com.apple.iokit.IONDRVSupport(2.3.7)[6C8CFC18-75F0-3DEF-86C7-CEB2C1FD6BB1]@0xff ffff7f8b656000

dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7f8b613000

com.apple.nvidia.nv50hal(8.1.2)[988EAF3A-3318-3787-8A5A-844830FA1522]@0xffffff7 f8b91b000->0xffffff7f8bbeffff

dependency: com.apple.NVDAResman(8.1.2)[96AE69DE-8A37-39D0-B2D3-D8446A6AA670]@0xffffff7f8b6 6a000

dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f8b46a000

com.apple.driver.AGPM(100.12.87)[A7004F02-7D39-3398-8BD3-729DCC404E5F]@0xffffff 7f8d014000->0xffffff7f8d023fff

dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f8b46a000

dependency: com.apple.driver.IOPlatformPluginFamily(5.3.0d51)[2C131EAF-F74C-39D1-A702-A499B 39C293C]@0xffffff7f8bf8b000

dependency: com.apple.iokit.IONDRVSupport(2.3.7)[6C8CFC18-75F0-3DEF-86C7-CEB2C1FD6BB1]@0xff ffff7f8b656000

dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7f8b613000



BSD process name corresponding to current thread: kernel_task



Mac OS version:

12E55



Kernel version:

Darwin Kernel Version 12.4.0: Wed May 1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64

Kernel UUID: 896CB1E3-AB79-3DF1-B595-549DFFDF3D36

Kernel slide: 0x000000000ac00000

Kernel text base: 0xffffff800ae00000

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



System uptime in nanoseconds: 6608974841899

last loaded kext at 43599930310: com.apple.driver.AppleHWSensor 1.9.5d0 (addr 0xffffff7f8ce0e000, size 36864)

last unloaded kext at 391727326418: com.apple.driver.AppleUSBUHCI 5.2.5 (addr 0xffffff7f8bdb9000, size 65536)

loaded kexts:

com.Cycling74.driver.Soundflower 1.5.1

com.iospirit.driver.rbiokithelper 1.8.0

com.orderedbytes.driver.ControllerMateFamily 4.4.3

com.orderedbytes.driver.CMUSBDevices 4.4.3

com.apple.driver.AppleHWSensor 1.9.5d0

com.apple.driver.AudioAUUC 1.60

com.apple.driver.AGPM 100.12.87

com.apple.driver.AppleMikeyHIDDriver 122

com.apple.driver.AppleHDA 2.3.7fc4

com.apple.GeForce 8.1.2

com.apple.filesystems.autofs 3.0

com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport 4.1.4f2

com.apple.driver.AppleUpstreamUserClient 3.5.10

com.apple.driver.AppleMikeyDriver 2.3.7fc4

com.apple.driver.SMCMotionSensor 3.0.3d1

com.apple.iokit.IOUserEthernet 1.0.0d1

com.apple.iokit.IOBluetoothSerialManager 4.1.4f2

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.AppleSMCPDRC 1.0.0

com.apple.driver.ApplePolicyControl 3.4.5

com.apple.driver.AppleSMCLMU 2.0.3d0

com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0

com.apple.driver.AppleLPC 1.6.0

com.apple.driver.AppleIntelHDGraphics 8.1.2

com.apple.driver.AppleIntelHDGraphicsFB 8.1.2

com.apple.driver.AppleMuxControl 3.4.5

com.apple.driver.AppleMCCSControl 1.1.11

com.apple.driver.AppleUSBTCButtons 237.1

com.apple.driver.AppleUSBTCKeyboard 237.1

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.BootCache 34

com.apple.driver.AppleUSBCardReader 3.1.7

com.apple.iokit.SCSITaskUserClient 3.5.5

com.apple.driver.XsanFilter 404

com.apple.iokit.IOAHCIBlockStorage 2.3.1

com.apple.driver.AppleFWOHCI 4.9.6

com.apple.driver.AirPort.Brcm4331 615.20.17

com.apple.driver.AppleUSBHub 5.5.5

com.apple.iokit.AppleBCM5701Ethernet 3.6.1b4

com.apple.driver.AppleAHCIPort 2.5.2

com.apple.driver.AppleUSBEHCI 5.5.0

com.apple.driver.AppleEFINVRAM 1.7

com.apple.driver.AppleSmartBatteryManager 161.0.0

com.apple.driver.AppleACPIButtons 1.7

com.apple.driver.AppleRTC 1.5

com.apple.driver.AppleHPET 1.8

com.apple.driver.AppleSMBIOS 1.9

com.apple.driver.AppleACPIEC 1.7

com.apple.driver.AppleAPIC 1.6

com.apple.driver.AppleIntelCPUPowerManagementClient 196.0.0

com.apple.nke.applicationfirewall 4.0.39

com.apple.security.quarantine 2.1

com.apple.driver.AppleIntelCPUPowerManagement 196.0.0

com.apple.driver.DspFuncLib 2.3.7fc4

com.apple.iokit.IOAudioFamily 1.8.9fc11

com.apple.kext.OSvKernDSPLib 1.6

com.apple.nvidia.nv50hal 8.1.2

com.apple.NVDAResman 8.1.2

com.apple.kext.triggers 1.0

com.apple.iokit.AppleBluetoothHCIControllerUSBTransport 4.1.4f2

com.apple.driver.AppleSMBusPCI 1.0.11d0

com.apple.iokit.IOSurface 86.0.4

com.apple.iokit.IOSerialFamily 10.0.6

com.apple.iokit.IOBluetoothFamily 4.1.4f2

com.apple.iokit.IOFireWireIP 2.2.5

com.apple.driver.AppleHDAController 2.3.7fc4

com.apple.iokit.IOHDAFamily 2.3.7fc4

com.apple.driver.AppleSMC 3.1.4d2

com.apple.driver.IOPlatformPluginLegacy 1.0.0

com.apple.driver.IOPlatformPluginFamily 5.3.0d51

com.apple.driver.AppleGraphicsControl 3.4.5

com.apple.driver.AppleBacklightExpert 1.0.4

com.apple.iokit.IONDRVSupport 2.3.7

com.apple.driver.AppleSMBusController 1.0.11d0

com.apple.iokit.IOGraphicsFamily 2.3.7

com.apple.driver.AppleUSBMultitouch 237.3

com.apple.iokit.IOSCSIBlockCommandsDevice 3.5.5

com.apple.iokit.IOUSBMassStorageClass 3.5.1

com.apple.iokit.IOUSBHIDDriver 5.2.5

com.apple.driver.AppleUSBMergeNub 5.5.5

com.apple.driver.AppleUSBComposite 5.2.5

com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.5.5

com.apple.iokit.IOBDStorageFamily 1.7

com.apple.iokit.IODVDStorageFamily 1.7.1

com.apple.iokit.IOCDStorageFamily 1.7.1

com.apple.iokit.IOAHCISerialATAPI 2.5.1

com.apple.iokit.IOSCSIArchitectureModelFamily 3.5.5

com.apple.iokit.IOFireWireFamily 4.5.5

com.apple.iokit.IO80211Family 530.4

com.apple.iokit.IOEthernetAVBController 1.0.2b1

com.apple.iokit.IONetworkingFamily 3.0

com.apple.iokit.IOUSBUserClient 5.5.5

com.apple.iokit.IOAHCIFamily 2.3.1

com.apple.iokit.IOUSBFamily 5.6.0

com.apple.driver.AppleEFIRuntime 1.7

com.apple.iokit.IOHIDFamily 1.8.1

com.apple.iokit.IOSMBusFamily 1.1

com.apple.security.sandbox 220.3

com.apple.kext.AppleMatch 1.0.0d1

com.apple.security.TMSafetyNet 7

com.apple.driver.DiskImages 345

com.apple.iokit.IOStorageFamily 1.8

com.apple.driver.AppleKeyStore 28.21

com.apple.driver.AppleACPIPlatform 1.7

com.apple.iokit.IOPCIFamily 2.7.3

com.apple.iokit.IOACPIFamily 1.4

com.apple.kec.corecrypto 1.0

System Profile:

Model: MacBookPro6,2, BootROM MBP61.0057.B0F, 2 processors, Intel Core i7, 2.66 GHz, 8 GB, SMC 1.58f17

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

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

Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x80AD, 0x484D54333531533641465238432D47372020

Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x80AD, 0x484D54333531533641465238432D47372020

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

Bluetooth: Version 4.1.4f2 12041, 2 service, 18 devices, 1 incoming serial ports

Network Service: Ethernet, Ethernet, en0

Network Service: AirPort, AirPort, en1

Serial ATA Device: ST9500420ASG, 500.11 GB

Serial ATA Device: MATSHITADVD-R UJ-898

USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfa100000 / 2

USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0236, 0xfa120000 / 5

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

USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8218, 0xfa113000 / 6

USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfa130000 / 3

USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2

USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 4

USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0xfd110000 / 3

MacBook Pro, OS X Mountain Lion (10.8.4)

Posted on Jun 12, 2013 10:59 AM

Reply
219 replies

Dec 26, 2013 10:54 PM in response to Grant Bennet-Alder

I think the Consumer Reports cost of repair argument is a red herring. Since when is $350, or even $500, more than half the cost of a new MacBook Pro? Unless you want the latest and greatest, it still makes more sense to pay for a new logic board than a new computer.


That's IF the Apple Store doesn't honour the recall. If the cause if provably a known issue, I think it's just really bad PR to take a callous attitude toward their customers. IMO the blame lies mostly with the stores that are doing this, not with Apple, since clearly the stores have discretion to allow some leeway with expired warranty/AppleCare. I'm still hopeful that my store will make good, assuming the VST test uncovers the defect.

Dec 27, 2013 10:29 AM in response to Grant Bennet-Alder

Thats what im hoping that the test reveals as this isnt my first logic board replacement as the first one died when the charger shorted out and almost caught fire shortly after I got the machine; which killed the USB bus on the board. I had the first test run only a few hours after I starting to see the issue so it could be that the hardware wasnt fuly settled and gave a false negitive as I was trying to see if I could get the issue fixed as I relie on this machine for school and work. I have also been getting the same issue to occur and can in fact cause it to occur on command within my bootcamp install. I not only get constant driver/graphics drop outs but also full reboots as well after the most recent bootcamp update. These issues seem to be triggered by the switching between nvidia and intel on both sides as the issue happens when ever it seems that I need the extra graphics card.


Would I still get a MBP again? I would as I have loved my mac otherwise and personally I would get another one as apple has realized the source of the flaw ...nvidia... they switched to ATI for the next revisions before returning to nvidia as it seems that the new chipsets are vastly surpior in quality to the eariler versions. Ive been wondering if this might have been the cause for that switch to ATI for a bit before returning to nvidia?


Our issue is apple didnt realize this issue till it was too late and production had ended and everyone had a machine that could contain the bad chipset. Now here were TS4088 comes in it is an attempt at detection and fixing the possible bad chipsets. I understand the amount of planning and cost a model line wide recall could cause if run sucessfully. If everyone remembers correctly the massive case action suit against nvidia a few years before or even the ipod nano battery recall. Those recalls even when planned and excuted in the best of each comapanys ability caused more problems for the consumer than the problem could have caused if they hadnt experience the issue yet. Case in point the recall of nanos, I have friends that would have replaced their own battery but had to send the device to apple and in the begining be without the unit for weeks or get a 6th gen in return which wasnt compatible with their accessorys. I mass recall of all mid 2010 MBP could lead you to be without a machine for weeks or even cause apple to run out of logic boards requiring they then update the customer to the most recent equivalent MBP. Now while you might think that "YAY i get a free quad code or retina" even if you have to wait a few weeks. What if its without a super drive, mic input, firewire 800, or native network port? I know in my case that would be very bad as I use the: onboard network, firewire, super drive, usb mouse, external DAC and display port all at once in course of my schooling and work when preforming video work and missing those feature might not be support and arent availble to someone with a new MBP. A forced recall would cause tons of cases similar to mine and force us to Imacs or back onto windows for video work.


Apple is treating this issue just as if it were an automotive company in my opinion as I have also dealt with Chevy in a similar fashion. Issue a service bulletion with a test and fix but not widely distribute the material outside of people in the know or that have researched the issue. Chevy acted the same way with bad ABS wheel speed sensors on 2001-2006 Chevy silverado. The sensors would cause the ABS to kick in at low speeds prevent you from fully stopping at speeds less than 3mph in the worse case or just cause a shudder otherwise if it were just 1 wheel. Since no life is in imediate danger not recall was issued in this case.


My question about this is why not release it to the public and allow all mac owners with this issue self run the test at home as it seems to not require any technican input or interpertation? Does the test contain some secret that apple knows but doesnt want revealed to the public about the hardware? I bet a lot of people would love to be able to run this test as part of their self diagnoises just like the hardware test can be run.

Dec 27, 2013 11:11 AM in response to harry2110

I do find it funny that the forums crashed as I was editing my last post for style/content.


I would also like to think that apple could have handled the issue better than TS4088.


Why place a time limit on the replacement? It shouldnt matter if it was 3 years or 3 years and 1 day if it takes that long to notice the issue apple could still take of the issue instead of making them seem greedy and evil in a custoemrs eyes leading to bad attention. Electronics are completely diffentent than cars and the thought about them goes similar. You dont mind paying to repair your car for an issue if it isnt documented but on electronics if a company can widely acknowledge a bad production run in most cases its fixed for free or kept completely secret.

By placing this limit on the fix for a known issue that is in fact popping up more now that you have released/forced users to upgrade to the newiest OS shortly after your timeframe has expired has planned obsoletance written all over it and for a $2000 item is a terrible buisness decision. Now I could see they tried that with the last updates killing core2duo machines but that was a physical chip limitation for a certain set of instructions as windows 8 did similar or atleast that was my guess as its seems they can now be updated with maverick. But doing similar just to 1 set of production as 13in and 17in arent affected shouldnt be used plus you do get hold outs just like microsoft is experiencing with xp I know alot of people that want to stay on 10.6 till forced but atleast in microsofts case its been over 10 years not 3 so that their hardware is also now extremely out of date when they were being forced to a newer OS. Our 2010 MBP are still extremely capable computers and arent old sluggish relics that need to be retired but it seems that would believe they do. If you have to play the lottery now when you upgrade to maverick that will your hardware be affected but now not covered under warranty how do you think customers feel?


By removing the time limit or atleast setting it to like 7 years you could in fact make more good press about your company as it would like your cared for customers even after purchase and could lead to an increase in sales. Just like brands such as craftsmen, granite gear, or even companys like REI are completely based on their customer support and support of the customer after purchase. Now apple doesnt have to extend it to all issue but just fixing an known issue on a certain model would end most bad press associated with this issue.

Dec 27, 2013 11:46 AM in response to Grant Bennet-Alder

My goal is to get this thread away from the bashing of apple or you and back on helping other users fix the issue and showing the train of thought that might end this.


Those both posts should have been combined to one but the forums crashed as I was submiting my second draft of the first post that combined the two postings. It seems you cant edit or delete post after you send them.


Further research and editing is needed as I would like to see the end or atleast extension of the time frame as its about to expire for all affected MBPs soon(feburary).

Dec 28, 2013 6:22 PM in response to harry2110

An update on my case that might help to deflect some of the Apple bashing. It took a lot of pushing to get them to do it -- they stress tested my machine for two nights and did everything EXCEPT run the VST test (which is even listed on the copy of the work order they gave me at the Genius bar). Finally this evening, I called them and was told that it had passed all tests and the next thing to try was to do an erase and reinstall. I asked them if they had run the VST test -- turned out they hadn't but it would only take a few minutes -- so they ran it while I waited for a callback and it FAILED. Hooray!


And the better news is that they will ship it out to replace the logic board under their Quality Assurance program and thus I will be completely covered. Estimated time to return to store: 3-5 days.


So at least some of the stores do know how to treat customers fairly. I have to guess that Apple leaves this at the discretion of the franchise.


Thanks to the valuable information on these boards and the knowledgeable users here who share it!!

Jan 3, 2014 9:53 PM in response to Eddy5

So how did it go, Eddy? Inquiring minds...


As for me, I have my Mac back from the repair depot, with a new logic board, at no cost to me even though I was 4 months past the 3 year limit, and out of Applecare coverage. Picked it up last night, and after 24 hours, it remains panic-free. I do hope your experience turns out as positive as mine.

Jan 4, 2014 3:33 AM in response to Liz A.

Unfortunately the appointment didn't seem to have been made. I called before hand as I couldn't see any sign of it online and the store had no record too. Apple Chat saw that it was in the chat records, but couldn't confirm with the store as they don't have access to their systems.

Anyway I've got an appointment for Monday evening so let's see how I get on.

Sounds like you've had a spot on experience. hope it stays panic free too.

Jan 4, 2014 4:48 AM in response to Eddy5

I thought it would be helpful for others to describe my experience at the Apple Store in the UK with this issue.


My Macbook Pro was bought in June 2010 - with full Applecare, though this expired back in June 2013. Since upgrading to 10.9 this Autumn I'd been having increasingly frequent GPU panics when switching graphics cards, making the machine often unuseable. However, some days it worked ok and somedays it didn't and I couldn't find a pattern in there to explain this.


I booked an appointment and took it along to the Solihull store, taking with me a bunch of printouts (including parts of this thread) explaining that it was a known problem. However, the printouts weren't needed: what they were interested in was the list of kernel.panics in the logs, viewable from the Console application.


Once they saw this and I described it occuring when changing between graphics cards they said it was a known problem. Then they ran the hardware/graphics test (which it passed in huge green letters saying "PASSED"), but agreed to fix it free of charge, even though the machine was more than 6 months out of warranty, as it was a known issue.


If I had had to pay it would have been £418, but there was not even a discussion about paying for it to be fixed - they just said straightaway it would be free. No idea if the other Apple products I own contributed to the decision, but I was certainly going to mention them if a charge had been discussed. It took five days to fix and now appears to work fine when switching which graphics card is in use.


So my advice to anyone in the UK is to try and get theirs fixed as part of this known issue ASAP.

Jan 6, 2014 12:07 PM in response to alder89

My MacBook did also pass the test. But my problem was exactly the same as that of all the other people complaining here. So I got my board replaced but had to pay € 475,- 😟. Now I get no kernel panics anymore but the graphics get sometimes mixed up. Now the Intel Graphics produces sometimes stripes instead of shadows around Dock icons and window borders.

User uploaded file

Maybe the RAM is defective or the Intel graphics chip is faulty two? Never had such problems before with Apple products.

It´s ok that you got lucky but Apple does make so much money they could really be less restrictive with free of charge repairs. I sometimes feel as if we Germans are those who have to pay all the time.

It´s a sad joke that I have to pay money for some updates in the App store (iPhoto, iWork) that are for free if I change my default language to english! Who made that idiotic decission? I am beginning to think Apple has become to big like IBM in the old days.

Jan 6, 2014 3:10 PM in response to Saxifraga

Saxifraga-


the graphics get sometimes mixed up. Now the Intel Graphics produces sometimes stripes instead of shadows around Dock icons and window borders.

Those kinds of problems are likely to be software issues, where a programmer made a bad choice or something changed and the software did not keep up. Make sure you have all the latest updates.


Graphics Hardware problems cause horrible, ugly, nonsensical problems, bizarre shapes and colors, arbitrary tiling and repeating of cookie-cutter sections of the image on screen and the like.

Jan 6, 2014 11:45 PM in response to Grant Bennet-Alder

Thank you for your response.


But I don´t think that third party software is the cause of the problem.

When I go to 'System Preferences -> Energy Saving' and activate 'Automatic graphics switching' the artifacts vanish the moment the NVIDIA GPU is used. If I untick the box the artifacts reappear and the Profiler shows the Intel graphics to be active. Reticking the box rectivates the Nvidia GPU and the artifacts disappear again.

It´s either hardware or programmers at Apple don´t have that switching process under control. Then it has to be a systems graphics library. It looks as if some of the graphics context gets lost. Maybe pointers into the dedicated GPU RAM still point to RAM not available to the Intel graphics? 😟 (It has nothing to do with the App the window belongs to. That I am sure of.)

Jan 7, 2014 12:08 AM in response to Saxifraga

You can force the system to run with discrete graphics only, if that eliminates the problem (using gfxCardStatus). It could be that the integrated graphics chip is borderline broken. I would try resetting everything possible (SMC etc). It's unlikely that Apple is producing new motherboards as spare parts for the repairs, so the replacements are likely either old stock (which will certainly run out sooner or later) or refurbished/repaired motherboards from MacBooks that were sent in for repairs. With an odd/intermittent non-fatal problem like yours, I can understand why it could go undetected and instead of the board actually getting properly repaired before it goes out again, it gets used as a spare part.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

kernel panic, looks GPU related

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