Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

XP Pro SP3 getting bsod at shutdown

Status
Not open for further replies.

onebigdog

Technical User
Jan 16, 2003
65
US
I have XP Pro SP3 and am getting a bsod at shutdown.
When I shut down the computer it goes through its normal shut down procedures, although much slower than before. Once the Windows shutting down screen goes blank, I will see a quick BSOD before the computer starts to reboot again (remember…I was shutting the computer down for the night).
Using my video camera I captured the screen. It is a Bad_Pool_Header error with a stop 0x019 error.
I tried the Verify.exe program in System32 but it just causes a bsod at bootup and just stays in that loop. I don’t understand what it was suppose to be doing for me to figure out what driver is causing the problem.

Any suggestions?
 
0x00000019: BAD_POOL_HEADER

A pool header issue is a problem with Windows memory allocation. Device driver issues are probably the most 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.)
source: aumha.org

So, check the drive for issues, e.g. run CHKDSK /R from the CMD Prompt, on all partitions...

run the drive manufacturers diagnostic utility on the drive...

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."
 
Thanks for the suggestion.
I ran chkdsk /r and if found and replaced a bad cluster in file 155351 of name \system~1\_restore{7375869F-EA65-45DC-8D20-652DAAF74F49}\RP15\snaps hot\_REGISTRY_MACHINE_SOFTWARE.

I have no idea what that was or whether that was the cause or not of my bad_pool_header BSOD at shut down. But my suspicion is that it was not the cause of the BSOD. The only reason I say that is it appears that the only time the BSOD happens is after Ghost ver 9 runs its daily scheduled image backup (Monday thru Friday only). If I turn the computer off before the backup...no problem. As a test I left the computer on all day last Saturday and turned it off without a problem.

Chkdsk also found some free space that was mismarked as allocated and fixed that as well.

I guess I will find out more tomorrow evening after a full day with an image backup.
Thanks for the help.
BD

 
That file location you mention is a System Restore restore point (number 15), this suggests that System Restore might not be 100% reliable for future use on this computer. It also suggests that the hard drive may be coming to the end of its working life, so make sure you have "usable backups" of your valuable data.

The drive manufacturer will have free diagnostic software to thoroughly check the condition of your hard drive.

For future use, you can also turn off "automatically restart after an error" so it will just halt at the fault and display the full Stop Error and blue screen.

Right-click My Computer, and then click Properties .
On the Advanced tab, click Settings under Startup and Recovery .
Click to clear the Automatically restart check box under System failure , and then click OK . The error message on a blue screen should remain on the screen so you can record the error information.
 
PROBLEM SOLVED!
Thanks to all that posted...but I had a hunch that it might be Norton Ghost (see my previous post) so I uninstalled Ghost ver 9, went into the registry and removed all instances that I could find of Ghost, went into system32/drivers folder and removed the ghost drivers and re-installed Ghost...still got the bsod, so I uninstalled Ghost 9 and installed Ghost 14 (trial). BINGO! No more BSOD at shut down. I will purchase ver 14 now.
I wish there was a program that could be run when you suspect a faulty driver is causing a BSOD, that could pinpoint the faulty driver. Anyone know of such a software product?
Onebigdog
 
HOW TO: Verify Unsigned Device Drivers in Windows XP

Debugging a DUMP file in XP
thread779-1292544

Windows Debugger, part of Never-Ending-Problem
thread779-1064535

314084 - How to gather information after a memory dump in Windows XP

315271 - How to Use Dumpchk.exe to Check a Memory Dump File

254649 - Overview of memory dump file options for Windows 2000, for Windows XP, and for Windows Server 2003

315263 - How to read the small memory dump files that Windows creates for debugging
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top