cbaytech
asked on
BAD_POOL_CALLER on a brand new Win 2003 server.
I have recently built up a new server and have installed Server 2003 on the system. While running Windows update, the system require a reboot. Upon rebooting, the unit crashed with the BSOD. I have searched around and have seen that this means bad memory or bad drivers. I have ran Memtest on all of the memory, and they pass with flying colors. I do not know how to read the technical stop errors, so hopefully someone can help me out. The stop message is as follows:
Stop: 0x000000C2 (0x00000007, 0x0000121A, 0x00000000, 0x8B87F7C0)
Any assistance on this one is greatly appreciated.
Stop: 0x000000C2 (0x00000007, 0x0000121A, 0x00000000, 0x8B87F7C0)
Any assistance on this one is greatly appreciated.
ASKER
I guess where I am getting hung up on is that I do not know how to use the debugger that is in the article. Is that a utility that is installed with Windows?
ASKER
Any advice on how to use the debugger? The Microsoft KB article is unclear to me. Thanks.
ASKER
Ok, well I figured out how to use the debugging tool on my own. Attached is the latest minidump file which I have ran through the debugger. Thoughts??
BSOD.TXT
BSOD.TXT
ASKER
Well, it has been 3 1/2 days since I have last heard anything, so I am assuming this thread is no longer being looked at?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://support.microsoft.com/kb/265879 give some advice on identifying the driver if its a non-essential driver try disabling the device until you can source an updated driver.