In most cases we will capture what is known as a It may also be necessary to capture a complete memory dump of the server while it is in the problem state.
If you are prompted for a password or for UAC consent, follow the prompts In the Start Search box and then click Perfmon in the programs list.
To capture a Performance Monitor log on Windows Vista and later operating systems, follow the steps below: Please use the table below to set the capture interval.
The length of time it takes the server to go from a normal state, to the problem state will determine the Perfmon capture interval. Performance Monitor logs that include the timeframe when the memory issue occurred. Additional data required may include the following: With the General, Internet and Networking, Business Networks and Server Components diagnostics, or a Performance-oriented MSDT manifest must be done. Is an application crashing or hanging when using a large amount of memory?Īre event log entries being logged that indicate some sort of memory issue?īoth 20 event log errors with a source of SRV are relatively common, and indicate a depletion of non-paged or paged pool memory respectively. The questions to ask when suspecting a problem with memory management may include:Īre you getting errors stating you are out of a virtual memory or another memory resource? A 64-bit operating system has a much higher limit on virtual memory structures, with more information available Our second post on Troubleshooting Memory Issues Our first post on Troubleshooting Memory Issues In our post on Windows Server 2008 Kernel Addressing More information on virtual memory concepts can be found The concept of virtual memory is unrelated to the amount of physical memory installed however the amount of physical memory can have an effect on certain memory structures. The amount of virtual memory that is actually being used will typically be much smaller than the amount that is technically available this is why virtual memory can be larger than physical memory. This allows much more headroom for load and makes most memory issues much less likely. The primary difference between Windows Vista or Windows Server 2008 and previous Windows versions is that many of the primary kernel resources This memory space is by default divided into a 2 gigabyte piece for the kernel and a 2 gigabyte piece for each individual process running on the machine. A 32-bit operating system can address up to 32-bits of memory, which works out to 4 gigabytes of virtual memory (4,294,967,296 bytes). That Windows can use for applications or system use. Is the term used to describe the amount of memory The pagefile acts like RAM, and applications see it as RAM, but it will typically be slower than physical RAM due to disk throughput and latency. A pagefile is a file on a system hard disk that is configured and treated as though it were physical RAM. Is considered the total of physical RAM and the pagefile or pagefiles configured on the system. Memory management is the term used to describe how Windows handles the manipulation and allocation of both virtual and physical memory resources. MEMORY MANAGEMENT (GENERAL: WINDOWS VISTA AND LATER) First published on TECHNET on Apr 10, 2009