Win XP "Possible Deadlock condition" & "Error detected between two drivers"

We have a Windows XP machine being backed up nightly by Backup Exec 2010 R2.

Occasionally the job will fail with the Windows XP machine getting a Deadlock Error with the following in event viewer. Does anyone have a possible solution to this or know why it may be happening?

 

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date:  3/1/2011
Time:  2:49:29 AM
User:  N/A
Description:

Application popup: Windows - EXCEPTION : Possible deadlock condition.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

============================

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date:  3/1/2011
Time:  2:49:30 AM
User:  N/A
Description:

Application popup: Windows - System Error : An error was detected between two drivers or within an I/O driver.

============================

Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 57481
Date:  3/1/2011
Time:  2:49:33 AM
User:  N/A
Computer:
Description:

An unusual error (87) was encountered while enumerating the contents of the directory:

 \\ComputerName.Domain.com\C:\

It is possible that files or subdirectories have not been backed up. Please examine your job log or catalogs to ensure this directory tree was backed up in its entirety.

2 Replies

Hello Mbjoe,

Try the following steps:

1) Reboot the target server to get rid of left out .VSP files

2) Configure Antivirus to exlude .VSP from scanning. From the Anti virus scanning exclude the Advanced Open File Option (AOFO) folder which must be on the C: drive of the server (may be hidden folder). Also exclude RAWS folder from the installation path of Backup Exec.

3) check out the document: http://www.symantec.com/docs/TECH32393

 

Thanks,

-Sush...

We are running a script to

We are running a script to disable our anti-virus on-access scanning before backups take place and turn it back on after the job is complete.

Could this still be causing the problem?