BAD_POOL_HEADER on VSS backup after disk clone

I recently cloned my hard disk using the Seagate version of True Image (DiscWizard). Now, whenever I use any backup software that uses Volume Shadow Copy Service (VSS), I get the Windows Blue Screen of Death (BSOD) with a title of BAD_POOL_HEADER.

I see numerous reports of other users experience the exact same problem (e.g. see http://www.techspot.com/vb/topic94820.html or Google "BAD_POOL_HEADER Acronis").

What can be done to resolve this problem short of reformatting the drive and reinstalling everything?

Many of us are DESPERATELY looking for some help from Acronis on this issue. Please be our hero!

 

Well I think the techspot conclusions may be a red herring - not that TI has a problem with VSS - but in the method used to deduce it. I have two S-ata drives and a USB S-ata which holds my images - I haven't had any problems.

What might cause a problem though is the chipset that the motherboard uses. Is your motherboard very recent, and if so, what chipset does it use?

Colin

 

SOLUTION to BAD_POOL_HEADER on VSS backup after disk clone problem

The solution to this problem can be found at http://www.techspot.com/vb/showthread.php?p=563391#post563391

The basic cause of the problem is that the cloned drive needs to have a new Master Boot Record signature so that Windows recognizes it as a new drive and reinitializes some things essential to proper operation of Volume Shadow Copy Service (VSS).

The solution is quite simple and does not require reinstalling or repairing Windows. You can use the MbrFix utility (from http://www.sysint.no/en/Download.aspx) to regenerate the drive signature with a command like:

Code:

MbrFix /drive 0 generatesignature

and then reboot the computer to have Windows detect the "new" drive. Windows will ask for one more reboot and then the problem is solved. Please read the post listed above for all the details.

Since so many people have experienced this problem (see the post for just some of us), it would really be nice if Acronis updated its cloning code to avoid this problem in the first place.