Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 711
  • Last Modified:

Possible memory leak

We believe that our SMS 2003 server has memory leak issue with a DELL Poweredge R710 server.  
The server is running Windows Server 2003 Standard Edition (32-bit) SP2, and has the minimum possible physical memory installed of 8GB, plus the usual Dell Broadcom Extreme network cards and teaming software

The server appeared to work fine for 8 weeks then has steadily degraded to the point where a reboot is required daily to recover the machine. At staged intervals the following has been done:
•      All KB articles have been applied to the system.
•      Dell advised that we update the BIOS to the latest version and change two settings for memory addressing and power saving by the processor, these were the C1E and C-states both of which were disabled, also memory power usage was changed to “maximum”.
•      We have recently added the following switches to the boot.ini /3GB /Userva=3030.

The server starts to fail with an event ID 2019 Srv – The server was unable to allocate from the system nonpaged pool because the pool was empty.

We then see an event ID 2021 Srv – The server was unable to allocate a work item 1 times in the last
60 seconds. The event ID 2019 is repeated 3 or 4 times.

We then get an event ID 333 Application Popup - An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, one of the files that contain the system’s image of the Registry. This error then repeats about every 6 seconds until the server stops responding.

We also see the ping response from the server stop and start several times before the server finally stops responding.
0
samymac
Asked:
samymac
  • 2
1 Solution
 
rxdeathCommented:
have you done a memtest86 run?  you can download it and burn it here maybe you have some unfriendly ram.

http://www.memtest86.com/
0
 
samymacAuthor Commented:
I've removed two of the DIMMS to bring the RAM back down to 4GB (as the x86 OS wont address more than this) and it seems to have resolved.
0
 
samymacAuthor Commented:
Possible faulty DIMM
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now