Has anyone experienced BSOD 7B after removing ADD 10 or ADD 11 in Windows XP SP3

I have experienced the same basic problem with Acronis Disk Director (ADD) 10 and ADD 11 that leaves you with an unbootable system upon system restart. What you receive is a blue screen of death on both the normal boot sequence and also using the safe mode (with or without network option). I don't remember all of the register values on the BSOD but the stop value was 7B. I have not able to conclusively set up the conditions to duplicate this error, but I have had it occur enough times on different machines to consider it a bug. The only way that I have found to recover the machine when this happens is to reload the machine from a previous backup. Here is the behavior that I have noticed.
1. Both ATI and ADD have to initially be installed on the same machine.
2. Remove ATI first. If you don't get a message to restart your machine you have a good chance of duplicating the error.
3. Without rebooting after the removal of ATI go to the add remove programs and remove ADD.
4. When ADD is finishing up the removal it encounters some type of error and the removal seems to stop. The best I can tell is that ADD is restoring or writing something to the hard disk when it fails and an error message appears.
5. Upon re-boot you will receive the BSOD with the 7B identification. I have experienced this with ADD 10 and ATI 2009, ADD11 and ATI 2010, and other combinations.
Has anyone else experienced this type of behavior and if so have you found a better solution to recover your system besides reloading from backup? Usually I am removing both applications to install some other beta version to perform testing. The first time or two I attributed it to the beta application. However, I have had it happen removing the stable versions of the applications before installing the beta application.

- Se connecter pour poster des commentaires

That problem happens when the snapman driver doesn't get properly uninstalled. It's basically causing the BSOD for the same reason as when the storage driver is incorrect (0x7B). Fixing it usually requires manually repairing either the install or the uninstall of the driver.
Restoring to a previous backup is another option (and probably quicker/easier than fixing it).
- Se connecter pour poster des commentaires