Wscript running high cpu
We have few windows 2003 terminal servers which every so often reach 100 % cpu and the process wscript is taking all this cpu. I have checked all the group policies and cant see why any script would cause this. I have anti-spyware running
on these servers as well.
Can anyone point out what would be causing wscript to have high cpu, or how u can find out what would be causing this, or any tools which can assist in finding out. Its a big issue for us.
Thanks
October 21st, 2010 10:53am
To get an idea of what the process is doing and which threads are running in it, you can use the process explorere tool:
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
Extract the zip file to a folder and set the symbol file path to the microsoft public symbol server:
Options menu > Configure symbols
set the symbol file path to: http://msdl.microsoft.com/download/symbols
Restart process explorer
Click on the View menu and select show lower pane view option, click on "lower pane view" you can either select DLLs or handles, to start with select handles
Select the process that has high CPU, on the lower pane you will see the handles for this process, look through the list and see if you can find any file, DLL that you think might be responsible.
Next, right click the process that has the high CPU problem and go to properties
Go to the "threads" tab and sort the threads by CPU (the second column)
To have a look at the thread stack and get an idea of the kind of functions, you can select a thread and click the Stack button below.
There are other advanced tools available, like Xperf to drill down the problem further:
http://blogs.msdn.com/b/pigscanfly/archive/2008/03/02/using-the-windows-sample-profiler-with-xperf.aspx
http://blogs.msdn.com/b/pigscanfly/archive/2009/08/06/stack-walking-in-xperf.aspx
http://blogs.technet.com/b/askperf/archive/2008/06/27/an-intro-to-xperf.aspx?wa=wsignin1.0
http://blogs.msdn.com/b/ntdebugging/archive/2010/03/22/using-xperf-to-root-cause-cpu-consumption.aspx
Hope this helps.
Thanks,
Madhurjya
Free Windows Admin Tool Kit Click here and download it now
October 24th, 2010 9:29am
To get an idea of what the process is doing and which threads are running in it, you can use the process explorere tool:
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
Extract the zip file to a folder and set the symbol file path to the microsoft public symbol server:
Options menu > Configure symbols
set the symbol file path to: http://msdl.microsoft.com/download/symbols
Restart process explorer
Click on the View menu and select show lower pane view option, click on "lower pane view" you can either select DLLs or handles, to start with select handles
Select the process that has high CPU, on the lower pane you will see the handles for this process, look through the list and see if you can find any file, DLL that you think might be responsible.
Next, right click the process that has the high CPU problem and go to properties
Go to the "threads" tab and sort the threads by CPU (the second column)
To have a look at the thread stack and get an idea of the kind of functions, you can select a thread and click the Stack button below.
There are other advanced tools available, like Xperf to drill down the problem further:
http://blogs.msdn.com/b/pigscanfly/archive/2008/03/02/using-the-windows-sample-profiler-with-xperf.aspx
http://blogs.msdn.com/b/pigscanfly/archive/2009/08/06/stack-walking-in-xperf.aspx
http://blogs.technet.com/b/askperf/archive/2008/06/27/an-intro-to-xperf.aspx?wa=wsignin1.0
http://blogs.msdn.com/b/ntdebugging/archive/2010/03/22/using-xperf-to-root-cause-cpu-consumption.aspx
Hope this helps.
Thanks,
Madhurjya
October 24th, 2010 4:28pm