"Howard Kaikow" wrote:

> On 27 Jan 2006, I ran Win Update for the first time since, I believe, 30 Nov
> 2005.
> So lots of stuff got installed.
>
> On Feb 2 2006, I replaced my keyboard and installed MSFT Intellitype Pro 5.5
> and MSFT Intellipoint 5.5.
>
> Since then, on one day, I got a few BAD_POOL_CALLER errors when trying to
> use the icon in the  system tray to swap out a USB hard drive. THe problem
> seemed to occur only with a particular drive (all it drive 2), but not with
> the drive with which it was swapped (call this drive 1),
>
> A few hours ago, the problem repeatedly occurred trying to remove drive 2.
> I was able to power down, replace drive 2 with drive 1, reboot and then swap
> the drives, both  2 for 1 and 1 for 2.
>
> Could this be due to a flakey drive 2?
> Should I uninstall Intellipoint?
> I need to keep Intellitype Pro for the new keyboard.
>
> Any ideas what's going on?
>
> Assuming I copied the error correctly, the last time the error codes were:
>
> 0x000000C2 (0x00000040, 0x00000000, 0x80000000, 0x00000000)
> BAD_POOL_CALLER
>
> --
> http://www.standards.com/; See Howard Kaikow's web site.
>
>
>

"Adriana Viola" <AdrianaVi***@discussions.microsoft.com> wrote in message
news:05D62CA3-EC52-43E0-B3EE-28FF56F9552C@microsoft.com...
> I guess that you already done the MSFT Intellipoint driver updates, and
the
> USB ports and USB HDD driver as well.
>
> I had a similar case once, and after doing all the necessary updates
(mainly
> concerning the USB drivers), the problem was still persisting.
>
> After that, and without hope, it has been contacted the dealer in which it
> has been explained what was happening. They accepted to receive and
> substitute it for a new one. After installing the new device, the problem
> didn't repeat again.
>
> If you cannot request to substitute it, try to use just the HDD's or the
> keyboard in other computer, to try to individualize the device that is
giving
> you this error.
>
> Otherwise, you could check the dump file with Windows Debugging tool to
see
> which specific driver is giving you the blue screen.
>
> Hope these sugestions could help you in one or other way...