Windows Server 2003 SP2: 48MB of PagedPool? What happened?

This post discuss an issue revolves around the amount of maximum PagedPool memory available on the server following the Windows Server 2003 Service Pack 2 install and the subsequent reboot.  In the cases we’ve seen, the systems have been generating the infamous Event ID 333. As you can see, the error messages clearly point to some sort […]

Share online:

This post discuss an issue revolves around the amount of maximum PagedPool memory available on the server following the Windows Server 2003 Service Pack 2 install and the subsequent reboot.  In the cases we’ve seen, the systems have been generating the infamous Event ID 333. As you can see, the error messages clearly point to some sort of resource issue.  However, since no Event 2020 (which indicates a depletion of PagedPool memory) has been generated, nothing immediately indicates that we have a PagedPool issue.

Full Article

About The Author

Deepak Gupta is a IT & Web Consultant. He is the founder and CEO of diTii.com & DIT Technologies, where he's engaged in providing Technology Consultancy, Design and Development of Desktop, Web and Mobile applications using various tools and softwares. Sign-up for the Email for daily updates. Google+ Profile.