janshim
asked on
Win2KPro-Bad_Pool_Caller
Hi there,
My home P4 2.8GHz, 1GB RAM, 60GB WD HD PC running Windows 2000 Pro (SP4) has developed an intermittent blue screen whenever it shuts down. The error is a STOP 0x000000C2 Bad_Pool_Caller and I've investigated much of this on the internet. I've not yet found one that's caused during a shutdown with most if not all happening during an OS install/upgrade. The computer is directly attached to a HP LaserJet 1200 so there isn't the documented issue with a Print Server that seems to be causing the STOP error. Mainboard is by Taiwan manufacturer, CHAINTECH and running the latest BIOS. OS is running latest Service Pack 4. I haven't a clue what else to look for.
Jan Shim
My home P4 2.8GHz, 1GB RAM, 60GB WD HD PC running Windows 2000 Pro (SP4) has developed an intermittent blue screen whenever it shuts down. The error is a STOP 0x000000C2 Bad_Pool_Caller and I've investigated much of this on the internet. I've not yet found one that's caused during a shutdown with most if not all happening during an OS install/upgrade. The computer is directly attached to a HP LaserJet 1200 so there isn't the documented issue with a Print Server that seems to be causing the STOP error. Mainboard is by Taiwan manufacturer, CHAINTECH and running the latest BIOS. OS is running latest Service Pack 4. I haven't a clue what else to look for.
Jan Shim
ASKER
What I've done so far:
* re-installed Service Pack 4
* downloaded and installed Chaintech's latest S3 ProSavage video drivers (the ones from S3's own website repeatedly failed to install)
* downloaded and installed Chaintech's latest USB 2.0 drivers, not that they are new but to eliminate chance of driver corruption
So far no problems seen after 5 Shutdowns. But noted that the problem had been intermitten so I'm monitoring this closely.
* re-installed Service Pack 4
* downloaded and installed Chaintech's latest S3 ProSavage video drivers (the ones from S3's own website repeatedly failed to install)
* downloaded and installed Chaintech's latest USB 2.0 drivers, not that they are new but to eliminate chance of driver corruption
So far no problems seen after 5 Shutdowns. But noted that the problem had been intermitten so I'm monitoring this closely.
well at least you've gotten that far, sounds like a plan to me
ASKER
Win2000 problems are completely new to me. I skipped a generation when I switched from Win98SE to XP Pro and haven't looked back since. I have been tuning and tweaking XP almost since it was released and needless to say, crashed it many times because I didn't know when to stop, always pushing performance tuning to the very edge. Each lesson had cost me several nights of restoration work because of my customised OS! And then there's this Bad_Pool_Caller problem that appeared out of the blue (no pun intended) and I hadn't even touched the machine (tweaking and what not).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Alright, after monitoring ths situation for 3 days and countless number of Shutdowns laters .. I conclude the steps I had taken earlier to have worked. Except for one moment of oversight, I was so thrilled about the progress I enabled all the feature sets in the BIOS including Shadow RAM that should have remain Disabled. This prompted another case of Bad_Pool_Caller error. My bad ... after disabling this, all is OK once again.
ASKER
Problem is back and we've seen this twice, after printing. You could go through a week of shutdowns and there would be no incidence of Bad_Pool_Caller but the minute you start sending prints to the HP LaserJet 1200, the followin Shutdown is affected. I originally had the PC print to a Linksys Print server driver but after reading information from various sites including Microsoft's I switched over to parallel cable connection. Even then, it didn't help .. any ideas ?
have a look here http://www.aumha.org/win5/kbestop.htm
hope this helps