We have a Win2K Server We get this error in the System event log stating that "The server was unable to allocate from the system paged pool because the pool was empty" - event ID 2020. Shortly after that, everyone looses their connection to the server, and a reboot is required to fix the problem. I can't find a fix anywhere we tried everything that we found on the internet and nothing works. If anyone had that problem and knows how to fix it please help. Matt
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Event ID 2020 Crashing a Server please help
- Thread starter mzysk
- Start date
Accordingly to Microsoft this is a "memory leaking", from a faulty app :
Is this machine connected to internet? Try to "kill" any suspect process in the TaskManager. Spyware, Malware?...
Is this machine connected to internet? Try to "kill" any suspect process in the TaskManager. Spyware, Malware?...
I have had this issue a couple of times with various clients.
The first time it was fixed by running a chkdsk on the machine - scandisk the drives and click ok to do them the next reboot.
The other time, we found a particular program(we traced it to a HP printer resolver) was hitting the server with a query whereby an error report was generated every minute in the end getting to the SRV error stage , where as you mentioned, a reboot is the best way to recover.
I suggest doing what Jonabrv mentions above - check your logs for any other errors which may be leading to the SRV errors. Check your Processes for any unknown processes or a process that is cosuming a lot of memory. It it is a legitimate program, check to see if there any patches/updates to it to fix this. If you have no idea what the process is (try using google for this) or identify a malware, remove it and try and figure out how it got there in the first place.
If in doubt, post your finding here and someone may be able to assist you.
Claudius (What certifications??)
The first time it was fixed by running a chkdsk on the machine - scandisk the drives and click ok to do them the next reboot.
The other time, we found a particular program(we traced it to a HP printer resolver) was hitting the server with a query whereby an error report was generated every minute in the end getting to the SRV error stage , where as you mentioned, a reboot is the best way to recover.
I suggest doing what Jonabrv mentions above - check your logs for any other errors which may be leading to the SRV errors. Check your Processes for any unknown processes or a process that is cosuming a lot of memory. It it is a legitimate program, check to see if there any patches/updates to it to fix this. If you have no idea what the process is (try using google for this) or identify a malware, remove it and try and figure out how it got there in the first place.
If in doubt, post your finding here and someone may be able to assist you.
Claudius (What certifications??)
- Thread starter
- #4
- Status
Similar threads
- Locked
- Question
