New 2015 MacBook Pro - Kernel Panic since 10.10.3 update

Question

Level 1

15 points

New 2015 MacBook Pro - Kernel Panic since 10.10.3 update

Hi,

Since the 10.10.3 Yosemite update, I'm getting daily kernal panics as shown below on my new 2015 MBP Force Touch. Any ideas as to what's causing this and/or how to resolve?

Thanks,

Mike

Anonymous UUID: 0526B03C-2C0E-C58B-EE36-1412A5A473FD

Sat Apr 11 10:30:10 2015

*** Panic Report ***

panic(cpu 2 caller 0xffffff8016217cc2): Kernel trap at 0xffffff7f981d7b06, type 14=page fault, registers:

CR0: 0x0000000080010033, CR2: 0xffffff88e76f6fe8, CR3: 0x000000000a09f019, CR4: 0x00000000003627e0

RAX: 0x00000000ffffffff, RBX: 0x00000000e00002bc, RCX: 0xffffff7f981fc154, RDX: 0xffffff80403b0600

RSP: 0xffffff8120083820, RBP: 0xffffff8120083820, RSI: 0x00000000ffffffff, RDI: 0xffffff80e76f5000

R8: 0xffffff80403b0600, R9: 0xffffff81200839d0, R10: 0xffffff7f971ed950, R11: 0xffffff8120083b80

R12: 0xffffff80e76f5000, R13: 0xffffff80327882b4, R14: 0xffffff80403b0600, R15: 0x0000000000000002

RFL: 0x0000000000010297, RIP: 0xffffff7f981d7b06, CS: 0x0000000000000008, SS: 0x0000000000000010

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

Backtrace (CPU 2), Frame : Return Address

0xffffff81200834d0 : 0xffffff801612bda1

0xffffff8120083550 : 0xffffff8016217cc2

0xffffff8120083710 : 0xffffff8016234b73

0xffffff8120083730 : 0xffffff7f981d7b06

0xffffff8120083820 : 0xffffff7f981e88f0

0xffffff8120083860 : 0xffffff7f981fc164

0xffffff81200838b0 : 0xffffff7f981fc39d

0xffffff81200838d0 : 0xffffff80166d41ce

0xffffff8120083910 : 0xffffff7f981fc408

0xffffff8120083960 : 0xffffff7f981b2d74

0xffffff8120083980 : 0xffffff7f981b2eb1

0xffffff8120083a00 : 0xffffff7f986045c9

0xffffff8120083a60 : 0xffffff80166d41ce

0xffffff8120083aa0 : 0xffffff7f986049d8

0xffffff8120083af0 : 0xffffff7f981b2eb1

0xffffff8120083b70 : 0xffffff7f981b284e

0xffffff8120083bc0 : 0xffffff80166ff0c3

0xffffff8120083d00 : 0xffffff80161e21e7

0xffffff8120083e10 : 0xffffff801613000c

0xffffff8120083e40 : 0xffffff80161149f3

0xffffff8120083e90 : 0xffffff801612531d

0xffffff8120083f10 : 0xffffff80162031ea

0xffffff8120083fb0 : 0xffffff8016235396

Kernel Extensions in backtrace:

com.apple.AppleGraphicsDeviceControl(3.10.22)[44D7223C-9628-3FEA-A3B8-27DE9E1CE 0C3]@0xffffff7f981b2000->0xffffff7f981b7fff

com.apple.driver.AppleIntelBDWGraphicsFramebuffer(10.0.6)[BD924979-4EEE-345B-95 A3-59BC631819CD]@0xffffff7f981b8000->0xffffff7f9820bfff

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

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

dependency: com.apple.iokit.IOAcceleratorFamily2(156.14)[BE7D765B-49C1-34F9-B75E-3EAF8A4062 A3]@0xffffff7f98135000

dependency: com.apple.iokit.IOReportFamily(31)[781C9DD1-4CE9-3AEB-85EA-D420CEC18916]@0xffff ff7f97129000

dependency: com.apple.AppleGraphicsDeviceControl(3.10.22)[44D7223C-9628-3FEA-A3B8-27DE9E1CE 0C3]@0xffffff7f981b2000

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[82EAD591-67E3-39CB-A232-A8095CA30E92]@0 xffffff7f971c9000

