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.

Cold restarts after 10.10.3 update.

Hi,

Ever since the 10.10.3 update I am experiencing two problems on my mac mini. I am not entirely sure that they are related to the update but since I haven’t changed anything (hardware or software) on my mac, I can only assume that the update probably triggered the issues.

The first problem is that every now and then I get a bunch of pixels flickering on some random position of my screen. Another user reported the exact same error and posted a video here: https://www.facebook.com/georgetasioulis/videos/10203713632115564/ Once I drag a window over these pixels, the problem is gone.

The second and more major problem is that I get random cold restarts. It could be 5 minutes since I booted my mac or even a day after. There is no specific app that I’m running when the mac restarts. In other words I can’t seem to find a pattern on when this happens.

After reading many forum posts I ended up doing a clean installation of Yosemite and started installing everything from scratch. After a while the same thing happened. I noticed that some “power users” can make sense of the kernel panic logs so here is my latest one:

Anonymous UUID: DFD8BE96-203B-C244-A890-73E40E563534

Sat Apr 18 09:26:15 2015

*** Panic Report ***

panic(cpu 2 caller 0xffffff8030417cc2): Kernel trap at 0xffffff803053ea88, type 13=general protection, registers:

CR0: 0x000000008001003b, CR2: 0x0000000004b77e1e, CR3: 0x0000000023f5e036, CR4: 0x00000000001626e0

RAX: 0xffffff805c11e020, RBX: 0xffffff804fd3ac00, RCX: 0xff0e1b2aff0e1a2a, RDX: 0xffffff804fd3ac50

RSP: 0xffffff822e4f3d30, RBP: 0xffffff822e4f3dd0, RSI: 0x0000000000000025, RDI: 0xffffff804fd3ac18

R8: 0x0000000000000001, R9: 0x0000000000000000, R10: 0x0000000000002000, R11: 0x0000000000000012

R12: 0xffffff805c11e000, R13: 0x0000000000000000, R14: 0xffffff804fd3ac18, R15: 0xffffff804fd3ac50

RFL: 0x0000000000010282, RIP: 0xffffff803053ea88, CS: 0x0000000000000008, SS: 0x0000000000000010

Fault CR2: 0x0000000004b77e1e, Error code: 0x0000000000000000, Fault CPU: 0x2

mp = 0xffffff804fd3ac00, phys = 0x31183c00, prev (0x7: 0x30113000-0x30200000)

vp = 0xffffff804fd3ac00, phys = 0x709000, prev (0: 0xa0000-0xc0000)

0xffffff804fd39000: YwAAAGcAAABtAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAICA gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAACAgB4fCQcgAACACAAAACETGg2GU6LSgoMZPwACAgACKggAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAgEAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAG1hcCBhdXRvX2hvbYjEe0+A////AAACAP8PAAAAAAA h/////z8AAAAAhOJQ4IHtUVi9mzYAjtNPAKLTT4D////QoSCysACmMLCE7VHAg+1RUJjTTwgAUAQAAAg AAAQAAAACAAABAAAsFAAAAGF1dG9mcwAAL25ldG1hcCAtaG9zwMwAAOAODu7g7t7uDgUODWWAACAgBLA 5gDsgAAH8/zeAgw8GdAMAAAAA

0xffffff804fd3a000: fwAAAIgAAACTAAAAAAAAAAAAAAAAAAAAAACAgB4fCQcgAACACAAAACETGg2G06LTgoMqK0QBMwACKQQ AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AADAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAwMAeH4mHLQAKwAgAAAAhExYNqtIqH4qPGr9oAuoAAhoAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAj/fE+A////AAACAP8PAAAAAAAh/////z8AAAAAM3p QwIPtUYDLmjYAmNNPAKzTT2AtpjBQAKYwcNjeT/CAW2Og195PUKLTT4D///9gotNPgP///wAQEAQAEBA AqCFET2RldmYvZGV2AAACAP8PAAAAJGWK/////6AjAAApJAAAAAAAIT8AAAAAc9dP3GSWHQCi00+A/// /4HuvMF6YAQCYl/5VAAAAAkgCpzCQ/6UwgBfdYyAPElwA4BFcMN7eTwDQgAQAAN2AEAAAAAAQAAAAABA AqBR7A/UV4QL1G+ACs/iaAAIAAAERAAAAaGZzAMwAAAwODu7u4O7uDgAAMAABzswA4ODg4Oju4ODuLu7 eBwAAACAACAIBbA44DghQE/8DDiBs2TkBc4AAICAEICibAw44DgjwP4CDYQovAAAA

