Photoshop CC: Whole Macbook freezes on MacOS 10.10

  • 1
  • Problem
  • Updated 3 years ago
  • (Edited)
Every time I am working with Photoshop CC (newest version) on my Macbook Pro (almost 1 year old) Yosemite 10.10.2 my whole Mac is freezing and I can't do anything but start it new with the power switch. Please help!
Photo of Care

Care

  • 3 Posts
  • 0 Reply Likes
  • frustrated

Posted 3 years ago

  • 1
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 767 Reply Likes
Applications cannot shut down, reboot, or freeze an entire system on modern OS versions. The only things that can shut down, reboot, or freeze an entire system are OS bugs, bugs in low level drivers, and defective hardware.

By far, the most common cause of this that we have seen is defective RAM.

But MacOS 10.10 does have a number of low level bugs that Apple is still working to solve. So was your system freezing when running a stable version of MacOS, prior to installing MacOS 10.10?
Photo of Care

Care

  • 3 Posts
  • 0 Reply Likes
No, it just happened with MacOS 10.10, but not in the beginning, I have it since 2 months or so and the freezing just happened while running Photoshop and it started a week ago.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 766 Reply Likes
If you aren't seeing the kernel panic screen (gray screen and forced reboot), then the most likely cause would be a hardware defect (something either locking the system bus, or stopping the GPU from updating the display).
Bad RAM is still the most common cause of problems like that, but we've also seen bad motherboards, bad power supplies, bad GPUs, bad disks, etc.

Did you change or add anything around the time that this started? Drivers for new hardware, utility programs, etc.?
Photo of Care

Care

  • 3 Posts
  • 0 Reply Likes
I was in the store now and they said it could be the graphics board, but they couldn't help me further. I just downloaded a new action to photoshop from a reliable source.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 766 Reply Likes
An action couldn't do anything like that. Only a driver or OS kernel extension could do it. Yes, bad hardware is still the most likely cause.