com.apple.driver.AppleGraphicsDevicePolicy(3.7.7)[59E7CF6C-C2D1-3FFC-A122-DB048 907FB67]@0xffffff7f98600000->0xffffff7f98606fff

dependency: com.apple.driver.AppleGraphicsControl(3.10.22)[61967104-88AF-3605-82F5-A480A280 0A78]@0xffffff7f985dc000

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

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

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[82EAD591-67E3-39CB-A232-A8095CA30E92]@0 xffffff7f971c9000

dependency: com.apple.AppleGraphicsDeviceControl(3.10.22)[44D7223C-9628-3FEA-A3B8-27DE9E1CE 0C3]@0xffffff7f981b2000

BSD process name corresponding to current thread: displaypolicyd

Mac OS version:

14D131

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: 0x0000000015e00000

Kernel text base: 0xffffff8016000000

__HIB text base: 0xffffff8015f00000

System model name: MacBookPro12,1 (Mac-E43C1C25D4880AD6)

System uptime in nanoseconds: 26248860005879

last loaded kext at 4513715085545: com.apple.filesystems.smbfs 3.0.1 (addr 0xffffff7f98795000, size 389120)

last unloaded kext at 4070556686544: com.apple.driver.AppleUSBAudio 295.23 (addr 0xffffff7f98799000, size 315392)

loaded kexts:

com.apple.filesystems.smbfs 3.0.1

com.apple.driver.AppleBluetoothMultitouch 85.3

com.apple.filesystems.autofs 3.0

com.apple.driver.AudioAUUC 1.70

com.apple.iokit.IOBluetoothSerialManager 4.3.4f4

com.apple.driver.AGPM 110.19.5

com.apple.driver.ApplePlatformEnabler 2.2.0d4

com.apple.driver.X86PlatformShim 1.0.0

com.apple.driver.AppleOSXWatchdog 1

com.apple.driver.AppleHDA 272.18

com.apple.driver.AppleGraphicsDevicePolicy 3.7.7

com.apple.driver.AppleUpstreamUserClient 3.6.1

com.apple.iokit.IOUserEthernet 1.0.1

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.AppleLPC 1.7.3

com.apple.driver.AppleCameraInterface 5.33.0

com.apple.driver.AppleHWAccess 1

com.apple.driver.AppleHV 1

com.apple.driver.AppleSMCLMU 2.0.7d0

com.apple.driver.AppleBacklight 170.7.4

com.apple.driver.AppleMCCSControl 1.2.11

com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.3.4f4

com.apple.driver.AppleThunderboltIP 2.0.2

com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0

com.apple.driver.AppleIntelBDWGraphics 10.0.6

com.apple.driver.AppleIntelBDWGraphicsFramebuffer 10.0.6

com.apple.driver.AppleUSBCardReader 3.5.5

com.apple.iokit.SCSITaskUserClient 3.7.5

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.BootCache 36

com.apple.driver.XsanFilter 404

com.apple.iokit.IOAHCIBlockStorage 2.7.1

com.apple.driver.AppleUSBHub 705.4.2

com.apple.driver.AppleAHCIPort 3.1.2

com.apple.driver.AppleTopCaseHIDEventDriver 67

com.apple.driver.AirPort.Brcm4360 930.37.3

com.apple.driver.AppleUSBXHCI 710.4.11

com.apple.driver.AppleRTC 2.0

com.apple.driver.AppleSmartBatteryManager 161.0.0

com.apple.driver.AppleACPIButtons 3.1

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.nke.applicationfirewall 161

com.apple.security.quarantine 3

com.apple.security.TMSafetyNet 8

com.apple.driver.AppleBluetoothHIDKeyboard 176.2

com.apple.driver.IOBluetoothHIDDriver 4.3.4f4

com.apple.kext.triggers 1.0

com.apple.driver.DspFuncLib 272.18

com.apple.kext.OSvKernDSPLib 1.15

com.apple.driver.AppleGraphicsControl 3.10.22

com.apple.driver.AppleHDAController 272.18