0xffffff804fd3b000: WQAAAF0AAABjAAAAAAAAAAAAAAAAAAAAACAgIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAwgIAaHwoHLQAGQAoxAAAAABIDABAAAIAAFn0AAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAHh8JByAAAIAAAAAAAAAiAS9kZXYvZGlzazBzMggY30+A////AAAAAgABAAAAAEA AAwAAANNuCwAAAAAhAN/eTwEAAABAc9dPQLbTTwAQAAAAAAIA/w8AAAAAACH/////wGyqTwIAAAAAAAA AAOUO7u4DzgMADOwAAIIQAIiO/T+AC/A/gEMJJgCBACAgBAA4

Backtrace (CPU 2), Frame : Return Address

0xffffff820ef35e10 : 0xffffff803032bda1

0xffffff820ef35e90 : 0xffffff8030417cc2

0xffffff820ef36050 : 0xffffff8030434b73

0xffffff820ef36070 : 0xffffff803053ea88

0xffffff822e4f3dd0 : 0xffffff80307552f7

0xffffff822e4f3eb0 : 0xffffff803055879b

0xffffff822e4f3ed0 : 0xffffff8030542e24

0xffffff822e4f3f40 : 0xffffff803054d027

0xffffff822e4f3f50 : 0xffffff803084ba86

0xffffff822e4f3fb0 : 0xffffff8030435376

BSD process name corresponding to current thread: sync

Mac OS version:

14D136

Kernel version:

Darwin Kernel Version 14.3.0: Mon Mar 23 11:59:05 PDT 2015; root:xnu-2782.20.48~5/RELEASE_X86_64

Kernel UUID: 4B3A11F4-77AA-3D27-A22D-81A1BC5B504D

Kernel slide: 0x0000000030000000

Kernel text base: 0xffffff8030200000

__HIB text base: 0xffffff8030100000

System model name: Macmini6,2 (Mac-F65AE981FFA204ED)

System uptime in nanoseconds: 648750639627

last loaded kext at 243977764692: com.apple.filesystems.msdosfs 1.10 (addr 0xffffff7fb112b000, size 69632)

loaded kexts:

com.Logitech.Unifying.HID Driver 1.3.1

com.Logitech.Control Center.HID Driver 3.9.1

at.obdev.nke.LittleSnitch 4240

com.apple.filesystems.msdosfs 1.10

com.apple.iokit.IOBluetoothUSBDFU 4.3.4f4

com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.3.4f4

com.apple.driver.AppleUSBCDC 4.3.3b1

com.apple.filesystems.autofs 3.0

com.apple.iokit.IOBluetoothSerialManager 4.3.4f4

com.apple.driver.AGPM 110.19.5

com.apple.driver.X86PlatformShim 1.0.0

com.apple.driver.ApplePlatformEnabler 2.2.0d4

com.apple.driver.AppleOSXWatchdog 1

com.apple.driver.AudioAUUC 1.70

com.apple.driver.AppleMikeyHIDDriver 124

com.apple.driver.AppleHDAHardwareConfigDriver 272.18

com.apple.driver.AppleUpstreamUserClient 3.6.1

com.apple.driver.AppleMCCSControl 1.2.11

com.apple.driver.AppleHDA 272.18

com.apple.iokit.IOUserEthernet 1.0.1

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.AppleHWAccess 1

com.apple.driver.AppleIntelHD4000Graphics 10.0.6

com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0

com.apple.driver.AppleHV 1

com.apple.driver.AppleSMCPDRC 1.0.0

com.apple.driver.AppleMuxControl 3.10.22

com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0

com.apple.driver.AppleFIVRDriver 4.1.0

com.apple.driver.AppleLPC 1.7.3

com.apple.driver.AppleIntelFramebufferCapri 10.0.6

com.apple.driver.AppleMikeyDriver 272.18

com.apple.driver.AppleThunderboltIP 2.0.2

com.apple.driver.AppleUSBDisplays 372.1

