Adobe Photoshop CS3 & CC 2017 (trial) has stopped working

[Murray Groat]

Hi all,

A few weeks ago I got an error from my Photoshop CS3 software. When I opened it I got to the initial splash screen with it stating "Adobe Photoshop CS3 has stopped working" and I had press CLOSE. I have used this program for nearly 10 years and it has been excellent. I uninstalled/reinstalled it again and again. No luck! After a week of looking through the internet for some sanity, I asked an online art friend and they mentioned that I should get the trial version of Photoshop CC 2017. See what happens. If it works, great. If not, worry. I installed the trial version of Pshop CC 2017 and it opened as far as the initial splash screen then the dreaded error popped up "Adobe Photoshop CC has stopped working" then I had to press CLOSE. Anti-Virus software was temp switched off for CC 2017 install.

I looked up all kinds of Adobe/Photoshop forums for more insight. Nothing helped.

I tried these which did nothing:

- Altering TWAIN plugin with a tilde symbol

- No Lava file thingy dll to alter to OLD in Windows folder

- Event viewer (no idea on this)

- Defrag

- CCleaner clean out of temp files

- Error Check

- Virus scan

My current specs are:

- Acer Aspire notebook E 5742

- Windows 7 Home Premium 64-BIT OS

- Intel(R) Core(TM) i3 CPU M380 @ 2.53GHz

- 8.00 GB RAM

- 506 GB Free Memory Space

- Graphics card is up to date

- McAfee Internet Security + Windows Defender

- Wacom Intuos3 tablet (update drivers)

p.s: Btw should I uninstall Pshop CS3 before installing the trial version of Pshop CC 2017?

Best Regards.

[JJMack]

Post your Window Crash report details for you Photoshop stopped working crashes CS3 and CC 2017.

[Murray Groat]

Hi JJMack,

I hope this helps you. I am not very technical savvy with computers. I included the NODE error report details at the end of this message. It pops up after Photoshop CC 2017 error on opening also.

[JJMack]

The Problems seem to be happening when Photoshop is trying to use some system code.   May be something like a device driver problem.  

If you can please use CS3 and CC 2017 menu Help>System Info and copy and paste that information here.

If CS3 does not open try resetting your CS3 Preferences and see it it open then.   The way you do that is use the Icon you start CS3 with the immediately if not sooner press and hold down the folding keys Shift+Ctrl+Alt.  If done in time Photoshop should open a dialog window asking if you want the delete your preferences reply Yes

[Murray Groat]

Hi JJMack,

My Device Drivers have no red error marks on them.

And I have tried the 'Shift+Ctrl+Alt' at Photoshop startup for both versions before, manually and the 'Shift+Ctrl+Alt' way. Still not opening. Cannot access Pshop MENU>SYSTEM INFO. Sorry.

[JJMack]

When you used Shift+Ctrl+Alt did you get the Dialog and reply Yes?

At one time CS3 was working on you machine.  Something changed and it would no longer open. You the uninstall CS3 and Reinstalled and CS3 still would not open. 

One thing that can cause Photoshop to not open are corrupt preferences.   Re-installing CS3 does not replace corrupt Preferences.   Preferences are not created when you install Photoshop. Uninstalling Photoshop does not delete Preferences. They are create when you use Photoshop when your user ID does not have them.

That is why I want to know if you if you replied  YES.

If you did there should be no corrupt CS3 preferences on you system Therefore something other then Preferences change on your system and causes CS3 to crash.  What was change  before CS3 started to crash?. 

You wrote "My Device Drivers have no red error marks on them." That does not mean they do not have any problems there may. may still be bugs in their code.  If both CS3 and CC 2017 do not open  Make sure you have the latest Display device driver available from the manufacture's web site installed for your adapter.

[Murray Groat]

Hi JJMack,

Yes I got YES when I selected 'Shift+Ctrl+Alt' at opening. Clicked it, but Error message popped up as before. Closed it. Re-opened Pshop and still the dreaded ERROR message as before.

I may have uninstalled MACROMEDIA PROJECTOR at some point. Maybe that.

Also seems IAStorDataSvc stopped working also.

Does this help?

[JJMack]

If you look in the reliability history viewer for the First CS3 Crash and read some of the history prior to that crash you may be able to see what was changed. 

[Murray Groat]

I linked screenshots of prior CS3 crashes in my last message. ^^

