• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Startup Woes

So I was starting up my computer today, when suddenly instead of the WinXP loading screen I get a screen telling me that one of the windows system files is missing or corrupt. It also forwarded me to get to the setup screen by booting up my computer with the WinXP CD in. So I did, except when I try to repair via the recovery console, or try to re-install windows all together, I get a blue screen. It says "A problem has been detected and Windows has been shut down to prevent damage to your computer. BAD_POOL_CALLER" I believe this is called a STOP screen?

I have no idea what to do, I really don't want to re-install windows or format my hard drive because I have information on there that I actually need, but it seems like even that's not an option because I keep running into this blue screen. Can anyone give me any advice on what to do? Thank you very much for your time and attention.
 
I googled bad pool caller and got this:

If you are getting this error message first diconnect the printer and network cable. After that disconnect all USB devices.
Then Restart your computer and go to BIOS set all USB devices to no boot.

You will not get that error messages again.

There also might be getting that message from bad memory??? This was also in some quick googling. Might as well give it a shot.
 
Give us some system/rig specs. Especially PSU.

D/l and run memtest. May have some bad ram in there.

Fern
 
Thank you so much for the responses. Sorry that I was slow about getting back but I suddenly became very busy.

I did some more diagnostics and found out that the hard drive was faulty. I've RMA'd it. So if anyone has this problem in the future, try using a different hard drive and see if it works.
 
Back
Top