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 MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BAD_POOL_CALLER

Status
Not open for further replies.

aich69

Technical User
Apr 23, 2004
588
GB
I have an XP machine that during boot was blue screening with a BAD_POOL_CALLER 0x0C2 message. The machine wouldn't boot into safe mode so was basically inaccessable.
I decided to do a repair install of XP. As it reaches the 'completing installation' phase of the install....it blue screens, possibly the same error but too fast to see.
I have checked the RAM, and that's good, I have removed all PCI cards from MOBO and replaced the AGP card with one I know to be good, I have disabled all onboard devices (ones I can do without)....all to no avail.
Anybody have any suggestions as to where to go next?

Any ideas greatly welcomed and appreciated.
 
Stop 0xC2 or BAD_POOL_CALLER

Have you tried stopping, if you have it, any Bios virus scanning? Setting the Bios to Safe Defaults, or updating it?

Might be a job for the Repairer, things like CPU and Motherboards come to mind, I hope I'm wrong, I usually am.
 
Hey linney....

No BIOS virus scanning is operating. Haven't tried BIOS to Safe Defaults... good call. Unfortunately, in this instance...I am the repairer... and I think you could be right about MOBO... I had this machine about a year ago after the onboard NIC gave up the ghost. Maybe it's on a slow self distruct?!

Thanks for the input.

aich69



(I beg to differ on the 'wrong' comment...you've come to the rescue before.)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top