We were getting these events and backup of our SharePoint content database was failing. Investigation showed that our SQL backup maintenance plan (backup to disk) and Symantec Backup Exec jobs were running at approximately the same time. I changed the server order of the Backup Exec job to avoid the conflict and have not had the error since.
Error code: 995 Description: "The I/O operation has been aborted because of either a thread exit or an application request." - This problem occurs because of a race condition. The race condition incorrectly logs the event in the Application log. See ME934396
for a hotfix applicable to Microsoft SQL Server 2000 and Microsoft SQL Server 2005.
Error code: 288 Description: Attempt to release mutex not owned by caller. - After months of trying to resolve this and applying CU6 and several hotfixes I had to contact Microsoft and ask for the hotfix mentioned in ME934396
. They sent the 100 MB hotfix ME936305
several times but eventually I insisted on this 10 MB one and no more SQLVDI errors.
Additional information may sometimes be obtained from the SQLVDI log. The VDI.log file is located in the C:\Program files\Microsoft SQL Server\MSSQL\LOG directory by default.
From a newsgroup post: "I got rid of this by making sure that I backup at least 1 file on each drive array. I had not been backing up the Transaction log array, it only holds the transaction logs and we don't need to back up the individual files since we do 4 hour full backups to another disk. Seems that something MS changed affected the backup process."