Question

Locked

BAD_POOL_HEADER error

By david.girard1 ·
I've got a computer on my network right now that's really annoying me. It continues to get a BSOD with BAD_POOL_ERROR being the stop code.

Stop code: 0x00000019
Stop code message text: bad_pool_header
BSOD Hex parameters: (0x00000020, 0x85A85E48, 0x85A85E58, 0x1a020001)

We've reimaged the machine already, changed memory allocations for diskeeper (Read that could be a cause), and tried repushing software.

Just wondering if anyone out there has another idea to try, or if they've came across it themselves. Thanks!


Dave

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

Read the Dump

by BFilmFan In reply to BAD_POOL_HEADER error

Have you used the Microsoft Debugging Tools to read the Memory Dump?

http://www.microsoft.com/whdc/devtools/debugging/default.mspx

Collapse -

Couple thoughts.....

by ---TK--- In reply to BAD_POOL_HEADER error

There is a whole mess of stuff on the net regarding this error... It seems that there is no pattern with the software thats causing it... other than it appears that its an issue with a driver accessing a memory location thats already in use...
I might try changing the HDD and/or changing the RAM thats installed... B/C there is one thing in common, they all seem to say its a software issue.... yet it never gets fixed... A bad sector on the drive can cause weird issues, and if the Page File is sitting on it...
Also Bad RAM can be a real headake to diagnose, I have seen test after test done to RAM, everything checks out fine, but when we replaced the RAM the issue went away... just some things to ponder on... hopefully this helps.

Back to Hardware Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums