XP repair leading to BSOD - BAD_POOL_CALLER

  Keith4321 16:10 10 Apr 2007

Following a couple of power cuts, Windows (XP Home SP2) cannot start because \WINDOWS\SYSTEM32\CONFIG\SYSTEM is "missing or corrupt".

When I try to use the XP install CD to repair, as recommended by the error message, I get a blue screen with a BAD_POOL_CALLER message. Error code is 0x000000C2 (0x00000043,0xC3059000,0x00000000,0x00000000).

What does this mean? I've removed all PCI cards - what should I try next?

  VoG II 16:11 10 Apr 2007
  Keith4321 16:22 10 Apr 2007

Been there, but it's when I try to get into the Recovery Console as described in this article that I get the BSOD as described.

Also, slightly concerned to see in the referenced article a statement that this procedure should not be used if the computer has OEM Windows - it has!

  Graham. 16:41 10 Apr 2007
  Keith4321 17:47 10 Apr 2007

Been there too, but can't make much sense of it. As far as I can see, my "Parameter 1" is 0x43, which doesn't feature in the list. And how do I get my hands on the "Kernel Debugging tool" referred to? And if it is something to do with a driver, how can I fix it when I can't even get the PC running?

  moorie- 18:08 10 Apr 2007

could be a memory issue,is there more than one stick,so that you can try one at a time? or try pulling out/check and reseat

  Keith4321 18:18 10 Apr 2007

Only one stick, which I've pulled out and inserted into the other slot. No change. And POST memory check runs OK before first error message appears.

This thread is now locked and can not be replied to.

Elsewhere on IDG sites

Huawei MateBook X Pro review: Hands-on

The art of 'British' pulp fiction

Best password managers for Mac

TV & streaming : comment regarder le Tournoi des Six Nations 2018 ?