com.apple.driver.AppleIRController 327.5

com.apple.driver.AppleFileSystemDriver 3.0.1

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.BootCache 36

com.apple.driver.AppleUSBOHCI 656.4.1

com.apple.driver.XsanFilter 404

com.apple.iokit.IOAHCIBlockStorage 2.7.1

com.apple.driver.AirPort.Brcm4331 800.20.24

com.apple.iokit.IOAHCIPassThrough 1.0.3

com.apple.driver.AppleSDXC 1.6.5

com.apple.iokit.AppleBCM5701Ethernet 10.1.3

com.apple.driver.AppleUSBHub 705.4.2

com.apple.driver.AirPort.Brcm4360 930.37.3

com.apple.driver.AppleFWOHCI 5.5.2

com.apple.driver.AppleAHCIPort 3.1.2

com.apple.driver.AppleUSBEHCI 705.4.14

com.apple.driver.AppleUSBXHCI 710.4.11

com.apple.driver.AppleACPIButtons 3.1

com.apple.driver.AppleRTC 2.0

com.apple.driver.AppleHPET 1.8

com.apple.driver.AppleSMBIOS 2.1

com.apple.driver.AppleACPIEC 3.1

com.apple.driver.AppleAPIC 1.7

com.apple.driver.AppleIntelCPUPowerManagementClient 218.0.0

com.apple.nke.applicationfirewall 161

com.apple.security.quarantine 3

com.apple.security.TMSafetyNet 8

com.apple.driver.AppleIntelCPUPowerManagement 218.0.0

com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.3.4f4

com.apple.kext.triggers 1.0

com.apple.iokit.IOSerialFamily 11

com.apple.driver.DspFuncLib 272.18

com.apple.kext.OSvKernDSPLib 1.15

com.apple.iokit.IOSurface 97.4

com.apple.driver.IOPlatformPluginLegacy 1.0.0

com.apple.driver.AppleBacklightExpert 1.1.0

com.apple.iokit.IONDRVSupport 2.4.1

com.apple.driver.AppleGraphicsControl 3.10.22

com.apple.driver.X86PlatformPlugin 1.0.0

com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0

com.apple.iokit.IOUSBUserClient 705.4.0

com.apple.iokit.IOFireWireIP 2.2.6

com.apple.driver.AppleHDAController 272.18

com.apple.iokit.IOHDAFamily 272.18

com.apple.driver.IOPlatformPluginFamily 5.9.1d7

com.apple.iokit.IOAcceleratorFamily2 156.14

com.apple.AppleGraphicsDeviceControl 3.10.22

com.apple.iokit.IOGraphicsFamily 2.4.1

com.apple.driver.AppleSMBusController 1.0.13d1

com.apple.driver.AppleSMC 3.1.9

com.apple.driver.AppleSMBusPCI 1.0.12d1

com.apple.driver.AppleThunderboltEDMSink 4.0.2

com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.5

com.apple.iokit.IOUSBHIDDriverPM 710.4.7

com.apple.driver.AppleUSBAudio 295.23

com.apple.iokit.IOAudioFamily 203.3

com.apple.vecLib.kext 1.2.0

com.apple.driver.IOBluetoothHIDDriver 4.3.4f4

com.apple.iokit.IOBluetoothFamily 4.3.4f4

com.apple.iokit.IOUSBHIDDriver 705.4.0

com.apple.driver.AppleThunderboltDPInAdapter 4.0.6

com.apple.driver.AppleThunderboltDPOutAdapter 4.0.6

com.apple.driver.AppleThunderboltDPAdapterFamily 4.0.6

com.apple.driver.AppleThunderboltPCIUpAdapter 2.0.2

com.apple.driver.AppleThunderboltPCIDownAdapter 2.0.2

com.apple.driver.AppleUSBMergeNub 705.4.0

com.apple.driver.AppleUSBComposite 705.4.9

com.apple.driver.AppleThunderboltNHI 3.1.7

com.apple.iokit.IOThunderboltFamily 4.2.2

com.apple.iokit.IOEthernetAVBController 1.0.3b3

com.apple.iokit.IO80211Family 730.60

com.apple.driver.mDNSOffloadUserClient 1.0.1b8

com.apple.iokit.IONetworkingFamily 3.2

