I posted some other options in your first question thread. If those don't work, and you re-install windows, do not install SP3, and see if there is any difference
Have you OC'd anything? Or updated the BIOS when this started happening? Changed the ram/ram settings at all? Have you tried taking out your ram and trying one at a time? I know we covered some things in the previous posts, but need a little refresher here.
Also, after swaping the ram, try running Memtest and see if it causes any errors.
Also, install dumpchk from Microsoft. Dumpchk is located on the Windows XP CD-ROM. Install the Support Tools by running Setup.exe from the Support\Tools folder on the CD-ROM. By default, Dumpchk.exe is installed to the Program Files\Support Tools folder.
After a crash occurs, run dumpchk from the Start/Run command and post what it lists here.
Dumpchk is a little bit wierd to use, so you can also follow the steps HERE to download windows debugging tools. After downloading and following the steps for both the tools and the Symbols package, run the software and find the last minidump, they post here what it lists.
* they post here = then post here
usually it is caused by memory/ram access. Although, I've heard that it can be caused by SP3. Have you tried installing with SP2 only and playing the games? Does it still happen then?
also, have you downloaded the latest patches for those games?
I have read and heard that sometimes Microsoft Indexing servive may cause this problem on SP2 and later. You could try to disable that from startup and see if it still causes a problem...
TO do so, click on start menu and then on run. Type in the box:
services.msc
and press enter..
Find "Indexing Service" in the list and right click on it and choose properties. Then in the new box, change startup type to disabled, then click ok. Close services, and reboot the system, run the game and see if that helps..
If not, then just go back into the services.msc and change startup type back to automatic.
You've really stumped me on this one, I will continue to keep this on my list of things, and if I find updates or info, I will post here from time to time.. Hopefully something will show itself and we'll find a fix!
×
75 views
Usually answered in minutes!
Hi Psonics
I froze my XP Blue screen of death and it comes up with bad_pool_header and bad pool call when the game reboots my PC. I disabled theose features but still getting the error. Any ideas?
My card is overclocked by manufacturer to high specs (asus TOP) but every other title works fine. Even the near FEAR Preseus runs flawlessly at max settings. Its just Crysis and Quake wars that reboot the minute the title/selection screen comes up and that bad_pool comes up. Do you know what the cause of that is perhaps? Is it a 3d setting or windows Kernel fault? Apparently its windows, maybe service pack 2 related ive been told, but im running SP3
Hey Psi
Thanks for your replies.
Yeah, it still hapopens. Only with those games still. Everything else plays well. Its not SP2, it did that with a clean install. I wrote to the game manufacturers and no reply. The one said check DX9...whatever...
I downloaded the latest updates and still errors. Once in a while my PC now boots then as it loads the desktop it crashes and bad_pool_header is displayed again. WTF... I gess the only ppl that would know is microsoft now.
×