bad_pool_header

[drnkenmonkey]

wuts that supposed to mean? keep getting a BSOD... the problem was bad_pool_header...anyone?

[Yawgm0th]

You're going to have to provide a lot more information than that, if you want anyone to post anything helpful.

[Darthtanion]

Agreed. Even doing a search in the MSKB comes up with no matches for your error. We'll need a minimum of base system specs, operating system being used and the exact wording of the BSOD error message.

[drnkenmonkey]

ok... sorry... yep i couldnt find anything online so... ok when it happens again ill post everything... thx for the help

[Yawgm0th]

Post your operating system and system specifications, while you're at it...

[Darthtanion]

I thought I had asked for that, but maybe I'm mistaken?

[wayout44]

You were not mistaken.

[Darthtanion]

I know... Just being an ass.

[trickyt]

BSOD the Solution:

Did you install Service Pack 2? Are you now suffering from the Blue Screen of Death (BSOD)?. Here is the solution. I have spent 4 days hunting down the cause of my machine crashing and have finally cracked it. Maybe other people have a different cause than mine so my solution may not work for everyone.

After installing SP2 I suffered many crashes. In particular the Screen would turn blue and display a message starting "Bad_Pool_Header". And ending with STOP: 0X000000019....

Then my four day hunt for the cause started.

BSOD Solution
Basically I found two causes of the BSOD.
Cause 1: Corrupted file or folder.
Cause 2: Microsoft Indexing Service

Possibly these two causes are linked.

Solution for Cause 1
Onen up Explore (right click the start button), and expand your directory tree, starting from the C: drive. Click on each folder in turn and see if any cause the BSOD to appear. If so, reboot, and simply attempt to copy the folder, and then delete it.

Solution for Cause No 2
Switch off Microsoft's indexing service. You can do this by clicking the start button, select "Run", then type "msconfig", then select the "Services" TAB, scroll down to the Indexing Service and Switch it off. Reboot your computer, and good luck - maybe it will work, It solved the problem for me.

At first I thought I must have a third party software or hardware conflicting with SP2, but even after I had disconnected the internet, switched off all items in the startup TAB of msconfig, was still getting the BSOD. I tried surface scans, chkdsk, scan disk etc all to no avail. I tried defragmenting the disk, but the frequent crashes may have made things worse.

I discovered the computer was now crashing after about 7.5 minutes of being switched on. It did not matter whether anyone logged in or not.

Finally I went to msconfig (Start Run, MSCONFIG) and switched off "process System.ini files, Load System files, Load Startup Items. And the comuter stopped crashing. So then I added the item back one by one until I discovered the Microsoft Corporation Indexing Service which was causing the crash. I switched it off and switched everything else back on and AT LAST... No more BSOD

[Yawgm0th]

It's better to do it through services.msc. I would recommend disabling the Indexing service even if you don't have SP2.