I'm running photoshop CS5 under Windows 7 SP1 with an nVidia GT9500 video card. I have 4Gb of RAM of which 1GB is reserved for something other than the system. With that as a background, when I process files on PS, I am constantly getting a windows message that "Photoshop has stopped working" and then I have to close it and start again. I have looked on the Adobe website for answers but there are none. The Windows event viewer tells me that PS is experiencing errors 1000 and 1001. This is very frustrating and makes processing files tedious and time consuming. (I have to save after every processing step lest I lose my latest edits.)
HELP! Does anyone have any insight into this problem.
In the Event Viewer, select the entry, right click and then select from 'Properties'. There should be some text there that gives some info about the error. Also, in the 'properties' box, there should be a link that will take you to MS Help and Support. The answer may be there.
Also, if you could let know what the Event Viewer says about errors 1000 and 1001, that might help us track this down.
If you have only 1GB allocated to non-system files, you could be running out of resources (RAM). Try allocating more RAM for use by programs, or allocate more memory for use by Photo Shop in the PS Preferences.
Also, the photoshop settings for performance.
Available RAM: 1631 Mb
Ideal Range: 897-1174 Mb
Let Photoshop Use: 1158 Mb (71%)
As for the memory allocation, the 1 Gb that is not availanle to the system, I believe is reserved for the video card, even though the card has it's own 1 Gb of RAM. This means that the system has 3 Gb available. As I understand, Windows 7 only has the capacity to address 3 Gb while reserving 1 Gb for hardware.
Hooray!! After uninstalling Capture One, the problem seems to be solved. John, thanks for the tip. I never would have associated ImgcoreDLL.dll with CaptureOne. I wonder why there is a conflict and if other people are experiencing similar problems.
I am glad you got it sorted out. They call these kinds of issues 'dll hell'.
--P
Posted by Paul DeCesare on March 24, 2011 at 2:09 PM
That's the second time in two weeks that I saw that happen to someone with Capture One installed. I did have v5 Standard installed but I never use it, I just like ACR, so I've also blown Capture One away.
Posted by Bill Chambers on March 24, 2011 at 3:10 PM
Hmmm, that's strange. I've used Capture One for years through CS, CS2,3, & 4 and have naver had a problem, But I haven't upgraded to to CS5 yet though.
Nick, I just read your post. CS5 likes a powerful processor as much as it does Ram. From reading your post I take it you are running a 32 bit OSystem. PS can only use the 3 out of 4 gigs of ram you have installed with that system. 64 bit is the way to go and then add all the Ram you like. As Bill mentioned, Capture One is not the culprit here. CS5 needs resources. Disabling Capture One simply freed some of them up.
I believe the 3GB limit on RAM is imposed by Windows. Also, I believe, and correct me if I'm wrong, that 32 bit PS can only access 2GB, the remaining being used by the OS. So, it's quite likely Nick's issue is memory related.
I am now using 64-bit Windows 7 and 64-bit PSCS5 with 16GB of RAM with a quad core CPU, and my system has no trouble at all with 2.5+GB TIF files. So, 64-bit is the way to go, if one can do it.
Preston - 32-bit PS can use up to 4GB of RAM (just by the math -- 2^32 = ~4G), but you're correct that there are other limits within the OS that keep it from actually using that much. I believe most people on 32 bit Windows can use between 2.5 and 3 GB. (There are some tricks to play there, but by FAR the better solution is to go to a 64-bit OS.)
Actually you can increase the amount of ram any OS uses, whether 32 bit or 64bit. In this way PS can use 3 gigs, although its not always a prudent thing to do.
Was one of the CS5 beta testers, and I didn't want to run the tests on my big machine, so I used another home built. It already had 8 gigs of ram for it's 64bit system, so I installed a 32 bit OS in dual boot and then ran CS5 betas on it. It ran okay, although not fast. But when it came to using Content Aware it took forever to complete a task, and often refused to complete.
Btw, another little item CS5 likes is a powerful video card.
Anyway here's a link to Adobe on mem and such http://kb2.adobe.com/cps/404/kb404439.html
Discussion
14 repliesHELP! Does anyone have any insight into this problem.
In the Event Viewer, select the entry, right click and then select from 'Properties'. There should be some text there that gives some info about the error. Also, in the 'properties' box, there should be a link that will take you to MS Help and Support. The answer may be there.
Also, if you could let know what the Event Viewer says about errors 1000 and 1001, that might help us track this down.
If you have only 1GB allocated to non-system files, you could be running out of resources (RAM). Try allocating more RAM for use by programs, or allocate more memory for use by Photo Shop in the PS Preferences.
--P
Following is the text from the event properties for error 1000.
Log Name: Application
Source: Application Error
Date: 3/22/2011 1:22:49 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Mach4
Description:
Faulting application name: Photoshop.exe, version: 12.0.3.0, time stamp: 0x4d0359bf
Faulting module name: ImgCoreDll.dll_unloaded, version: 0.0.0.0, time stamp: 0x4bbad15b
Exception code: 0xc0000005
Fault offset: 0x4c938591
Faulting process id: 0x14f4
Faulting application start time: 0x01cbe8cd94787d06
Faulting application path: C:\Program Files\Adobe\Adobe Photoshop CS5\Photoshop.exe
Faulting module path: ImgCoreDll.dll
Report Id: 27760532-54c2-11e0-93c5-001111e1c4ef
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-03-22T20:22:49.000000000Z" />
<EventRecordID>19957</EventRecordID>
<Channel>Application</Channel>
<Computer>Mach4</Computer>
<Security />
</System>
<EventData>
<Data>Photoshop.exe</Data>
<Data>12.0.3.0</Data>
<Data>4d0359bf</Data>
<Data>ImgCoreDll.dll_unloaded</Data>
<Data>0.0.0.0</Data>
<Data>4bbad15b</Data>
<Data>c0000005</Data>
<Data>4c938591</Data>
<Data>14f4</Data>
<Data>01cbe8cd94787d06</Data>
<Data>C:\Program Files\Adobe\Adobe Photoshop CS5\Photoshop.exe</Data>
<Data>ImgCoreDll.dll</Data>
<Data>27760532-54c2-11e0-93c5-001111e1c4ef</Data>
</EventData>
</Event>
Also, the photoshop settings for performance.
Available RAM: 1631 Mb
Ideal Range: 897-1174 Mb
Let Photoshop Use: 1158 Mb (71%)
As for the memory allocation, the 1 Gb that is not availanle to the system, I believe is reserved for the video card, even though the card has it's own 1 Gb of RAM. This means that the system has 3 Gb available. As I understand, Windows 7 only has the capacity to address 3 Gb while reserving 1 Gb for hardware.
Thanks for your help.
I am glad you got it sorted out. They call these kinds of issues 'dll hell'.
--P
Anyway, I'm glad you have fixed your problem!
I believe the 3GB limit on RAM is imposed by Windows. Also, I believe, and correct me if I'm wrong, that 32 bit PS can only access 2GB, the remaining being used by the OS. So, it's quite likely Nick's issue is memory related.
I am now using 64-bit Windows 7 and 64-bit PSCS5 with 16GB of RAM with a quad core CPU, and my system has no trouble at all with 2.5+GB TIF files. So, 64-bit is the way to go, if one can do it.
--P
--P
Was one of the CS5 beta testers, and I didn't want to run the tests on my big machine, so I used another home built. It already had 8 gigs of ram for it's 64bit system, so I installed a 32 bit OS in dual boot and then ran CS5 betas on it. It ran okay, although not fast. But when it came to using Content Aware it took forever to complete a task, and often refused to complete.
Btw, another little item CS5 likes is a powerful video card.
Anyway here's a link to Adobe on mem and such http://kb2.adobe.com/cps/404/kb404439.html