I also had a program previously installed called DRIVER MANAGER. It was very helpful, when it worked. The company that owned it had eventually shut down (roughly a year ago'ish) and left me with a program that could not update or would never open again. I tried to remove it a while ago but maybe parts of it lingers on my pc. I go back in my history and it errors alot. It seems to search online automatically.

Just a thought.

Btw I updated the DISPLAY DEVICE DRIVER/ADAPTER and it said it was up to date.

[JJMack]

What did the history viewer show was updated prior the your first CS3 crash.

Also if you can in CC 2017 program folder there should be a Program named SNIFFER open a commant prompt and run that program.

Post what it displays here.

C:\Program Files\Adobe\Adobe Photoshop CC 2017>sniffer

Tester="Photoshop"

snifferStart="2017-06-16_23:10:14"

AIFCoreInitialized=1

AIFOGLInitialized=1

OGLContextCreated=1

NumGLGPUs=1

glgpu[0].GLVersion="4.1"

glgpu[0].IsIntegratedGLGPU=0

glgpu[0].GLMemoryMB=2048

glgpu[0].GLName="NVIDIA Quadro 4000"

glgpu[0].GLVendor="NVIDIA Corporation"

glgpu[0].GLVendorID=4318

glgpu[0].GLDriverVersion="21.21.13.7735"

glgpu[0].GLRectTextureSize=16384

glgpu[0].GLRenderer="Quadro 4000/PCIe/SSE2"

glgpu[0].GLRendererID=1757

glgpu[0].HasGLNPOTSupport=1

glgpu[0].GLDriver="C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispwi.inf_amd64_2db35200ede2a85a\nvd3dumx,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispwi.inf_amd64_2db35200ede2a85a\nvwgf2umx,C:\WINDOWS\System32\DriverStore\FileRepository\nv_

dispwi.inf_amd64_2db35200ede2a85a\nvwgf2umx,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispwi.inf_amd64_2db35200ede2a85a\nvwgf2umx,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispwi.inf_amd64_2db35200ede2a85a\nvd3dum,C:\WINDOWS\System32\Driver

Store\FileRepository\nv_dispwi.inf_amd64_2db35200ede2a85a\nvwgf2um,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispwi.inf_amd64_2db35200ede2a85a\nvwgf2um,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispwi.inf_amd64_2db35200ede2a85a\nvwgf2um"

glgpu[0].GLDriverDate="20170501000000.000000-000"

glgpu[0].CanCompileProgramGLSL=1

glgpu[0].GLFrameBufferOK=1

gputag.GL_SHADING_LANGUAGE_VERSION=35724

glgpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="4.50 NVIDIA"

gputag.GL_FRAGMENT_PROGRAM_ARB=34820

gputag.GL_MAX_PROGRAM_INSTRUCTIONS_ARB=34977

glgpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[65536]

gputag.GL_MAX_TEXTURE_UNITS=34018

glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]

gputag.GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS=35661

glgpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]

gputag.GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS=35660

glgpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]

gputag.GL_MAX_TEXTURE_IMAGE_UNITS=34930

glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]

gputag.GL_MAX_DRAW_BUFFERS=34852

glgpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]

gputag.GL_MAX_VERTEX_UNIFORM_COMPONENTS=35658

glgpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]

gputag.GL_MAX_FRAGMENT_UNIFORM_COMPONENTS=35657

glgpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[4096]

gputag.GL_MAX_VARYING_FLOATS=35659

glgpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]

gputag.GL_MAX_VERTEX_ATTRIBS=34921

glgpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]

gputag.AIF::OGL::GL_ARB_VERTEX_PROGRAM=69

glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1

gputag.AIF::OGL::GL_ARB_FRAGMENT_PROGRAM=27

glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1

gputag.AIF::OGL::GL_ARB_VERTEX_SHADER=70

glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1

gputag.AIF::OGL::GL_ARB_FRAGMENT_SHADER=28

glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1

gputag.AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT=81

glgpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1

gputag.AIF::OGL::GL_ARB_TEXTURE_RECTANGLE=58

glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1

gputag.AIF::OGL::GL_ARB_TEXTURE_FLOAT=53

glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1

gputag.AIF::OGL::GL_ARB_OCCLUSION_QUERY=37

glgpu[0].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1

gputag.AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT=68

glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1

gputag.AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD=47

glgpu[0].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=1

NumCLGPUs=1

clgpu[0].CLPlatformVersion="1.2"

clgpu[0].CLDeviceVersion="1.1 CUDA"

clgpu[0].IsIntegratedCLGPU=0

clgpu[0].CLMemoryMB=2048

clgpu[0].CLName="Quadro 4000"