com.apple.iokit.IOFireWireFamily 4.5.6

com.apple.iokit.IOAHCIFamily 2.7.5

com.apple.iokit.IOUSBFamily 720.4.4

com.apple.driver.AppleEFINVRAM 2.0

com.apple.driver.AppleEFIRuntime 2.0

com.apple.iokit.IOHIDFamily 2.0.0

com.apple.iokit.IOSMBusFamily 1.1

com.apple.security.sandbox 300.0

com.apple.kext.AppleMatch 1.0.0d1

com.apple.driver.AppleKeyStore 2

com.apple.driver.AppleMobileFileIntegrity 1.0.5

com.apple.driver.AppleCredentialManager 1.0

com.apple.driver.DiskImages 396

com.apple.iokit.IOStorageFamily 2.0

com.apple.iokit.IOReportFamily 31

com.apple.driver.AppleFDEKeyStore 28.30

com.apple.driver.AppleACPIPlatform 3.1

com.apple.iokit.IOPCIFamily 2.9

com.apple.iokit.IOACPIFamily 1.4

com.apple.kec.Libm 1

com.apple.kec.pthread 1

com.apple.kec.corecrypto 1.0

I would really appreciate if someone could point me to the right direction in order to figure out what to do next. My spec is a mac mini (late 2012) 2.3GHz i7 with 16GB RAM from Crucial and a Corsair SSD Force 3 240GB. It is connected to an Apple Thunderbolt display with only one peripheral: a Logitech Anywhere MX mouse.

One last thing… the above kernel crash log is kinda rare. Most of them have this:

Kernel Extensions in backtrace:

com.apple.iokit.IOACPIFamily(1.4)[70E2B65E-A91A-3522-A1A0-79FD63EABB4C]@0xfffff f7f82ecb000->0xffffff7f82ed3fff

com.apple.iokit.IOPCIFamily(2.9)[52E715FC-521D-3869-B2EA-5228FA4BEA34]@0xffffff 7f82524000->0xffffff7f82552fff

com.apple.driver.AppleACPIPlatform(3.1)[97299A71-6EDD-3AD9-AE1D-2F7B61E8AA72]@0 xffffff7f8458b000->0xffffff7f845e9fff

dependency: com.apple.iokit.IOACPIFamily(1.4)[70E2B65E-A91A-3522-A1A0-79FD63EABB4C]@0xfffff f7f82ecb000

dependency: com.apple.iokit.IOPCIFamily(2.9)[52E715FC-521D-3869-B2EA-5228FA4BEA34]@0xffffff 7f82524000

Not sure if this helps but “com.apple.iokit.IOACPIFamily” is mentioned most of the times.

Mac mini, OS X Yosemite (10.10.3), Late 2012, 2.3 GHz i7

Posted on Apr 18, 2015 12:00 AM

488 replies

Barney-15E

Level 10

116,926 points

Jul 7, 2015 4:44 AM in response to MrCamaleo

MrCamaleo wrote:

One thunderbolt to mini display and the second thunderbolt to the first one.

So both displays are pure Thunderbolt?

Anybody else with problems using Thunderbolt enabled displays?

MrCamaleo

Level 1

102 points

Jul 7, 2015 5:22 AM in response to Barney-15E

Yep, two of these:

http://www.apple.com/displays/

macudo

Level 1

58 points

Jul 7, 2015 2:20 PM in response to BG2k

I will try it soon.

I have an Lenovo 24" external Display attached with original Apple mini Display to DVI Adapter.

alfa78

Level 1

5 points

Jul 9, 2015 1:37 PM in response to macudo

Hi all!!!

I've just downloaded the "Apple Service Diagnostics v.3S151" (for Mac Mini Late 2012 and other Mac machines) and I've created a bootable USB Pendrive.

I run all the tests both if EFI and OS mode and all test have passed, so it's another confermation: my Mac Mini Late 2012 (and all your Mac machines having Intel HD Graphics 4000 as GPU) hasn't any hardware issues, but the problem is in the software!!!

Here a picture of the last test (OS mode):

Bye!!!

Barney-15E

Level 10

116,926 points

Jul 9, 2015 3:53 PM in response to alfa78

Can you post a thorough set of steps I can use to cause my exact same mini to exhibit the behavior you describe?

