Sign in with
Sign up | Sign in
Your question

Bad Pool Caller error

Last response: in Windows XP
Share
Anonymous
March 7, 2005 1:51:32 AM

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Trying to start Windows XP, I get the Blue Screen error that says "Bad Pool
Caller." It says
STOP: 0x000000C2 (0x00000060, 0x00000000, 0x00000000)

I have SP 2, and have for a long time before this started happening. No
recently installed software or hardware, either.

System Restore won't come up for me, and I can only start in safe mode.
Would love a solution that doesn't result in resorting to the total system
recovery, blanking out all my data.

More about : bad pool caller error

Anonymous
March 7, 2005 11:11:11 AM

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

A bad paging file for virtual memory is often the cause of that error. I would suggest an intensive check of the disk for errors.

Boot to the XP setup CD, and press 'r' for recovery console, run the command : CHKDSK /R

--

Mark L. Ferguson (NOT an MS-MVP)
FAQ for MS Antispyware version 1.0.509
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
marfers notes for windows xp http://www.geocities.com/marfer_mvp/chatNotes.htm
..
"John S" <John S@discussions.microsoft.com> wrote in message news:3CE1DA06-32E5-483A-85CB-EF838780AD1C@microsoft.com...
> Trying to start Windows XP, I get the Blue Screen error that says "Bad Pool
> Caller." It says
> STOP: 0x000000C2 (0x00000060, 0x00000000, 0x00000000)
>
> I have SP 2, and have for a long time before this started happening. No
> recently installed software or hardware, either.
>
> System Restore won't come up for me, and I can only start in safe mode.
> Would love a solution that doesn't result in resorting to the total system
> recovery, blanking out all my data.
Anonymous
March 9, 2005 2:11:02 AM

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

I have run the chkdsk, but the BSOD still comes up. Any other suggestions
would be much appreciated.

"Mark L. Ferguson" wrote:

> A bad paging file for virtual memory is often the cause of that error. I would suggest an intensive check of the disk for errors.
>
> Boot to the XP setup CD, and press 'r' for recovery console, run the command : CHKDSK /R
>
> --
>
> Mark L. Ferguson (NOT an MS-MVP)
> FAQ for MS Antispyware version 1.0.509
> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
> marfers notes for windows xp http://www.geocities.com/marfer_mvp/chatNotes.htm
> ..
> "John S" <John S@discussions.microsoft.com> wrote in message news:3CE1DA06-32E5-483A-85CB-EF838780AD1C@microsoft.com...
> > Trying to start Windows XP, I get the Blue Screen error that says "Bad Pool
> > Caller." It says
> > STOP: 0x000000C2 (0x00000060, 0x00000000, 0x00000000)
> >
> > I have SP 2, and have for a long time before this started happening. No
> > recently installed software or hardware, either.
> >
> > System Restore won't come up for me, and I can only start in safe mode.
> > Would love a solution that doesn't result in resorting to the total system
> > recovery, blanking out all my data.
>
>
>
Anonymous
March 9, 2005 3:21:18 AM

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Try disabling services like antivirus or anything else that
might have components running in kernel mode.

Can you boot into VGA mode? What about safe mode
with networking?

If you can see the network, make sure you have Windows
Error Reporting enabled. After you reboot from the crash
you will be prompted to submit an error report. This will
tell you if it's a known problem.

"John S" wrote:

>I have run the chkdsk, but the BSOD still comes up. Any other suggestions
> would be much appreciated.
!