on the "Blue screen"

**Stop: 0x0000000c2 (0x00000007,0x000000b8a...)
Bad_pool_caller
Beginning dump of phisical memory
Dumping physical memory to disk

You would really need to contact MS support to actually "debug" the dump for
this, however I did find another case that matched up to the 3 paramaters
you included (not sure what the last two were). While the cause/solution
for their case may not be related in any way to yours, maybe luck will come
in here;
In their case, it was apparently caused by some Hummingbird software, which
required them to contact that vendor, but I don't know if you have anything
like that installed on your system or not. However with just those 3
paramaters, and without looking at the dump itself, it's almost impossible
to tell you what caused it.

DEBUGGING:
==========
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad
IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000b8a, (reserved)



--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
"Denis" <(E-Mail Removed)> wrote in message
news:011201c3db8d$ac289bc0$(E-Mail Removed)...
> on the "Blue screen"
>
> **Stop: 0x0000000c2 (0x00000007,0x000000b8a...)
> Bad_pool_caller
> Beginning dump of phisical memory
> Dumping physical memory to disk
>