If this is a problem in the software, I would think I could replicate it somehow.

Also, the Mid 2010 Macbook Pro had a faulty graphics card that could not be detected as faulty with any of the Apple Hardware tests or even Apple's service department tests. They had to create a special set of tests to detect it. So, just because the Apple Diagnostics doesn't find anything wrong, or even Apple's service department cannot find anything wrong, there could still be some hardware fault.

alfa78

Level 1

5 points

Jul 9, 2015 10:27 PM in response to Barney-15E

If there was an hardware fault, this should have been present with Yosemite 10.10.2 as well...instead, the problem is present from Yosemite 10.10.3 onwards in EVERY Mac machine having Intel HD Graphics 4000 as GPU: given that this GPU is present in several mac (Mac Mini Late 2012, MacBook Pro as well, etc...) and that this issue didn't occur in Yosemite 10.10.2 and previous versions, it's NOT an hardware fault!

We don't know how to replicate it because it's random! Someone argues that all software adding graphical icons on top menubar (as Little Snitch or iStat Menus) may cause the glitch problem.

Let's hope that "El Capitan" can fix this issue.

Anyway, in the meanwhile everybody having the glitch issue, can open a ticket to (please, DO IT!!!):

https://bugreport.apple.com/

Bye!!!

Barney-15E

Level 10

116,926 points

Jul 10, 2015 5:08 AM in response to alfa78

alfa78 wrote:

If there was an hardware fault, this should have been present with Yosemite 10.10.2 as well

Sorry, but that is not absolute. 10.10.3 and later could be using features that trigger the fault to appear. Just as the fault in the Macbook Pro Mid 2010 was normally not triggered by 10.6. It was most often discovered when a later operating system drove features that triggered the fault.

If it was Software, I would expect I would see the problem on my very same Mini. I don't load crapware system modifications on my Mac, so your example scenario I certainly cannot replicate.

n748

Level 1

34 points

Jul 13, 2015 3:14 AM in response to Barney-15E

Barney-15E wrote:

Sorry, but that is not absolute. 10.10.3 and later could be using features that trigger the fault to appear. Just as the fault in the Macbook Pro Mid 2010 was normally not triggered by 10.6. It was most often discovered when a later operating system drove features that triggered the fault.

If it was Software, I would expect I would see the problem on my very same Mini. I don't load crapware system modifications on my Mac, so your example scenario I certainly cannot replicate.

Hello Barney-15E.

Do you have an idea what could have changed in 10.10.3, that could provoke a hardware bug to show up? I am not aware of major concept changes in 10.10.3 (maybe 10.10.4, abandoning discoveryd). I am pretty much convinced that this has to be a software bug. The last 2 years my Macbook Pro has been rock solid on Mountain Lion.

Today I had my first kernel panic in 10.10.4 😟. Again BOOM, BOOM! (Crashing twice)

Barney-15E

Level 10

116,926 points

Jul 13, 2015 4:22 AM in response to n748

n748 wrote:

Barney-15E wrote:

Sorry, but that is not absolute. 10.10.3 and later could be using features that trigger the fault to appear. Just as the fault in the Macbook Pro Mid 2010 was normally not triggered by 10.6. It was most often discovered when a later operating system drove features that triggered the fault.

If it was Software, I would expect I would see the problem on my very same Mini. I don't load crapware system modifications on my Mac, so your example scenario I certainly cannot replicate.

Hello Barney-15E.

Do you have an idea what could have changed in 10.10.3, that could provoke a hardware bug to show up? I am not aware of major concept changes in 10.10.3 (maybe 10.10.4, abandoning discoveryd). I am pretty much convinced that this has to be a software bug. The last 2 years my Macbook Pro has been rock solid on Mountain Lion.

Today I had my first kernel panic in 10.10.4 😟. Again BOOM, BOOM! (Crashing twice)

I have no idea. But I do think if it was a software bug, I would see kernel panics too. I don't.

It also may be a software bug, but not Apple's software.

Again, If it is a bug in the OS, I should be able to replicate it somehow, but I would need to get some usage patterns that trigger it to test.

Someone else had thunderbolt displays. I don't have any. Initially, I remember some mentions of problems with Thunderbolt, but I don't remember what or if it was display related. If there is a bug in the Thunderbolt display drivers, it would not affect me.

