IT WORKS !!!!

OK, got up early and brave...

Downloaded the Mbrfix tool and rebooted to Windows XP safe mode.

Opened a command prompt window.

Followed LarryD's steps 2-5 above. After first reboot, it took a good 8-10 minutes for the initial boot to complete, but then got something like "new hardware added not available until reboot". Rebooted, all is normal.

Used both NTBackup and Ghost 12.0 to perform Shadow Copy backup...no errors, no problems !!! Yahoooooo!

I have to say a huge thanks to everyone on this thread...NICE WORK !!! Extra thanks to halholme for the key discovery !

(I hope Acronis finds this and fixes the process to avoid others going through the pain we all have had with this.)

Generating a new drive signature with MbrFix worked for me too. But I did it from the command prompt from within Windows XP Pro SP 2 and I wasn't in Safe Mode - the only thing I shut down was Symantec AntiVirus. Windows Backup Utility is running in the background as I write this.

Thanks Hal - Thanks Larry -

Wildman, kam, zippy - have you guys had a chance to try MbrFix??

I haven't used MbrFix. Before this solution was offered I wiped the entire drive and started over from scratch.

I found this to be a good solution for me because I can reinstall only the software that I use and keep the junk off of my system. I had a lot of programs that have been installed and uninstalled over the course of 2 years. So this wasn't all that bad for me. I had a backup of the folder "Documents and Settings" and printed out all of my security settings and used Belarc Advisor to tell me what software I had installed along with the keys. In less than 24 hours I had the entire system backup and running with all the configuration and software that I wanted installed including updates. The system is running a lot faster than it was.

This is something that I try to do every year because Windows can get really gummed up with junk over time. You can use all the tools in the world to prevent this but I have always found it best to just reinstall everything. I was just trying to avoid from doing it this time. I wanted the next clean install to be when I upgrade to Vista. It didn't happen that way!

Sorry, I've been out of town but I'm dying to try it so hopefully this week-end.

I'll report back how it goes.

OK, I tried this as outlined above using the comand prompt within windows and everything appears fine. Did the two re-boots, put PartMgr back into the upper filters and the backup program using shadow copy works great. This looks like the FINAL solution to this bug.

Thanks to everyone for advancing this to a good and easy solution. I just can't believe the lack of support that you get from the software companies.

You solved my BSOD problem with msbackup and norton ghost. I deleted the upperfilter, altho you have more recent posts about the signatures. One serindipitous effect this had is that my system tray--notification area was always corrupt and that fixed the problem. Some icons didn't used to show up, but now they all do. You should tell Seagate about this problem. Thanks again, genius! I joined this forum just to thank you. My Dell computer is 5 years old and stable as a rock. Am going to Vista Business now that I installed a 500G hard drive.

I had the same problem BSOD when with windows live trying to backup to my WD extrenal drive from my new Seagate 160GB. Followed the instructions below and it's on its way without errors. I did notice that the backup that is being created is all Zip folders. Is this normal?

Disabling shadow copy won't get the most up to date versions of the files. You should change the MBR signature and reenable shadow copy. By the way, my system tray started being corrupt again--many have this problem with XP. I just learned to assign a password and pause a bit before typing it in. This, unrelatedly, allows all the system tray icons to appear. Also, I like seeing the hidden partition on my Dell hard disk and will leave the upperfilters as kam33mitch posted, without altering the signature.

I ALSO FOUND THIS FIX ON ANOTHER SITE....IUSED IT AFTER REENABLING SHADOW COPY AND IT WORKERD GREAT....

"I have a Dell 4600 and upgraded from my failing original SATA 120GB to a Seagate SATA 300GB (ST3300631AS). I use Dantz Retrospect 7.5 to backup to a Maxtor external USB drive. I used Acronis Easy Migrate 7.0 to clone the drives. Every time I tried to backup, Retrospect would say "preparing backup" then I would get the blue screen of death (BSOD) error saying "Bad_Pool_Header Stop: 0x00000019".

Here is the fix and it works brilliantly: I found it on

1. Go to windows Device Manager
2. Click "view" and select "show hidden devices"
3. Scroll down to "storage volumes"
4. Click on the plus to expand.
5. Click on each one listed and right click and uninstall. (you will get a message on some staying to reboot before it takes effect. Select no until you do them all.)
6. Reboot.
7. Wait till windows automatically reinstalls devices. Will prompt to reboot again.
8 Reboot.
Now it should work.

The problem was they got corrupted using DiscWizard and Acronis (which is the DiscWizard engine). There are other explaination at that site, but the above works WITHOUT A REINSTALL OF WINDOWS OS!!!!"

Whopp

I don't remember reading that anyone else in this thread tried what you suggest.

I fixed my problem by generating a new drive signature with MbrFix running under XP. So I wonder if your suggestion - uninstalling the storage volume - accomplishes the same thing?

