Share via

csrss.exe instances keep on increasing continuously which leads to increase in RAM consumption

Anonymous
2024-07-17T13:15:33+00:00

This is for Windows Server 2022 R2 Commercial,

csrss.exe instances keep on increasing continuously which leads to increase in RAM consumption ,

dont understand why this csrss.exe instances are keep on increasing?

At this point dwm.exe process exit occured.

Windows for business Windows Server Performance System performance

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-07-17T15:57:43+00:00

    Hello

    Thank you for posting in Microsoft Community forum.

    The issue with csrss.exe instances increasing continuously, leading to higher RAM consumption, could be related to several factors. One potential cause could be insufficient pagefile size or free space on the boot partition, which can prevent proper memory dumps and lead to system instability. Another possibility is a memory leak in kernel mode drivers, which can be identified using the Poolmon utility to monitor nonpaged and paged pool usage. It's also important to ensure that there are no binary mismatches or issues with SCSI drivers or firmware that could prevent memory dumps from being written.

    Regarding the dwm.exe process exit, it could be related to system hangs that are not explained by resource consumption but rather by threads waiting in specific states. To further investigate these issues, you may want to use tools like Poolmon to monitor memory usage and check for leaking trends, or Xperf for detailed analysis of process lifetime and image virtual address ranges in process memory.

    PoolMon - Windows drivers | Microsoft Learn

    Windows Performance Recorder | Microsoft Learn

    Best Regards,

    Wesley Li

    0 comments