• WSJoenutt

    WSJoenutt

    @wsjoenutt

    Viewing 4 replies - 1 through 4 (of 4 total)
    Author
    Replies
    • in reply to: BAD_POOL_CALLER (Windows XP SP2) #1052137

      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.

    • in reply to: BAD_POOL_CALLER (Windows XP SP2) #1052121

      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.”

    • in reply to: BAD_POOL_CALLER (Windows XP SP2) #1052112

      yes.

    • in reply to: BAD_POOL_CALLER (Windows XP SP2) #1052108

      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)

    Viewing 4 replies - 1 through 4 (of 4 total)