Bluescreen errors:"windows root\system32\hal.dll" is either missing or corrupt.", PAGE_FAULT_IN_NON_PAGED_AREA (0x00000050), BAD_POOL_CALLER (0x000000C2).

Question

Original title: blue screen on startup regardless of startup mode and at a real loss

Hi,

My PC went off as a result of a power cut and now when i try to load the PC it goes to advanced startup menu but no matter which selection i go for I get a BSOD pop up really quickly and then the computer restarts. I have tried to use XP emergency recovery boot disc and it says that a file "<<windows root\system32\hal.dll" is either missing or corrupt. I have tried the XP setup disc and when I try the recovery console it only gives me my d:/ and when i select that I get a different BSOD which stays and shows PAGE_FAULT_IN_NON_PAGED_AREA (0x00000050) If I try to do an overwrite install of XP from the disc then as soon as I agree to the license agreement it give me another BSOD!!! This time is is BAD_POOL_CALLER (0x000000C2).

Thinking it may be RAM related, I have tried to test the RAM by having just one just in at a time and alternating between them and I get the same BSOD loop. I followed a guide at: http://www.support.com/blog/post/how-identify-bad-memory-module-your-pc and tried to load the Memtest86+ software onto a USB, but my Bios does not let me choose a removable drive as the boot device.

The only other thing I could think that could be causing it is the HDD, but the bios is showing the drive correctly and theres a lot of stuff I would like to save from the drive.

I cant get into Windows or DOS and am really at a loss now so any tips would be greatly appreciated.

Thanks

Answer 1

Hi,

The make & model is Compaq SR5219uk and it does have a SATA HDD.

Another person has advised that it could be possible that "the logical Structure" of the HDD may be damages and has recommended trying a format.

Does this sound plausible as I really would rather retain the information on the HDD?

Thanks

Answer 2

If you are getting a BSOD, that is coming from XP so your system is recognizing your HDD.

What is the system make and model and do you know if the system is using SATA drives?

Answer 3

Hi Guys, 

I have tried with the OEM Windows XP CD and tried to enter the recover console from there, but when it loads it only shows me the D:\ and the only volume with windows that I can repair and when I select that it BSOD's with the 0x00000050 page fault screen.

When attempting the install it BSOD's aswell so I dont think it even gets far enough to start making system changes. I have even tried a DOS boot disc but this created a virtual drive and would not let me access my HDD or CD-ROM drive.

For method 2 above: It seems the BIOS version installed is pretty old and has very limited functionality as I cant boot from removable drives or control the hardware.

The thing I am quite worried about is that all of the error messages are ones that are being seen as a result of different troubleshooting, but I still dont know which one is being displayed as Windows is trying to load. I am unable to access DOS through F8 and still havent been able to determine whether my HDD is even being recognised by the PC.

I did try the xp_rec_con.iso boot disc and this time it does does the the drive volume as c:, but when I try to do chkdsk c: /r it says "the volume appears to contain one or more unrecoverable problems." I have been having a bit of a play with some of the options available within the recovery console and am seemingly unable to access or change anything on the HDD so im thinking that its FUBAR - chkdsk doesnt work with /p or /r as the extension and if I try to do "dir" then it says "an error occurred during the directory enumeration"

Is it worth trying fixmbr, fixroot or even format (in a worse case scenario) to see if the HDD is recoverable?

Thanks

Answer 4

If your system gives you that error and especially after a power interruption, the likely problem is that the NT File System (NTFS) has gotten corrupted and XP just can't find the file.

The first thing to do is to verify the integrity of your file system by running a chkdsk /r from the XP Recovery Console.  That will usually straighten things out.

I don't know what an XP emergency recovery boot disk is, but if you have no genuine bootable XP installation CD from which you can boot into the XP Recovery Console or are not sure what you have for bootable media, you can create a bootable XP Recovery Console CD (no XP media required), boot on that and then run your chkdsk /r from there.

Since it sounds like you have some kind of something or another kind of XP CD and you have tried to overwrite your install, there is no telling what condition things are in now.  Plus, if the file system is corrupted, you would want to fix that first anyway or your efforts to overwrite your install may be futile.

If you have no bootable XP media (or are not sure what you have) create a bootable XP Recovery Console CD and be sure what you have (no XP media required).

This is not the same as any recovery disks that might have come with a store bought system. 

You can make a bootable Recovery Console CD by downloading an ISO file and burning it to a CD.

The bootable ISO image file you need to download is called:

xp_rec_con.iso 

Download the ISO file from here:

http://www.mediafire.com/?ueyyzfymmig

Use a new CD and this free and easy program to burn your ISO file and create your bootable CD (do not install UniBlue or the Ask Toolbar - ever!):

http://www.imgburn.com/

Here are some instructions for ImgBurn:

http://forum.imgburn.com/index.php?showtopic=61

It would be a good idea to test your bootable CD on a computer that is working.

You may need to adjust the computer BIOS settings to use the CD ROM drive as the first boot device instead of the hard disk.  These adjustments are made before Windows tries to load.  If you miss it, you will have to reboot the system again.

When you boot on the CD, follow the prompts:

Press any key to boot from CD...

The Windows Setup... will proceed.

Press 'R' to enter the Recovery Console.

Select the installation you want to access (usually  1: C:\WINDOWS)

You may be asked to enter the Administrator password (usually empty).

You should be in the C:\WINDOWS folder.  This is the same as the 

C:\WINDOWS folder you see in explorer.

The Recovery Console allows basic file commands like: copy, rename, replace, delete, cd, chkdsk, fixboot, fixmbr, etc.

For a list of Recovery Console commands, enter help at the prompt or read about the XP Recovery Console here:

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/recovery_console_cmds.mspx?mfr=true

A good idea before starting things is to first verify the integrity of your file system using the chkdsk command.

From the command prompt window run the chkdsk command on the drive where Windows is installed to try to repair any problems on the afflicted drive.

Running chkdsk is fine even if it doesn't find any problems.  It will not hurt anything to run it.

Assuming your boot drive is C, run the following command:

chkdsk C: /r

Let chkdsk finish and correct any problems it might find.  

It may take a long time for chkdsk to complete or it may appear to be 'stuck'.  Be patient.  If the HDD light is still flashing, chkdsk is doing something.  Keep an eye on the percentage amount to be sure it is still making progress.  It may even appear to go backwards sometimes.

You should run chkdsk /r again until it finds no errors to correct.

Remove the CD and type 'exit' to leave the RC and restart the computer.

You do not have to adjust the BIOS again to boot on the HDD since the CD will not be present.

Answer 5

HI,

1.       Which version of service pack is installed on the computer?

Method 1:

For the error message “Windows\System32\Hal.dll missing” try the troubleshooting steps provided below.

Error message in Windows XP SP2: “Windows could not start because the following file is missing or corrupt. Windows\System32\Hal.dll”

http://support.microsoft.com/kb/945380

Method 2:

For the Error BAD_POOL_CALLER (0x000000C2)

The Stop 0xC2 error message indicates that a kernel-mode process or driver incorrectly tried to perform a memory operation. Typically, faulty device drivers or device software can cause this error message.

You may disable hardware devices such as sound, network controller fromthe BIOS (Basic Input Output System) and then try to reinstall the operating system.

Additionally, you may also disable the USB ports while installation if the keyboard and mouse are not connected through USB port to the computer.

Note: Modifying BIOS/ chipset incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the configuring of BIOS/chipset can be solved. Modifications of the settings are at your own risk.

Method 3:

For the Error PAGE_FAULT_IN_NON_PAGED_AREA (0x00000050)

Try the steps provided in the link below.

You may receive an error message on a Windows-based computer: "STOP 0x00000050" or "STOP 0x0000008e"

http://support.microsoft.com/kb/903251

---

---