Results 1 to 11 of 11
  1. #1
    New Lounger
    Join Date
    Aug 2006
    Location
    St Paul, Minnesota, USA
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    BAD_POOL_CALLER (Windows XP SP2)

    I have a problem. When ever I start my computer, I get an error message (Displayed on the blue screen of death) That says I have a "BAD_POOL_CALLER."
    This comes, just a day after I installed a new RAM package. It was a Supertalent 2GB set. I would like to know if there are any known problems with that brand of memory.
    I have read that the number stand displayed with the message is important. The strand that my computer displays is *** STOP: 0x000000c2 (0x00000043, 0xc274F000, 0x00000000, 0x00000000)

    Could somebody please reply quickly, as I need to use my computer. Thank you.

    Joe =)

  2. #2
    Platinum Lounger
    Join Date
    Jan 2001
    Location
    Quedgeley, Gloucester, England
    Posts
    5,333
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: BAD_POOL_CALLER (Windows XP SP2)

    Remove the new memory. Does that improve matters? If so, I suggest you check whether it is the correct type and/or get it replaced.

    Here is a Microsoft article on debugging STOP 0xC2 messages, although if removing the new memory causes things to work again, you have your answer!

    John

    PS A thought strikes me - how much memory do you already have in the computer? If you already have 1 or 2 GB you might like to read this article.
    <font face="Script MT Bold"><font color=blue><big><big>John</big></big></font color=blue></font face=script>

    Ita, esto, quidcumque...

  3. #3
    Uranium Lounger
    Join Date
    Mar 2001
    Location
    New Jersey
    Posts
    6,684
    Thanks
    1
    Thanked 11 Times in 11 Posts

    Re: BAD_POOL_CALLER (Windows XP SP2)

    First thing I would suspect is that the memory is bad. I'd return it or replace it. Can you put back the old RAM and see if the problem persists ???
    <IMG SRC=http://www.wopr.com/w3tuserpics/DocWatson_sig.gif>

  4. #4
    New Lounger
    Join Date
    Aug 2006
    Location
    St Paul, Minnesota, USA
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: BAD_POOL_CALLER (Windows XP SP2)

    I have already done that, i suppose i forgot to mention that in my original statement. Anyway, I did replace the old memory, and that did not change the situation any.

    Joe =)

    (P.S. The old memory was a Kingston 512MB chip, and here is the link to the page that i bought the new memory from: http://www.newegg.com/Product/Product.asp?...82E16820609058)

  5. #5
    Uranium Lounger
    Join Date
    Mar 2001
    Location
    New Jersey
    Posts
    6,684
    Thanks
    1
    Thanked 11 Times in 11 Posts

    Re: BAD_POOL_CALLER (Windows XP SP2)

    So what you are saying is that when you return the machine to the original configuration it still doesn't work ???
    <IMG SRC=http://www.wopr.com/w3tuserpics/DocWatson_sig.gif>

  6. #6
    New Lounger
    Join Date
    Aug 2006
    Location
    St Paul, Minnesota, USA
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: BAD_POOL_CALLER (Windows XP SP2)

    yes.

  7. #7
    Uranium Lounger
    Join Date
    Mar 2001
    Location
    New Jersey
    Posts
    6,684
    Thanks
    1
    Thanked 11 Times in 11 Posts

    Re: BAD_POOL_CALLER (Windows XP SP2)

    I don't want to go through this one question at a time, so can you give a brief timeline of what led up to this error message and problem ??? Did the machine ever work with the new RAM installed ???
    <IMG SRC=http://www.wopr.com/w3tuserpics/DocWatson_sig.gif>

  8. #8
    New Lounger
    Join Date
    Aug 2006
    Location
    St Paul, Minnesota, USA
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: BAD_POOL_CALLER (Windows XP SP2)

    It's not something I want to do either.

    The computer worked for about a day with the new RAM.
    After I installed it, I used the computer until I went to bed that night, at which point, I shut the computer down. I had restarted it a few times during that period due to some problems with the wireless network adapter, and every time I restarted it, it booted up just fine. Then, the next day, after I got home (5 O'clock, roughly 24 hours after the initial installation of the RAM), I started the computer, and just after Windows Start-up Screen, and just before the Welcome screen, I got the blue error message screen, telling me that I had a "BAD_POOL_CALLER."

  9. #9
    Uranium Lounger
    Join Date
    Mar 2001
    Location
    New Jersey
    Posts
    6,684
    Thanks
    1
    Thanked 11 Times in 11 Posts

    Re: BAD_POOL_CALLER (Windows XP SP2)

    Unfortunately, I think that the MSKB article John linked to previously might be your best option to diagnose this problem. I was hoping that it was something obvious with your hardware, but that doesn't seem to be the case.
    <IMG SRC=http://www.wopr.com/w3tuserpics/DocWatson_sig.gif>

  10. #10
    New Lounger
    Join Date
    Aug 2006
    Location
    St Paul, Minnesota, USA
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: BAD_POOL_CALLER (Windows XP SP2)

    Well, thanks anyway.
    What I decided to do was to put in the XP disc, boot from the disc, and run the repair. So far, that seems to be doing the job well, and Windows in is in the process of repairing itself.

  11. #11
    Uranium Lounger
    Join Date
    Mar 2001
    Location
    New Jersey
    Posts
    6,684
    Thanks
    1
    Thanked 11 Times in 11 Posts

    Re: BAD_POOL_CALLER (Windows XP SP2)

    That's often the easiest and best thing to do.

    Frequently, one ends up there anyway. <img src=/S/wink.gif border=0 alt=wink width=15 height=15>
    <IMG SRC=http://www.wopr.com/w3tuserpics/DocWatson_sig.gif>

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •