- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Resolution: Boot into Recovery Console and run "fixmbr" to repair the MBR
--
Symptoms: "A disk read error occurred" "NTLDR is missing" "NTLDR is compressed"
Cause: Corrupt boot sector
Resolution: Boot into Recovery Console and run "fixboot" to repair the boot sector
--
Symptoms: "BOOT.INI is missing or corrupt" "Boot device inaccessible" "Windows could not start because the following file is missing or corrupt: <Windows root>\system32\hal.dll"
Cause: BOOT.INI missing, corrupt or out of date as a partition has been inserted
Resolution: Boot into Recovery Console and run "bootcfg /rebuild" to repair the BOOT.INI
--
Symptoms: "Windows could not start not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"
Cause: Corrupt/missing system hive
Resolution: 1. Boot into Recovery Console and run "chkdsk C: /f" to check the system disk for errors and fix them, then reboot. 2. If the error continues and System Restore is enabled, copy the system hive from the last restore point into \WINDOWS\SYSTEM32\CONFIG 3. If the error continues, copy the system hive from \WINDOWS\REPAIR into \WINDOWS\SYSTEM32\CONFIG 4. If the error continues, perform a repair installation by booting from the Windows installation media
--
Symptoms: "Windows could not start because of a computer disk hardware configuration problem. Could not read from the selected boot disk, Check boot path and disk hardware."
Cause: Boot volume (with Windows folder) is not accessible as defined in BOOT.INI
Resolution: Check the boot volume is accessible
--
Symptoms: Dual-boot 32-bit Windows and 64-bit Windows system reports "NTOSKRNL.EXE is corrupt" trying to boot into 64-bit Windows
Cause: System volume contains an older boot loader than the boot volume requires - e.g. XP SP2 installed after XP x64
Resolution: Copy NTDETECT.COM and NTLDR from XP x64 installation media to the root of the system volume
The most common reason a computer won't start can be a piece of hardware has failed or is causing a problem but that hardware isn't usually a hard drive, the part of your computer that stores all of your files. To fix such kinds of issue, you can take the following steps.1.create a bootable usb or cd ,there are kinds of software for you to complete this step, you can choose Fix Boot,EasyBootDisk or Windows Boot Genius. I suggest you to useWindows Boot Genius, it is easier and more effective.2.boot your computer from the created disk3.fix the issue after run the softwareBy the way, before any further steps you should make sure the power supply is good. Any hardware issues such as pc power and cable,motherboard corrupted should be troubleshooted.I don't suggest you to try the solution above until you are sure there is nothing to do with the hardware. source:http://windows-8-password-recovery.com/computer-wont-boot.html
Well this means one of important files needed to start Windows is corrupted (it's a registry file). I'd recommend repairing Windows installation. If you have Windows XP and also the Original Windows CD follow: this guide.
Its looping. Basically, files needed to boot it into windows are missing or corrupt. Try the following in order:
On boot up, before windows loads, press F8 and boot intro safe mode. If this works, click on the hard drive icon and ask it to repair any faults (Right mouse click, Properties, tools, repair) and reboot. See if that works
If it does, as soon as possible, download a command line virus scanner such as DR WEB, store it on a usb drive or similar, reboot the computer using F8 and safe mode and run the virus scanner from the USB , just to check you have not got a virus.
If it fails to work, you have an issue that will require repairing the windows OS, for which you will need a windows CD. Boot from the CD ( a lOAD of guides on the internet on this) and at the point you get asked to install windows, let if find the existing windows installation and repair it.
Usually a device driver or a Windows update got corrupted, try starting in safe mode and remove any new devices that were recently added that could be a culprit. Alternately, try using windows system restore and go back to before the problem occured. Hardest part is figuring out what is causing the problem.
Sounds like possibly a corrupt file system or possibly a bad program install.
Try to boot to SAFE MODE. Restart your computer and press F8, select safe mode from the boot choices. If Windows loads try to use system restore or remove any program you may have installed just before this happend.
If it still won't start restart, press F8 and select the repair option then follow the onscreen prompts
Two possible reasons: 1. Since the Win98 PC hasn't been used for some time, it can be assumed that somehow the CMOS/BIOS has reverted to default values including its recognition of what HD is installed (or in this case failure to recognize the HD). What needs to be done is the let the PC detect what HD is installed. To do this, on most PCs you need to press "Del" key on boot up (when prompted by a bottom screen display of "Press Del to change BIOS values".... or something like that. Somewhere, there should be an option to manually detect the HD, save setting exit, reboot. 2. If the above does not detect the HD and boot, it may be that the HD has suffered physical/hardware fault such as stuck spindle motor or something else. In some instances, it maybe the IDE cable or even the 4-wire power connector.
Hope this be of some help/idea. Pls post back how things turned up or should you need additional information.
×