JSI Tip 0052 - Out of Memory or user32.dll failure.

Jerold Schulman

January 28, 1997

1 Min Read
ITPro Today logo in a gray background | ITPro Today

If you get user32.dll failure when starting a service or out of memory errors when you have available memory, try this:

HKEY_LOCAL_MACHINESystemCurrentControlSetControlSession ManagerSubSystemsWindows

Scan for SharedSection=xxxx, yyyy where xxxx defines the maximum size of the system-wide heap (in kilobytes) and yyyy defines the size of the per desktop heap. Add ",zzzz" immediately after yyyy where zzzz is the size of the hidden desktop heap created by non-interactive processes. Setting this to 512 will often solve your problem. When you're done, this string will look like SharedSection=xxxx, yyyy, zzz.

If you still get out of memory errors, increase yyyy by 256 until the application runs.

You might also delete RegistrySizeLimit from HKEY_LOCAL_MACHINESystemCurrentControlSetControl and setting PagePoolSize to 0 at
HKEY_LOCAL_MACHINESystemCurrentControlSetControlSession ManagerMemory Management.
You will need to reboot.

NOTE: SharedSection=1024,3072,512 is the Windows XP default.



Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.

You May Also Like