- 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.
You have to go into your BIOS and select booting from Disk not hard drive when i say disk i mean either the cdrom or dvd disk players attached to your motherboard. also you can get a boot disk to try that at the link below.
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
This stop error means that your ntfs file system is corrupt (damage in the file system, bad hard drive data, corrupt SCSI or IDE drivers or a corrupt ntfs.sys file).
You should try to access your ntfs partitions by making a ntfs boot disk with NTFS4DOS . You can download it from http://www.geekswhoknow.com/files/ntfsinst.exe After you load the bootable floppy disk onto your damaged system, select either option one (1) or option three (3). If you selected option one (1), type chkdsk /r at the command prompt, and your problem should go away after the disk has been repaired. Unfortunately there is a chance that your partition is corrupt beyond repair and all of your data is lost. In that case, you need to reinstall Windows and select the full format during the install
H there this mean a file is corrupt and you need to repair the damage file,you can do this by using a recovery disk for the computer if you have one.If you don't do not have a recovery disk for the computer you can use the operating system disk to repair it,please follow these steps:insert the operating system disk into the drive,restart the computer, press F12 and choose boot from CD save and exit.As the computer loading it will ask you to press any key to boot from CD, press any key, a blue screen will appear while its loading, when it get to the first set of options you will press enter to continue. when it get to the second set of options it will ask you to install the operating system or repair it, choose repair and follow the steps from there, this should solve the problem. But should backup your files before doing this even though no file will be lost but its better to backup just in case something goes wrong.
If you are using windows,System files(boot.ini, config.sys, autoexec.bat, msdos.sys, io.sys) might have lost or corrupted accidentally. You can fix it easily by connecting your hard disk to any other system having windows. boot from the host computer's operating system. open my computer, select folder options from tools menu. select second tab (view) scroll down to uncheck "hide protected operating system files (recommended)" and click ok. now go to C drive. Now you can see the system files mentioned above. copy all the required files to your hard disks partition's root and shutdown. now take out your hard disk and connect to your computer and re-start. another method is to make a bootable pendrive (visit: http://www.esnips.com/doc/0882f54e-3445-41b6-830d-e43fd7d02dc2/Active+Password+Changer+-+Boot+Disk+Creator to download application to make bootable pendrive.) copy all the system files from another computer. boot your system using this pendrive and select option 3 to exit from the menu to prompt. copy all the files to your OS partition and now reboot. this will solve your problem (you may need to change bios setting to boot from usb). for further details you can contact firstname.lastname@example.org
Below is a listing of the full error message that may be related to this error.
Windows NT could not start because the below file is missing or corrupt:
Cause: Keyboard issue Miscellaneous corruption Corrupt boot.ini file. Missing boot.ini file. Missing or corrupt ntoskrnl.exe file. Windows NT installed on a partition bigger then 7.8GB Corrupted hard disk drive or severely corrupted Windows.
This issue has also been known to be caused by a short in the ground wire in the keyboard cable. Make sure this is not the cause of your error by replacing the keyboard with a different keyboard or simply just disconnecting the keyboard from the computer.
Before trying any of the below recommendations it's recommend that you attempt to load the last known good configuration. Additional information about doing this can be found on document CH000626.
Corrupt boot.ini file
This issue is often caused when the boot.ini is missing or improperly configured. This issue often arises after a user has recently added or removed an operating system on the computer or added or removed hard disk drives in the computer.
Make sure the line pointing to the operating system and it's drive and partition is properly configured in the [boot loader] and [operating systems] section. Additional information about boot.ini can be found on document CH000492.
Missing boot.ini file
Microsoft Windows XP users:
If the boot.ini is severely corrupted or missing a user running Microsoft Windows XP can rebuild the boot.ini to resolve this issue. Additional information about rebuilding the boot.ini can be found on document CH000648.
Microsoft Windows NT and Windows 2000 users:
To restore the original boot.ini file in Microsoft Windows NT or Windows 2000 you will need an ERD and follow the below steps. If you do not have an ERD you will be unable to follow these steps.
Boot the computer with your Windows NT three setup diskettes or the Windows 2000 setup disc. In the setup menu, type R to start the repair. When prompted for the ERD diskette insert the diskette and inspect the startup environment.
Missing or corrupt ntoskrnl.exe file If the ntoskrnl.exe file is corrupt or missing this can also generate the error. To restore this file follow the below steps.
Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue. Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
Select the operating system you wish to fix, and then enter the administrator password. Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32 You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file. Type exit to reboot the computer.
Windows NT installed on a partition bigger then 7.8GB If you are running Microsoft windows NT 4.0 on a partition larger than 7.8GB this issue can occur if the boot files are located outside this limitation. When this error occurs your computer will have the
error message as shown below.
OS Loader v4.01 Disk I/O error status=00000001 Windows NT could not start because the below file is missing or corrupt: winnt\system32\Ntoskrnl.exe
Please reinstall a copy of the above file.
If your system partition is larger than 7.8GB you will need to delete the partition and recreate the partition to 7.8GB or less. Additional information about this issue can be found on Microsoft KB Q224526.
Corrupted hard disk drive or severely corrupted Windows Attempt to check the hard disk drive for any errors by running the chkdsk error. To do this follow the below steps.
Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue. Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
In the Microsoft Windows XP setup menu press the R key to enter the recovery console. Select the operating system you wish to fix, and then enter the administrator password. Once at the recovery console type chkdsk /r Once completed type exit and see if issue is resolved. If after trying all of the above steps you are still encountering the same issue it's likely that Windows is severely corrupted and it is recommended you attempt to reinstall Windows. Additional information about erasing the computer and starting over can be found on document CH000186.
Finally, if during the Windows installation you encounter errors it's likely that your hard disk drive is bad.