.NET (295) administrative (41) Ajax (42) AngularJS (2) ASP.NET (144) bicycle (2) books (180) browser (8) C# (133) cars (1) chess (28) CodePlex (10) Coma (8) database (47) deployment (3) Entity Framework (2) essay (110) flash/shockwave (2) flex (1) food (3) friend (2) game (20) idea (5) IIS (8) javascript (82) LInQ (2) Linux (6) management (4) manga (42) misc (670) mobile (1) movies (90) MsAccess (1) murder (2) music (64) mysql (1) news (99) permanent (1) personal (68) PHP (1) physics (2) picture (307) places (12) politics (13) programming (502) rant (120) religion (3) science (43) Sharepoint (3) software (58) space (1) T4 (2) technology (11) Test Driven Development (4) translation (2) VB (2) video (97) Visual Studio (44) web design (45) Windows API (8) Windows Forms (3) Windows Server (5) WPF/Silverlight (63) XML (11)

Friday, March 16, 2007

svchost 100% CPU utilisation

For a while now, whenever I start my computer at work, I get to wait about 5 minutes with my CPU up to 100% due to svchost.exe. Of course, this being an important component of Windows, I cannot delete or disable it, neither can I see what subprocess is causing this utilisation with the normal Task Manager. However, one can download Process Explorer and see a lot more information. I highly recommend it.

Anyway, back to the original problem. I noticed that the problem was the ntdll.dll (ntdll.dll!RtlAllocateHeap+0x18c to be exact) which is, again, a Windows important file.

Only googling to the extreme did I find that the issue is caused by Windows Update, scanning your computer each time you start it. If you disable Windows Update, you don't get the updates, but you get rid of the wait.

Here is a discussion with Microsoft MVPs about possible solutions.
Also, try this link.

And if you do have Process Explorer, you can set the priority of the offending task to Bellow Normal, which will allow you to run any program normally while the Windows Update process runs only on spare CPU. Normal Task Manager does not allow you to change the priority of the process.

1 comment:

Mike said...

I fell victim to the same exact problem. I saw the ntdll.dll in process explorer was eating the cpu up, so i googled the filename and got your blog. If all it is, is windows update, i'll be so happy! I just disabled it and restarted.......

Worked like a charm! That was driving me insane for a while. I even did a format and xp pro reinstallation. The problem came back! Great programming on the windows update. Way to go M$!