- 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.
Problem May be #1: Actually the support for Windows XP has been ended from Microsoft, and on the other side you are trying to install Earth, which is updated many times after Windows XP. That's why Windows XP could not install it.
Problem May be #2: Check your hardware properly. All capacitors and insulators. RAMs, Hard-Disk, bad sectors, etc.... These also cause any software lose its action.
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 "NTLDR is missing", error displays very shortly after the computer is first started; after the Power On Self Test (POST) is complete. Windows XP might only initially load when the NTLDR error message appears. Causes of this error message include corrupt and misconfigured files, hard drive and operating system upgrade issues, corrupt hard drive sectors, an outdated BIOS, and damaged or loose IDE cables. Get more help and information for Windows XP hope this helps you.
This sort of error usually signifies a hardware error. Either an incorrect driver installed (try starting windows in safe mode and update your video card and motherboard drivers) or some sort of hardware failure (memory failure, overheating, etc...). Overheating can be diagnosed by an application such as speedfan (freeware). You can also look into your system event viewer to get a bit more information about the error and it's cause
If you can install Windows Vista and only XP not work for sure this is the solution : SATA operation mode is AHCI To change this : Open BIOS Look for SATA Operation Mode or somethin equivalent and change-it to IDE or Compatibility Mode.
Windows restarts without warning Cause: This issue could be caused by any of the below possibilities.
Software issue or error. Hardware issue or error. Heat related issue. Computer virus. Issue with operating system. Answer: Software issue or error Errors generated by software programs can cause a computer to reboot unexpectedly or without warning. If you are running Windows XP see the below section "For Windows XP users" before continuing.
If you are not running Windows XP or following the below steps still cause your computer to reboot without warning. Boot your computer into Safe Mode, and let the computer run in Safe Mode.
If the computer is still rebooting in Safe Mode the issue is likely not software related but something else, skip to the next section. If the computer is not rebooting in Safe Mode it is likely you have software related issue. We would recommend you run through the basic troubleshooting section for your operating system. For Windows XP users
Windows XP is designed to automatically reboot each time an error occurs such as a BSoD. Although this may be nice for errors that do not occur often, users who have a re-occurring error may wish to identify the error to troubleshoot it. Below are the steps on how this feature can be disabled and enabled in Windows XP.
From the desktop right-click on My Computer. Click the Properties option. In the System Properties window click the Advanced tab. In Advanced click the Settings button under Startup and Recovery. In the Startup and Recovery window uncheck the Automatically restart check box. Click Ok. Now if the computer generates and error it should not automatically restart and enable you to display any errors your computer may be experiencing. Hardware issue or error Any failing hardware component in your computer could cause your computer to unexpectedly generate an error and/or reboot without warning. If you have recently attempted to add a new hardware device, remove that device to make sure it is not causing your issues.
Make sure you are not encountering any hardware conflicts by viewing Device Manager for errors.
New drivers can also cause this issue, if you have recently performed any hardware driver updates you may wish to try an earlier version of the drivers.
If you have updated drivers and removed any hardware that could be causing this issue and continue to experience random reboots, it's possible that the memory is bad in the computer.
Finally, hardware devices that are not installed properly in the computer can also cause random reboots. Make sure all the cables and expansion cards are connected properly to the computer. The best way to determine this is to disconnect and reconnect all cables and expansion cards. Computer virus Computer viruses such as the blaster virus are written to reboot your computer without warning. Usually these viruses will make the computer reboot ever 5, 10, 15 or 30 minutes after the computer has booted.
If you believe your computer may be infected with a virus or are uncertain if your computer is infected with a virus make sure your virus scanner definitions are up to date.
Heat related issue Many computer today are designed to turn off or automatically reboot if the computer, processor, or other device in your computer gets to hot. If you have heard any abnormal noises coming from your computer recently such as a high squealing this could indicate a fan may be failing in your computer.
You can first start by verifying the fan on the power supply is working by examining the back of the computer and seeing if the fan is moving and moving smoothly. For all other fans in the computer you will need to either open the computer and make sure the fan are working (processor fan and case fan) and/or if your BIOS monitors the RPM of the fans enter BIOS and make sure the BIOS does not report any errors.
Users may also be able to determine how hot their computer is by onboard thermal sensors, if your computer comes equipped with these sensors make sure your CPU is not running to hot. Issue with operating system If after following each of the above recommendations your computer still continues to reboot it is likely that you are experiencing a Microsoft Windows operating system related issue that cannot be explained. To help make sure this is the case please try the below steps.
Reboot the computer and enter CMOS setup as the computer is booting. After you have loaded the computer in CMOS setup let the computer sit. If the computer does not reboot while letting the computer sit in CMOS it is likely that you are in fact experiencing an issue with Microsoft Windows and it is recommend that if you have followed all of the above recommendations that you reinstall your version of Microsoft Windows.
The Blue Screen of Death (also known as a stop error, BSOD, bluescreen, or Blue Screen of Doom) is an error screen displayed by some operating systems, most notably Microsoft Windows, after encountering a critical system error which can cause the system to shut down, to prevent damage.
Bluescreens on NT-based Windows systems can be caused by poorly written device drivers or malfunctioning hardware. In the Win9x era, incompatible DLLs or bugs in the kernel of the operating system could also cause bluescreens.
Bluescreens can also be caused by physical faults such as faulty memory,
power supply issues, overheating of components, or hardware running
beyond its specification limits. Bluescreens have been present in all
Windows-based operating systems since Windows 3.1; earlier, OS/2 and MS-DOS suffered the Black Screen of Death, and early builds of Windows Vista displayed the Red Screen of Death after a boot loader error.
A stop error occurs when Windows XP Professional stops responding. Stop error messages can be caused by hardware or software malfunctions. The error messages appear on a blue or black background. The following steps, which also appear on the stop error screen, help you find out the cause of a stop error and how to fix the problem.
To troubleshoot General Stop Errors:
1. Restart your PC. Unplug each new hardware device, one at a time, to see if this resolves the error. Try to run any hardware diagnostic software supplied by your computer manufacturer.
2. If this is a new installation of hardware or software, contact the manufacturer for any Windows XP Professional updates or drivers you might need. Click Get support, or find information in Windows XP newsgroups (under "Ask for assistance") and then click Get help from Microsoft in the left-hand column.
3. Check the Microsoft Hardware Compatibility List (HCL) to verify that all your hardware and drivers are compatible with Windows XP Professional.
4. If you can start Windows XP Professional, check the System Log in Event Viewer for additional error messages that might help identify the device or driver causing the problem.
5. If you cant start Windows XP Professional, try to start your computer in safe mode, and then remove or disable any newly added programs or drivers.
6. Search the Microsoft Knowledge Base for "Windows XP Professional" and the number associated with the stop error you received. Specific Stop Errors Some stop errors display descriptive messages such as "DATA_BUS_ERROR" that can help you determine the exact solution for the error. This section discusses how to troubleshoot specific stop errors, based on the type of error you receive.