if you have high cpu usage of the system process, this article will help you to track down the offending driver or kernel module. in my case, it was intelppm causing an abnormally large percentage of cpu time in the kernel. intelppm is a microsoft intel power management driver for intel processors that executes in kernel mode (hence the high cpu of the system process). i tried to use the process explorer thread tab on the system process, but since i didn’t have windbg installed and configured with the microsoft online symbol server, all i could see was hex.
after searching for ways to look at kernel threads, i found mark russinovich’s blog post and he suggested kernrate, a command line kernel profiling tool. symbol files are not required if kernrate finds a device driver. after installing kernrate i ran kernrate_i386_xp.exe on a windows 2003 x86 server during the high cpu, then hit crtl+c to stop profiling when it returned to normal. you can use a tool called xperf for newer x64 systems (win7/8/2008/2012). the following output is what i found:
results for kernel mode:
outputresults: kernelmodulecount = 137
percentage in the following table is based on the total hits for the kernel
time 49788 hits, 25000 events per hit ——–
module hits msec %total events/sec
intelppm 33834 33953 67 % 24912378
ntoskrnl 13018 33953 26 % 9585309
win32k 864 33953 1 % 636173
hal 690 33953 1 % 508055
klif 450 33953 0 % 331340
fltmgr 294 33953 0 % 216475
vdtw30 131 33953 0 % 96456
ntfs 120 33953 0 % 88357
tcpip 93 33953 0 % 68477
npfs 51 33953 0 % 37551
rdpdd 36 33953 0 % 26507
scsiport 29 33953 0 % 21353
snapman 27 33953 0 % 19880
wdica 18 33953 0 % 13253
mraid35x 18 33953 0 % 13253
e1000325 15 33953 0 % 11044
classpnp 14 33953 0 % 10308
partmgr 14 33953 0 % 10308
afd 12 33953 0 % 8835
ctxsbx 9 33953 0 % 6626
termdd 9 33953 0 % 6626
ctxaltstr 8 33953 0 % 5890
ndis 6 33953 0 % 4417
pdcrypt2 4 33953 0 % 2945
rdpwd 4 33953 0 % 2945
ipsec 4 33953 0 % 2945
tdtcp 3 33953 0 % 2208
tdi 3 33953 0 % 2208
pdrframe 2 33953 0 % 1472
ipnat 2 33953 0 % 1472
disk 2 33953 0 % 1472
rasacd 1 33953 0 % 736
dcdipm32 1 33953 0 % 736
volsnap 1 33953 0 % 736
ftdisk 1 33953 0 % 736
it was obvious that intelppm is the offending driver because it accounted for 67% of the hits in the kernel. i searched for an updated intelppm driver but couldn’t find any newer versions and since there hasn’t been any changes to the server, i decided to cross my fingers and uninstall the driver. it turns out that intelppm is safe to uninstall even on an intel system. so far it has been stable. there are two methods for windows server 2003/xp:
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 work around this issue, follow these steps:
- click start, click run, type regedit, and then click ok.
- locate and then click the following registry key:
- in the right pane, right-click the start entry, and then click modify.
- in the value data box, type 4, and then click ok.
- exit registry editor.
- restart your computer.
to work around this issue, run the recovery console by using the cd. then, select the recovery option.
- insert the windows cd in the cd drive. then, restart the computer.
note if you are prompted, click to select any options that are required to start the computer from the cd drive.
- when the “welcome to setup” screen appears, press r to start the recovery console.
- if you have a dual-boot computer or a multiple-boot computer, select the installation that you want to access from the recovery console.
- when you are prompted, type the administrator password.note press enter if the administrator password is blank.
- at the recovery console command prompt, type the following command, and then press enter:
- to exit the recovery console and to restart the computer, type exit at the recovery console command prompt, and then press enter.
if you’re as lazy as i am, here are registry files you can download and run instead of performing these operations yourself:
feel like beefing up your understanding of threads, processes and memory management in windows? david solomon, author of windows internals presents at technet talks in 2005, focusing on understanding processes, threads, memory management in windows. it was so good that i created it’s own post
processes and thread troubleshooting – part 1
processes and thread troubleshooting – part 2
understanding and troubleshooting memory problems – part 2