Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
BSOD - Bad Header Pool 0x00000019 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I have one computer (XP Home, AMD3000, 1gb ram, 160gb HD, Abit Motherboard, ATI128mb Radeon9600 Video) giving me fits with backup. Nine times out of 10, it will fail the backup, computer is locked up. However, after a fresh boot, it will backup automatically without problem (if within the scheduled backup time period). Today, after rebooting and doing the auto backup, I was renaming a group of pictures. I decided to do another manual backup. It started and then BSOD, Bad Pool Header, 0X00000019. It appeared to die at the same point that other backups had failed, just when Windows bumps the floppy drive ( I am assuming it is unloading files/processes for backup). The floppy drive light is always lit when the failed backups take place and it was with the BSOD also. I have an HP PSC2510 All In One attached to this computer via USB. Possibilities?? I don't know. I've done all the usual checks/tests/diagnostics that I can find to try and it coninues to fail/lockup at backup unless it was rebooted just prior to the backup starting. All software and drivers are up to date.

    Ideas?

    One last thing, there is a patch available for 2003 Server software that apparently addresses this issue ( the stop error). WHS is stable on it's platform and all other XP machines are backing up with no problems. I am stumped. MemTest detects no problems, chkdsk, no problems, all the usual culprits don't seem to have any problems, just backup. Could it be a problem with WHS?

    Grasping for straws.......

    Cruise
    Monday, September 3, 2007 9:03 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Once again, backup failed. So rather than screw around any more with this PC, I have installed AutoShutdown and have it set to reboot the computer at midnight every night. Backup is scheduled at 1 AM. Unless that fails, let's call this closed/answered. I'll give one more update tomorrow.

    Cruise
    Thursday, September 6, 2007 9:10 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    I've not seen this issue, but if I were you I'd try to remove the connector via "add and remove programs" reboot the computer, reboot whs, reinstall the connector, reboot the computer, then try the backup.  You might also remove the backups of this computer on whs.

     

    edit:

     

    This is MS help on the error:

     

    You may receive a "STOP: 0x00000019" error message on a Windows Server 2003-based computer

     

    http://support.microsoft.com/kb/892260

     

    From the above page, you can click on a link to go to a "hot fix."  but that is for the server

     

    when I google "0X00000019 windows xp" it seems that people are saying it is a driver issue... so reinstall of the connector might help.  If none of the others reply, you might do the same search and read all the threads. 

    Monday, September 3, 2007 10:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I did research the problem before posting and found the MS KB article you refer to, but it does say for 2003 based computers. It's not a server problem, I know/think it's the PC. I did do a driver update and found there was a new driver/update for the HP printer I have, so installed that. By the time I was done searching/updating and rebooting, it was fairly late so I didn't have the opportunity to work the PC much before it was bed time for old Bonzo (me). It did backup last night, which doesn't surprise me too much after the reboot. Tonight will tell me if I've made progress or not. Wife has been using the computer almost all day and I told her not to reboot so that I could see if this problem might be cured.

    I have 5 other computers (4 XP Pro and one MCE) all backing up without problem, just the one with HOME on it. So if I can get that one backing up regularly without failure, I'll be sitting pretty until the release is available, then we can all see what kind of fun we can have.

    Thanks for your input.

    Cruise
    Tuesday, September 4, 2007 11:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    What would likely be a good idea would be to use a System Restore Point (On the PC you are experiencing the problem with) that was created before you began seeing this issue. If the problem is being caused by a bad registry entry, this could fix the issue. 

     

    Please have a look at this KB article on using Restore Points:

    http://support.microsoft.com/kb/306084 

    Wednesday, September 5, 2007 1:19 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Another failure last night. This computer has never had a good automatic backup to WHS unless it has been restarted and little to nothing done on the computer between times. So, a restore point is useless. It has done the same thing with CTP and RC1. Restart the computer (PC) and it will backup perfectly. Use the computer and it will fail the backup. Connector reinstall does not help.

    Today, I have dumped the pagefile and created a new one. It did a backup shortly thereafter without issue, but that does not surprise me. Tonight will tell the tale if it does it's regularly scheduled backup without a restart previous to that time. The PC is stable, no issues at all except for the backup. Doesn't always bluescreen, but it does freeze.

    Cruise
    Wednesday, September 5, 2007 6:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The bad pool header error can be caused by undervoltage (bad power supply), a driver conflict (try turning off the USB printer during a backup), bad memory, a corrupt registry entry or a filesystem problem. You mentioned that the floppy drive light is always lit when this error occurs, out of curiosity have you disabled the floppy drive or unplugged it altogether to see if it may be a floppy or floppy controller issue?

    Wednesday, September 5, 2007 7:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    Just maybe something to do with the HP Multifunction - it generates driver problems on other XP machines - usually after the computer has accessed the printer for one function or another. The main problem I've seen, have been when using the scanner portion, but I've no idea why.

    Recently,on one machine, stopping the HP devices loading at startup cured the problems, but on an identical machine in the same house and on the same network, only removing the software and re-installing it, made any improvement.

     

    Sorry not to be more help, but it might help you isolate it.

     

    Colin

    Wednesday, September 5, 2007 7:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I mentioned the floppy drive light as this is the point where the computer locks each time (with or without bluescreen). The blue screen has happened twice, but the lockup/freeze is each time it tries to backup after running and being used each day. I really don't feel it's realated to the floppy as I use it occasionally and have seen no other problems with it.

    When WHS starts the backup, the computer appears to unload processes that might be running at the time. I wish there was more info available on the bakcup activities that WHS has the PC do prior to and during backup. That info seems to be fairly scarce. The only other thing I have failed to mention previously, this PC is wireless. I have found an updated driver for the D-Link wireless card and installed today. So again, I guess another variable. but another shot at it too.

    Cruise
    Wednesday, September 5, 2007 8:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I will try to disable/shut off the HP printer and see if that helps if the wireless updated drivers don't help. If I donly do one thing at a time, it could be a long process. So, for today, I have replaced/ rebuilt the pagefile and updated the network card drivers. Will see how it goes.

    The last thing will be to shutdown the HP printer and unload the software to see if that makes a difference if the previous two items don't help.

    I have one ace, I will also try auto shutdown/restart of XP nightly if I have no sucess with the drivers etc. Probably should have done that first to save a few more gray hairs...........

    Cruise
    Wednesday, September 5, 2007 8:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Once again, backup failed. So rather than screw around any more with this PC, I have installed AutoShutdown and have it set to reboot the computer at midnight every night. Backup is scheduled at 1 AM. Unless that fails, let's call this closed/answered. I'll give one more update tomorrow.

    Cruise
    Thursday, September 6, 2007 9:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Could you try another Wireless card and see if you still get this error?

     

    Friday, September 7, 2007 1:12 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I don't have a spare wireless card right now, so I can't try swapping it out. I can however mask whatever the problem is by using AutoStart and rebooting the computer automatically before WHS does the backups. I set it up and tried it last night after running the computer all day and magically, I had a complete good automatic backup this morning. First time I have not had to manually backup or do manual restart in order for it to complete sucessfully. It just doesn't seem to be worth the effort to swap parts in and out and take a chance on screwing the rest of the system up when a simple tool like that can make it a forgotten (hidden) problem.

    I appreciate the input from all of you. And yes, I will be purchasing WHS when it is available in the US. It is more money (from what I've seen so far) than I really wanted to spend, and I think if MS were to drop the price it would really interest a lot more home users. I digress, but it doesn't hurt to voice an opinion when the chance arises.

    Thanks,
    Cruise
    Friday, September 7, 2007 8:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
     Marc Moon wrote:

    The bad pool header error can be caused by undervoltage (bad power supply), a driver conflict (try turning off the USB printer during a backup), bad memory, a corrupt registry entry or a filesystem problem. You mentioned that the floppy drive light is always lit when this error occurs, out of curiosity have you disabled the floppy drive or unplugged it altogether to see if it may be a floppy or floppy controller issue?




    I have been having the same

    "BAD_POOL_HEADER stop 0x00000019, 0x00000020, 0xE115E500, 0xE115E5F8, 0x0C1F0201"

    bsod error for about a month. This started after I installed an Asus a8n-sli deluxe motherboard. I have tried using 2 different power supplies, one 700w with 18a on the 12v rail, another 420w with 15a on the 12v rail. I have used 3 different sets of memory modules, 1gb (512x2, dual channel), 2gb (1gb x2 dual channel) and 2gb (4x512 dual channel). I have tried 2 different video cards, nvidia 7950 gt with 512mb of video ram, nvidia 5200 with 128 mb of video ram. I have tried 2 different hds, 1 from western digital and 1 from maxtor, both ide. I am currently using an amd 64 x2 3800+ with a zalman cnps9700 ultra quiet cpu cooler. I have 4 fans moving airflow from the bottom front of the case to the top rear and out the case.


    I get this error every time I try to install windows xp pro. I get through all of the windows install and, as soon as the windows xp splash screen comes up, it blue screens. I have never been able to get through the install, nor start windows xp. The bios says it is version 1303, but I cannot figure out how to flash it w/o having an os. Please help!
    Monday, August 25, 2008 1:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Ignoring the post immediately above mine...

    I have a similar problem as the original poster, a client PC that goes into a BSOD state during the backup process to my WHS. I have only had this problem on this particular computer and it is specifically the backup process that causes it. If I uninstall the WHS connector, my computer does not BSOD. I happened to be using the computer last night during the regulalry scheduled backup time and I postponed the backup once and later noticed heavy disk activity and found that a backup was in progress that completed without a problem. I have done manual backups previously and they also work without a problem. The problem occurs when my computer is in a standby state and a backup is initiated automatically.

    I have all my drivers and software updated. All my other comptuers backup fine, my WHS operates flawlessly.
    Monday, December 15, 2008 2:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Kiwi_in_KC said:

    Ignoring the post immediately above mine...

    I have a similar problem as the original poster, a client PC that goes into a BSOD state during the backup process to my WHS. I have only had this problem on this particular computer and it is specifically the backup process that causes it. If I uninstall the WHS connector, my computer does not BSOD. I happened to be using the computer last night during the regulalry scheduled backup time and I postponed the backup once and later noticed heavy disk activity and found that a backup was in progress that completed without a problem. I have done manual backups previously and they also work without a problem. The problem occurs when my computer is in a standby state and a backup is initiated automatically.

    I have all my drivers and software updated. All my other comptuers backup fine, my WHS operates flawlessly.



    Is the BSOD message the same as the message in this thread? "BAD_POOL_HEADER stop 0x00000019, 0x00000020, 0xE115E500, 0xE115E5F8, 0x0C1F0201" or are you receiving a different BSOD message?

    If not, please start a new thread as this thread has been marked as answered and pertains to a specific BSOD.  Also, please include what operating system the client that BSOD's is running if you start a new thread.
    Thank you
    Lara Jones [MSFT] Windows Home Server Team
    Monday, December 15, 2008 4:49 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    How do you hack windows 7
    ??????????????????
    nobody will ever now...........................
    Tuesday, November 24, 2009 1:43 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Okay everyone

    Here is the solution

    http://www.techsupportforum.com/microsoft-support/windows-xp-support/225647-solved-bad-pool-header-bsod-when-using-retrospect-carbonite.html

    http://www.techspot.com/vb/topic94820-4.html

     

    And I found this all on experts exchange.

    Peace-

    • Proposed as answer by jc031699 Monday, April 5, 2010 1:27 AM
    Monday, April 5, 2010 1:22 AM