Hmm, your saying lsass.exe? Strange indeed... Seems like some sort of authorization loop (lsass usually handles logons/authorization).
Isn't there anything suspicious in the Windows Event Log?
Also, is it only lsass.exe that takes up the CPU, or is it another process as well? (I mean, if you sort the process list according to CPU usage, which process is the 2nd?)
Thanks
Vlk