Re: BSOD bad_pooler_call 0x000000c2 on XP setup
- From: "Gerry" <gerry@xxxxxxxxxx>
- Date: Mon, 5 Jan 2009 18:16:27 -0000
Mick
What advice? I have only sought information in order to see whether I
can offer suggestions.
Good communication is an art. What may be clear to one person is not
clear to another!
--
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Mick Murphy wrote:
Gerry, you normally give good advice; not this time.
No-one wants to read posts correctly here, for some unknown reason!
--
Mad Mike
Marty
Ca you please post a complete copy of the Stop Error report.
Disable automatic restart on system failure. This should help by
allowing time to write down the STOP code properly. Keep pressing
the F8 key during Start-Up and select option - Disable automatic
restart on system failure. Do not re-enable automatic restart on
system failure. Check for variants of the Stop Error message.
BAD_POOL_CALLER;
STOP BAD_POOL_CALLER ( 0x???????, 0x???????, 0x???????, 0x???????,
). What appears on the line below what is above?
Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms796120.aspx
BAD_POOL_CALLER2: BAD_POOL_CALLER
(A kernel-mode process or driver incorrectly attempted to perform
memory operations. Typically, a faulty driver or buggy software
causes this. Source: http://aumha.org/a/stop.htm
--
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Marty wrote:
Hi all,
Can someone advise on the possible cause of the above when trying to
reinstall XP SP2 from a CD over an existing install?
It happens in the graphical setup screen where it shows the steps of
installation on the left side, during installing devices/hardware.
I've read through searches it could be ram or other hardware causing
it. It started basically because the PC would freeze up when loading
IE7
and had to be end-tasked. Then on hard reboot after it became
unresponsive windows just loaded to a white screen. Tried running
SFC which accessed the XP CD quite a bit replacing files.
Tried recovery console and chkdsk/r and that ran through but no
improvement.
Any ideas on causes or possible fixes? I've read many horror stories
about this particular BSOD issue...
Many thanks in advance
.
- Follow-Ups:
- Re: BSOD bad_pooler_call 0x000000c2 on XP setup
- From: Mick Murphy
- Re: BSOD bad_pooler_call 0x000000c2 on XP setup
- From: Mick Murphy
- Re: BSOD bad_pooler_call 0x000000c2 on XP setup
- References:
- BSOD bad_pooler_call 0x000000c2 on XP setup
- From: Marty
- Re: BSOD bad_pooler_call 0x000000c2 on XP setup
- From: Gerry
- Re: BSOD bad_pooler_call 0x000000c2 on XP setup
- From: Mick Murphy
- BSOD bad_pooler_call 0x000000c2 on XP setup
- Prev by Date: Re: BSOD bad_pooler_call 0x000000c2 on XP setup
- Next by Date: Re: Weird problem... any XP network wizards?
- Previous by thread: Re: BSOD bad_pooler_call 0x000000c2 on XP setup
- Next by thread: Re: BSOD bad_pooler_call 0x000000c2 on XP setup
- Index(es):
Relevant Pages
|
Loading