com.apple.iokit.IOHDAFamily 272.18

com.apple.iokit.IOAudioFamily 203.3

com.apple.vecLib.kext 1.2.0

com.apple.driver.AppleBacklightExpert 1.1.0

com.apple.driver.AppleSMBusController 1.0.13d1

com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.3.4f4

com.apple.iokit.IOBluetoothFamily 4.3.4f4

com.apple.iokit.IOUSBUserClient 705.4.0

com.apple.iokit.IOSerialFamily 11

com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0

com.apple.driver.X86PlatformPlugin 1.0.0

com.apple.driver.AppleSMC 3.1.9

com.apple.driver.IOPlatformPluginFamily 5.9.1d7

com.apple.iokit.IOSurface 97.4

com.apple.iokit.IONDRVSupport 2.4.1

com.apple.AppleGraphicsDeviceControl 3.10.22

com.apple.iokit.IOAcceleratorFamily2 156.14

com.apple.iokit.IOGraphicsFamily 2.4.1

com.apple.driver.AppleUSBMergeNub 705.4.0

com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.5

com.apple.iokit.IOUSBMassStorageClass 3.7.2

com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.5

com.apple.driver.AppleUSBComposite 705.4.9

com.apple.driver.CoreStorage 471.20.7

com.apple.iokit.IOAHCIFamily 2.7.5

com.apple.driver.AppleThunderboltDPInAdapter 4.0.6

com.apple.driver.AppleThunderboltDPAdapterFamily 4.0.6

com.apple.driver.AppleThunderboltPCIDownAdapter 2.0.2

com.apple.driver.AppleHIDKeyboard 176.2

com.apple.driver.AppleHSSPIHIDDriver 41.3

com.apple.driver.AppleMultitouchDriver 263.9.1

com.apple.driver.AppleThunderboltNHI 3.1.7

com.apple.iokit.IOThunderboltFamily 4.2.2

com.apple.iokit.IO80211Family 730.60

com.apple.driver.mDNSOffloadUserClient 1.0.1b8

com.apple.iokit.IONetworkingFamily 3.2

com.apple.driver.AppleHSSPISupport 41.3

com.apple.driver.AppleIntelLpssSpiController 2.0.56

com.apple.iokit.IOUSBFamily 720.4.4

com.apple.driver.AppleIntelLpssGspi 2.0.56

com.apple.driver.AppleIntelLpssDmac 2.0.56

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

com.apple.kec.Libm 1

com.apple.kec.pthread 1

Model: MacBookPro12,1, BootROM MBP121.0167.B02, 2 processors, Intel Core i5, 2.7 GHz, 8 GB, SMC 2.28f6

Graphics: Intel Iris Graphics 6100, Intel Iris Graphics 6100, Built-In

Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1867 MHz, 0x80AD, 0x483943434E4E4E424C54414C41522D4E5544

Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1867 MHz, 0x80AD, 0x483943434E4E4E424C54414C41522D4E5544

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x133), Broadcom BCM43xx 1.0 (7.15.166.24.3)

Bluetooth: Version 4.3.4f4 15601, 3 services, 27 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en0

Serial ATA Device: APPLE SSD SM0256G, 251 GB

USB Device: Internal Memory Card Reader

USB Device: My Passport 0748

USB Device: Bluetooth USB Host Controller

Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1201

MacBook Pro (Retina, 13-inch,Early 2015), OS X Yosemite (10.10.3), Kernel Panic

Posted on Apr 11, 2015 7:42 AM

Reply

Answer 1

morganic

Level 1

4 points

Jan 16, 2017 12:39 PM in response to cherrybombaz

So, I've done a lot of troubleshooting on my end and have confirmed that using an external monitor with the new 2016 MBP causes my machine to kernel panic. It is very inconsistent, but I can't go a week without it happening at least once. If I unplug my monitors at the end of the day, my cpu never crashes (been about 2 weeks now). Super annoying and inconvenient to have to unplug them when I'm not using my cpu. I am going to contact Apple and see what I can get from them. Will update.

OS X 10.12.2

Two external monitors connected via DisplayPort - LG 27UD68 and Dell U2713HM

Reply

Answer 2

