1.i could trace out which svchost - thread was causing the overload.2. i was able to get to the *actual* dll, which was causing trouble3. Which turned out to be a TAPI related thing dll and well, 4. There was ONLY one TAPI related application in my system - shoretel/shoreware client.5. Surprise - Surprise, the tapi logs under shoretel had grown to a whopping 4+ GB over these couple of months. Wierd!6. I got rid of shoretel/shoreware client and sweet me! all's well now!

Thanks a lot to SysInternals Tools.:) me's a happy system now. (and with 1GB of RAM)!