McAfee may not necessarily be to blame. Taken from this ComputerWorld article :
Wrong driver named
Often you will see an antivirus driver named as the cause. For instance, after using !analyze -v, the debugger reports a driver for your antivirus program at the line "IMAGE_NAME". This may well be the case, but bear in mind that such a driver can be named more often than it is guilty. Here's why: For antivirus code to work it must watch all file openings and closings. To accomplish this, the code sits at a low layer in the operating system and is constantly working. In fact, it is so busy it will often be on the stack of function calls that was active when the crash occurred, even if it did not cause it. Because any third-party driver on that stack immediately becomes suspect, it will often get named. From a mathematical standpoint it is easy to see how it will so often be on the stack whether it actually caused a problem or not.
It is as likely to be the application that's at fault. The 2009 version had a known problem which was apparently fixed in the 2010 upgrade. Have you asked about this on their forum?
Acronis True Image 2009 was not compatible with Windows 7 anyway. 7 support didn't start until 2010 and later.
Thanks for the info. I will upgrade Acronis to the current version.
OK, good luck.