Feb 11, 2017 10:53 AM in response to morganic

I'm interested in what you learn. I have contacted Apple support several times and it might be time for a genius bar appointment. I will try your DisplayPort unplug method on my 2015 MBP to see if it mitigates the issue. Its clear to me its a video driver issue.

Reply

Answer 3

Linc Davis

Level 10

209,739 points

Apr 11, 2015 11:44 AM in response to mjoshea148

The warranty entitles you to complimentary phone support for the first 90 days of ownership.

If you bought the product in the U.S. directly from Apple (not from a reseller), you have 14 days from the date of delivery in which to exchange or return it for a refund. In other countries, the return policy may be different. If you bought from a reseller, its return policy applies.

Reply

Answer 4

mjoshea148 Author

Level 1

15 points

Apr 12, 2015 5:10 AM in response to Linc Davis

Thanks. I was hoping to see whether others have encountered similar issues. This only became an issue for me after the 10.10.3 upgrade. Not prior, so I'm assuming it's software, not hardware related.

But, I think I'll need to take the path you're suggesting to start off.

Reply

Answer 5

Apr 21, 2015 7:02 AM in response to mjoshea148

Hmm I am getting precisely the same panic and trace.

Tue Apr 21 09:33:24 2015

*** Panic Report ***

panic(cpu 0 caller 0xffffff8006e17cc2): Kernel trap at 0xffffff7f88e23b06, type 14=page fault, registers:

CR0: 0x000000008001003b, CR2: 0xffffff89a4e01fe8, CR3: 0x00000003e072e01c, CR4: 0x00000000003627e0

RAX: 0x00000000ffffffff, RBX: 0x00000000e00002bc, RCX: 0xffffff7f88e48154, RDX: 0xffffff803b8b2600

RSP: 0xffffff81f198b820, RBP: 0xffffff81f198b820, RSI: 0x00000000ffffffff, RDI: 0xffffff81a4e00000

R8: 0xffffff803b8b2600, R9: 0xffffff81f198b9d0, R10: 0xffffff7f87e52950, R11: 0xffffff81f198bb80

R12: 0xffffff81a4e00000, R13: 0xffffff8028de78b4, R14: 0xffffff803b8b2600, R15: 0x0000000000000002

RFL: 0x0000000000010297, RIP: 0xffffff7f88e23b06, CS: 0x0000000000000008, SS: 0x0000000000000010

Fault CR2: 0xffffff89a4e01fe8, Error code: 0x0000000000000000, Fault CPU: 0x0

Backtrace (CPU 0), Frame : Return Address

0xffffff81f198b4d0 : 0xffffff8006d2bda1

0xffffff81f198b550 : 0xffffff8006e17cc2

0xffffff81f198b710 : 0xffffff8006e34b73

0xffffff81f198b730 : 0xffffff7f88e23b06

0xffffff81f198b820 : 0xffffff7f88e348f0

0xffffff81f198b860 : 0xffffff7f88e48164

0xffffff81f198b8b0 : 0xffffff7f88e4839d

0xffffff81f198b8d0 : 0xffffff80072d41ce

0xffffff81f198b910 : 0xffffff7f88e48408

0xffffff81f198b960 : 0xffffff7f88dfed74

0xffffff81f198b980 : 0xffffff7f88dfeeb1

0xffffff81f198ba00 : 0xffffff7f892645c9

0xffffff81f198ba60 : 0xffffff80072d41ce

0xffffff81f198baa0 : 0xffffff7f892649d8

0xffffff81f198baf0 : 0xffffff7f88dfeeb1

0xffffff81f198bb70 : 0xffffff7f88dfe84e

0xffffff81f198bbc0 : 0xffffff80072ff0c3

0xffffff81f198bd00 : 0xffffff8006de21e7

0xffffff81f198be10 : 0xffffff8006d3000c

0xffffff81f198be40 : 0xffffff8006d149f3

0xffffff81f198be90 : 0xffffff8006d2531d

0xffffff81f198bf10 : 0xffffff8006e031ea

0xffffff81f198bfb0 : 0xffffff8006e35396

Kernel Extensions in backtrace:

