hi tc
re, The Troubleshooting Flowchart...
maybe excellent, maybe not. it would be neat if several people here put it through its paces, or at least remembered it and turned to it when troubleshooting. might help the group to know this.
imo, these flowcharts are limited in scope and in specificity, but the good ones are useful tools, nonetheless.
i'm having a situation where some process is churning my hd during boot up, way past the log on point when it used to stop making noise. i'm trying a number of things to identify what may be the cause of this excessive writing to disk, and i turned to the flowchart. it didn't cover the prob i am experiencing.
the executable i am looking at right now is LSASS.EXE, which appears to be a rather important system file, acting mainly as an authenticator, to verify user logins. reason my attention has turned to LSASS.EXE is that its mem usage during bootup is 4332k, then when everything settles down (all the churning stops), the mem usage for that process has dropped to 932k. of the approximately three dozen processes running (viewable in task manager), none show a decrease in mem usage during this time span like LSASS.EXE. so i'm focused right there for now.
any thoughts from you on this would be welcome, of course.
:)
mark |
