DE, AX64 uses both a tracking mechanism to follow disk allocation changes (so it knows what to back up) and a "dirty bit" mechanism to determine if anyone/thing has possibly modified the system while it wasn't looking. That mechanism is violated by unexpected or forced shutdowns, as well as external BOOT mechanisms (BOOT CDs, external OSes, etc.) that may access that protected disk. When it comes back up and is asked to do its thing, it notices the violation and must now remap the drive to insure that its tracking mechanism is back in sync. It does take a bit of time but will still produce a proper small snapshot when complete. It has to do this to be sure the disk hasn't been tampered with otherwise it'll be out of sync with the storage utilization. It's just a delay, not a concern.