because the screen was still black and wouldn't wake up.Why exactly did you have to press Cmd + Ctrl + Eject after reconnecting the display?
because the screen was still black and wouldn't wake up.Why exactly did you have to press Cmd + Ctrl + Eject after reconnecting the display?
tell me about it!!!!!Huh, that's really odd.
Did you end up selling it? I'm just about to pick mine up after everything inside has been replaced.Mac Pro i out of my setup. I lost too much time and energy. This is end of the road for me and Late 2013 Mac Pro.
Did you end up selling it? I'm just about to pick mine up after everything inside has been replaced.
Yes, and I gave buyer a warning and very good price. It is still under warranty.....maybe computer hates me
I might do the same if I have the same problem after they replaced GPU A, GPU B and the motherboard lol. The problem is I bought this machine recently and will definitely be at a somewhat significant loss.
What were you using the MP for and what will you be using now?
Post production mostly, Avid / Final Cut / Compressor. After this experience, I don´t know what to buy now....I need fast and reliable machine....
1. PC - no
2. Hackintosh - no
3. MacBook Pro Retina 15 - maybe
4. Mac Pro 2010 / 2012 - maybe (depends on condition and age)
5. iMac 27/5k - probably not
I found out myself what was causing the problem. It was a dodgy usb device. Thankfully it's all sorted.
Lol I just picked my MP up from the apple store. I haven't tested long enough to see if it'll freeze again, but there's another crazy problem. The screen keeps flickering when I move stuff around... Sigh. This is unbelievable.
In my case the screen flickering was caused by the 60Hz refresh rate of the Dell P2415q UHD monitor. It completely disappeared by forcing a 50Hz refresh rate at whatever resolution. There was an identical flickering using boot camp and Windows 8 or 10. Miraculously the flickering in Windows is now gone even at 60 Hz. And even more miraculously there are almost no more hangs in Yosemite. The rare hangs in Yosemite can be resolved by disconnecting ALL TB connected peripherals and re-attaching the monitor, saving my work and rebooting. For now I have decided to live with that...Oh boy... I just switched monitors and that fixed that... I wonder if it has anything to do with the monitors we have.
In my case the screen flickering was caused by the 60Hz refresh rate of the Dell P2415q UHD monitor. It completely disappeared by forcing a 50Hz refresh rate at whatever resolution. There was an identical flickering using boot camp and Windows 8 or 10. Miraculously the flickering in Windows is now gone even with at 60 Hz. And even more miraculously there are almost no more hangs in Yosemite. The hangs in Yosemite can be resolved by disconnecting ALL TB connected peripherals and re-attaching the monitor, saving my work and rebooting. For now I have decided to live with that...
So, I'm at a point where I get a beachball hang about once every two weeks or so, usually when playing YouTube videos (but sometimes it happens when I have a screensaver active as well). I've figured out that I *can* fix it without rebooting by unplugging the back of my LG 34UM95-P Thunderbolt monitor and then reattaching the TB cable. The system unlocks, but becomes slow and unresponsive for a period of time. If I quit Chrome, and let it sit for a couple of seconds, it goes back to normal.
When this happens, nothing is in my logs (unless I just don't know how to look through my logs properly). I can't find anything about a GPU crash or Finder hang. It just stalls and doesn't report any errors.
My question is this...multiple people in this thread have mentioned getting GPU replacements and clean re-installing OS X to find the issue persists. I'm venturing to say this is a Yosemite/driver issue, and while nothing is conclusive, this started popping up for me around the time the update that improved compatibility for 4K/5K monitors was released (was it 10.10.2 or 10.10.3?).
Has anyone in this thread that is consistently having this issue tried El Capitan? Does it act the same?
My monitor is below 4K, but above Quad-HD (3440x1400). So that could be it. Or it could be an issue with TB/DP monitors in general, as some people have mentioned moving over to HDMI solves the problem.
I just can't believe that this is a hardware issue that would require replacing parts. Just hope it is fixed in El Capitan
It's most probably a driver issue that relates to 4K monitors, which is absolutely retarded.
I'm using a 20" cinema display till i can find a descent 4K monitor, and i have the same problems. So it's not limited to high res screens.
What's the resolution?
Hmm, that's odd indeed. I haven't had a problem since I've had my GPU replaced and started using the ROG Swift as my monitor.The screen resolution is 1680 x 1050.
At times i use two of these side by side, but the problem occurs with both one or two displays connected.