Besides the joy about the new animoniminimojis we got from Apple, which I always include in my error reports (seriously! - I can be really mad...): Did you try the modification from Eugy84?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Mac Pro (Late 2013) GPU (Driver) Issues
- Thread starter bax2003
- Start date
- Sort by reaction score
Besides the joy about the new animoniminimojis we got from Apple, which I always include in my error reports (seriously! - I can be really mad...): Did you try the modification from Eugy84?
That was a new special version. Just had it crash while doing almost nothing (just browsing the internet, not videos or anything), "rebooted" using the unplug-then-replug trick, and it crashed again 12 minutes after restarting.
Edit: Trying out the hack to disable display mirroring. Let's hope this helps.
Edit: Trying out the hack to disable display mirroring. Let's hope this helps.
Last edited:
There is something to that. My issues started after buying a new usb audio interface. I thought it was the interfaces fault until a member of their forum pointed me to this GPU thread. Perhaps these things are intertwined.
in the attached video you can clearly see that there is no device connected to the nMP. apart from my sony TV connected in hdmi .. it may be the TV to create the KP? boh
I did the modifications by Eugy84´s instructions yesterday after second kernel panic that day....and I have no KPs since then. It is to early to jugde, but really, those animoniminimojis are truly GREAT !
Apple needs more software engineers focused on that, we just can´t get enough of them.......who cares about OS X and Fire Pro drivers and so on.I did the modifications by Eugy84´s instructions yesterday after second kernel panic that day....and I have no KPs since then. It is to early to jugde, but really, those animoniminimojis are truly GREAT !
I did the modifications by Eugy84´s instructions yesterday after second kernel panic that day....and I have no KPs since then. It is to early to jugde, but really, those animoniminimojis are truly GREAT !
Sounds really promising - thanks for the reply, bax. I myself do have a couple of days! without any crash, without the modificiation, since the last update, doing all kind of stuff, including heavy internet browsing. We will see...
... don't forget the beautifully crafted watchband collection, we get updated about three times a year, bax
@Lele_ITA: I have two devices attached - besides the monitor (sorry, Apple - this is inevitable...) A Native Instruments Komplete Audio 6 and a USB Harddisk. But, you know: The machine is able to crash and still playing a whole sampled orchestra trough that interface. Lets you finish recordings blindfolded. The engineers are completely wrong, they have not the slightest clue, so they are brabbling some kind of garbage.
The peripherals thing is BS, I received panic one time with *nothing* connected but ethernet - not even a monitor - I remote desktop'd in through VNC.
I have not received a panic since applying Eugy84's modification. But as we know, this thing can disappear for days/weeks.
I have not received a panic since applying Eugy84's modification. But as we know, this thing can disappear for days/weeks.
I did this but, it wouldn't let me edit the original, rather it did a copy with the edited string. I deleted the original plist then copied the edited string into it's place, the difference being there was "copy" at the end of the plist name. Yes I did the command-r restart and disabled system integrity protection.I have the same problem for some time. Before i did not give him so much weight as it rarely happened to me, now that the Mac Pro is turned on day and night i notice that the problem has become more present.
The panic report has always reported the following string :
*** Panic Report ***
panic(cpu 0 caller 0xffffff7f9d11ed7a): "bool IOAccelDisplayMachine2::display_mode_did_change(uint32_t): vendor driver returns false"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOAcceleratorFamily_kexts/IOAcceleratorFamily-378.18.1/Kext2/IOAccelDisplayMachine.cpp:490
Going to analyze the system logs i found that always, just before going into the kernel panic, this error was present :
Jun 4 23:59:52 Mac-Pro-di-Eugenio com.apple.xpc.launchd[1] (com.apple.preference.displays.MirrorDisplays): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
After a series of searches i managed to eliminate this error from the console by following this steps :
- Disable System Integrity Protection so you can edit the .plist file. Do this by rebooting into the recovery partition with cmd-R, open Terminal from the Utilities menu, and type:
csrutil disable
- Reboot into yoru system, then edit the .plist file with this command:
sudo vi /System/Library/LaunchAgents/com.apple.preference.displays.MirrorDisplays.plist
- Comment out the line that causes the MirrorDisplays tool to load. Change this line:
<string>Aqua</string>
to this:
<!-- <string>Aqua</string> -->
- Then, reboot and reenable System Integrity Protection using the recovery partition as described above and type:
csrutil enable
After having made this change the log file no longer contains the error indicated above and, at least for the moment, i no longer had kernel panics.
P.S. i apologize for any writing errors
Is this going to work for me?
Last edited:
The edited plist needs to have the same name as the original. I copied the original to my Desktop, edited + saved, and then copied back, replacing the original.
Thanks that worked, after I redid the whole Command-R startup and disabling system integrity protection thing.
Are you sure you have changed the file by following the steps?
At the moment, for me, 12 day of uptime with no KP
Positive, this is a cut and paste of my plist <!--<string>Aqua</string>--> as of 2 minutes ago.
And for reference, had another kernel panic about 3 hours after the one I posted about. Was just scrolling through Facebook, went to edit a post and bang, everything frozen except the mouse.
I've been up for 38 days by just being on 10.13.5 beta.
10:50 up 38 days, 12:45, 8 users, load averages: 2.15 2.72 2.89
It freezes when it feels like it is how I understand it...
I'll update to the latest beta as well and see when this garbage freezes up again...
10:50 up 38 days, 12:45, 8 users, load averages: 2.15 2.72 2.89
It freezes when it feels like it is how I understand it...
I'll update to the latest beta as well and see when this garbage freezes up again...
Did any of you ever do the Apple Hardware Test on their own?
I've been to my Apple Reseller several times and they never found any problem with my hardware. Last month I took the can to the closest apple store, after a little more than one week they said they found there was a GPU problem. With that diagnosis I was able to tell my reseller that apple found the problem and so should you. And they actually did! For the first time they agreed that there is a GPU problem – the connected display would stay black when starting hardware diagnosis. I was kind of irritated, since I have never experienced any problems like that. They changed GPU B, "tested" the device and told me it is fixed. Of cause I had a freeze the very next day that I picked the Mac up from the technical support.
I tried the AHT by myself just now and it turns out my can is only able to boot into the hardware test in roughly 1 out of 3 times. In 2 out of 3 times the display stays black. I wonder if that is how a fixed machine acts like. I tested the same thing with my new MacBook Pro - its able to boot the test every time
I've been to my Apple Reseller several times and they never found any problem with my hardware. Last month I took the can to the closest apple store, after a little more than one week they said they found there was a GPU problem. With that diagnosis I was able to tell my reseller that apple found the problem and so should you. And they actually did! For the first time they agreed that there is a GPU problem – the connected display would stay black when starting hardware diagnosis. I was kind of irritated, since I have never experienced any problems like that. They changed GPU B, "tested" the device and told me it is fixed. Of cause I had a freeze the very next day that I picked the Mac up from the technical support.
I tried the AHT by myself just now and it turns out my can is only able to boot into the hardware test in roughly 1 out of 3 times. In 2 out of 3 times the display stays black. I wonder if that is how a fixed machine acts like. I tested the same thing with my new MacBook Pro - its able to boot the test every time
Have you checked on console, in the system log, the last process before the KP?