I've seen a lot on LSASS.EXE CPU and Memory Bloating. Since I'm having the problem in the context of SQL Server, I'm posting in this forum....but the hotfix solution i found might be the answer to other lsass.exe issues.
Note: I don't post a lot so please forgive me if I break some rule of etiquette
LSASS.EXE process consumes a lot of CPU...in my case maxed out to 100%.
I am on a WIN 2008R2 SP1 Server and doing a SQL Server 2008R2 Backup maintenance plan that includes file maintenance on TRN and BAK files (deleting old files by date).
Lots of DBs (A sharepoint system)....maybe 50 or so. Keeping a week of daily BAK and every-15-min TRN files....so the number of trn&bak files is a lot...but the total amount of data is not huge.
Also of note, the Full backup maintenance plan job takes 35 minutes but should only take 5 minutes given the data. I am using compression so i suspect the CPU issue is slowing down the backups.
I discover the CPU bloat for LSASS.EXE is happening during the file maintenance steps ...not the backup step. Evidently there is a lot of Active Directory authentication happening... maybe directly related to the number of files....so LSASS.EXE is executing a lot. I forgot to mention that LSASS.EXE is a microsoft Active Directory authentication resoution process. Still there shouldn't be 100% CPU usage.
I then discovered the answer in a hard to find Hotfix (these seem always hard to find even when you search using the right terms).
seems the CRYPTDLL.DLL used by LSASS.EXE is written poorly and is slow and eats CPU....maybe even a memory leak. Anyway, the hotfix addresses it and is for Windows Server 2008R2 with or without SP1. You can tell if you need it by looking at the version of your server's CRYPTDLL.DLL (right click/properties). The link gives the version numbers.
Hope it helps someone. if you find other LSASS.EXE related solutions post them here if you want...might help someone like me.