Quantcast
Channel: VMware Communities : Popular Discussions - VMware Server Archives
Viewing all articles
Browse latest Browse all 69891

Fatal Error: BAD_POOL_CALLER

$
0
0

I'm running VMware Server build  27828.  My host is Windows XP Home and I'm running Windows XP Pro and Windows Server 2003 as VM clients.

 

After 24 hours of running without incident, this morning my machine crashed (blue screen).  Following is a summary of the error message:

 

"A problem has been detected and Windows has been shutdown to prevent damage to your computer..."

 

BAD_POOL_CALLLER

 

\*** STOP: 0x000000c2 (0x00000007, 0x000000cd4, 0xf7a15944, 0xf7a1d920)

 

\----


 

This same problem occurred while running build 24927 with the following dump:

 

\*** STOP: 0x000000c2 (0x00000007, 0x000000cd4, 0xf7a15944, 0xf7a15920)

 

\----


 

In both cases there does not appear to have been any damage caused by the crash.  Disk checks fine, all open documents recovered, etc.

 

In both cases I was running and working with  Microsoft VS 6 C++ (SP6) in th Win XP Pro client (256mb mem).  I was running SQL Server services on the Win Server 2003 (384mb mem).  I was also running and working with various Microsoft Office 2003 tools on the host.  I was running and observing Task Manager on all three systems and memory seemed to be plentiful on all systems.

 

I am very new to VMware, this is just my second week of working with it.  So, I may be doing something very stupid.

 

Any advice will be appreciated,

 

Wendy


Viewing all articles
Browse latest Browse all 69891

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>