I actually experienced this problem just the other day. It was while the CPU usage was pegged at 100% on the SQL Server from an application that uses it. Once the CPU usage went back to normal the error stopped. It only happened twice in about 12 hours all the rest of the hourly T_Log backups went fine.