Kernerlbase.dll and Photoshop error

  • 1
  • Problem
  • Updated 4 years ago
I currently use Photoshop CS6 and for the longest time I have had no issues whatsover with it. Recently though I launched it and the app crashes. Looked in the event viewer and I see this:

Faulting application name: Photoshop.exe, version: 13.1.2.0, time stamp: 0x50e86403
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b83b16
Exception code: 0xc06d007e
Fault offset: 0x0000812f
Faulting process id: 0x13e0
Faulting application start time: 0x01cfb9c0a2baac1a
Faulting application path: G:\Applications\Photoshop\App\PhotoshopCS6\Photoshop.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: e44b6d39-25b3-11e4-ad4b-003067ee8e6e

I looked online and searched everywhere for a solution but nothing found yet. I'm hoping this issue has been solved before or if somebody has a similar problem to mine can help.
Photo of karim oumghar

karim oumghar

  • 9 Posts
  • 0 Reply Likes
  • frustrated

Posted 4 years ago

  • 1
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 818 Reply Likes
Usually that means that a driver or third party plugin has malfunctioned.
What have you changed on your system around the time that it started crashing?
Photo of karim oumghar

karim oumghar

  • 9 Posts
  • 0 Reply Likes
I haven't had any changes at all. I've had the same setup for a year now. I've checked the device manager for any drivers/hardware changes and nothing popped up. No errors. I have been getting a couple of BSODS lately about MEMORY_MANAGEMENT.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 814 Reply Likes
The BSOD is a bad sign, since it means a low level OS, driver, or hardware problem.

Do you have any third party plugins installed with Photoshop? (some auto-update, and could cause problems)

The details from the BSOD also might tell us what is causing problems (a particular module, or set of drivers for instance).
Photo of karim oumghar

karim oumghar

  • 9 Posts
  • 0 Reply Likes
see my reply on the BSOD...
Photo of karim oumghar

karim oumghar

  • 9 Posts
  • 0 Reply Likes
Well I looked into the BSOD and what drivers/modules were faulty.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 814 Reply Likes
You won't like this: the three most common causes of that BSOD are: bad RAM, bad motherboard, and bad CPU. It is possible that another device on the system could also cause it via direct memory access (like a disk drive or video card), but those are not quite as common.
Photo of karim oumghar

karim oumghar

  • 9 Posts
  • 0 Reply Likes
Please see new reply
Photo of karim oumghar

karim oumghar

  • 9 Posts
  • 0 Reply Likes
I recently ran MemTest86 (several times for good measure). All the tests came up the same, no errors, every test was passed. So I've ruled out anything bad RAM/CPU/Mobo. Any other suggestions as to what the cause might be for PS to crash?
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 814 Reply Likes
No, you really haven't ruled out much. Software based RAM checkers only find the most obvious errors (things that probably would have prevented most applications from working). They can't test timing errors, or pulse shape errors, and can only find the most blatant of power supply problems (not the supply itself, but the power supplied to the CPU and memory chips).
Photo of karim oumghar

karim oumghar

  • 9 Posts
  • 0 Reply Likes
I should also mention that I did get a virus not too long ago but that was taken care of immediately. I scanned for any rootkits or trojans that might exist but nothing was found.
Photo of karim oumghar

karim oumghar

  • 9 Posts
  • 0 Reply Likes
Its not bad ram or cpu bc I tried running PS in safe mode and it worked just fine
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 814 Reply Likes
So it is most likely a driver.
Photo of karim oumghar

karim oumghar

  • 9 Posts
  • 0 Reply Likes
re-installed it and it works like a charm, not even a driver problem :)
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 815 Reply Likes
OK, corrupt binaries don't usually crash that simply. But ok, glad you got it working again.