Bad Pool Header error after ghosting a T60 hard drive

[SeanC]

Hello,

I ghosted my 60g Hitachi T60 drive onto a 100g Hitachi T60 drive following the admin's guide and Windows does boot and seem to work fine, but I get random blue-screens with a "Bad Pool Header" error. I googled around and know that this has to do with conflicting drivers of some kind, but couldn't find a workable fix for it.

As a little random but maybe relevant information, I may (or may not) have left the original drive hooked up when I first booted the new hard drive--though it booted fine. The new drive worked fine all night for the first night (I left it on all night processing video files), and the Bad Pool Header message started in the morning of the next day.

I did hook up the old drive (as an external USB drive) the next morning and the crashing started soon after that, though it may have nothing to do with the crashing as I think the original drive had already been hooked up the night before (after the ghosting).

Any help is appreciated!

[BillMorrow]

Hello,

I ghosted my 60g Hitachi T60 drive onto a 100g Hitachi T60 drive following the admin's guide and Windows does boot and seem to work fine, but I get random blue-screens with a "Bad Pool Header" error. I googled around and know that this has to do with conflicting drivers of some kind, but couldn't find a workable fix for it.

As a little random but maybe relevant information, I may (or may not) have left the original drive hooked up when I first booted the new hard drive--though it booted fine. The new drive worked fine all night for the first night (I left it on all night processing video files), and the Bad Pool Header message started in the morning of the next day.

I did hook up the old drive (as an external USB drive) the next morning and the crashing started soon after that, though it may have nothing to do with the crashing as I think the original drive had already been hooked up the night before (after the ghosting).

Any help is appreciated!

i never heard of this error before..
have not cloned a drive for at least 6 to 8 months..
when i do i use acronis true image, not ghost..
(symantec seems to let acquisitions languish)

if you can determine which driver this error pertains to nthat would help..
unlikely the old drive being connected had anything to do with it unless it tried to boot from the USB drive first..

could this error be related to the video application..?

[GomJabbar]

I did a little searching on this. I see one user say it was caused by a bad memory stick (RAM). Another user said that having DLA enabled on the drive was the problem. Another that it is caused by conflicting device drivers.

Here are a couple of links to look at.
http://discuss.pcmag.com/forums/1004321 ... wPost.aspx
http://www.tweaksforgeeks.com/BAD_POOL_HEADER.html
http://www.tek-tips.com/viewthread.cfm? ... 414&page=1

[SeanC]

Hello,

I ghosted my 60g Hitachi T60 drive onto a 100g Hitachi T60 drive following the admin's guide and Windows does boot and seem to work fine, but I get random blue-screens with a "Bad Pool Header" error. I googled around and know that this has to do with conflicting drivers of some kind, but couldn't find a workable fix for it.

As a little random but maybe relevant information, I may (or may not) have left the original drive hooked up when I first booted the new hard drive--though it booted fine. The new drive worked fine all night for the first night (I left it on all night processing video files), and the Bad Pool Header message started in the morning of the next day.

I did hook up the old drive (as an external USB drive) the next morning and the crashing started soon after that, though it may have nothing to do with the crashing as I think the original drive had already been hooked up the night before (after the ghosting).

Any help is appreciated!

i never heard of this error before..
have not cloned a drive for at least 6 to 8 months..
when i do i use acronis true image, not ghost..
(symantec seems to let acquisitions languish)

if you can determine which driver this error pertains to nthat would help..
unlikely the old drive being connected had anything to do with it unless it tried to boot from the USB drive first..

could this error be related to the video application..?

I used TrueImage, I just thought "ghosting" was the general term for cloning.

Which video application?

Thanks.

[SeanC]

I did a little searching on this. I see one user say it was caused by a bad memory stick (RAM). Another user said that having DLA enabled on the drive was the problem. Another that it is caused by conflicting device drivers.

Here are a couple of links to look at.
http://discuss.pcmag.com/forums/1004321 ... wPost.aspx
http://www.tweaksforgeeks.com/BAD_POOL_HEADER.html
http://www.tek-tips.com/viewthread.cfm? ... 414&page=1

Thanks for the links, I'm going to check them out. What's really weird is the crashes are seemingly random. It'll go for a day or two without any crashes and then bam, 20 minutes of crashes and then fine again.

[steveg47]

SeanC, I think it would be a really good idea if you ran some hardware diagnostics on the new 100gb drive to eliminate it as the cause of your problem. I would use a diagnostic program downloaded from Hitachi: http://www.hitachigst.com/hdd/support/download.htm#DFT

This knowledgebase article may also have some relevance:
http://support.microsoft.com/kb/896926/en-us