Sign in with
Sign up | Sign in
Your question
Closed

I can't fix windows xp because of Bad Pool Caller Error Screen! Help

Last response: in Windows XP
Share
July 8, 2009 12:15:44 AM

I was initially testing out a faulty out a faulty PSU and got the problem rectified, I then proceed to shut down the computer to screw up a working PSU. After doing that, I boot up my computers but half-way through, I accidentally made a hard contact with one of the PSU cable and windows stalled so I had no choice but to turn off my computer in an improper way. But just when I was booting up to windows this error message appeared!

Problem:
You turn off your computer one day and then go to restart to find an error message that says:

Windows could not start because the following file is missing or corrupt
C:\windows\system32\config\system

You can attempt to repair this file by starting windows setup using the original setup CD-Rom. Select "r" at the first screen to start repair. Do NOT use an OEM "Recovery Disc". Only a valid Windows XP media will work or a disc from the OEM that says "Operating System" may sometimes work depending on how the manufacturer labeled the CD.

I knew immediately that the improper shutdown had caused one of the windows file to be corrupted so I proceed to insert my windows xp cd and when I tried reinstalling windows or go to the recovery screen this "Bad Pool Caller" error screen popped up which stopped me from fixing the corrupted file!

There is no way I could boot up windows because of the corrupted file and when I attempt to fix it or try to reinstall windows this "Bad Pool Caller" error screen prevents me from doing that! My computer is as good as dead now!

I done research for hours on another computer which is obviously not mine about to fix this blue screen error so I can start fixing the corrupted file and get windows running again! I also tried removing all pci cards, usb devices, vid card and left only my mouse, keyboard, onboard graphics, cd-drive, harddrive and monitor up and running and also disabling any removable and usb devices in my BIOS and testing out my ram which I found nothng wrong with it. I spent hours doing all these but to no avail. This error screen still prevented me from either fixing the corrupted file or reinstalling windows. I had tried everything and there;s nothing I can do right now to run windows. I need your help as too much important work projects are stored in my harddrive and I can't afford to lose them.

July 8, 2009 12:39:09 AM

I'm not sure if this has been tried, will work or how far the PC goes into the boot process.

Reboot the PC and tap the F8 key like you are going into safe mode. Instead of safe mode select the option to restore to the last known good configuration.

You may have to slave the HDD to another PC and recover all the files this way. It's a pain but should be doable.
July 8, 2009 12:47:05 AM

I had tried all that but the c:\windows\system32\config\system error even it attempts to boot in safe mode or go from the last known good configuration. The only way out is to reinstall windows or to fix the file but there is no way i can do that as the Bad Pool Caller screen prevents me from doing all that! I'm at no wits' end now!
Related resources
July 8, 2009 2:25:38 AM

I'm thinking that maybe using a Linux live CD that you should be able to replace the file.

I'm not too familiar with Linux distros although I have played around with a few different live CDs.

This way at least you will be able to boot into an operating system running in RAM. I know you can access the windows file structure with Linux, so there might be a way to copy a replacement file.

I'm going for a gander online to see if this has been done before.
July 8, 2009 5:59:31 AM

btk1w1 said:
I'm thinking that maybe using a Linux live CD that you should be able to replace the file.

I'm not too familiar with Linux distros although I have played around with a few different live CDs.

This way at least you will be able to boot into an operating system running in RAM. I know you can access the windows file structure with Linux, so there might be a way to copy a replacement file.

I'm going for a gander online to see if this has been done before.


Thanks so much! Please post more details here to help me fix this problem! I don't wish to waste money on a new harddrive!
July 8, 2009 6:19:05 AM

I'm a really lucky guy who found an old backup harddrive which is still working fine but with very limited capacity so there is nothing much I can do than to save it for basic usage!
I managed to install a fresh piece of Windows XP on it and got Windows up and running again! However, this is only a temporary fix as I had no idea how long this really old harddrive will last! OK, i need to make use of this golden opportunity right now to fix the previous harddrive corrupted file issue! Is there a way which I can copy the missing or corrupted file from this current harddrive onto the one which is already corrupted by slaving the harddrive with the corrupted file to rectify the problem? Can you provide me with some details for how I can do that? Thanks!!
July 8, 2009 7:21:52 AM

If they're IDE drives, take the jumper out of the corrupted one and set it to Slave.

Now hook it up to the PC (powered down and unplugged) with power and data cables.

Boot your PC up and it should just look for the new XP install.

Navigate through the file structure for the files you want to recover and transfer off it. I would burn them to CD or DVD to be safest, but any external device should work.

Then you can go about formatting and reinstalling the operating system to the original HDD.

I would run a HDD diagnostics test on the HDD too. Most HDD manufacturers have this utility for free to download on their website.
July 8, 2009 7:38:52 PM

My original HDD is a SATA drive and I had set it as a secondary boot disk and the temporary IDE HDD as the first boot disk in my BIOS! Will it work if I navigate to the C:\windows\system32\config folder on the IDE HDD and rewrite the entire folder onto the SATA HDD or will the problem still remain? I am afraid of doing that right as the sizes of C:\windows\system32\config files from both HDD are different and I don't want to mess up the files on the SATA HDD and make the situation worse! Plus, I had downloaded the Diagnostic Program and will my important files located in "My Documents" folder on the SATA HDD be gone during the test because the program urges me to strongly back up all my files first before proceeding and there is no way I can do that as the IDE HDD has too limited capacity! I'm waiting for your reply! Thanks!!
July 9, 2009 12:55:19 AM

Im not entirely sure what you want to do.

I assumed you wanted to retrieve all the important files off the HDD, back them up then Format and reinstall the OS and applications.

The system 32 files have registry pointers, run alot of services and basically run at the heart of the OS. Transferring these files over won't mean that the OS will be as it was on the other HDD, in fact it will probably cause i big mess.

As for the HDD diag utility, this recommendation was made so that after you back up all your important data, you could run it to check the integrity of the drive before using it with a nice clean OS.
July 9, 2009 1:33:35 AM

Look! I can't even reinstall windows on the SATA drive because of that Bad Pool Caller error! Looking at things, I am confident that it isn't my SATA drive which is faulty as I can still access those files without any lags as a secondary drive so I can be positive that it was the corrupted file which cause this big 'mess' to occur! The solution is to of course reinstall windows but I'm not able to do it because I received that Bad Pool Caller error when my Windows XP disk try to access my harddrive!
I had consulted a qualified technician about the problem and he suggested I take my system to let him fix it as he had mentioned to me that I may make the situation worse by trying to fix something I'm not familiar with! The reason why I post it here is that I may find someone who can offer me suggestions to fix this 'crap' so that I can save that hard-earned money to let someone fix it! Anyway, I appreciate that you are trying your best to picture my problem and help me fix it! Thanks a lot for that!
Lastly, any more final suggestions you can think of to help me fix this 'crap' before I have to spend $$ to let an expert fix it?!
July 9, 2009 8:52:58 PM

I think I had got part of the problem solved now! I guess it may have to do with my RAM overall which had started to get faulty! I tried taking out one of my two RAM chips and I'm able to get to the Windows Recovery Console booting from the SATA drive but I'm still not able to reinstall Windows as that Bad Pool Error screen reappears which I suspect may be also due to the only piece of RAM I'm using is starting to go bad! I will do an RMA for my RAM chips and see if I'm able to reinstall windows! Otherwise, I can conclude that the problem lies in the SATA drive which had some bad sectors which are unrepairable as the chkdsk test on the Windows Recovery Console detected some errors! If that is the case, I will just have to part with some cash to get a new harddrive!
September 3, 2009 3:58:27 AM

Hello, I am having this exact same problem - almost to the letter:

- Cant boot to SATA drive, getting same "cant find C:\windows\system32\config\system" boot error
- Cant boot XP disc for a fdisk MBR, or fixboot, etc. because of "Bad Pool Caller" BSOD
- Added small IDE HDD (10GB) and loaded XP no problem. I can access and control every part of the SATA drive from new IDE HDD. I also ran a windows chkdsk on the SATA HDD and found no errors.

I do not buy this RAM issue that nakedtons says that he/she has. If it was RAM, I couldnt use the computer anyway, let alone boot the XP disc to install an OS on the IDE drive the exact same way as I would for the SATA. I am fairly sure this is a driver issue for the SATA controller (many computers 5 years ago or so didnt have the newer SATA controllers integrated into the north or south bridge -- cant remember which off the top of the head). So, Ive looked for drivers to slipstream into my XP install and cant find any that will work for my computer. How do I solve this problem? Can I fixboot or fdisk the MBR of my SATA drive while I am booted from my IDE drive install? I dont have any spare hard drives large enough to back up my data, and I really really really would prefer not to reformat (even if i cant reformat as it is now). Thanks
September 11, 2011 5:57:47 PM

