BAD_POOL_CALLER

[lonewolf]

Hi all, after getting this BSOD BAD_POOL_CALLER and not being able to boot into safe mode or anything else I decided to try a repair installation with my XP Home disk. Part way into the installation, while it says "Installing Devices" I get the following:
Eception Occurred trying to run SISInst.dll,Inst
C:\windows\sisinf\sisgr.inf
I click OK and continue on with the install until it gets to Completeing Installation and then BAM BSOD again BAD_POOL_CALLER
Any suggestions on how to fix this without doing a format and install?
Thanks
Dave

[Midknyte]

SiSInst.dll would probably be a chipset or video driver. Did you change anything on the system before this happened?

How old is this system? I normally run a hard drive diag, memory test, and check for bad caps before trying to troubleshoot software. Otherwise, you could be wasting a lot of time on software when it's really bad hardware.

If the cpu fan/heatsink are dirty, it could also be a temp problem.

Note that when you run a repair install, it should be with a disc of the same SP level. I.E. if you have SP3 installed, then it should be an XP SP3 CD.

[lonewolf]

Nothing was changed on the board before this happened.
It's pretty old about 10 years.
The temp is fine well within normal parameters
The disc I used has SP2 on it. It's what came with the computer when I bought it. But I have updated to SP3 since then. I don't think there is a Win XP disc with SP3 on it?
I'm pretty sure its a graphic driver problem, during install before the Exception error the screen went blank 4 or 5times like it was installing the driver for the graphics chip.
Actually I popped in a 40gb drive I had here and did a fresh install on it and it works just fine.

[Midknyte]

I don't think there is a Win XP disc with SP3 on it?

Then you would have to slipstream an SP3 disc.
http://www.simplyguides.net/guides/u...streamer.shtml

Actually I popped in a 40gb drive I had here and did a fresh install on it and it works just fine.

It's quite possible that the old drive was going bad. Oh well. I'd run a diag on that drive before I'd use it again.