"Not enough memory (RAM)" error message

  • 1
  • Problem
  • Updated 2 months ago
Recently (in the past week or so) something has gone wrong with editing in Elements 14. I can open image files but many of the editing tools are no longer usable. I get the error message "Could not complete your request because there is not enough memory (RAM). I tried uninstalling and reinstalling the program from disk. Also did the PSE 14 update today as offered. Didn't help. I can't even exit the program the normal way. I have to open Task Manager and use "End Task." However, I still have PS Elements 8 and it works fine so I can't imagine why PSE 14 is acting up like this.
Photo of Jerry Berg

Jerry Berg

  • 7 Posts
  • 0 Reply Likes

Posted 2 months ago

  • 1
Photo of Michel BRETECHER

Michel BRETECHER, Champion

  • 1038 Posts
  • 219 Reply Likes
Photo of Steve Lehman

Steve Lehman

  • 592 Posts
  • 73 Reply Likes
Jerry, 

You can also do a SFC reset in Windows-10 in the Windows Power-Shell (if you haven't done this) to get Windows 10 to work nice with your application.  Tell me when you're ready for that.   It's just a command prompt in a DOS window.   Are you familiar with that already?   
Photo of Jerry Berg

Jerry Berg

  • 7 Posts
  • 0 Reply Likes
No Steve, afraid not. I tried opening Windows Power Shell but have never done anything there. Any guidance on it would be much appreciated.  Jerry
(Edited)
Photo of Steve Lehman

Steve Lehman

  • 592 Posts
  • 73 Reply Likes
Jerry,   I assume you have Windows 10?   
Photo of Steve Lehman

Steve Lehman

  • 592 Posts
  • 73 Reply Likes
Okay Jerry, let's reset a lot of stuff.   

I will do the reset in the Windows Power Shell, but first I want to go through a couple of routines that also reset the application.

We may need to reset the application (for PSE14).  In that case, in your PSE application, you can open the editor, then open any photo or image, and doing so, a ? (question mark) should appear at the bottom-right of the editing space.  Next to that will be a down-arrow menu.  Open the menu and click on Reset All.  That will reset the entire program, but if the question mark or the down-menu is not there, then there may be a more serious problem in the application.  There are other resets to try before going into a technical solution.    

If that does not work, let's reset the application in Windows 10:  Go to SettingsAppsApps & Features, and on the tight side list of programs, find the program, highlight it, then see if there is a blue hyper-link below its title.  If so, click on it, then on the next page will be a reset button on the left.  Click it and that application might just reset on its own. 

If the link is not there, we can go to the SFC reset.   For that, you will need to open the Windows Power Shell (in your program list).  In its DOS window, there will be a cursor blinking, and at the end of that blinking cursor, type scannow (without the underline) and press enter.  It'll work for a few minutes (or up to 15 minutes) then it will stop.  When it does stop, close the DOS window and reboot your computer.  When fully rebooted, try your program.  Sometimes this works, but most of the time if Windows doesn't find a problem with its applications, it stays the same.   

If none of these work, then you might need to look at sectors on the drive or RAM.   If an application suddenly disappears from the screen, it may indicate a serious hardware problem.   Have you ever had to stop your computer using the off/on button?  (power shut off)  Doing so can have an effect on the hardware.   Taking it to a technician might be on your agenda.   Find someone with A-1 certification or a software engineer with at least 7 certifications in hardware and software, like me,  although I don't have a shop for this type of test.   

Steve Lehman, MCSE (a highly certified software engineer from Microsoft)   
Photo of Jerry Berg

Jerry Berg

  • 7 Posts
  • 0 Reply Likes
Steve, I tried those suggestions. Here are the results:
"in your PSE application, you can open the editor, then open any photo or image, and doing so, a ? (question mark) should appear at the bottom-right of the editing space"
Nope, no question mark appeared.
"on the tight side list of programs, find the program, highlight it, then see if there is a blue hyper-link below its title."
Again, negative.
"open the Windows Power Shell (in your program list).  In its DOS window, there will be a cursor blinking, and at the end of that blinking cursor, type scannow (without the underline) and press enter.  It'll work for a few minutes (or up to 15 minutes) then it will stop."
No, the response was "The term 'scannow' is not recognized ..." etc.

At which point I gave up. I loaded the PSE 14 onto an older computer (pre Windows 10) and it works fine there. Not the best solution to the problem and overall I find this disappointing. I'm not clear about one thing. Is Adobe going to issue an update or something as a workaround? If not, this seems to be another example of planned obsolescence as a company policy. 
Jerry
Photo of Steve Lehman

Steve Lehman

  • 592 Posts
  • 73 Reply Likes
The scannow should be recognized if you have Windows 10.   You never told anybody which Windows platform you have.  Do you have Windows 10?   (Windows 7 and 8 had Windows Power Shell)   For everything else, I did say the things mentioned may not appear.  This was a test to eliminate the possibility whether it's a software problem and to determine if it's RAM or another hardware problem.   I think it is. Whether it's your RAM or main drive, take to your tech.  Your error message is about RAM memory.  If you think it's still about Software, then it's your Windows program which distributes memory.   For your last question, whether we  will know the future in PSE, this is a forum with people like you who have more experience with Adobe products.  We are not Adobe employees.  I am a Windows tech but I don't have connections to Adobe technicians.  None of us will know whether Adobe will make changes, or what changes or when, or whatever might happen.   It's easy to assume this forum has Adobe technicians.   None of us can promise an Adobe technician.  Also your last question is a developer question which makes software.  Even at Microsoft I was a test engineer, in development.   I could never make predictions of what will happen with the next build or with a re-Windows issue.   
Photo of Jerry Berg

Jerry Berg

  • 7 Posts
  • 0 Reply Likes
Yes, I do have Windows 10, and Photoshop Elements 14 worked fine until about a week or two ago. Around that time there was a major update to Win 10, so it's hard to avoid a suspicion that something in that update messed with the Photoshop functionality. 
Photo of Steve Lehman

Steve Lehman

  • 592 Posts
  • 73 Reply Likes
Jerry,

I have almost all of PSE versions including 14.  I have used PSE-14 for 4-5 years without a single error and I have received Windows 10 updates and some of the same ones, twice or 3-4 times and nothing has happened to my Adobe products.  Like I said, when an error comes up about the RAM it's usually a hardware problem.   Error messes do tell the truth about something.   

Back in college when studying for my MCSE engineering certifications (7 of them) my instructor messed up our classroom PC's sometimes to keep us on our toes.  We had just 2 minutes to resolve the problem and one of them was RAM chips which were ajar.  There is only one screw which holds them in at the chassis.  In newer computers, they don't have a screw they just have a clip.  I will bet a dollar that's the real problem.   That or it's a dead sector on your main drive.  How many times have you resolved problems by simply turning off the computer by holding the on-off button for a hard-boot-off?   That usually kills the drive somewhat.  Like I mentioned before, take it to a tech center and have them check out your PC.   I am happy you got it running on a Win-7 machine.   

Steve Lehman, mcse   
Photo of Steve Lehman

Steve Lehman

  • 592 Posts
  • 73 Reply Likes
Jerry,   

BTW, "scannow" in that DOS windows works in Windows 10.  It would have been recognized.  What it does is fixes the loss ends in the REG-edit whenever an update has knocked it around a bit.  I was doing your Windows 10 a favor.   Keep it in mind.    
Photo of Jerry Berg

Jerry Berg

  • 7 Posts
  • 0 Reply Likes
Steve - I tried again and was able to get scannow to run. I followed the instructions provided in Windows Central, including a couple of small but apparently important syntax details. Anyway, it ran the scan and ended with this: "Windows Resource Protection did not find any integrity violations." So ... appears the PSE issue is still a mystery. Guess I could go further down this road but instead I will follow the advice of WC Fields: "Try, try again but then don't be a damn fool. Give up."
But thanks for your efforts.   Jerry
Photo of Steve Lehman

Steve Lehman

  • 592 Posts
  • 73 Reply Likes
WC Fields is amusing but I have my own quote which I gave my class as I taught technology at Microsoft which was; "never look back, go forward, keep trying."  Everyone heard about it in the company.   That led to a tag-line for Microsoft's advertising in 90's, "keep current".   
Photo of Steve Lehman

Steve Lehman

  • 592 Posts
  • 73 Reply Likes
One more thing Jerry:   

Whenever it gives a "result" of anything it resets, it says one thing but when its reboots, it says the opposite sometimes.  For example:   When we use the "restore" feature in Windows 10 it only lists a few days prior to select to go back.   Then it works its process then says it failed, but it does go back anyway to what we select.   So on your "scannow" results, it's not necessarily a reset program for your particular application but it does a reset between Windows and its applications in the REG-edit files, and works especially for Windows updates.   So, your results may have seemed to fail (so it says) but sometimes it changes something that will reveal itself later.   One thing is for sure, I'm still confused whether you have Windows 7 or 10, or both.   
Photo of Jerry Berg

Jerry Berg

  • 7 Posts
  • 0 Reply Likes
10 on the primary machine, 7 on the older backup.