What does the SQL Server error message Lazywriter: WARNING, couldn't find slot, 8/8, scanned 8 mean?

There has been an internal corruption that is stopping the lazy writerprocess from working properly. This is rare, but there was a known bug in SP3,fixed in SP4, that could cause this. If this were happening then you would seeother errors/AV's before this particular error appeared.

The normal reason is just that the disk subsystem is too busy to processthe i/o requests. In which case look for non-SQL tasks that may be causingcontention on the same disk(s) - NT backups, file transfers, paging etc. Lookfor contending SQL processes on the same disk(s) - table scans, log file writesetc. You may need to move SQL devices to prevent contention. Alternatively youmay have the overrall level of i/o's that SQL is making too high - you may needto reduce the number of "max async io"'s that sp_configure allows.