n748

Level 1

34 points

Jul 13, 2015 7:57 AM in response to Barney-15E

Well - had another chat with AppleCare. This time the person told me about a replacement program: https://www.apple.com/support/macbookpro-videoissues/

Although it sounds pretty much like our problem, I fell like this is a 10.10.3+ bug. What about the Minis?

Will bring in my MBP on Tuesday...

About El Capitan: Well, I hate doing OS upgrades, since I have a quite specific development environment and setting that up (especially an new OSs) can be quite lengthy and painful. I had been running Mountain Lion until recently. I wish, I hadn't upgraded 😟

Jul 13, 2015 8:33 AM in response to n748

I feel the need to weigh in again.

1. Of course it could be a software issue.

2. About that replacement program: interesting; but obviously only concerns MacBook models with additional video cards (AMD and Nvidia), whereas in this thread the common aspect seems to be the onboard chip Intel HD Graphics 4000.

3. I don't use a thunderbolt display nor any other thunderbolt device.

Barney-15E

Level 10

116,926 points

Jul 13, 2015 5:01 PM in response to Udo from Berlin

Udo from Berlin wrote:

3. I don't use a thunderbolt display nor any other thunderbolt device.

Well then, there's a good test case to consider. What are you doing when it happens?

Are you pushing the limits of your RAM or CPU?

What type of apps are you running when it occurs?

What messages are in Console around the time of the panic?

n748

Level 1

34 points

Jul 14, 2015 1:05 PM in response to Barney-15E

I would wish very much that there would be a way to reliably reproduce the problem. On my MBP it occurs absolutely erratically: Sometimes with an external screen connected, sometimes right after the boot, sometimes when RAM is almost full.

The only things that are for sure on my system: Always crashing twice and when disabling GPU switching the problem does not occur so far. The graphic glitches recently disappeared for whatever reason.

Does anyone know of a way to reliably reproduce the kernel panic?

Apple wants to keep my Mac for five days and do some tests, but I am almost convinced that this will not help.

Concerning the replacement program, apparently my Mac is not qualified after all. Only Mid2012 retina. It is so annoying that AppleCare has basically no competences and each time you call you get totally different info.

Jul 14, 2015 2:39 PM in response to n748

I have the same symptoms on my mid-2012 Macbook Pro (non-retina), and haven't found any way to reliably reproduce the kernel panics. The problem started with 10.10.3, and can be worked around by disabling automatic graphics switching. I tried re-enabling graphics switching after installing 10.10.4, but received a kernel panic a few days later.

I really don't believe this is a hardware problem. I owned a 2010 Macbook Pro with a faulty graphics chip, and while something in the 10.7 update exacerbated the problem to the point where Apple finally agreed to fix it, that machine had issues from the day I purchased it. This computer, in contrast, has been rock solid for three years. It's run 10.7, 10.8, and 10.9 without issue. It was a workhorse while I was in grad school, during which it was in use 12+ hours a day, every day, for two and a half years. Apps would crash from time to time, certainly, but a kernel panic? Never. Not one cold restart in three years, until I installed the 10.10.3 update. With the update installed and graphics switching disabled (thus bypassing the Intel HD 4000 graphics chip and driver), the kernel panics vanished. Other folks with different Macs, but the same Intel HD 4000 graphics chip, report the same symptoms, and this isn't the first time that a driver problem has caused kernel panics for this particular graphics chip (see http://betanews.com/2012/06/29/google-comes-clean-yes-your-kernel-panic-is-chrom es-fault/, though the title is misleading: the problem wasn't Chrome, but Chrome's GPU acceleration was a common trigger).

Unfortunately, Apple closed my bug report on the issue, saying that can't troubleshoot kernel panics without a second Mac available to capture core dumps. If other registered Apple developers are reading this, please submit your own bug reports at https://bugreport.apple.com/. I'm not sure how else to attract their attention.

n748

Level 1

34 points

Jul 14, 2015 2:56 PM in response to fflewddur

I am so happy to see that I am not crazy and others experience the same problem. But only a small fraction of Intel 4000 HD Macs are affected, I guess. Otherwise this thread would probably be more crowded i also had all sorts of funky GPU switching issues on my previous Macs.

Can anyone register as a developper?

Cold restarts after 10.10.3 update.