Networks

Ask something
Question Locked

Blue screen in windows 2000 server

0 helpful
4 replies

by ericoduarte

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello, in the last days in a server with windows 2000 server, give to me a blue screen, with that error:

***Stop:0x000000C2(0x00000050,0xE42F2002,0x000032F2,0x10C00000)Bad_Pool_Caller

And a try too read somethink in the internet to discover where comes from that error, and some solutions talk about tou check the file: MEMORY.DMP, but i don't found that file.Who i can find and try to verify where come from the error?

4 replies

by baxenden

Usually this error relates to a driver which has been updated and is causing issues or bad RAM. If it is a driver issue you can always either do a restore to a time when it was working or use Microsoft Debug tool to find out which driver is causing the issue.

by mark

Just search the windows directory for .dmp. you may have it setup to use a mini dump instead of a full memory dump. From what I can see this is a difficult error to resolve. It could be a hardware issue with the ram or it could be the bios/OS. I would suggest researching online to see what others have found. there are about 30 different bad pool caller errors. keep track to see if you always get the same error or if it changes.

This discussion is closed to new replies.