Re: started with "blue screen" ended up with "missing system32\hal.dll

Tech-Archive recommends: Fix windows errors by optimizing your registry


"kittikatt60" <kittikatt60@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:528A4C61-DA3F-41B8-931B-C314B904975E@xxxxxxxxxxxxxxxx
Hi folks...
I'm praying somone can assist me as I've been waiting to hear back from
Microsoft on this as it started (when I noticed - my daughter's computer)
when trying to run updates from Microsoft.
Her system is older, running XP Pro and there isn't much on it believe it
or
not. AVG is the anti-virus and I've also tried running some registry
scans.
No avail, but cleaned a few things up. Mostly having to run in Safe Mode
and
Safe Mode w/Networking, yet will still eventually end up getting that blue
screen and many times re-looping and getting stuck & F8 doesn't always
work
either.

Again, this is my daughter's computer, and I believe this started about a
week or so ago. She finally told me a few days ago and when I started
taking
a look at her system, this is all new, not past issues I've experienced.

1. The first thing I tried to do was to run a scan on her system to see if
there were virus, etc.

2. Then I tried to run a windows update and that's when I personally
encountered the first blue screen of many.

3. I had already attempted many times to Use the "Last Known Good
Configuration" to no avail, a few times the system couldn't even get to
running Windows without having returned directly to the blue screen.

4. Then I was able to use the Safe Mode with Networking, tried running
Windows Update that way, didn't work. Multiple attempts each ending in
Blue
Screen

5. I noticed that a message finally gave me something about a Driver
issue,
so went to Device Manager, and updated/reinstalled drivers a display
screen
and a multimedia device (neither of which I am familiar), but then the
Device
Mgr was clear.

6. Then attempted to run Windows update and it did actually download the
Visualization Tool & Installed, thought I was actually getting somewhere.
But then after it asked me to continue on with scanning for updates, I was
back to the blue screen and it proceeded to no longer be able to start
Windows again, just re-routing back to Blue Screen.

7. Last Known Good Configuration again, didn't work.

I do have screen shots of the blue screens it gives, but the error codes
are
of no help as the four it gives me, always change.

I've finally turned the damn thing off as it was just re-looping to blue
screen and couldn't load windows, so after 3 days of tyring to figure it
out,
I've given up....

Lastly, apparently my daughter turned the computer on, and now all it
shows
is a black screen with the "missing system32\hal.dll" file.
Now I've seen this when I got a brand new system running both Mac & OS
systems, when I loaded windows. I figured out a work around for it on the
Mac, but this system only runs Windows, so not sure what to do from here
with
it...

She has some things on her system that she's hoping I don't have to do a
fresh install so any suggestions are tremendously appreciated.

Please let me know what further info I can provide to be of assistance.

Thanks so much,

Sunny


"Jason Cravens" <JasonCravens@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A6D7193F-733A-47E3-9F10-C2943D65EE50@xxxxxxxxxxxxxxxx
If you have the windows installation disks, insert cd and boot from the
disk.
IE. hit F12 during first post. Select windows repair option
3) Insert Windows XP Installation Disk
4) Select Windows repair option
5) Repair will launch Emergency Recovery Console
6) The prompt will indicate the drives to be repaired (most cases there is
only one option 1 C:/Windows)
7) Select the drive option
8) Enter Administrator password
9) C:/Windows prompt should appear
10) Enter chkdsk /p to run check disk on your hard drive
11) After completion Enter chkdsk /r
12) This will locate and repair bad sectors and recover readable
information
13) Reboot into safe mode and back up files (if back up was not available
before)
14) Reboot and PC should be good using correct sectors
15) If error occurs again, 90% of the time it's a corrupt hard drive


hope this helps


Sunny:
First of all, at least for the time being, hold off on the recommendations
you received from Paul. While there may be a hardware problem involved here,
the likelihood is it's a corrupt operating system (OS) that's causing the
problem as Jason indicates.

I'm assuming from your general description of the data on the HDD that
there's no crucial data (files, photos, etc.) that you (or your daughter)
must have. Am I correct about that? Because if there *is* such data that you
*absolutely* must have, it would be best to hold off on running the chkdsk
command as Jason recommends. Under those circumstances, before running the
chkdsk command, it would be best if you were able to connect the problem HDD
as a secondary HDD in another machine, access its contents (if possible),
and copy off any such data. (While the chkdsk /r process is generally benign
re losing/corrupting data it *can* and *does* happen, so it's best whenever
possible to *first* try to copy whatever user-created data you can from the
problem drive before invoking that command). In any event I have the feeling
that's probably impractical in your situation, so we'll go on...

Jason's recommendation about accessing the XP Recovery Console and invoking
the chkdsk /r command is, all things considered, a good one. But first
you've got to tell us whether you have available an XP OS installation CD
that was used to install the OS on your daughter's machine. Was it a retail
version of the XP installation CD? A non-branded OEM version? Or is this an
OEM machine (Dell, Gateway, HP, etc.) that came with only a so-called
"recovery" disk? What I'm trying to get at is whether you have such an XP
installation CD that will allow you to access the Recovery Console through a
boot to that CD. Are you following me on this? And then possibly go on from
there if chkdsk doesn't resolve the problem. (I'm not optimistic that chkdsk
/r will resolve the problem but it's certainly worth a first try if at all
possible).
Anna



.

Relevant Pages

  • Re: Hardware upgrade causing rebooting
    ... Now whenever I try to start the machine, it flashes the windows start screen quickly, then blue screens, and as soon as it blue screens, it then restarts. ... Normally, and assuming a retail license (many factory-installed OEM installations are BIOS-locked to a specific chipset and therefore *not* transferable to a new motherboard - check yours before starting), unless the new motherboard is virtually identical to the one on which the WinXP installation was originally performed, you'll need to perform a repair installation, at the very least: ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: How to force Chkdsk/F during Boot
    ... To start the Recovery Console, start the computer from the Windows XP CD-Rom ... XP installation, and then press C to use the Recovery Console. ... access any folders, but you can carry out commands such as chkdsk, fixboot, ...
    (microsoft.public.windowsxp.general)
  • Re: chkdsk crashes computer
    ... to the last installation this one looks perfect so far. ... CHKDSK runs on it's own if there's some kind of event that causes Windows to ... since the system restore ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: [OT] Borked drive
    ... - I tell it to test disc C, it says it has to reboot, I reboot, it ... You could boot into the recovery console from your Windows CD (or ... DVD) and run chkdsk from there. ... I had to get a replacement windows installation CD ...
    (rec.arts.anime.misc)
  • Re: Error message
    ... "A problem has been detected and windows has been shut down ... Since your system won't boot into Windows, ... going to be able to run chkdsk on that computer is through the ... put the XP installation CD in the drive and start the ...
    (microsoft.public.windowsxp.help_and_support)