- 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
sounds like either a RAM or HDD issue. First thing is if you have 2 sticks of ram pull one out and see if it boots ok if not pull the other stick out and put first stick back in. If neither stick lets you boot then I would run a HDD test (some have them in bios) if you do not have it in bios boot windows into safe mode with command prompt and in command prompt type chkdsk /f
Check the audio setting in the volume control in the accessories folder in the start menu. make sure that all of the audio channels are switcched on, and thaty none of them are muted. If this does not work, try uninsztalling the audio device in the Device Manager, and restart.