com.apple.AppleGraphicsDeviceControl(3.10.22)[44D7223C-9628-3FEA-A3B8-27DE9E1CE 0C3]@0xffffff7f88dfe000->0xffffff7f88e03fff

com.apple.driver.AppleIntelBDWGraphicsFramebuffer(10.0.6)[BD924979-4EEE-345B-95 A3-59BC631819CD]@0xffffff7f88e04000->0xffffff7f88e57fff

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

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

dependency: com.apple.iokit.IOAcceleratorFamily2(156.14)[BE7D765B-49C1-34F9-B75E-3EAF8A4062 A3]@0xffffff7f88d81000

dependency: com.apple.iokit.IOReportFamily(31)[781C9DD1-4CE9-3AEB-85EA-D420CEC18916]@0xffff ff7f87d8e000

dependency: com.apple.AppleGraphicsDeviceControl(3.10.22)[44D7223C-9628-3FEA-A3B8-27DE9E1CE 0C3]@0xffffff7f88dfe000

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[82EAD591-67E3-39CB-A232-A8095CA30E92]@0 xffffff7f87e2e000

com.apple.driver.AppleGraphicsDevicePolicy(3.7.7)[59E7CF6C-C2D1-3FFC-A122-DB048 907FB67]@0xffffff7f89260000->0xffffff7f89266fff

dependency: com.apple.driver.AppleGraphicsControl(3.10.22)[61967104-88AF-3605-82F5-A480A280 0A78]@0xffffff7f8923c000

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

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

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[82EAD591-67E3-39CB-A232-A8095CA30E92]@0 xffffff7f87e2e000

dependency: com.apple.AppleGraphicsDeviceControl(3.10.22)[44D7223C-9628-3FEA-A3B8-27DE9E1CE 0C3]@0xffffff7f88dfe000

BSD process name corresponding to current thread: displaypolicyd

It seems to occur when my macbook wakes from sleep and is connected with HDMI to an external monitor. Are you set up the same?

I did run a Verify Permissions check with the Disk Utility and it found that the above "displaypolicyd" has broken permissions. I'm repairing them to see if that helps, so you could try that.

Reply

Answer 6

mjoshea148 Author

Level 1

15 points

Apr 21, 2015 7:20 AM in response to spaceman79

Hi Spaceman,

I was set up exactly like you. Wake up from sleep and connected to external monitor with HDMI.

I called support, they had me fix permissions, reset PRAM and see what happened. Problem persisted. I reinstalled Yosemite from scratch BUT removed the external monitor for now. Wasn't worth the morning error. I may attach it again soon and see what happens. That said, the recent Yosemite 10.10.3 supplemental upgrade noted a" fix for a video driver that may prevent Mac from starting up when running certain apps that capture video." Have you installed that and was there any change?

EDIT: forgot to note, I also noticed the displaypolicyd permissions error. I fixed that before calling Apple - no joy at the time.

Mike

Reply

Answer 7

Apr 21, 2015 7:37 AM in response to mjoshea148

Yeah I installed the supplemental upgrade last Friday and the problem still persists, crashed this morning. After repairing permissions this morning I noticed that when I woke my machine from sleep it did not flicker between laptop and external monitor which is used to do, when deciding which one to put the login screen on. So thats some improvement.

It may or may not be related but I also noticed that on waking, all my windows are gathered onto one screen, unlike my previous laptop which was running Mavericks. It is a slight pain to move everything back to where I want it on two screens, but it may be symptomatic of the same problem. I'm going to see if the problem persists after repairing, and if it does I'm going to try leaving my machine connected using DVI rather than HDMI, in case it's a driver problem.

Reply

Answer 8

mjoshea148 Author

Level 1

15 points

Apr 21, 2015 8:43 AM in response to spaceman79

Thanks for sharing your updates. I don't have the luxury of attaching the monitor via DVI, so that's out. Prior to 10.10.3 I didn't have an issue at all, so my guess is it's something driver related.

I can't attest to the apps in multiple windows since I used the MBP in clamshell mode when attached to the monitor.

Only thing I can try, is whether the clean install worked. Maybe I'll set things back up this weekend and give it a go.

Reply

Answer 9

