Not enough storage is available to process this command
If you’re getting the “ERROR_NOT_ENOUGH_MEMORY” error code with the “Not enough storage is available to process this command” description, follow the troubleshooting steps listed in this article to fix it.
ERROR_NOT_ENOUGH_MEMORY: What you need to know about it
This error codes affects Windows servers, causing systems to crash with the message “Not enough storage is available to process this command” in the error log.
Microsoft explains that this error may occur if the IRPStackSize registry entry on the server is set too low. As a result, the best and simplest way to solve this problem is to tweak the registry in order to allocate a larger IRPStackSize value.
Fix: “Not enough storage to process this command”
The following steps involve modifying the registry. However, severe issues might occur if the registry values are changed incorrectly. Don’t forget to back up the registry before you modify it. In this manner, you can always restore it in case anything goes wrong.
Solution 1 — Modify the IRPStackSize value
1. Go to Start > Run > type regedit > hit OK.
2. Locate and then select the following registry subkey:
- Click Edit > New > click DWORD Value.
- Type IRPStackSize > hit ENTER. Type IRPStackSize exactly as it appears. Don’t forget that the value name is case sensitive.
4. Click IRPStackSize > Edit > Modify.
5. In the Data Value box, type a larger value > click OK. The values may range from 0x1 to 0xC, and are equivalent to 1 to 12 in decimal notation.
If the problem persists after you’ve modified the value, repeat the same steps and increase the value of IRPStackSize again.
Solution 2 — Modify the SharedSection values
1. Open the Registry Editor > locate the following subkey
2. Select the Windows value > go to the Edit menu > choose String.
- Windows NT uses the following format: SharedSection=xxxx,yyyy
Add “,256” or “,512” after the yyyy number.
- Windows 2000, Windows XP, and Windows Server 2003 use the following format: SharedSection=xxxx,yyyy,zzzz
For 32-bit operating systems, increase the yyyy value to “12288”; increase the zzzz value to “1024”.
For 64-bit operating systems, increase the yyyy value to “20480”; increase the zzzz value to “1024”.
Solution 3 — Block UI app forks
A Windows user recently described an interesting troubleshooting method to fix the “Not enough storage is available to process this command” error code.
If an important app runs out of storage, you can restart it. The error will temporarily disappear. However, the desktop heap for the window station service will encounter memory issues again. To permanently fix this issue, configure the xyzService.exe that runs out of memory to avoid UI application forks in session 0. Here’s how use BlueCode described the resolution adopted for this particular situation:
After talked with customer, I figured out that the whole story here is that, customer ran xyzService.exe with domain account DOMAINxyzServiceAccount in session 0, and xyzService.exe forks child processes xyzUIApplication.exe somehow periodically. Unfortunately the UI application did not exit as usually. This operation leaked the desktop heap in this specific window station Service-0x6-453186fc$ gradually until the depletion was detected by xyzService.exe while running queries.
To solve this issue, we simple configured the xyzService.exe and made it not forks UI application in session 0.
Solution 4 — Upgrade the Microsoft SQL Server
Install the latest Microsoft SQL Server updates to make sure that your system benefits from the latest improvements and patches. For more information about the available updates, go to the Update Center for Microsoft SQL Server.
As always, if you’ve come across other solutions to fix the ‘Not enough storage is available to process this command’ error, you can list the troubleshooting steps in the comment section below.
RELATED STORIES YOU NEED TO CHECK OUT:
- Fix: TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE error on Windows 10
- Fix: The Server Stumbled “0x80072F05” Error in Windows 10
Microsoft is all set to launch its next big update, Windows 10 version 1809 in October. While that should be a nice piece of news […]
The Windows 10 October 2018 Update (otherwise 18H2) rollout might now be two to three weeks away. For the last few months, new build previews […]