High cpu utilization in windows server 2008

Suddenly last week the server will become very slow to respond to client requests. There are no processes in particular that are causing the issue as far as I can gather from monitoring things in task manager and process explorer. I have tried ending all non-critical services and processes. After doing this, what generally happens is that for a minute it will seem like things are improving a bit and then it becomes quickly apparent that everything is still bogged down.

If I restart the server it will take a long time to finally restart and when things come back up the server is still heavily bogged down with high CPU usage.

I will restart the server a handful of times before finally giving up and fully shutting it down. The server will run fine for several days or a week or two and then it begins acting up again.

My question is two-fold. Firstly, are there any thoughts on what can be causing the slowness or what else I can look into? I should mention I also have tried disabling non-critical services and apps including our antivirus and Acronis Backup. I have also checked hardware logs-no issues to report. I have reset the WMI Repository. Second question is regarding shutdown vs restart; because a full shutdown seems to fix the issue every time, does this indicate a hardware issue?

Any thoughts or direction is very much appreciated! I asked this question on serverfault. Just looking for some insight from people with more experience. Rincoln This person is a verified professional. Verify your account to enable IT peers to see that you are a professional.

Mandamus May 4, at UTC. Thanks for your thoughts, I appreciate any bit of information. I know that this was common in XP, server , etc. But now I only seem to find posts for Vista. What is the reason? Once you know that much, edit it in to the question and we might be able to help. Since you're running Server and if you don't want to install software to figure out what's causing this and really, process explorer is very good , you can now do this from Task Manager.

The process is to With SVCHost a single instance may be associated with multiple services. As it happens, ProcessExplorer also can't distinguish between them. This is new with Server , and is a very nice addition. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:. If you do not see your language, it is because a hotfix is not available for that language. For more information about how to obtain a Windows Server R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:.

To have us create the registry value for you, go to the " Fix it for me " section. If you prefer to create the registry value yourself, go to the " Let me fix it myself " section. To create the registry value automatically, click the Fix it button or link. Then click Run in the File Download dialog box, and follow the steps in the Fix it wizard. Install the hotfix in the "Hotfix download available" section at the top of this Knowledge Base article before you run this Fix it solution. The MaxEndpointCountMult registry value is a multiplication factor that applies to the default scavenge value of 15, You can set the MaxEndpointCountMult registry value from 1 to 50, The recommended value is This wizard may be in English only.

I suppose the next step would be to clear Windows update history. And select OK. To delete the file, copy the following command in the command prompt: g. Try the patch, OP. It should resolve it, but I haven't tried it yet. Got the same issues with my servers Updates are from a WSUS too. I hope this was a one time bug from Microsoft.

Really annoying. Yep same issue for me, opened case with MS today. Has to be a bad patch. Keep us updated with it. Spent some time on phone with MS and they don't know what the issue is yet. Hi Guys, Any updates on this.

This was my big issue, it took all the priority from e. This topic has been locked by an administrator and is no longer open for commenting.

Read these next