We've got exactly the same problem on our SQL2K SP3 database. The same error occurred in SP2 too. Our log file looks remarkably similar to yours. We've reported out problem...