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
hm... this might be the answer..?
"The problem is that DSA keys are obsolete after OpenSSH 7.0, which the new system seems to use. I generated a new RSA key and things worked again. Also, in the process I found out that the authorized_keys2 file has been actually deprecated for a long time! So I advice everybody to use authorized_keys instead, which works both with protocols 1 and 2. That way Apple's original sshd_config will work as is."
taken from here:
https://forums.developer.apple.com/thread/48794
I had this issue:
http://apple.stackexchange.com/ques...n-t-seem-to-remember-ssh-keys-between-reboots
Then I started googling and found out that there are a lot more problems,
I updated to macOS Sierra 10.12.0 and had 19 continuous days of uptime.
Then I updated to 10.12.1 and have had 8 days of continuous uptime.
I'm using Safari and Chrome exclusively. Haven't had time to test with Firefox.
That's good to hear. I've not updated to 10.12.1 yet, but that gives me some confidence to do so.
I'm up to almost 2 months now on 10.12 without any issues at all. It's been a great OS release for me so far.
Last edited:
my experience with sierra seems a bit better than with el capitan, but freezings still occur. I installed sierra on october, 14, i had three freezings since then (so on average one per week). The freezing behavior has changed: the os seems able to detect the freezing and logs you off, so you are shown the login page, you can put the pwd and continue to work. But you will find a crash log with this type of information
and something like this in your system.log
Last edited:
Three freezes with Sierra so far. Two with that logoff "feature" - at least it recovers to a state where I can reboot. One black nirvana screen with no chance of any recovery - just black - and reset button.
I don't like the logoff either - if I have iTunes running, it is absolutely necessary to close it before any logoff or reboot. With my library on an external NAS I need to logon to that network drive first, otherwise iTunes forgets the external library (which is a pretty dumb feature as well...)
I don't like the logoff either - if I have iTunes running, it is absolutely necessary to close it before any logoff or reboot. With my library on an external NAS I need to logon to that network drive first, otherwise iTunes forgets the external library (which is a pretty dumb feature as well...)
Last edited:
My new trashcan (macOS 10.12.1) just killed my day. Machine never had any problems for 10 months at previous owner (a friend). Only difference is that there are two Cinema Displays connected to it (27 + 24 inch, because I am multitasking freak) instead one MiniDP BenQ monitor.
Pictures speak for themselves:
Those gpuRestart logs were written in background when this below happened on my monitors....red, then white with artifacts, and the right one became pixelated and distorted....
WindowsServer wakeups happened later and were handled with forced log off.
This is just cataclysmic.
There must be some logic why this is happening.
Pictures speak for themselves:
Those gpuRestart logs were written in background when this below happened on my monitors....red, then white with artifacts, and the right one became pixelated and distorted....
WindowsServer wakeups happened later and were handled with forced log off.
This is just cataclysmic.
There must be some logic why this is happening.
Software, my friend. Something is rubbish about how the trash can handles the signals from the GPUs to displays which causes the tragedy. Also you have to bare in mind that Microsoft Windows 10 is not supporting Thunderbolt 2 for its... problems. So I would guess, its a mixture of TB2+Software problems.
Edit. Nope, after thinking about it, I think it is more to do with Thunderbolt 2 controller, rather than anything else.
Edit. Nope, after thinking about it, I think it is more to do with Thunderbolt 2 controller, rather than anything else.
Yes - there is some logic, Bax - Screenshot number two (the right one). Exactly one of my crashes. Missed the left one, because I only have one monitor. (Dell P2415q, running at native resolution). Do send these screens to Apple...
...and koyoot: Windows 10 on my MP does a very good job. Much better than OS X. There are some glitches, and graphics crashes. So far only while watching videos - Youtube for example. But it ALWAYS recovers to a state where Windows remains really stable. After a crash the screen flickers from time to time, which simply tells me, it is time to reboot (after quietly having saved my work)
remains a real mystery...
...and koyoot: Windows 10 on my MP does a very good job. Much better than OS X. There are some glitches, and graphics crashes. So far only while watching videos - Youtube for example. But it ALWAYS recovers to a state where Windows remains really stable. After a crash the screen flickers from time to time, which simply tells me, it is time to reboot (after quietly having saved my work)
remains a real mystery...
Last edited:
Sumbitted to Bug Report.
The fact that there are similar GFX issues in Windows X tells us that there are some serious design issues here and that we cant blame this entirely on macOS.
Thanks for this. Crashes in Windows also tell it is all due to Thunderbolt buses rather GPU problems. The connection crashes the drivers.
Again, read this post: https://forums.macrumors.com/thread...u-driver-issues.1860297/page-33#post-23644593
Its also important that on my MacBook Pro the crashes also appeared sometimes, however lately I have had no crash for months. And crashes always appeared when watching youtube only.
I would ask all of you who have GPU/Driver problems with Mac Pro (Late 2013) to post replay in this form so we can try to trace the source of issues:
Mac: Mac Pro (Late 2013)
Bought on: December 2015.
macOS version: macOS 10.12.1
SMC version: 2.20f18
Boot ROM Version: MP61.0116.B21
CPU: 6-Core Intel Xeon E5 3.5 GHz
GPUs: D300
RAM (ecc/non ecc/MHz): 32GB (4 x 8GB) 1866MHz ECC
SSD: APPLE SSD SM0256G
No. of monitors: 2
Monitor(s) brand/model/connection: Apple Cinema Display 27" (miniDP) / Apple Cinema Display 24" (miniDP)
Input Devices: BT Logitech K811, Logitech G300 (USB)
Sound output: Logitech Z906 (via Toslink)
Issue appears mostly when: heavy multitasking (iTunes, Chrome, Safari, Preview, Photoshop, VMWare).
UPS / Voltage Stabilizer: none
Mac: Mac Pro (Late 2013)
Bought on: December 2015.
macOS version: macOS 10.12.1
SMC version: 2.20f18
Boot ROM Version: MP61.0116.B21
CPU: 6-Core Intel Xeon E5 3.5 GHz
GPUs: D300
RAM (ecc/non ecc/MHz): 32GB (4 x 8GB) 1866MHz ECC
SSD: APPLE SSD SM0256G
No. of monitors: 2
Monitor(s) brand/model/connection: Apple Cinema Display 27" (miniDP) / Apple Cinema Display 24" (miniDP)
Input Devices: BT Logitech K811, Logitech G300 (USB)
Sound output: Logitech Z906 (via Toslink)
Issue appears mostly when: heavy multitasking (iTunes, Chrome, Safari, Preview, Photoshop, VMWare).
UPS / Voltage Stabilizer: none
Last edited:
I am running a base configuration of the 4Core D300 16GBRAM 1TB SSD with only an Elgato Thunderbolt Dock and a TB Monitor. With one important difference: I did hook the whole shebang to an APC UPS. Looking at your (familiar) screenshot. It is definitely not the (unstable) Powersource then...
Oh, and: Frequently running Windows 10 12 hours a day with no reboot or crash....
Issues: browsing a heavy ad-overloaded internet site for example, like these nowadays newspapers or watching a video with VLC (mainly Windows 10). The issues in VLC are somewhat reproducible, sometimes it's "just wait, it will crash"
No issues: Heavy Video Editing in OS X or Win 10 or running a whole Orchestra in OS X in Logic Pro getting the NMP to its limits.
Oh, and: Frequently running Windows 10 12 hours a day with no reboot or crash....
Issues: browsing a heavy ad-overloaded internet site for example, like these nowadays newspapers or watching a video with VLC (mainly Windows 10). The issues in VLC are somewhat reproducible, sometimes it's "just wait, it will crash"
No issues: Heavy Video Editing in OS X or Win 10 or running a whole Orchestra in OS X in Logic Pro getting the NMP to its limits.
Mac: Mac Pro (Late 2013)
Bought on: March 2015.
macOS version: macOS 10.12.1
SMC version: 2.20f18
CPU: 4-Core Intel Xeon E5 3.7 GHz
GPUs: D300
RAM (ecc/non ecc/MHz): 12GB 1866MHz DDR3
SSD: APPLE SSD SM0256F
No. of monitors: 1
Monitor(s) brand/model/connection: LG 34UC87M-B 34" 3440X1440 (TB)
Input Devices: Apple wired mouse, Microsoft wired keyboard (or Apple wired keyboard)
Sound output: internal speakers
Issue appears mostly when: randomly browsing the internet, video streaming, no clear circumstances (browsing sites with flash can be dangerous at times but the issue happens also on sites not using flash).
UPS / Voltage Stabilizer: eaton ellipse eco 1200
[doublepost=1478377597][/doublepost]well actually another freezing happened today and it happened in the old bad way, with the aggravating circumstance that i had to use the computer power button to stop the freezing (pulling off the monitor cable is not effective). So two types of freezing with sierra
- the logout type
- the classical type with the need to power off the computer with power button
The more i speak and post of it the more the errors increase, to show that the situation with sierra is not any better than before.
Bought on: March 2015.
macOS version: macOS 10.12.1
SMC version: 2.20f18
CPU: 4-Core Intel Xeon E5 3.7 GHz
GPUs: D300
RAM (ecc/non ecc/MHz): 12GB 1866MHz DDR3
SSD: APPLE SSD SM0256F
No. of monitors: 1
Monitor(s) brand/model/connection: LG 34UC87M-B 34" 3440X1440 (TB)
Input Devices: Apple wired mouse, Microsoft wired keyboard (or Apple wired keyboard)
Sound output: internal speakers
Issue appears mostly when: randomly browsing the internet, video streaming, no clear circumstances (browsing sites with flash can be dangerous at times but the issue happens also on sites not using flash).
UPS / Voltage Stabilizer: eaton ellipse eco 1200
[doublepost=1478377597][/doublepost]well actually another freezing happened today and it happened in the old bad way, with the aggravating circumstance that i had to use the computer power button to stop the freezing (pulling off the monitor cable is not effective). So two types of freezing with sierra
- the logout type
- the classical type with the need to power off the computer with power button
The more i speak and post of it the more the errors increase, to show that the situation with sierra is not any better than before.
Last edited:
I just want to point out to those who have freezing where it seems that only solution is power button - machine is still alive on the unix level and it can be access through SSH, or as Apple calls it "Remote Login" in sharing preferences. When freeze happens - use another machine in network or directly with patch cable to one of the configured Eth Ports to connect to Mac Pro via SSH. Or simply use any network way, shape or form to connect to Mac Pros IP adress (static or DHCP).
example:
ssh bax2003@mpipadress
Accept SSH keys and in the new line type:
sudo reboot
Now wait for Mac Pro to reboot.
example:
ssh bax2003@mpipadress
Accept SSH keys and in the new line type:
sudo reboot
Now wait for Mac Pro to reboot.
Mac: Mac Pro (Late 2013)
Bought on: Replaced in September 2016
macOS version: macOS 10.12.1
SMC version: 2.20f18
CPU: 4-Core Intel Xeon E5 3.7 GHz
GPUs: D300
RAM (ecc/non ecc/MHz): 12GB ECC 1866MHz DDR3
SSD: APPLE SSD SM0256G
No. of monitors: 1
Monitor(s) brand/model/connection: LG 34UC98 3440X1440 (Thunderbolt)
Input Devices: Microsoft Arc Mouse, Logitech K810 Bluetooth wireless keyboard, Logitech T651 trackpad
Sound output: internal speakers
Issue appears mostly when: using lots of browser tabs, MSFT office apps, Apple Remote Desktop
UPS / Voltage Stabilizer: CyberPower CP1350AVRLCD
Other: Sonnet Echo 15 Thunderbolt 2 docking station with Blu-Ray player
My original Mac Pro had it's D300 cards replaced and was in for Genius Bar analysis several times since December 2015. They ultimately replaced it a few months ago.
Recently, the replacement had a GPU restart loop for several hours. I was SSH'ed into it and saw .gpuRestart files repeatedly generated.
So, I followed up with Apple Support but they didn't respond for 2+ weeks. After calling them back, they insisted I get it checked out at the Genius Bar since it was a different machine. To no surprise, it passed all their tests but they wanted to take it and run extended tests. I refused since they had the other machine for 2 weeks and didn't find anything.
Apple uses the same rigid support playbook. Showing them documented threads & articles doesn't seem to matter. The 'sysdiagnose' output I send is never addressed. They just say they want to get it working for me.
Attached is a screen photo when I had a Samsung SyncMaster T240 connected via HDMI so I don't think it's squarely a Thunderbolt issue.
Bought on: Replaced in September 2016
macOS version: macOS 10.12.1
SMC version: 2.20f18
CPU: 4-Core Intel Xeon E5 3.7 GHz
GPUs: D300
RAM (ecc/non ecc/MHz): 12GB ECC 1866MHz DDR3
SSD: APPLE SSD SM0256G
No. of monitors: 1
Monitor(s) brand/model/connection: LG 34UC98 3440X1440 (Thunderbolt)
Input Devices: Microsoft Arc Mouse, Logitech K810 Bluetooth wireless keyboard, Logitech T651 trackpad
Sound output: internal speakers
Issue appears mostly when: using lots of browser tabs, MSFT office apps, Apple Remote Desktop
UPS / Voltage Stabilizer: CyberPower CP1350AVRLCD
Other: Sonnet Echo 15 Thunderbolt 2 docking station with Blu-Ray player
My original Mac Pro had it's D300 cards replaced and was in for Genius Bar analysis several times since December 2015. They ultimately replaced it a few months ago.
Recently, the replacement had a GPU restart loop for several hours. I was SSH'ed into it and saw .gpuRestart files repeatedly generated.
So, I followed up with Apple Support but they didn't respond for 2+ weeks. After calling them back, they insisted I get it checked out at the Genius Bar since it was a different machine. To no surprise, it passed all their tests but they wanted to take it and run extended tests. I refused since they had the other machine for 2 weeks and didn't find anything.
Apple uses the same rigid support playbook. Showing them documented threads & articles doesn't seem to matter. The 'sysdiagnose' output I send is never addressed. They just say they want to get it working for me.
Attached is a screen photo when I had a Samsung SyncMaster T240 connected via HDMI so I don't think it's squarely a Thunderbolt issue.
In 10.9.5 and 10.12.1 are only OS X version where I got screen corrupted image.
10.12 introduced fored log-off when WindowServer crashes.
All other versions just hang (in random situations) in which case nMP is still alive on the Unix level and you can reboot it via SSH.
One thing I noticed last few days is that WindowServer loves to crash when I initiate heavy network traffic, especially when I need few GBs large files copied to virtual machine (VMware) running on nMP.
Nobody likes to diagnose this kind of behaviour.....I think this is firmware/software related.
10.12 introduced fored log-off when WindowServer crashes.
All other versions just hang (in random situations) in which case nMP is still alive on the Unix level and you can reboot it via SSH.
One thing I noticed last few days is that WindowServer loves to crash when I initiate heavy network traffic, especially when I need few GBs large files copied to virtual machine (VMware) running on nMP.
Nobody likes to diagnose this kind of behaviour.....I think this is firmware/software related.
To this day I still don't have a freeze or distortion issue with 5 monitors in OS X 10.9.5 (all 30 inch with dual-DVI adapter). As you recall I had plenty of issues with OS X 10.10 and OS X 10.11. I didn't try OS X 10.12 yet.
A few weeks ago I added one more 30 inch monitor to make it an even six and since then the computer shuts down during sleep once in a while. It never shuts down while it is actively being used. Nor does it freeze up during usage. I am still fiddling around with the USB devices to see if any of those are the cause of the sleep issues since I had to add more USB hubs to connect the USB power portion of the dual-DVI adapters. Overall 10.9.5 seems to work fine even with the maximum number of monitors that can be connected to the Mac Pro.
[doublepost=1478916234][/doublepost]Just looking at my stats it appears that one of the Dual-Link DVI Adapter has an older Firmware (1.02). This could be the cause of my sleep issues. Here is the complete report of an otherwise trouble free 'working system' as long as OS X 10.9.5 is used:
Model Name: Mac Pro
Model Identifier: MacPro6,1
Processor Name: Quad-Core Intel Xeon E5
Processor Speed: 3.7 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 10 MB
Memory: 64 GB
Boot ROM Version: MP61.0116.B17
SMC Version (system): 2.20f18
Illumination Version: 1.4a6
SSD: APPLE SSD SM0512G Media (2015 MacBook Pro swap)
Input devices: 1 Apple wired keyboard, 1 Apple wireless keyboard, 2 Apple wireless trackpads, 2 third party wired USB mice
Chipset Model: AMD FirePro D300
ROM Revision: 113-C4012F-687
gMux Version: 4.0.11 [3.2.8]
Displays:
Cinema HD:
Display Type: LCD
Resolution: 1600 x 2560
Pixel Depth: 32-Bit Color (ARGB8888)
Mirror: Off
Online: Yes
Rotation: 270
Adapter Type: Apple Mini DisplayPort To Dual-Link DVI Adapter
Adapter Firmware Version: 1.03
Cinema HD:
(identical)
Cinema HD:
(identical)
Cinema HD:
(identical)
Cinema HD:
(identical)
Cinema HD:
Adapter Type: Apple Mini DisplayPort To Dual-Link DVI Adapter
Adapter Firmware Version: 1.02
A few weeks ago I added one more 30 inch monitor to make it an even six and since then the computer shuts down during sleep once in a while. It never shuts down while it is actively being used. Nor does it freeze up during usage. I am still fiddling around with the USB devices to see if any of those are the cause of the sleep issues since I had to add more USB hubs to connect the USB power portion of the dual-DVI adapters. Overall 10.9.5 seems to work fine even with the maximum number of monitors that can be connected to the Mac Pro.
[doublepost=1478916234][/doublepost]Just looking at my stats it appears that one of the Dual-Link DVI Adapter has an older Firmware (1.02). This could be the cause of my sleep issues. Here is the complete report of an otherwise trouble free 'working system' as long as OS X 10.9.5 is used:
Model Name: Mac Pro
Model Identifier: MacPro6,1
Processor Name: Quad-Core Intel Xeon E5
Processor Speed: 3.7 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 10 MB
Memory: 64 GB
Boot ROM Version: MP61.0116.B17
SMC Version (system): 2.20f18
Illumination Version: 1.4a6
SSD: APPLE SSD SM0512G Media (2015 MacBook Pro swap)
Input devices: 1 Apple wired keyboard, 1 Apple wireless keyboard, 2 Apple wireless trackpads, 2 third party wired USB mice
Chipset Model: AMD FirePro D300
ROM Revision: 113-C4012F-687
gMux Version: 4.0.11 [3.2.8]
Displays:
Cinema HD:
Display Type: LCD
Resolution: 1600 x 2560
Pixel Depth: 32-Bit Color (ARGB8888)
Mirror: Off
Online: Yes
Rotation: 270
Adapter Type: Apple Mini DisplayPort To Dual-Link DVI Adapter
Adapter Firmware Version: 1.03
Cinema HD:
(identical)
Cinema HD:
(identical)
Cinema HD:
(identical)
Cinema HD:
(identical)
Cinema HD:
Adapter Type: Apple Mini DisplayPort To Dual-Link DVI Adapter
Adapter Firmware Version: 1.02
I just confirmed that a Dual-link DVI adapter below firmware 1.03 can cause flickering and wake from sleep issues (https://support.apple.com/en-us/HT203352).
My firmware issue will probably not apply to most of the users on this thread but it raised my suspicion that the freeze issues experienced in OS X 10.10 or later are related to the software implementation of Thunderbolt 3 and USB 3.1.
My firmware issue will probably not apply to most of the users on this thread but it raised my suspicion that the freeze issues experienced in OS X 10.10 or later are related to the software implementation of Thunderbolt 3 and USB 3.1.
Last edited:
1080Ti spotted at Zauba.
10GB? Well, seems like another 970 all over again if this is true. If it is, will they ever learn? Unless they're not using all mem controllers, it seems they disabled one and not use the full 384b width. Let's wait and see.
Sorry, wrong thread. Having a few open might lead to this
10GB? Well, seems like another 970 all over again if this is true. If it is, will they ever learn? Unless they're not using all mem controllers, it seems they disabled one and not use the full 384b width. Let's wait and see.
Sorry, wrong thread. Having a few open might lead to this
Because they advertise it as 10GB that means they have learned from the past. This isnt even the right thread to talk about this, nor is the one to post information about Nvidia upcoming GPUs.