K
kes
I am running on Win XP Pro (SP3) ona DELL Dimension.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
P
Peter Foldes
0x00000019: BAD_POOL_HEADER
A pool header issue is a problem with Windows memory allocation. Device driver
issues are probably the msot common, but this can have diverse causes including bad
sectors or other disk write issues, and problems with some routers. (By theory, RAM
problems would be suspect for memory pool issues, but I haven’t been able to confirm
this as a cause.)
http://msdn.microsoft.com/en-gb/library/ms793223.aspx
http://msdn.microsoft.com/en-us/library/aa489507.aspx
STOP: 0x00000019†error message on Windows Server 2003 {KB 892260} Server 2003 (NTFS
problem corrected in current Service Pack)
a.. Error message when a Delayed Write Failure event is reported in Windows Server
2003: “Stop 0x00000019 - BAD_POOL_HEADER†or “Stop 0xCD
PAGE_FAULT_BEYOND_END_OF_ALLOCATION†{KB 925259} Server 2003 (driver issue; hotfix
available)
a.. When backing up to Clarion storage in a SAN environment, Windows Server 2003 may
stop responding after restart {KB 884585} Server 2003 (caused by adding more than 20
mount points during the backup; hotfix available)
a.. When trying to control a Systems Management Server 2003 client from a remote
location, Stop error on SMS 2003 client {KB 905795} SMS 2003 (driver issue
--
Peter
Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.
A pool header issue is a problem with Windows memory allocation. Device driver
issues are probably the msot common, but this can have diverse causes including bad
sectors or other disk write issues, and problems with some routers. (By theory, RAM
problems would be suspect for memory pool issues, but I haven’t been able to confirm
this as a cause.)
http://msdn.microsoft.com/en-gb/library/ms793223.aspx
http://msdn.microsoft.com/en-us/library/aa489507.aspx
STOP: 0x00000019†error message on Windows Server 2003 {KB 892260} Server 2003 (NTFS
problem corrected in current Service Pack)
a.. Error message when a Delayed Write Failure event is reported in Windows Server
2003: “Stop 0x00000019 - BAD_POOL_HEADER†or “Stop 0xCD
PAGE_FAULT_BEYOND_END_OF_ALLOCATION†{KB 925259} Server 2003 (driver issue; hotfix
available)
a.. When backing up to Clarion storage in a SAN environment, Windows Server 2003 may
stop responding after restart {KB 884585} Server 2003 (caused by adding more than 20
mount points during the backup; hotfix available)
a.. When trying to control a Systems Management Server 2003 client from a remote
location, Stop error on SMS 2003 client {KB 905795} SMS 2003 (driver issue
--
Peter
Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.
A
Anna
kes:
Setting aside your problem with creating a disk image in connection with
your "source" HDD, i.e., your day-to-day boot drive, can we assume that
there's no other problem(s) with that disk? It boots without incident and
functions without any problems?
Are you indicating that you're able to create a disk-image backup of your
source HDD with whatever disk-imaging program you're using, but when you
attempt to restore the system to another HDD using whatever recovery/restore
process your program utilizes, it's at that point that you get the
"BAD_POOL-HEADER..." error message when you attempt to boot to the
(supposedly) restored HDD? So it's obvious that something went awry with the
disk-imaging process?
Or are you indicating that somehow the problem arises when you attempt to
create a disk-image of your source HDD with your disk-imaging program?
Although I can't quite figure out how you would get the "BAD_POOL-HEADER..."
message under those circumstances.
Since you indicate that "I am without an image backup for over a month now",
I take it (notwithstanding this disk-imaging situation) there's no problem
(at least that you're aware of) re your source HDD, right?
Anna
Setting aside your problem with creating a disk image in connection with
your "source" HDD, i.e., your day-to-day boot drive, can we assume that
there's no other problem(s) with that disk? It boots without incident and
functions without any problems?
Are you indicating that you're able to create a disk-image backup of your
source HDD with whatever disk-imaging program you're using, but when you
attempt to restore the system to another HDD using whatever recovery/restore
process your program utilizes, it's at that point that you get the
"BAD_POOL-HEADER..." error message when you attempt to boot to the
(supposedly) restored HDD? So it's obvious that something went awry with the
disk-imaging process?
Or are you indicating that somehow the problem arises when you attempt to
create a disk-image of your source HDD with your disk-imaging program?
Although I can't quite figure out how you would get the "BAD_POOL-HEADER..."
message under those circumstances.
Since you indicate that "I am without an image backup for over a month now",
I take it (notwithstanding this disk-imaging situation) there's no problem
(at least that you're aware of) re your source HDD, right?
Anna
K
kes
:
Correct. In every other respect (boot-up, defrag, disk-scan, etc) my HDD
behaves normally.
Correct. The only problem I have with the new HDD is when I attempt to do an
'image' backup of the C: drive. (I have no problem backing up individual
files, working documents, etc.)
kes:
Setting aside your problem with creating a disk image in connection with
your "source" HDD, i.e., your day-to-day boot drive, can we assume that
there's no other problem(s) with that disk? It boots without incident and
functions without any problems?
Correct. In every other respect (boot-up, defrag, disk-scan, etc) my HDD
behaves normally.
No, sorry, I am NOT saying any of the above.Are you indicating that you're able to create a disk-image backup of your
source HDD with whatever disk-imaging program you're using, but when you
attempt to restore the system to another HDD using whatever recovery/restore
process your program utilizes, it's at that point that you get the
"BAD_POOL-HEADER..." error message when you attempt to boot to the
(supposedly) restored HDD? So it's obvious that something went awry with the
disk-imaging process?
Or are you indicating that somehow the problem arises when you attempt to
create a disk-image of your source HDD with your disk-imaging program?
Correct. The only problem I have with the new HDD is when I attempt to do an
'image' backup of the C: drive. (I have no problem backing up individual
files, working documents, etc.)
K
kes
Hi Peter, thanks for pointers to the the various possibilities:
Well, I have done a 'scan disk' and as far as I can tell, the new disk has
no bad sectors or disk write issues. (I have not tried to update the HDD
device driver (Maxtor STM3320613AS) , fearing to make things worse.)
Peter Foldes said:0x00000019: BAD_POOL_HEADER
A pool header issue is a problem with Windows memory allocation. Device driver
issues are probably the msot common, but this can have diverse causes including bad
sectors or other disk write issues,
Well, I have done a 'scan disk' and as far as I can tell, the new disk has
no bad sectors or disk write issues. (I have not tried to update the HDD
device driver (Maxtor STM3320613AS) , fearing to make things worse.)
A
Anna
kes said:Correct. In every other respect (boot-up, defrag, disk-scan, etc) my HDD
behaves normally.
kes said:No, sorry, I am NOT saying any of the above.
kes said:Correct. The only problem I have with the new HDD is when I attempt to do
an
'image' backup of the C: drive. (I have no problem backing up individual
files, working documents, etc.)
kes said:Hi Peter, thanks for pointers to the the various possibilities:
Well, I have done a 'scan disk' and as far as I can tell, the new disk has
no bad sectors or disk write issues. (I have not tried to update the HDD
device driver (Maxtor STM3320613AS) , fearing to make things worse.)
kes:
I'm still not clear on how the BAD_POOL-HEADER... error message would appear
*during* a disk-imaging operation. Like millions of others I've encountered
that error message only upon a failed boot attempt. But we'll let that pass.
Anyway, you indicated in your OP that you work with DriverImage XML or the
Macrium Reflect disk-imaging programs. While I've worked with the former
program my experience with it is very limited. And I've never even heard of
the Macrium Reflect program. And you're indicating the same problem with
creating a viable disk-image is present using either program? Even though
you indicate your source HDD functions perfectly. Very strange to say the
least.
I would guess that you've heard of the Acronis True Image program and
possibly you've even worked with that program. Do you think it would be
worthwhile (just as a test) to use the ATI program? Acronis has a trial
version available so at least there would be no cost to you.
Actually, our choice as a comprehensive backup program is the Casper 5
program. However it's a disk-cloning program and does not have disk-imaging
capability so I don't know if that would be of any interest to you. In any
event a trial version of that program is also freely available from
http://www.fssdev.com in case you're interested.
I'm not at all familiar with your Maxtor HDD. From the model # you've
indicated it has a Seagate designation. Anyway, it's difficult to imagine
this is a driver issue involving the HDD but notwithstanding your internal
disk scanning exercise(s) it would be a good idea to check out the disk with
the HDD diagnostic utility you can download from Seagate (Maxtor).
Anna