How To Fix “Not Enough Memory Resources Are Available To Process This Command”

The ‘memory’ on your PC is made up of HDD and RAM, which are types of storage areas. If the RAM is low or the program you are trying to run is using too much of it, you might get an error, which then needs to be fixed with registry editing, system cleanup or a software update.

Not Enough Memory Resources Are Available To Process This Command

According to Microsoft, you might get this error if you don’t have the IRPStackSize registry entry on the server set high enough. This is why tweaking the registry can be one of the easiest fixes for this issue.

You should always be careful when changing registry values because if you incorrectly change something, you might cause a serious system problem.

Remember to back up the registry before making any changes so you can always put it back the way it was if something does go wrong.

Not Enough Memory Resources to Process this Command

5 Ways To Fix “Not Enough Memory Resources Are Available To Process This Command”

Let’s take a look at 5 easy ways to get rid of “Not Enough Memory Resources Are Available To Process This Command” problem.

Fix #1: Change the IRPStackSize Value

  1. Press the Windows key and R together to open the Run dialog
  2. Type this then press OK: regedit
  3. Find and choose this subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
  4. If the IRPStackSize entry isn’t available do the following:
  5. Click Edit then New then DWORD Value
  6. Type IRPStackSize and press Enter
  7. Press Edit then Modify
  8. Type a bigger number in the Data Value box and click OK
  9. The values range from 0x1 to 0xC and refer to numbers 1 through 12

If you still get the same problem, repeat these steps making the IRPStackSize larger again.

Fix #2: Change the SharedSection Values

  1. Press the Windows key and R together to open the Run dialog
  2. Type this then press OK: regedit
  3. Find and choose this subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems
  4. Click on the Windows value
  5. Go to Edit and click on String
  6. Make the SharedSection parameter higher
  7. The format will read like this on Windows NT: SharedSection=xxxx,yyyy
  8. Add either 256 or 512 after the yyyy figure
  9. The format will read like this on Windows 2000m XP or Server 2003: SharedSection=xxxx,yyyy,zzzz
  10. Increase the yyyy value to 12288 and the zzzz value to 1024 if you’re using a 32-bit system
  11. Increase the yyyy value to 20480 and the zzzz value to 1024 if you’re using a 64-bit system

Fix #3: Block UI App Forks

If an app runs out of storage you can restart the app and make the error go away. However this is only a temporary fix.

If you want to permanently fix the problem, you need to configure the xyzService.exe which is running out of memory to avoid any UI application forks in session 0.

If you are running, for example, xyzService.exe in session 0 and using domain account DOMAINxyzServiceAccount, this can result in a UI fork with the UI app not exiting correctly. You would need to configure the xyzService.exe not to fork UI application in session 0.

Fix #4: Upgrade Microsoft SQL Server

It is important to ensure you have installed the newest version of Microsoft SQL Server so your PC can have the latest patches and improvements.

Go to Microsoft’s SQL Server update page to check whether your version is up to date.

Fix #5: Erase Temporary Folder Contents

By default this is a hidden folder because there are Windows configuration files in there.

It is a good idea to back up the temporary files folder before changing anything, just in case something goes wrong and you need to put it back as it was.

This folder can be found in the Windows partition. Check ‘Hidden items’ in the view tab so you can see it.

Alternatively you can access it this way:

  1. Press the Windows key and R
  2. Type this then press Enter: %temp%
  3. Now press Ctrl and A to select all files
  4. Click Delete
  5. Go to your C: drive or whichever Windows is installed on
  6. Find the temp folder
  7. Delete all the files in there as well
  8. Restart your PC and see whether the problem is fixed