My problem is fixed so I have no need to try your suggestion - but can you really uninstall your boot drive in device manager? Will it let you do that? And if it will, will you then be able to reboot?

I tried what whoppsrus5254 suggested on my Dell Dimension 2400 and didn't use mbrfix and it worked. Simply uninstall the storage volumes. No BSOD on shadow copy! I can easily say this is a better solution since it involves no third party software, merely Windows. I put my partman upperfilters registry entry back and everything. My Dell FAT16 partition is again hidden. I have an extra "Removable DIsk" in My Computer but that's because of my fiddling with the drive letters to get my USB drive back to G:; where it was before I removed the Upperfilters entry. Thanks. By the way, 5254 is the last four digits of the Kim Komando radio show's call in toll free number, any relation? She has a competing message board at www.komando.com, but it costs to post to it. I have posted many items as "ladlers".

I'm really glad I discovered this thread! I have the same problem: cloned my boot disk using SeaTools and now Mozy backup is generating the BSOD. One thing to note: I cloned from a PATA disk to a new PATA disk, so it's not limited to SATA drives.

I want to try the whoppsrus5254 solution of deleting storage volumes. One question: is it necessary to delete all of the storage volumes from device manager, or only the boot drive volume?

Ok, here's another solution I found on the wildersecurity forum:

"Right click My Computer and select Properties, select Hardware, Device manager, select View, select View Hidden Devices, and then for each Genric-volume entry under Storage Volumes, right click and select update and let windows try to find a better driver for the Generic volume. If windows says it doesn't a better driver, that's okay, but it will probably update at least one of the entries. Then close down the device manager and reboot. Prob should be gone."

When I looked at my "storage volumes" in device manager, I saw that drilling down, several of the entries had corrupted names (i.e., weird characters after "Generic volume ".) Instead of deleting all of the storage volumes, I ran the "Update Driver" routine for each of these entries. After the update, the volume name was fixed. This probably accomplishes the same thing as deleting the storage volumes, but it seems a little less kludgy.

I haven't verified that this will fix the BSOD problem, but I'm hopeful that it will, based on other people's experiences. Someone else fixed the problem by going into the registry and updating the volume names, but using "Update driver" is simpler and more straightforward.

My 0x00000019 BSOD / BAD_POOL_HEADER problem began when I moved to a new 250Gb hard drive on my laptop from a 40 Gb drive. After moving to the new hard drive, whenever I used my usual WD Backup to back up data to my MyBook drive, the Bad Pool problem caused a BSOD.

Apricorn makes some wonderful, inexpensive, easy-to-use products for cloning disks, and I used one of their products with their EZ Gig software to accomplish the clone. The whole thing went perfectly -- thank you, Apricorn. I had to install EZ Gig in order to create the bootable Emergency Recovery disk, which accomplished the actual disk clone.

But EZ Gig was the problem as it turned out. To fix the Bad Pool problem, I didn't uninstall EZ Gig, so I have no idea whether that would help. Instead, I used System Restore to restore XP (on the new hard drive) back to before the EZ Gig install (which took place on the old hard drive from which the new hard drive was cloned).

Problem gone!

I have noticed that other users on the Web have this problem in conjunction with the many re-labeled versions of Acronis software bundled as backup solutions from many disk manufacturors. In this case, Acronis is the actual creator of both EZ Gig AND WDBackup. How ironic that uninstalling one Acronis product allowed the other to work in my case.

Acronis -- EZ Gig is terrific -- but you really should fix this Bad Pool problem! I'll send Acronis an email.

Cheers.

OK, my previous solution (updating the drivers for the storage volumes) didn't seem to work. Deleting the storage volumes and rebooting did the trick, though.

The MBRfix routine above worked for me too (like everyone else).

I found an article from a dev at ACronis that said the cause is that there are 4 bytes in the MBR that are supposed to be "unused" which defrag and Acronis both alter to provide information on when the drive was defragged and/or imaged. Unfortunately windows VSS uses those 4 bytes for something (nobody knew what) so it causes problems. Resetting the MBR altogether forces VSS to reinitialize and accept the new MBR.

So we have Cause --> Effect --> Solution, I'd say the MBR fix should be pretty reliable.

Cheers,

dark green

YES! I have the same problem! I did a clone using Maxtor MaxBlast(Seagate/Acronis) about 2 months ago and I get the 0x00000019 BSOD when I try to use windows backup. I also have Seatools. Some one mentioned that was also a possible cause?

If there are 4 "unused" bytes in the MBR, then why does uninstalling (I would say, the preferred method) the storage volumes work?

I did the Mbrfix routine and now I just completed my first successful Windows backup off the cloned drive. I had Windows running in safe mode during the fix........no problems. Thanx Larry and Everyone else involved and thanx to techspot forums. I've been dealing with this issue for over 2 months!