View Single Post
  #2 (permalink)  
Old January 27, 2013, 10:05 AM
Daedalus2002 Daedalus2002 is offline
Top Prospect
F@H
 
Join Date: Mar 2012
Location: Toronto
Posts: 52
Default

tasklist /SVC in a command prompt when it all goes haywire. It will tell you exactly what processes are running under svchost (there will be multiple instances). Then start killing svchost instances using the pid numbers till things get back to normal (taskkill /pid xxxx). You will need to do reboots as when you kill an instance, essential services may stop.

When you identify which svchost instance you can use process explorer to kill individual processes running in that svchost instance.When you know which process is the one causing issues then you really know where to start looking for a fix.


Whats the CPU usage like when this is happening? Usually you see high CPU usage at the same time. I remember back in the WXP days there was a bug with automatic updates that had the same symptoms. We had to reset the windows update cache to fix that one.
Reply With Quote