J
jason.hill
Guest
Hi,
We installed the critical update KB958644 on a Windows Server 2008
machine 2 days ago and have experienced a massive increase in CPU
utilisation, apparently for the System process. Our performance
monitor reports typically showed the web server running in the 5-15%
CPU utilisation range for the whole day even under fairly heavy load.
For the last 2 days, the CPU graph now looks like an earthquake has
hit and we have had to reboot the server both days to reset the CPU to
normal.
Today, the graph was showing 90%+ CPU utilisation and we were not able
to RDP to the box and all web sites were non-responsive so had to get
the ISP to do a hard reboot. The graph showed the server in this 90%+
CPU usage state for several hours before we were made aware of the
problem so it was not just a temporary problem.
Has anyone else had problems with this security update? If we have
this problem again tomorrow, then I think we will have to uninstall
the update and ensure we are as secure as possible with the
workarounds in the technet article.
Thanks,
Jason
We installed the critical update KB958644 on a Windows Server 2008
machine 2 days ago and have experienced a massive increase in CPU
utilisation, apparently for the System process. Our performance
monitor reports typically showed the web server running in the 5-15%
CPU utilisation range for the whole day even under fairly heavy load.
For the last 2 days, the CPU graph now looks like an earthquake has
hit and we have had to reboot the server both days to reset the CPU to
normal.
Today, the graph was showing 90%+ CPU utilisation and we were not able
to RDP to the box and all web sites were non-responsive so had to get
the ISP to do a hard reboot. The graph showed the server in this 90%+
CPU usage state for several hours before we were made aware of the
problem so it was not just a temporary problem.
Has anyone else had problems with this security update? If we have
this problem again tomorrow, then I think we will have to uninstall
the update and ensure we are as secure as possible with the
workarounds in the technet article.
Thanks,
Jason