Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

What do you think is the source of the graphics issues on Mac Pro (Late 2013) ?

  • Hardware

    Votes: 69 53.1%
  • Software

    Votes: 28 21.5%
  • Hardware & Software

    Votes: 32 24.6%
  • Other

    Votes: 1 0.8%

  • Total voters
    130
Just now in 10.13.6 Beta 1 on my MacPro6,1 (D300):

Code:
panic(cpu 8 caller 0xffffff7f8a9a766f): "displayModeDidChange failed: set_display_mode_and_vram failed!

So no, I don't think it's fixed yet. :)
 
Just now in 10.13.6 Beta 1 on my MacPro6,1 (D300):

Code:
panic(cpu 8 caller 0xffffff7f8a9a766f): "displayModeDidChange failed: set_display_mode_and_vram failed!

So no, I don't think it's fixed yet. :)

Crap... and mine has done almost 16 hours of heavy transcoding.. just as I was feeling some hope.
 
Installed 10.13.5 30 minutes ago. My D300 just crashed again with the "displayModeDidChange failed" error.

So no fix there.
 
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 ;)
 
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 ;)

Cool! Keep us updated- whether or not the problem stays away.
 
  • Like
Reactions: Martyimac
as of 10.3.5 I haven't experienced a crash for almost 3 days! previously I was getting 3 or 4 crashes per day
 
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 ;)

So you haven't had any freezes since doing this? Please keep us updated on how this goes!
 
I haven't had a crash since updating to 10.3.6 beta 1 *knocks on all wood surfaces*. It's been about a week and the machine has done a lot of heavy lifting with transcoding. I feel comfortable enough to put the eGPU away. Of course, now that I've said that...
 
From the limited reading I've done in this thread, I have the same issue: Kernel panics where the *.panic Logs start with these lines:
Code:
panic(cpu 0 caller 0xffffff7f9878c577): "displayModeDidChange failed: set_display_mode_and_vram failed!
"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/GPUDriversAMD/GPUDriversAMD-1.66.42/Common/GLKernel/ATI/Accel/AMDAccelDisplayMachine.cpp:299

As for others, the KP doesn't result in an automatic reboot, but freeze of the UI (including menu bar clock) with spinning beach ball. Connecting with SSH is still possible, and things looks pretty normal when doing that. I usually do a sudo reboot via SSH when it happens.

I'm using a Mac Pro 6,1 at work for software development (mostly Java-based stuff). Config: quad-core, 16 GiB, 256 GB, D300s, latest macOS (v10.13.5), driving two displays (one Dell 5K and one Dell UHD).

I've experienced two KPs last Friday (2018-06-08) and two today (2018-06-11). Previously the KPs were much less frequent (say every few months) and thus easier to tolerate. But they've been increasing of late – previous two KPs were on 2018-05-22.

This is my second Mac Pro. My first one (bought June 2014) was replaced in December 2016 in a somewhat interesting way:
  • As it no longer displayed anything (or was it distorted? I forgot) we weren't surprised by the "defective video card" diagnosis, nor by the estimated cost of ~400 bucks, which we were willing to pay (out of warranty).
  • What was surprising was that they instead replaced the whole Mac Pro with a brand new one, for free.
Update: Old news, but I assume this explains why I got a free replacement: Apple Launches Repair Program for Late 2013 Mac Pro Video Issues
Update 2: Because of the next post let me add that my 5K display needs two DisplayPort (v1.2) connections, while the UHD display needs one. I connected them such that each of them uses a separate TB bus, so all three buses used. No other TB peripherals attached.
 
Last edited:
[...] because I install 2 monitors on 1 thundlerbold bus 2 (2,4 ports), when I install 1 monitor on thunderbolt bus 1(1 port) and second monitor on thunderbolt bus 2(2 port), freeze not repeat again. [...]

Sadly that doesn't help much when you have more than 3 monitors, on a device sold as supporting up to 6 monitors.

To add my voice to the noise, I just got the official update to 10.13.5, and while it ran for a few days, I definitely got the error again. As usual for me, it's almost always triggered when watching a video (inside Firefox, but that shouldn't matter).

