• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Sign in to follow this  
Followers 0
sysbuilder

Windows 2000 could not start (Loader error 3)

5 posts in this topic

I have a user with a Dell laptop (not sure of the exact model) who recently received the following error message:

Windows 2000 could not start because of an error in the software.

Please report this problem as :

Loader error 3.

Please contact your support person to report this problem.

Prior to booting the laptop and getting that message he received the message upon boot up that his system time was incorrect and to press (F?) to reset or (F?) to continue. He proceeded to boot into windows and corrected the system time. Again, after that change he rebooted and received the error message above.

I can't find anything in the MS Knowledge Base pertaining to "Load error 3". I feel a bit better following a KB article opposed to someone's post I find googling, but, no luck on the MS KB.

I have googled "Load error 3" which gave me some ideas. I am going to have him replace NTLDR first, though, some of the posts claim that did not resolve the problem and to go as far as using FIXBOOT from the recovery console.

Outside of those suggestions I would think the registry has become corrupt. Does anyone have any recommendations or tools that can quickly resolve a corrupt registry?

Any thoughts would be great. Thanks in advance.

0

Share this post


Link to post
Share on other sites

boot up the laptop using a bart/win PE disk and run a check disk from there, this should determine if there is an corruption on the disk.

More in on BartPE of you aren't familiar

BartPe

0

Share this post


Link to post
Share on other sites

If you can, boot to a recovery console and do a chkdsk /f /r on the boot volume. This can also be caused by corruption in the system hive, which can be repaired as well via chkreg.exe if chkdsk doesn't find any problems.

Edited by cluberti
0

Share this post


Link to post
Share on other sites

go with cluberti's option first as it will be faster if you cannot get to the recovery console use the bart pe method, :) just so used to the laptops and machines my clients sending me that won't even boot properly the bart is the first thing i use :)

0

Share this post


Link to post
Share on other sites

Thanks guys,

The user was able to load a ghost image that was quite out dated, which gave him some stability, however, the old image was made when prior to a domain migration so he wasn't able to connect to many resources on our network. He will be shipping his laptop to me and I will reload it and configure appropriately.

Again, thanks for the suggestions!

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.