load dlls to kernel error 3

[langleyl]

Need help with this error. My sister's computer just went blank and then rebooted to the following error message:

Windows could not start because of an error in the software. Please report this problem as : load needed dlls for kernel.

Now the computer can't get past this message. I've tried setting the BIOS to optimized default settings, this didn't work. Tried clearing the CMOS, this didn't work. How can I fix this?

Thanks,
langleyl

 

[linney]

Looks like you will have to reinstall.

326671 - Error Message: Windows Could Not Start Because of an Error in...

http://support.microsoft.com/default.aspx?scid=kb;en-us;326671&FR=1&PA=1&SD=HSCH

164448 - Error Message: Load Needed DLLs for Kernel

http://support.microsoft.com/default.aspx?scid=kb;en-us;164448&FR=1&PA=1&SD=HSCH

You may like to try this recovery method first just in case it works.

An easy to follow recovery console description when unable to start computer due to corrupt registry.

http://www.digitalwebcast.com/2002/03_mar/tutorials/cw_boot_toot.htm

http://www.mediaworkstation.com/htm/homeset1.htm

Click on Tutorial then the Charlie White article on XP crash.
This is a layman's version of Q307545 in simple language.

 

[langleyl]

Thanks linney! But the recovery isn't working... The repair attempt was halted by cannot copy file. It couldn't copy the software or sam files so I just quite that attempt.

My other option was the re-install... However, after attempting this I got the error message that my drive was corrupt... And then when I rebooted (just for the hell of it), I got this message:

Windows could not start because the following file is missing or corrupt: (Windows root>\system32\hal.dll

Any suggestions for a fix? And, what the heck is causing this?

Thanks again!

 

[wolluf]

Was it a clean install (ie, did you wipe the drive before installing)? If it was, I'd suggest the machine has developed a hardware fault (could be anything, process of elimination - I'd start with RAM, checking CPU fan...).

If you were installing on top - I'd still suspect hardware, but would backup any data needing saved (eg, slave drive to another - eg your - machine and copy files off), wipe drive and try a clean install. If that fails - look at hardware.

 

[langleyl]

Thanks for replying Wolluf. Yes, it was a clean install. However, the fresh install was prompted by a somewhat similar problem about a year ago. Then, the computer somehow managed to eat the config.sys file. I tried to salvage that install (Recovery Console) with the same results - nada!
Obviously, something is wrong somewhere. I'll heed your advice and start checking hardware... but I'm pretty sure I did this the last time because I really thought it was the bios giving me the problems. Talked to Soltek reps and came away scratching my head but they somehow convinced me that it wasn't the board. Ended up pulling everything, reinstalling, cleared CMOS, and then I was finally able to reinstall OS.
While the computer is getting a little old, everything in it is quality stuff... and I've built quite a few of them. The system:
Soltek SL75-DRV4 board (Rev K4, P2)
AMD 1700 XP - stock cooling;
512Mb Corsair 2400 DDR;
Quantum 40G HD - Win XP Pro, FAT32
Antec mid-tower case/Antec 300W PS/3 Antec case fans.

 

[SYAR2003]

From :

http://www.theeldergeek.com/clean_installation_of_windows_xp.htm

When XP is first installed it tries to determine what type of BIOS is available on the computer. Newer systems have what is known as Advanced Configuration and Power Interface (ACPI) capability. Unfortunately, XP doesn't always recognize a computer BIOS is ACPI capable and doesn't install the support for ACPI. Even more unfortunate is the fact that if ACPI support isn't determined at the initial install it's virtually impossible to correct this at a later time short of reinstalling XP over the top of the previous XP installation. To do so requires changing the Hardware Abstraction Layer (HAL). The chances of successfully changing a HAL after XP has been installed is pretty close to zilch.

Once you drop the CD in the tray and fire up the computer to install XP, the first thing you'll see at the bottom of the screen is the option to press F6 if you need to install a SCSI or RAID controller. Don't press F6. Press F5 instead. This will take you to a separate menu of Hardware Abstraction Layer's where you can choose an appropriate HAL that supports ACPI. The choices will be:

ACPI Multiprocessor PC

ACPI Uniprocessor PC

Advanced Configuration and Power Interface (ACPI) PC

Compaq SystemPro Multiprocessor or 100% Compatible PC

MPS Uniprocessor PC

MPS Multiprocessor PC

Standard PC

Standard PC with C-Step i486

Other

In the majority of installations the 'Advanced Configuration and Power Interface (ACPI) PC' HAL is the one you will want to use. A few cautions are also in order:

Obtain and install the latest BIOS for your motherboard before you begin the XP installation.

Equally as important as using the proper HAL on ACPI capable systems, is NOT using it on systems that are not ACPI compatible. The install may complete but the system will almost surely fail to start when it reboots.

There are situations where it is definitely not desirable to use an ACPI HAL even if it is supported by the BIOS. This predominately applies to servers, but to insure that an ACPI HAL will not be used or automatically detected and used, press F7 instead of F5 as discussed previously.

Considering the number of problems that users have with systems not shutting down completely I wonder why this feature is not prominently mentioned and documented. It could save many headaches, but now you know. A good piece of knowledge to have tucked away for your next XP install.

As a final note, to determine if your computer was detected as being ACPI enabled:

Right click My Computer then click Properties > Hardware > Device Manager.
Expand the entry called Computer.

If the entry is 'Advanced Configuration and Power Interface (ACPI) PC' you're all set. If it says 'Standard PC' the computer BIOS was not detected as being ACPI capable.