Apr 21, 2015 9:27 AM in response to mjoshea148

Hi there, I have the exact same problem as you describe with my new macbook 2015 pro 13". I did a clean reinstall yesterday and I can say the problem still persist for me. I also use an external monitor via HDMI and it seems to fault in the same as you. I have installed all the latest patches from Apple but to no good. For me it always occurs when the computer wakes up again from sleep. My colleague who has the same laptop spec and same monitor do not have this problem. I did run a memory checker for 16 hours this weekend but it did not find any errors.

I have Virtualbox installed, do you think that it may be the cause? Since the kernel crash seem related to something with the Apple graphics driver my suspicion goes to either HDMI port or thunderbolt. After the reinstall my computer worked very fine for a couple of hours waking up from sleep. But now when I got back being away from the computer for around 2 hours the computer had crashed again with the exact same error again.

Reply

Answer 10

mjoshea148 Author

Level 1

15 points

Apr 21, 2015 12:28 PM in response to kanchenjunga103

I don't think Virtualbox is the issue. I have/had a pretty lean set up and got the same issues. And considering all was fine before the update, I'd put my money on Apple having changed something in the display drivers.

Reply

Answer 11

Apr 21, 2015 11:32 PM in response to mjoshea148

So you dont think it is a HW related problem? I am very close to sending in my Macbook Pro. Today when I got back to work the computer had been sleeping all night and woke up just fine. I just got mine when 10.10.3 came out so I have only experienced trouble. 🙂

Reply

Answer 12

mjoshea148 Author

Level 1

15 points

Apr 22, 2015 4:43 AM in response to kanchenjunga103

I don't think so. I had no problems prior to the 10.10.3 update. So, it's hard to accept (but could be wrong) that we all develop hardware issues simultaneously. That said, the problem still exists, right?

Mike

Reply

Answer 13

Apr 22, 2015 6:11 AM in response to mjoshea148

Well so far so good since the repairing permissions. Machine woke up fine after a night asleep (that is when it has had most problems), and all wake ups no longer have that flickering indecision about which monitor to make the primary that I was describing. Still early, I'll report back if the issues reoccur.

For anyone else reading who doesn't know how to fix permissions: Go to Applications>Utilities>Disk Utility, Select your hard-drive and then click Verify Permissions. If you see any issues you can click Repair Permissions. In particular for this problem "displaypolicyd" had permissioning issues that fixing seems to have resolved it.

Reply

Answer 14

mjoshea148 Author

Level 1

15 points

Apr 22, 2015 6:20 AM in response to spaceman79

So, I hooked back up the Acer monitor, calibrated, etc.

Then deliberately put the unit back to sleep for a bit and removed external power. When I returned, plugged in and woke it up, I got a grey screen with a message that the unit had crashed and had to restart. When it did, there was no crash log shown.

So, I just checked permissions again and sure enough "displaypolicyd" was there. I just repaired now and we'll see how it goes.

But keep in mind, I did a clean wipe and reinstall of all upgrades and apps. No issues. Then hooked up the monitor and got that crash pretty quickly.

So, I'll let you know how it goes, but I'm still thinking it's not hardware. What do you think? Do you leave the MBP hooked up to power 24/7? I turn off to get rid of the green light (it's in the bedroom). Just trying to see if we can establish any similarities. Also, did you switch away from HDMI to DVI?

Reply

Answer 15

Apr 22, 2015 7:29 AM in response to mjoshea148

I get the displaypolicyd problem everytime I reboot when I verify permissions. Yes I keep my Macbook connected 24/7 to a powersource at work. I dont see the crash logs anymore either.. very weird. I did a clean reinstall of the laptop on Monday and still I see random crashes.

I have tried with DVI via Thunderbolt and it has also crashed for me. Do you find anything interesting under /Library/Logs/DiagnosticReports ? I only see old crashes there now.

I see this also in com.apple.networking.discoveryd.log but maybe that is another issue:

Apr 22 10:40:26.965168 localhost discoveryd_helper[268]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Apr 22 10:40:26.965589 localhost discoveryd_helper[268]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7fdd2bc03990: start (pid=72, <unknown> not root)

Reply