Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

BAD_POOL_CALLER on a brand new Win 2003 server.

Posted on 2008-10-28
6
Medium Priority
?
490 Views
Last Modified: 2012-05-05
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.
0
Comment
Question by:cbaytech
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
6 Comments
 
LVL 70

Expert Comment

by:KCTS
ID: 22822635
Typically its a driver issue - make sure you have the latest drivers installed for your system.
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.
0
 

Author Comment

by:cbaytech
ID: 22822775
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?
0
 

Author Comment

by:cbaytech
ID: 22830287
Any advice on how to use the debugger?  The Microsoft KB article is unclear to me.  Thanks.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:cbaytech
ID: 22843311
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
0
 

Author Comment

by:cbaytech
ID: 22853832
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?
0
 

Accepted Solution

by:
cbaytech earned 0 total points
ID: 22879424
After fumbling around with this one, on my own, it turned out to be a corrupt UltraVNC driver.  Removed and reinstalled, tested fine.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recently, I had the need to build a standalone system to run a point-of-sale system. I’m running this on a low-voltage Atom processor, so I wanted a light-weight operating system, but still needed Windows. I chose to use Microsoft Windows Server 200…
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
This course is ideal for IT System Administrators working with VMware vSphere and its associated products in their company infrastructure. This course teaches you how to install and maintain this virtualization technology to store data, prevent vuln…
Want to learn how to record your desktop screen without having to use an outside camera. Click on this video and learn how to use the cool google extension called "Screencastify"! Step 1: Open a new google tab Step 2: Go to the left hand upper corn…

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question