SharePoint 2010 100% cpu w3wp.exe after windows server update desember 2013

Question

Hi
Using SharePoint 2010 with 2 frontend webservers and 1 appserver:
Our ApplicationPool for our portal workerprocess has for a second time gone up to and stuck on 99% CPU on one of our 2 frontend webservers. 
What happens is that this server falls out of the NLB cluster, and the only way to get it back is to log onto the server and through task manager stop the worker process (w3wp). We checked to see what the applicationPool was, and it was for the portal site.
The first time it happened was just after the installation of the following windows server patches: Actuall on the very same day. The patches were installed on the early morning of the 18th december 2013.
The event id for the spesific events show:
18.12.2013 14:45 Event id 7011, Service Control manager:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the VMTools service.
and
09.01.2014 08:36 Event id 7011 Service Control Manager
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
In adition there are a lot of random:
Event id 105, Warning: NLB:
NLB cluster []: Timer starvation has been detected. This might be due to a denial of service attack or a very high server load. During this period, some connections might fail. If this problem recurs frequently, analyze the threat and take appropriate measures
and/or add more servers to the cluster. An informational event log entry will be logged when the attack has subsided.
I'm suspecting that this was caused because of one of the updates, allthough the "Event id 105", Warning: NLB did exist prior to the patch updates, but would only appear once every 2-3 weeks. After December 18 2013 these "Event id 105"
messages appear about 6-11 times a day!
any one seen something like it?
I see microsoft: http://support.microsoft.com/kb/922918/eng
Event 7011, has a workaround to increase the default time-out value for the service to for example 60 seconds instead of 30. Would this be a good solution?
brgs
Bjorn

Answer 1

Hi ,
For the temp solution u can do app pool recycle or iisreset when the cpu usage goes 100%.
And check which worker processor is consuming that much memory and checked related to that web application.
Please remember to click "Mark As Answer" if a post solves your problem or "Vote As Helpful" if it was useful. It'll help other users who are visiting your thread for the similar problem.