314492 How to Debug a Stop 0xC2 or Stop 0x000000C2 Error
http://support.microsoft.com/?id=314492
Typically these are related to third party services interferring.
--
Joseph W. Conway, MCSE
Windows 9x/NT/2000/XP/2003 Server Group
This posting is provided "AS IS" with no warranties, and confers no rights.
"D.Currie" <(E-Mail Removed)> wrote in message
news:bofbl6$1dgtqc$(E-Mail Removed)...
> Try loading XP clean without first loading 98. If that doesn't work, you
can
> start looking for hardware problems.
>
> "Mike Kirsch" <(E-Mail Removed)> wrote in message
> news:07fc01c3a48d$0d4e86e0$(E-Mail Removed)...
> > I have just replaced my old PII motherboard with an Asus
> > P4S800.
> > I am attempting to load WinXP Home to a newly formatted
> > harddrive.
> > After many many hours of frustration I am looking for some
> > assistance.
> > System: Asus P4S800 mb Lan and sound on board, 1.7Ghz
> > Celeron, 256mb Kingston KVR333 mem module, GeForce2 Abit
> > Siluro graphics card w/64mb, Diamond Fireport SCSI card
> > for Plextor CD and zip drive, Aopen FM56-SVV modem.
> > I have tried installing XP from the I386 directory using
> > winnt.exe to no avail. I have had success loading Win98.
> > When I try to install XP over 98 I get the BSOD before
> > installation is complete. I get as far as installing
> > windows-installing devices. About halfway through the
> > status bar of installing devices I get the BSOD. It says
> > BAD_POOL_CALLER blah blah
> > Technical Information:
> > ***STOP: 0X000000C2 (0X00000007, 0X00000CD4, 0X11111111,
> > 0X8147DC48) after reboot the last hex series is the only
> > one that changes. It changed to 0X814FFC48 then
> > 0X8144BC48, then 0X814F6C48, then 0X814F1C48. After
> > shutdown then restart it went to 0X814F3C48. At the end of
> > the message it reads: Beginning dump of physical memory,
> > physical memory dump complete.
> > I am having a physical memory dump myself.
> > Also, I modified some CMOS settings that I had read about
> > in some other threads, and this last time I did not
> > install any new drivers. New drivers or not dosen't seem
> > to make a difference. I tried running the memtest and it
> > did not appear to work correctly, blinking cursor for a
> > long period of time.
> >
> > Any help would be appreciated!!!
>
>