I was having problems with XP so I wanted to reinstall it. I started with the installation CD and about 10 min. into the install it would stop the blue screen would appear with the message "
"BAD_POOL_CALLER" It then tries to walk you through the process to recover .
The instructions tells you that If this is the first time you've seen this stop error screen restart your computer. If this screen appears again, follow these steps.
Check to make sure any new hardware or software is properly installed. If this new installation, ask your hardware or software manufacturer for any windows updates you might need.
If this problem continues, Disable or remove any newly installed hardware or software. Disable Bios memory options such as caching or shadowing. If you need safe mode to disable components, restart your computer, press F8 to select advance start up options and then select safe mode.
This message with this code was also on the blue Screen.
The BIOS options you mentioned aren't available in a Dell BIOS and are already disabled by default. Your best course of action would be to post your problem in the
Software - Windows XP forum which would be a more appropriate venue in which to get an answer. Compared to the BIOS forum, the XP forum is a very busy place and visited by some very knowledgable people. You shouldn't have to wait long for a reply.
Click here for a direct link to that forum.
Regarding a memory error message "BAD_POOL_CALLER" and a hexadecimal address codes followed after “STOP:” with BSOD, the cause appears to be an incompatible or outdated device driver. Refer to this Microsoft Knowledge Base article ID: 309155-- http://support.microsoft.com/default.aspx?scid=kb;en-us;Q309155
After safe mode boot, if possible, run Msinfo32.exe to diagnose the issues you are encountering. If you want to do so, click
Start, click
Run, type msinfo32.exe in the
Open box, and then click
OK. For example, categories you may look for in first place will be Hardware Resources, Conflicts/Sharing, Problem Devices and so on.
Also, you may want to check Event logs in Event Viewer.
Best wishes for identifying the culprit.
Fumiaki Kawashima
Tokyo
Message Edited by F_Kawashima on 01-24-2005 09:43 AM
Majestic
2 Intern
•
9371 Posts
333
0
Posted January 18th, 2005 16:00