I'm using NOD32 on my two Windows 2000 Servers, and amon.sys is causing a BSOD crash when my backups are run. We've figured out the problem and have instituted workarounds, but wanted to make sure Eset knows about the problem. The problem is this: using Windows Backup utility amon.sys will crash the system as soon as the backup file gets to 4GB in size. If we divide the backup schedule to make finished backup files less than 4GB in size then the crash doesn't occur. Instead of two or three nicely organized backup jobs, we have to have 15 or so to make sure the backup files don't approach 4GB. These are automated backups set to run each night, so there is no way we can disable the scanner before running the backups, unless there's an automated way of doing that I'm not aware of. I also haven't looked at the possibility of excluding an entire directory (our backup folder). Anyone know if this is a known issue? Am I doing something wrong to cause this? Are there better workarounds than simply creating a myriad of backup jobs to keep the final backups under 4GB? TIA.