Adobe CC/Photoshop CC hitting kernel panics in MacOS 10.9

  • 1
  • Problem
  • Updated 4 years ago
  • (Edited)
For a couple of months my MacBook Pro has been shutting down intermittently due to kernel panics. I spoke with apple support via chat and was told to erase and re-install OSX and begin adding software back in to determine if it was software or hardware. I was given the impression it was a hardware issue. I later started having screen scrambling, so I finally took it in to the apple store to have it looked at (I added new ram somewhere in there, didn't solve the problem). After two days of running tests, they insist that it is Adobe CC (I think specifically Photoshop) is the issue. They say it is incompatible with Mavericks. I thought, that doesn;t seem right, I keep it up to date, there aren't thousand of people saying that Adobe CC is causing their Macbook to crash, so I thought I'd throw it on here. The Apple store is saying it is a bug with this software. Any thoughts?
Photo of Jeremiah Austin

Jeremiah Austin

  • 5 Posts
  • 0 Reply Likes
  • pissed

Posted 4 years ago

  • 1
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 823 Reply Likes
Applications cannot cause kernel panics.

Kernel panics can only be caused by bugs in the OS code, bugs in low level drivers, and hardware defects. (and Apple support should have known this!) All the application can do is try to use the OS or hardware via the normal APIs and then encounter an existing defect in the OS code, driver, or hardware.

No, Photoshop CC is not incompatible - that sounds like you got someone who had no idea what they were talking about and just wanted to get you off the phone quickly. And I can't believe that someone in the Apple store would be so lacking in basic computer diagnostic knowledge as to blame an application for a kernel panic.

"Screen scrambling" sounds like you may have a problem with your VRAM or GPU. The details of the kernel panics (accessible in your logs directory, or browsable from the Console application) would list the module that triggered the panic - in this case, most likely the video driver.