//flex table opened by JP

Click to See Complete Forum and Search --> : BAD_POOL_CALLER


Mal
05-21-2002, 01:57 PM
I first got this error last night and I can't seem to get rid of it.

These are the parameters, STOP 0xC2 (0x43. 0xC2BF4000, 0x0, 0x0). I've taken everything out and can't seem to load WinXP, even in safe mode and recovery console, without getting this error. I've checked my RAM with various memory checking apps without receiving any error messages. I also have linux installed on a partition on the same drive as WinXP and it runs well. I can access and read files on my Winxp partion without any problems. I have important data on my drive so formating is a last resort.

herosrest
05-21-2002, 07:14 PM
Hi Mal.

I took this hit upgrading 512mb ecc ram to 1gig several weeks ago with Xp pro on a Compaq AP400 twin plll 700's Bx chipset scsi.
Two further sets of ram and sniffing around Compaq/ MS/ ram suppliers the consensus was hardware but l still don't actually know any more than day 1.
I got the error to jump around the mobo slots 3 to 1 but it just became a huge pain.
Linux is ok, Me is ok as single processor and Beos.
It's gotta be XP right - NO its hardware they say.
I just know l'm missing something ?????
This one is still pending for me so i'm just tagging along for the ride if hats ok.

BipolarBill
05-22-2002, 03:02 AM
http://www.google.com/search?hl=en&lr=&ie=UTF8&oe=UTF8&q=BAD_POOL_CALLER+XP

Mal
05-22-2002, 10:30 AM
Well if Windows would've loaded in any mode, I would've had a chance to solve the problem, but since it didn't I just had to re-install.