A CPU hog could be an NLM™ program that is poorly designed or has become corrupted and, as a result, is using up so many of the server's CPU cycles that other NLM programs are not able to run properly.
CPU hog problems are indicated on the Health Monitor page by a suspect or bad status for the CPU Utilization-x indicator.
To track down a CPU hog:
Under theheading, click the link.
Identify the offending thread and Parent NLM.
In thetable, note the thread and the Parent NLM that is taking the longest execution time.
To see which tasks the thread is trying to perform, do one of the following:
Identify which part of the NLM program is causing the problem by looking at the Nearest Symbol information.
From here you can trace each procedure including the one that is being called most often (indicated by the highest Call Count).
If possible, unload the offending NLM program to see if the problem disappears.