schlick said:
Hello, I am having this exact same problem - almost to the letter:

- Cant boot to SATA drive, getting same "cant find C:\windows\system32\config\system" boot error
- Cant boot XP disc for a fdisk MBR, or fixboot, etc. because of "Bad Pool Caller" BSOD
- Added small IDE HDD (10GB) and loaded XP no problem. I can access and control every part of the SATA drive from new IDE HDD. I also ran a windows chkdsk on the SATA HDD and found no errors.

I do not buy this RAM issue that nakedtons says that he/she has. If it was RAM, I couldnt use the computer anyway, let alone boot the XP disc to install an OS on the IDE drive the exact same way as I would for the SATA. I am fairly sure this is a driver issue for the SATA controller (many computers 5 years ago or so didnt have the newer SATA controllers integrated into the north or south bridge -- cant remember which off the top of the head). So, Ive looked for drivers to slipstream into my XP install and cant find any that will work for my computer. How do I solve this problem? Can I fixboot or fdisk the MBR of my SATA drive while I am booted from my IDE drive install? I dont have any spare hard drives large enough to back up my data, and I really really really would prefer not to reformat (even if i cant reformat as it is now). Thanks



Did you ever get this problem completly fixed??

SWS
December 28, 2011 8:44:14 AM

Yes, it was fixed! It was a RAM problem! Things went back to normal after I received new RAM!
January 14, 2012 7:00:52 PM

btk1w1 said:
I'm not sure if this has been tried, will work or how far the PC goes into the boot process.

Reboot the PC and tap the F8 key like you are going into safe mode. Instead of safe mode select the option to restore to the last known good configuration.

You may have to slave the HDD to another PC and recover all the files this way. It's a pain but should be doable.

How do I slave the HDD to another PC? :pfff: 
February 15, 2012 3:32:01 AM

I had the same problem of Windows XP getting a BSOD with a BAD_POOL_CALLER xC2 error and I was not able to use the Windows XP CD to repair Windows or get into Recovery Console. After trying many things suggested on various web pages I found that my problem was not a hardware problem but rather corrupted registry files. I stumbled upon a relatively simple fix that completely cured my problem.
1. Obtain a copy of the excellent Hiren's Boot CD which should be in everyone's possession - http://www.hirensbootcd.org/download/
2. Unzip and burn an ISO copy to a DVD
3. Boot from the DVD
4. Select the Mini Windows XP option
5. Select the HBCD Menu then select Browse Folder
6. The left-hand pane will show your various devices so choose the hard drive that is causing the problem - typically C:
7. Expand the files on the drive and open the WINDOWS\system32\config folder.
8. Rename the following files to have a suffix like .xxx. This is in the rare case that you might want to restore the original files. Ensure that you are renaming the files that have no suffixes on them.
Rename default to default.xxx
Rename SAM to SAM.xxx
Rename SECURITY to SECURITY.xxx
Rename software to software.xxx
Rename system to system.xxx
9. From the left pane, scroll up to open the System Volume Information folder
10. There should be a folder that starts with _restore. Open that folder and scroll down and open the next to the last folder that starts with RP. These are system restore folders. On my system the last RP folder is RP1704 so I want to open RP1703.
11. Open the Snapshot folder and you will find four files that start with _REGISTRY_MACHINE and one that is named _REGISTRY_USER_.DEFAULT.
12. Highlight these five files, right click and select copy.
13. Go back to the WINDOWS\system32\config folder and paste the five file into the folder.
14. Individually right click on each of the five _REGISTRY files that you just pasted and select Rename.
Rename _REGISTRY_MACHINE_SAM to SAM
Rename _REGISTRY_MACHINE_SECURITY to SECURITY
Rename _REGISTRY_MACHINE_SOFTWARE to SOFTWARE
Rename _REGISTRY_MACHINE_SYSTEM to SYSTEM
Rename _REGISTRY_USER_.DEFAULT to DEFAULT
15, You are through. Shutdown Hiren's and reboot the computer. My BSOD problems were cured and hopefully yours will be also. At this point you should be able to go into System Restore and restore to any restore date that you wish however the latest one was sufficient for me. Good luck.
January 22, 2014 6:52:56 AM

MMCLR.....

Thank you so much.....it worked like a charm.
!