- Unable to allocate from system paged pool
- Posted by A Lake on October 11th, 2005
I have 3 Windows 2003 Servers SP1 running as DCs. Recently all 3 have been
unable to connect users shares (theres about 300-500 on each) due to the
error 'Unable to allocate from the system paged pool because the pool was
empty' Event ID 2020. A reboot sorts the problem but is obviously far from
ideal!
I've checked out MS Q312362 and implemented that but I'm worried as to why
all three suddenly fail within days of each other after months of trouble
free operation - the only thing that has changed is a) the users data and b)
Sophos Antivirus updates daily.
Is there any methods I can track down what caused the system to run out of
memory?
Similar Posts
- Windows XP & non-paged pool (Drivers) by v_mirgorodsky@yahoo.com
- Non-paged pool is exhausted (Drivers) by Boris
- server is unable to allocate memory from the system paged pool (Windows Server) by moses
- Server is unable to allocate memory from the system paged pool (Windows Server) by MRORIE
- The server was unable to allocate from the system paged pool because the pool wa (Windows NT) by Muhammad Abbas