I'm glad this thread exists, because I was ready to format and reinstall this stupid thing, but that would have been a major time sink for me.
 
Sadly that doesn't help much when you have more than 3 monitors, on a device sold as supporting up to 6 monitors.

To add my voice to the noise, I just got the official update to 10.13.5, and while it ran for a few days, I definitely got the error again. As usual for me, it's almost always triggered when watching a video (inside Firefox, but that shouldn't matter).

I'm glad this thread exists, because I was ready to format and reinstall this stupid thing, but that would have been a major time sink for me.
This was also when I got the freeze. To add some info, got rid of Firefox and have been using Safari exclusively. I still get occasion "displaymodedidfail" errors, the difference being, High Sierra will shutdown and then restart itself giving me the notification of failure upon restart. I haven't had to do a hard shutdown since i shifted from Firefox.
 
Using Safari over FF is not an option for me, personally. And if it still is shutting down doesn't improve the experience much—at least right now I can remotely or blindly close some applications to make sure everything is saved.

I've found that I can force the shutdown & restart pretty easily just by unplugging and re-plugging back in a monitor (though I'm worried that'll stress the ports, since the miniDP / Thunderbolt port is pretty awful about that).
 
So I went from a clean streak of about two weeks with no panics to FOUR freezes today on 10.13.6 b1. This is maddening to troubleshoot.
 
Not surprising, since Apple itself is unable to discover (or unwilling to admit) the root problem.
This is really the problem. i am sure that  has LOTS of reports about this failure. I know they have received at least 10-15 from me alone. And every one of them says the same thing about displaymodedidfail. Yet they refused to accept my nMP for repair when the fault was not reproducible. It spent almost a week at the local  store and never once froze or rebooted during that time. But even with a copy of one failure given to them, until it fails they won't touch it.
I'm pretty fed up with  hardware support. Since it's a closed system, I am getting close to abandoning them. If they are all about the user experience, they sure don't walk the talk when it comes to computers.
 
Is this problem only happening to people that are using 110V/60Hz?

No, it's happening all over the world. However, it's not happening to everyone and it's still not clear why.

What we lack is data for a statistical analysis. I wonder if 200 Mac Pro users would be willing to participate in a survey (100 with freezes, 100 without).
 
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 ;)

Has anyone else tried this change? I've never had Kernel Panic since i did it, and about 10 days have passed.
 
Has anyone else tried this change? I've never had Kernel Panic since i did it, and about 10 days have passed.

I did just now, after my nMP panicked again (first time since my previous post on Monday, when it panicked twice).

My feeling is that it won't help, as those log messages seem more like a symptom of the problem – other things also go nuts during the freeze/before the panic. I'd love to be wrong on this though. ;)
 
  • Like
Reactions: swithdrawn
I did just now, after my nMP panicked again (first time since my previous post on Monday, when it panicked twice).

My feeling is that it won't help, as those log messages seem more like a symptom of the problem – other things also go nuts during the freeze/before the panic. I'd love to be wrong on this though. ;)

... as Bootcamp Windows is just displaying a slight flicker in this case, it could make sense. Just "not do something" in case of a crash.

It would be kind of disastrous for the genious Apple engineers, if this simple modificiation would help, but I would greatly appreciate it.
 
No KP for the moment... :eek:
Schermata 2018-06-16 alle 12.48.53.png
 
** Panic Report **
panic(cpu 4 caller 0xffffff7f838ca577): "displayModeDidChange failed: set_display_mode_and_vram failed! "@/BuildRoot/Library/Caches/com.apple.xbs/Sources/GPUDriversAMD/GPUDriversAMD-1.66.42/Common/GLKernel/ATI/Accel/AMDAccelDisplayMachine.cpp:299

Anyway, new emojis are top notch !
 

Attachments

  • Kernel_2018-06-15-220202_Mac-Pro-61.panic.zip
    4 KB · Views: 226
  • Kernel_2018-06-16-152005_Mac-Pro-61.panic.zip
    4.8 KB · Views: 211
Lesson to world - avoid MP 6,1. Especially those with D300s.

I wonder if that's why Apple discontinued the D300 versions.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.