XP Pro account anomaly: password asked for on accounts wit..

Hello, everyone. I am running Windows XP Proffesional SP2 with one
password-protected user/administrator account and two
non-password-protected user accounts. Windows boots up and runs normally,
but after logging out of an account, Windows will occassionally ask for
non-existant passwords on the two unprotected accounts and says the correct
password is wrong for the one account that has a password. I looked in the
event log and didn't see any warnings or problems, and I haven't messed with
anything in the registry. I searched Microsoft's forums and newsgroups as
well as Google, but can't find anything similar to my question, and the
techs I have asked have never heard of this happening. It may be that I am
asking the wrong question, or perhaps I am not describing the problem well.
Can anyone point me in the right direction so I can discover a solution?
I'm concerned that this is a symptom of a greater problem and I want to
correct it myself, but am hoping to avoid a reinstallation. Thanks for your
attention, A. Johnson

If you didn't set a password, who did? Here's what I think: The password
was set by the malicious software that infected your computer. *All*
user accounts should be password protected.

---
Leonard Grey
Errare humanum est

Andrew wrote:
> Hello, everyone. I am running Windows XP Proffesional SP2 with one
> password-protected user/administrator account and two
> non-password-protected user accounts. Windows boots up and runs
> normally, but after logging out of an account, Windows will
> occassionally ask for non-existant passwords on the two unprotected
> accounts and says the correct password is wrong for the one account that
> has a password. I looked in the event log and didn't see any warnings or
> problems, and I haven't messed with anything in the registry. I
> searched Microsoft's forums and newsgroups as well as Google, but can't
> find anything similar to my question, and the techs I have asked have
> never heard of this happening. It may be that I am asking the wrong
> question, or perhaps I am not describing the problem well. Can anyone
> point me in the right direction so I can discover a solution? I'm
> concerned that this is a symptom of a greater problem and I want to
> correct it myself, but am hoping to avoid a reinstallation. Thanks for
> your attention, A. Johnson
>