0x000000c2 ERROR : BAD_POOL_CALLER

  • Thread starter Thread starter Lawrence Bishop
  • Start date Start date
L

Lawrence Bishop

I need the fix for this but microsoft wont let me have it
because my OS is OEM, what the hell does that matter,
does that now mean i have to pay them 5 pounds to get a
200k file that stops my computer randomly rebooting now?

If anyone can help me, i would much be abliged and would
return the favour...

You can email me at "(e-mail address removed)"
 
Lawrence

Well it matters because OEMs do not always provide identical versions to the
retail version and there is a corresponding reduction in cost to the end
purchaser, i.e. you. If you have not changed your hardware then contact
your OEM. If you have changed the hardware then even the OEM will refuse to
support what will then be different from the system they sold you and you'll
have to purchase a retail version of XP before MS will provide support for
it.

Unfortunately thems the breaks
Pete
 
Lawrence Bishop said:
I need the fix for this but microsoft wont let me have it
because my OS is OEM, what the hell does that matter,
does that now mean i have to pay them 5 pounds to get a
200k file that stops my computer randomly rebooting now?

If anyone can help me, i would much be abliged and would
return the favour...

You can email me at "(e-mail address removed)"
Click to expand...

Hi Lawrence,

OEM versions are often modified. If you had written something, sold it, and
the person who bought it, modified it, and sold it again, would *you* feel
obligated to help the third party when they had a problem? I thought not.

It's ok. I know you were venting. That's totally understandable. Now
about that pesky error...

The link for what Microsoft says about it:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/w2kmsgs/1159.asp
(It's filed in the Win2k section, but should still apply to XP, if that's
what you're running)

And here's a link to a site that has a pretty decent list of STOP Error
messages, and what they commonly mean (sadly, it was nearly silent on this
error, but I include it because it is generally a good resource.)
http://aumha.org/win5/kbestop.php

Based upon the gist of the message, have you considered trying your
motherboard manufacturer's website for a driver update?
Give that a shot. Also, consider searching their FAQs or User forum - if
they have them.

You may be pleasantly surprised, and only a few clicks, and a download away
from fixing the problem.

Regards
 
Back
Top