A
Abeness
I'm perplexed again. When I login as my primary user on my production
system (XP Pro SP2, fully patched, lots of RAM and HDD space), the
system stalls for about a minute-plus between entering the password and
when the desktop icons appear, while lsass.exe maxes out the CPU. Even
after the desktop appears, the system remains sluggish until lsass.exe
finishes whatever its doing. This does not happen on other user accounts.
Some months ago I had the problem, and solved it by creating a new user
account for myself, then moving all my settings over. It wasn't pretty,
because of the need to reconfigure settings paths and what-have-you, and
I'm not anxious to repeat the process. However, the delay is pretty
darned annoying.
What I'd like to do is get to the bottom of why lsass.exe goes nuts, and
eliminate the problem without having to recreate my account.
I've carefully examined the event logs but cannot pinpoint a specific
error during the stall, or a system change that prompts the stall. The
System log simply indicates a gap of about a minute and 30-45 seconds
between the time that TCP/IP loads (event ID 4201, network adapter
detected as connected to the network and normal operation initiated) and
the next service loading.
During the period of the delay, the Security log shows about 100 success
audits for the first 15 seconds of the delay and one failure audit in
the middle of those, then there's a gap of about 30 seconds between the
time explorer.exe is audited and when taskman is audited (cuz I'm trying
desperately to see what's going on), then another 15 seconds before
userinit is audited, then a component of my mouse software is audited,
then another 15 seconds till wuauclt.exe is audited, then another 10
secs till the next startup process is audited, and then things start to
load faster, towards the last 20 seconds or so of the stall period.
I've also tried to use ProcessExplorer from SysInternals to try to
pinpoint the problem, without really getting anywhere as I can't load it
in time. Googling hasn't turned up a precise description of the problem.
Anyone seen this and resolved it? Any ideas on how to figure this out?
Is there a way to log what lsass.exe is trying to do when it's stuck?
Better places to post this?
Any assistance will be much appreciated. This is really bugging me!
Abe
system (XP Pro SP2, fully patched, lots of RAM and HDD space), the
system stalls for about a minute-plus between entering the password and
when the desktop icons appear, while lsass.exe maxes out the CPU. Even
after the desktop appears, the system remains sluggish until lsass.exe
finishes whatever its doing. This does not happen on other user accounts.
Some months ago I had the problem, and solved it by creating a new user
account for myself, then moving all my settings over. It wasn't pretty,
because of the need to reconfigure settings paths and what-have-you, and
I'm not anxious to repeat the process. However, the delay is pretty
darned annoying.
What I'd like to do is get to the bottom of why lsass.exe goes nuts, and
eliminate the problem without having to recreate my account.
I've carefully examined the event logs but cannot pinpoint a specific
error during the stall, or a system change that prompts the stall. The
System log simply indicates a gap of about a minute and 30-45 seconds
between the time that TCP/IP loads (event ID 4201, network adapter
detected as connected to the network and normal operation initiated) and
the next service loading.
During the period of the delay, the Security log shows about 100 success
audits for the first 15 seconds of the delay and one failure audit in
the middle of those, then there's a gap of about 30 seconds between the
time explorer.exe is audited and when taskman is audited (cuz I'm trying
desperately to see what's going on), then another 15 seconds before
userinit is audited, then a component of my mouse software is audited,
then another 15 seconds till wuauclt.exe is audited, then another 10
secs till the next startup process is audited, and then things start to
load faster, towards the last 20 seconds or so of the stall period.
I've also tried to use ProcessExplorer from SysInternals to try to
pinpoint the problem, without really getting anywhere as I can't load it
in time. Googling hasn't turned up a precise description of the problem.
Anyone seen this and resolved it? Any ideas on how to figure this out?
Is there a way to log what lsass.exe is trying to do when it's stuck?
Better places to post this?
Any assistance will be much appreciated. This is really bugging me!
Abe