clgpu[0].CLVendor="NVIDIA Corporation"

clgpu[0].CLVendorID=4318

clgpu[0].CLDriverVersion="377.35"

clgpu[0].CUDASupported=1

clgpu[0].CUDAVersion="8.0.0"

clgpu[0].CLBandwidth=7.47914e+10

clgpu[0].CLCompute=191.663

NumNativeGPUs=0

snifferEnd="2017-06-16_23:10:17"

C:\Program Files\Adobe\Adobe Photoshop CC 2017>

[Murray Groat]

Are these the history events (screenshots) that you need to see that happened before CS3 started crashing?

Also I have found the SNIFFER.exe file and I can open the Command Prompt ok, but I am useless on what you need me to do so far. I am not very puter clever. Sorry. Even if i double click the SNIFFER.exe, the Command Prompt pops up for a second flashing code then closes. No way to copy'n'paste it for you to see. Please help, I am a noob at this.

[Terri Stevens]

I think you should be looking at your hard disk. Photoshop cannot trigger crashes in low level system hardware-according to Adobe . Graphics cards can crash but that's generally a bug in the driver not Photoshop. IAStorDataMgrSvc is an Intel driver involved in controlling your hard disk(s) and should be stable. Are you using a RAID? I'm wondering if something is wrong there?

[Murray Groat]

Hi Terri,

As far as I know I do not have RAID on my computer. Your mention of it is the first I have heard of it. I did a START search for RAID. Nothing. Sorry, but thanks.

Best regards.

[JJMack]

https://forums.adobe.com/people/Murray+Groat  wrote

Are these the history events (screenshots) that you need to see that happened before CS3 started crashing?

Also I have found the SNIFFER.exe file and I can open the Command Prompt ok, but I am useless on what you need me to do so far. I am not very puter clever. Sorry. Even if i double click the SNIFFER.exe, the Command Prompt pops up for a second flashing code then closes. No way to copy'n'paste it for you to see. Please help, I am a noob at this.

Your only showing critical event on a single day  You need to look at all event that took place prior to your first failure to see what changed  What was update, remover, installed etc. They are not critical events.

To run the sniffer you need to open a command prompt and fun it from there,  You have to CD to Photoshop's  folder of enter the command path in quotes if you double click on it you may see a flash on you display you will not see sniffer's output. The command is

"C:\Program Files\Adobe\Adobe Photoshop CC 2017\sniffer"

[Murray Groat]

Hi JJMack,

As per what you said about PRIOR things...

- 'What was update, remover, installed etc. They are not critical events.',

do you want me to screenshot the 'problem details' info for 'each error' mentioned the day before my first CS3 error? Please bare with me, I am not a pc boffin. Sorry.

And here is the SNIFFER code you asked for via the Command Prompt:

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Murray>"C:\Program Files\Adobe\Adobe Photoshop CC 2017\sniffer"

Tester="Photoshop"

snifferStart="2017-06-17_17:08:37"

AIFCoreInitialized=1

AIFOGLInitialized=1

OGLContextCreated=1

NumGLGPUs=1

glgpu[0].GLVersion="2.1"

glgpu[0].IsIntegratedGLGPU=0

glgpu[0].GLMemoryMB=3803

glgpu[0].GLName="Intel(R) HD Graphics"

glgpu[0].GLVendor="Intel"

glgpu[0].GLVendorID=32902

glgpu[0].GLDriverVersion="8.15.10.2993"

glgpu[0].GLRectTextureSize=8192

glgpu[0].GLRenderer="Intel(R) HD Graphics"

glgpu[0].GLRendererID=70

glgpu[0].HasGLNPOTSupport=1

glgpu[0].GLDriver="igdumd64.dll,igd10umd64.dll,igdumdx32,igd10umd32"

glgpu[0].GLDriverDate="20130130000000.000000-000"

glgpu[0].CanCompileProgramGLSL=1

glgpu[0].GLFrameBufferOK=1

gputag.GL_SHADING_LANGUAGE_VERSION=35724

glgpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="1.20  - Intel Build 8.15.10.2

993"

gputag.GL_FRAGMENT_PROGRAM_ARB=34820

gputag.GL_MAX_PROGRAM_INSTRUCTIONS_ARB=34977

glgpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_

ARB]=[1447]

gputag.GL_MAX_TEXTURE_UNITS=34018

glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[8]

gputag.GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS=35661

glgpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[16]

gputag.GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS=35660

glgpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[16]

gputag.GL_MAX_TEXTURE_IMAGE_UNITS=34930

glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[16]

gputag.GL_MAX_DRAW_BUFFERS=34852

glgpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]

gputag.GL_MAX_VERTEX_UNIFORM_COMPONENTS=35658

glgpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[512]

gputag.GL_MAX_FRAGMENT_UNIFORM_COMPONENTS=35657

glgpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[1024]

gputag.GL_MAX_VARYING_FLOATS=35659

glgpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[41]

gputag.GL_MAX_VERTEX_ATTRIBS=34921

glgpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]

gputag.AIF::OGL::GL_ARB_VERTEX_PROGRAM=69

glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1

gputag.AIF::OGL::GL_ARB_FRAGMENT_PROGRAM=27

glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1

gputag.AIF::OGL::GL_ARB_VERTEX_SHADER=70

glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1

gputag.AIF::OGL::GL_ARB_FRAGMENT_SHADER=28

glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1

gputag.AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT=81

glgpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1

gputag.AIF::OGL::GL_ARB_TEXTURE_RECTANGLE=58

glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1

gputag.AIF::OGL::GL_ARB_TEXTURE_FLOAT=53

glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1

gputag.AIF::OGL::GL_ARB_OCCLUSION_QUERY=37

glgpu[0].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1

gputag.AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT=68

glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1

gputag.AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD=47

glgpu[0].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=0

NumNativeGPUs=0

snifferEnd="2017-06-17_17:08:37"

C:\Users\Murray>

[JJMack]

No you look at the events Your Display device driver is 4 year old you should be able to fine a newer diver to install the would be better for cc 2017.

glgpu[0].GLMemoryMB=3803

glgpu[0].GLName="Intel(R) HD Graphics"

glgpu[0].GLVendor="Intel"

glgpu[0].GLVendorID=32902

glgpu[0].GLDriverVersion="8.15.10.2993"

glgpu[0].GLRectTextureSize=8192

glgpu[0].GLRenderer="Intel(R) HD Graphics"

glgpu[0].GLRendererID=70

glgpu[0].HasGLNPOTSupport=1

glgpu[0].GLDriver="igdumd64.dll,igd10umd64.dll,igdumdx32,igd10umd32"

glgpu[0].GLDriverDate="20130130000000.000000-000"

[Murray Groat]

I opened DEVICE MANAGER...

then....

Searched, and...

So for whatever reason the driver is fine.

I tried to open Pshop CC 2017 and it is still errors as before.

Have I done this correctly? Sorry if this is doing your head in, as much as me.

[Terri Stevens]

No Murray, you need to visit the Intel website-that Windows dialog rarely finds new drivers. It helps if you know the exact chipset your graphics system uses, but Intel has a tool on their website that is supposed to analyse your computer and work out the drivers you need. The link is below.

Drivers & Software

[Murray Groat]

Thanks Terri,

Running the Intel Driver software now. It's taking it's time in a download queue.

[Murray Groat]

Hi Terri,

I got the driver download. Installed it. Deleted download files as stated in info. Restarted. A Command Prompt window popped up containing info that driver was installed. Windows opened slowly. Ran Photoshop CC 2017 and CS3. Still errors and not opening as before.

Btw here is my system info of my DISPLAY info. Hope it is of some help....

[JJMack]

Do not use Microsoft Windows Device manager to check for newer display driver for your Intel graphics HD model.  Find out the model HD Graphics that is in your PC and the go to Intel's web site and check what the latest device driver version they have for your your HD model for use with your Windows 7 system make sure you have their latest one installed,

[Murray Groat]

Hi JJMack,

I am running the Intel Driver software now, from the URL that Terri just linked me too.

It's taking it's time in a download queue.

[Murray Groat]

While I am waiting on the Intel Driver software/website to do it's thing, here are the prior installs the day before Pshop CS3 started crashing. I think this is what you requested...

Hope these help.

[Murray Groat]

Hi JJMack,

My CS3 opened ok a few days ago. I was happy for a few minutes.

My Wacom Driver had an error. My wacom software did not install properly so I re-installed my Wacom Driver from the WACOM website.

I restarted my pc, then opened my CS3. Sadly it has gone back to the initial ERROR message.

I am thinking of chucking in Photoshop painting/drawing. I am not a technical person with pc's. I am just an artist.

[JJMack]

I would think a program design as a drawing and Paint application from the ground up would be more appropriate for an artiest for they would have tools designed for creating works of art. Where and Image processor will have tools better suited for a darkroom. Though Photoshop brush engine is quite powerful and sypports pens.