English Deutsch Français Italiano Español Português 繁體中文 Bahasa Indonesia Tiếng Việt ภาษาไทย
All categories

everytime i start my computer, it lets me log on but then i get an error that says something happened and it won't let me on so damage won't be done to my computer or something.
so it says if i get that once, restart but if i get it again, remove/disable any stuff i installed lately and then run a memory check to make sure it's aligned right + w/e. i went in safe mode (like i am now) uninstalled all the stuff i'd installed recently and it still won't let me log on.
what should i do? :(

2007-02-22 12:43:21 · 5 answers · asked by rizmo 1 in Computers & Internet Hardware Desktops

oh and i don't have the disc anymore because i got this computer when my neighbor left so idk what he did with it.

2007-02-22 12:58:26 · update #1

5 answers

I think you are going to have to format ur hard drive and reinstall windows from the disc

2007-02-22 12:50:12 · answer #1 · answered by D McC 7 · 0 0

basically that version of abode windows has taken a crap and should be reinstalled. If the main suitable Board became Corrupted you may get a device blunders and if it became a force you may get a Boot blunders. in view that your no longer even getting the Blue exhibit screen of dying tells me that's a utility concern with abode windows. a considerable Board errror might have given you reminiscence or cashe errors and run so slow and basically stall out or does no longer even boot up in any respect wish you have backed up your archives

2016-09-29 12:08:29 · answer #2 · answered by puzo 4 · 0 0

try these

1-If XP won't start it may be due to a damaged boot sector or a missing or corrupt ntldr or ntdetect.com files.

To replace damaged ntldr and ntdetect.com you can copy fresh files from the XP CD using the COPY command. Boot with the XP CD and enter the Recovery Console(put cd of xp let it boot when blue wellcome screen appears then go for "R" now u r in Recovery Console .... Just press enter all options). At the Command Prompt type the following (where "X" is your CD-Rom drive letter) allowing the files to overwrite the old files
COPY X:\i386\NTLDR C:
COPY X:\i386\NTDETECT.COM C:

To repair a damaged Boot Sector at the command prompt type FIXBOOT and press Enter. Then answer "Y"

2-if still not work then go with this microsoft article:

"Invalid Boot.ini" or "Windows could not start" error messages when you start your computer

View products that this article applies to.

Article ID


:


330184

Last Review


:


June 2, 2004

Revision


:


1.0

This article was previously published under Q330184
SYMPTOMS

When you start your computer after you upgrade to Microsoft Windows XP, you may receive one or both of the following error messages:

Invalid Boot.ini

Windows could not start because the following file is missing or corrupt:

Windows\System32\Hal.dll

Back to the top
CAUSE

This issue may occur if the Boot.ini file is missing, damaged, or contains incorrect entries.

Back to the top
RESOLUTION

To resolve this issue, start the computer from the Windows XP CD, start the Recovery Console, and then use the Bootcfg.exe tool to rebuild the Boot.ini file. To do this, follow these steps:

1.


Configure the computer to start from the CD-ROM or DVD-ROM drive. For information about how to do this, see your computer documentation, or contact your computer manufacturer.

2.


Insert the Windows XP CD-ROM into your CD-ROM or DVD-ROM drive, and then restart your computer.

3.


When you receive the "Press any key to boot from CD" message, press a key to start your computer from the Windows XP CD-ROM.

4.


When you receive the "Welcome to Setup" message, press R to start the Recovery Console.

5.


If you have a dual-boot or multiple-boot computer, select the installation that you have to use from the Recovery Console.

6.


When you are prompted, type the administrator password, and then press ENTER.

7.


At the command prompt, type bootcfg /list, and then press ENTER. The entries in your current Boot.ini file appear on the screen.

8.


At the command prompt, type bootcfg /rebuild, and then press ENTER. This command scans the hard disks of the computer for Windows XP, Microsoft Windows 2000, or Microsoft Windows NT installations, and then displays the results. Follow the instructions that appear on the screen to add the Windows installations to the Boot.ini file. For example, follow these steps to add a Windows XP installation to the Boot.ini file:

a.


When you receive a message that is similar to the following message, press Y:

Total Identified Windows Installs: 1

[1] C:\Windows
Add installation to boot list? (Yes/No/All)

b.


You receive a message that is similar to the following message:

Enter Load Identifier

This is the name of the operating system. When you receive this message, type the name of your operating system, and then press ENTER. This is either Microsoft Windows XP Professional or Microsoft Windows XP Home Edition.

c.


You receive a message that is similar to the following:

Enter OS Load options

When you receive this message, type /fastdetect, and then press ENTER.

Note The instructions that appear on your screen may be different, depending on the configuration of your computer.

9.
Type exit, and then press ENTER to quit Recovery Console. Your computer restarts, and the updated boot list appears when you receive the "Please select the operating system to start" message.
....................but if stilln not then install fresh copy of Xp ..done bye

2007-02-22 13:03:02 · answer #3 · answered by Anonymous · 0 0

If you have added or removed hardware like videocard or ram, then try and remove the new hardware or replace hardware that was removed
A reinstall may fix this unless you have faulty hardware. Your best bet would be if it doesn't fix itself or you remove any programs you recently installed and it still doesn't work, take it to the computer shop and have them look at it.

Cheers Rik

2007-02-22 13:18:29 · answer #4 · answered by rik1938 2 · 0 0

Have you tried starting up from last known good settings?

2007-02-27 04:57:15 · answer #5 · answered by HAWKEYE 2 · 0 0

fedest.com, questions and answers