Windows could not start because of a computer disk hardware configuration problem как исправить

For a Windows 2000 version of this article, see 124550.

Symptoms

When you attempt to start Windows XP, you may receive one of the following error messages:

Error message 1

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.

Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information.

Error message 2

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

Winnt_rootSystem32Ntoskrnl.exe

Please re-install a copy of the above file.

Error message 3

Winnt_rootSystem32Hal.dll missing or corrupt:

Please re-install a copy of the above file.

Additionally, you may experience one or more of the following behaviors:

• If you start the computer to the Recovery Console, a command prompt may appear with no option to log on to the Windows installation.

• If you try to access the Windows folder, you may receive the following error message:

  Access denied.

• If you try to perform a Repair operation from the Windows XP CD-ROM, the Windows installation is not detected and you cannot repair Windows.

Cause

This behavior can occur if any or some of the following conditions are true:

• The Default value in the [Boot Loader] section of the Boot.ini file is missing or invalid.

• Windows XP is not installed in the location specified in the Boot.ini file.

• The Ntoskrnl.exe file is missing or damaged.

• The partition path in the Boot.ini file is not set correctly.

• General hardware failure.

Resolution

To resolve this issue, use either of the following methods.

Method 1

Edit the Boot.ini file to restore or correct the Default entry and to ensure that the other entries in the [Operating Systems] section of the Boot.ini file point to the appropriate directories.

For more information about how to edit the Boot.ini file, click the following article number to view the article in the Microsoft Knowledge Base:

289022 How to edit the Boot.ini file in Windows XP

Method 2

Use the Bootcfg utility in the Recovery Console to correct the Boot.ini file:

1. Use the Windows XP CD-ROM to start your computer.

2. When you receive the message to press R to repair Windows by using the Recovery Console, press the R key.

3. Select the Windows installation that you want, and then type the administrator password when prompted.

4. Type bootcfg /rebuild, and then press ENTER.

5. When the Windows installation is located, the following instructions are displayed:

   Add installation to boot list? (Yes/No/All)
   
   [Type Y in response to this message.]

   Enter Load Identifier:
   [This is the name of the operating system. Type Windows XP Professional or Windows XP Home Edition.]

   Enter OS Load options:
   [Leave this field blank, and then press ENTER].
   After you perform the preceding steps, restart the computer, and then select the first item on the boot menu. This should allow Windows XP to start normally.

   After Windows XP has successfully loaded, the Boot.ini can be modified to remove the incorrect entry.

For more information about how to edit the Boot.ini file, click the following article number to view the article in the Microsoft Knowledge Base:

289022 How to edit the Boot.ini file in Windows XP

Method 3

1. Start the computer by using your Windows XP CD-ROM. Press any key to boot from the CD.

2. After the setup files are finished loading press R to repair using Recovery Console.

3. When you are in the recovery console, select the installation to log on to (usually number 1), and then press ENTER.

4. Login to the Administrator account by typing the password for this account, and then press ENTER.

5. At the recovery console command prompt, type the following command, and then press ENTER:

   For Uni-Processor systems:

   expand <cd-drive>:i386ntoskrnl.ex_ <hd-drive>:Windowssystem32ntoskrnl.exeFor Multi-Processor systems:

   expand <cd-drive>:i386ntkrnlmp.ex_ <hd-drive>:Windowssystem32ntoskrnl.exe
   Note In these two commands, the <cd-drive> placeholder represents the drive letter of your CD drive, and the <hd-drive> placeholder represents the drive letter of the hard disk on which windows is installed.

6. If you receive a prompt to overwrite the file, press Y.

7. Type exit, and press ENTER at the command prompt.

Method 4

Start the computer by using the Recovery Console, and then run theCHKDSK /rcommand.

Note You do not have to include the /p switch in the Chkdsk command-line because the /r switch causes the Chkdsk utility to locate bad sectors and recover readable information. This command implies the /p switch..

More Information

If the Default value in the [Boot Loader] section of the Boot.ini file is missing, Windows XP displays a new entry, Windows (default), on the OS Loader (boot loader) menu, and then defaults to the new entry. The Windows (default) entry points to the following path to load Windows XP:

multi(0)disk(0)rdisk(0)partition(1)WINDOWS
For more information about the Boot.ini file, click the following article number to view the article in the Microsoft Knowledge Base:

102873 Boot.ini and ARC path naming conventions and usage

For more information about Recovery Console in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:

307654 How to install and use the Recovery Console in Windows XP

• 
  Дата статьи: 26.02.2011
• 
  Автор:
  

Если вдруг ваша Windows XP перестала запускаться и выдает на экран что-то вроде:»Windows could not start because the following file is missing or corrupt: C:WindowsSystem32hal.dll» значит файл hal.dll был испорчен или удален.

Для восстановления hal.dll в Windows XP, вам необходимо выполнить следующие действия:

1. Конечно же убедиться, что при старте Windows XP вы видите на экране одну из следующих ошибок:

   * Windows could not start because the following file is missing or corrupt:
   C:WindowsSystem32hal.dll
   Please re-install a copy of the above file.
   * C:WindowsSystem32hal.dll missing or corrupt:
   Please re-install a copy of the above file.
   * 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.
   Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information.
   Эти ошибки значат, что система не может запуститься из-за повреждения или удаления файла hal.dll. Также возможно, что в конфигурацию были внесены какие-либо изменения и Windows ищет этот файл в другом месте.

2. Отыщите у себя на полке, среди кучи дисков, загрузочный диск с Windows XP и загрузитесь с него.
3. Когда увидите на экране приглашение к установке Windows, нажмите на клавишу R.
4. Далее пункт восстановления Windows (как правило, это первый пункт среди появившихся на экране).
5. После запроса пароля администратора, введите его.
6. Появится командная строка, в которой вы и должны, поочередно, выполнить все нижеприведенные команды:ATTRIB -H -R -S C:BOOT.INI затем: DEL C:BOOT.INI затем: BOOTCFG /REBUILD FIXBOOT
7. Выньте диск с Windows из дисковода и перезагрузите компьютер.

Если после этих действий, на экране появляется все та же ошибка, попробуйте повторить действия 1-5 и, в командной строке, выполнить восстановление hal.dll с загрузочного диска Windows XP. Для этого выполните команду:EXPAND F:I386HAL.DL_ C:WINDOWSSYSTEM32HAL.DLL(здесь F — это имя моего CD/DVD-дисковода)

После этого вновь перезагрузите компьютер.

Надеюсь, что этот совет вам очень помог в решении восстановления hal.dll в Windows XP.

---

Error message: «Windows could not start because of a computer disk hardware configuration problem»

For a Windows 2000 version of this article, see 124550.

Symptoms

When you attempt to start Windows XP, you may receive one of the following error messages:

Error message 1

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.

Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information.

Error message 2

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

Please re-install a copy of the above file.

Error message 3

Winnt_rootSystem32Hal.dll missing or corrupt:

Please re-install a copy of the above file.

Additionally, you may experience one or more of the following behaviors:

If you start the computer to the Recovery Console, a command prompt may appear with no option to log on to the Windows installation.

If you try to access the Windows folder, you may receive the following error message:

If you try to perform a Repair operation from the Windows XP CD-ROM, the Windows installation is not detected and you cannot repair Windows.

Cause

This behavior can occur if any or some of the following conditions are true:

The Default value in the [Boot Loader] section of the Boot.ini file is missing or invalid.

Windows XP is not installed in the location specified in the Boot.ini file.

The Ntoskrnl.exe file is missing or damaged.

The partition path in the Boot.ini file is not set correctly.

General hardware failure.

Resolution

To resolve this issue, use either of the following methods.

Method 1

Edit the Boot.ini file to restore or correct the Default entry and to ensure that the other entries in the [Operating Systems] section of the Boot.ini file point to the appropriate directories.

For more information about how to edit the Boot.ini file, click the following article number to view the article in the Microsoft Knowledge Base:

289022 How to edit the Boot.ini file in Windows XP

Method 2

Use the Bootcfg utility in the Recovery Console to correct the Boot.ini file:

Use the Windows XP CD-ROM to start your computer.

When you receive the message to press R to repair Windows by using the Recovery Console, press the R key.

Select the Windows installation that you want, and then type the administrator password when prompted.

Type bootcfg /rebuild, and then press ENTER.

When the Windows installation is located, the following instructions are displayed:

Add installation to boot list? (Yes/No/All)
[Type Y in response to this message.]

Enter Load Identifier:
[This is the name of the operating system. Type Windows XP Professional or Windows XP Home Edition.]

Enter OS Load options:
[Leave this field blank, and then press ENTER].
After you perform the preceding steps, restart the computer, and then select the first item on the boot menu. This should allow Windows XP to start normally.

After Windows XP has successfully loaded, the Boot.ini can be modified to remove the incorrect entry.

For more information about how to edit the Boot.ini file, click the following article number to view the article in the Microsoft Knowledge Base:

289022 How to edit the Boot.ini file in Windows XP

Method 3

Start the computer by using your Windows XP CD-ROM. Press any key to boot from the CD.

After the setup files are finished loading press R to repair using Recovery Console.

When you are in the recovery console, select the installation to log on to (usually number 1), and then press ENTER.

Login to the Administrator account by typing the password for this account, and then press ENTER.

At the recovery console command prompt, type the following command, and then press ENTER:

For Uni-Processor systems:

expand :i386ntoskrnl.ex_ :Windowssystem32ntoskrnl.exeFor Multi-Processor systems:

expand :i386ntkrnlmp.ex_ :Windowssystem32ntoskrnl.exe
Note In these two commands, the placeholder represents the drive letter of your CD drive, and the placeholder represents the drive letter of the hard disk on which windows is installed.

If you receive a prompt to overwrite the file, press Y.

Type exit, and press ENTER at the command prompt.

Method 4

Start the computer by using the Recovery Console, and then run theCHKDSK /rcommand.

Note You do not have to include the /p switch in the Chkdsk command-line because the /r switch causes the Chkdsk utility to locate bad sectors and recover readable information. This command implies the /p switch..

More Information

If the Default value in the [Boot Loader] section of the Boot.ini file is missing, Windows XP displays a new entry, Windows (default), on the OS Loader (boot loader) menu, and then defaults to the new entry. The Windows (default) entry points to the following path to load Windows XP:

multi(0)disk(0)rdisk(0)partition(1)WINDOWS
For more information about the Boot.ini file, click the following article number to view the article in the Microsoft Knowledge Base:

102873 Boot.ini and ARC path naming conventions and usage

For more information about Recovery Console in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:

307654 How to install and use the Recovery Console in Windows XP

Источник

Windows could not start because of error in software and loads needs DLLs for kernel

References to Vista also apply to Windows 7.

Saving any needed data and re-installing Windows 7 might be the best option though here are a
few others.

You can save your files by putting the drive in another computer or an external drive case and then
backing them up. Do so using several methods in a redundant manner. Of course a real computer
shop or your System maker can help recover the files.

Or you could use an Ubuntu boot CD to back up the data.

First check this thread in case its a simple one and if not come back to this thread.

Black screen issues are extremely tough to repair and any fix is usually on a hit or miss
basis. That there is no information on a black screen like there is on a blue screen just
adds to the difficulty. Often using a restore point nor startup repair will have any effect.

You can try a google to see suggested repairs some of which have worked however these
cover a wide field of efforts.

Here is a video of one fix.

Do you have a Window 7 Disk? You can try System Restore from it. If you do not have the
disks your system maker will sell them cheap. Or try from Safe Mode if you can get
there.

You can create a Recovery Disk or use someone else’s same version (to do the System Restore
it only has to be bootable).

These require the correct Windows 7 Disks (especially if you can’t boot into Safe Mode.)

Try StartUp Repair from Recovery Options or a Windows 7 boot disk

Here are Google searches where several have found different solutions :

If needed and you can access regular Windows at all.

If nothing works you can do a repair installation.

cd c:WindowsSystem32winevt (there is a space between cd and C: )

ren Logs LogsOLD (there are spaces between ren and Logs and Logsold)

These help is some cases :

There are backups in the C:WindowsSystem32ConfigRegback folder.

Use these methods to replace the registry with a backup.

Boot with a Windows 7 disk. Both of the below accomplish restoring
a registry backup.

How to recover from a corrupted registry that prevents Windows XP
from starting ( Vista and Windows 7 also using the manual instructions)
http://support.microsoft.com/kb/307545/

Источник

Подскажите пожалуйста, что это может быть.
При начале загрузки системы, комп надолго виснет, затем появляется сообщение следующего содержания:
Windows could not start because of an error in the software.
Please report this problem as: load needed Dlls for kernel.
Please contact your support person to report this problem.
Предыстория.
Все нормально работало. Посещение сайта. Все повисло. Пришлось вырубать компьютер вручную. И началось.
Я правильно понимаю, что скорее всего проблема не в аппаратном обеспечении.
А в программном, как и гласит предупреждение.
Мб вирус поразил системку и все гавкнулось.
Что скорее всего формат партишена с виндой все решит.
Или могут быть другие нюансы? Или все совсем не так?

Денис сколько раз тебе говорил не лазь ты по порносайтам,
тем более тебя девушки со вторым размером рассматривают =)
а по теме давай аську объясню чо как.

ООО
По теме: у меня сестра на сайт по учебе зашла
282356980

Корреляция чего-то там)

Переставь винду, но не на чистую, должно помочь. только желательно до этого на харде вирусняки пролечить.

из пушки по воробьям?

В зеркальце посмотри

ну не убивая предыдущую установку, он фактически обновит виндовские файлы на оригинальные, тем самым восстановив те же дллки, например, или еще что. Просто тупо ставишь винду новую поверх старой, не выбирая новую установку и не форматя старую винду.

То есть ты тоже думаешь, что проблема чисто в софте?

ну если ты вдруг умолчал о том, что когда этот глюк случился, ты фиганул по системнику кувадой, то нет. Ну если железо очень старое и пылью забитое, то тоже мб не в софте дело. Если винт постоянно перегревался, то мог тоже поглючить.

Я бы 99% дал софту. Если аппартно, то в принципе если в тот момент был скачек напряжения недостаточно сглаженный фильтрами и БП, то могло проглючить винт- отсюда проблемы. Но полюбэ нужно начинать с перестановки винды не на чистую. если будут какие-то проблемы в процессе или потом- заморачиваться с железом.

В ответ на:
из пушки по воробьям?

Все равно этим заканчивается, так что лучше уж сразу
Хорошо, если система поставлена на отдельный логический диск!

ой не нада. У карниенки 6 год винде идет, работает. А что с ней только не было

Ипать. Я бы запостил скрин с Эвереста на Хабрахабре! )

4гб винт убрать
систему с cd-юка сразу ставить на sata (если sata установщик не видит, то подпихнуть при установке с дискеты или флешки дрова sata, либо интегрировать в дистр)

Я пробовал этот вариант.
Как раз Sata он и не видел.
Дрова на него не подпихивал, но они у меня есть.
В итоге на Sata винду я тоже поставил.
Но когда убираешь сидюк и 4Гб, он не хочет грузиться с Sata.
Точно также не хочет грузиться и с 4ГБ.
Короче без сидюка ничего делать не хочет.

при вставленном сидюке и sata-диске, при рестарте он сразу грузится с sata, или сначала дергает сидюком?

стоит еще bios перепрошить (на всякий случай если появилась более новая прошивка.

стоит еще bios перепрошить (на всякий случай если появилась более новая прошивка.

Вот это я никогда не делал.
Прошивка старая, полагаю.
Года полтора где-то.
Как осуществить перепрошивку?

в disk manager-е кстати партиция на sata-диске: показана как primary и помечена как Active?

Опа. Не знаю.
Где это можно посмотреть?
Что за диск-менеджер?

Ты имеешь в виду: «Управление компьютером—управление дисками»?
Active = Основной (выбор из основного, дополнительного и логического) в данном случае?
Точно не помню.
Но навскидку так и есть.

Источник

Windows Startup Error “load needed DLLs for kernel”.

Original Title: I have a toshiba satellite that says load needed DLLs for kernel (xp)

It has a toshiba MK6021GAS the model is a toshiba satellite A35-S159

If you mean you are seeing a message like this:

Windows could not start because of an error in the software.
Please report this problem as :
load needed DLLs for kernel.
Please contact your support person to report this problem.

. and when you choose to boot in Safe Mode, the last thing you will see loading is:

then you will see the same message as before:

Windows could not start because of an error in the software.
Please report this problem as :
load needed DLLs for kernel.
Please contact your support person to report this problem.

The meaning is that this file is probably missing or corrupt:

Since that is one of the 3498 files that Windows File Protection cares about, it should never be missing. If it really is missing, it was probably quarantined (effectively deleted) by your unspecified antivirus/antimalware application.

There are likely to be good copies of the file on your system here:

There is also one on my SkyDrive that you can download to a working machine and sneakernet it using a floppy or USB memory device to the afflicted machine and copy it to where it belongs.

Depending on your registry setup, you may not be able to access the floppy or USB stick once you get into the Recovery Console, but you will always be able to using a Hiren’s BootCD (it has it’s own registry), but try the easy stuff first.

The kdcom.dll is the same for SP2 and SP3 so somehow or another you need to boot on something to replace your missing or corrupted one.

You can create a bootable XP Recovery Console CD (no XP media required) and then when you do, you would enter a command like this:

copy c:windowssystem32dllcachekdcom.dll c:windowssystem32

or (depending how SP3 was installed).

copy c:windowsServicePackFilesi386kdcom.dll c:windowssystem32

Respond in the affirmative if asked to overwrite and existing file and you should see a message the one file(s) was copied.

Make yourself a bootable XP Recovery Console first since that is easy and something you can always use on some other rainy day. If that doesn’t get it for you, or the file is nowhere to be found on your system, you can download it from my SkyDrive, but try the easy stuff first.

Here is how to make a bootable XP Recovery Console CD (no XP media required):

If you have no bootable XP media (or are not sure what you have) create a bootable XP Recovery Console CD and be sure what you have (no XP media required).

This is not the same as any recovery disks that might have come with a store bought system.

You can make a bootable Recovery Console CD by downloading an ISO file and burning it to a CD.

The bootable ISO image file you need to download is called:

Download the ISO file from here:

Here are some instructions for ImgBurn:

It would be a good idea to test your bootable CD on a computer that is working.

You may need to adjust the computer BIOS settings to use the CD ROM drive as the first boot device instead of the hard disk. These adjustments are made before Windows tries to load. If you miss it, you will have to reboot the system again.

When you boot on the CD, follow the prompts:

Press any key to boot from CD.

The Windows Setup. will proceed.

Press ‘R’ to enter the Recovery Console.

Select the installation you want to access (usually 1: C:WINDOWS)

You may be asked to enter the Administrator password (usually empty).

You should be in the C:WINDOWS folder. This is the same as the

C:WINDOWS folder you see in explorer.

The Recovery Console allows basic file commands like: copy, rename, replace, delete, cd, chkdsk, fixboot, fixmbr, etc.

For a list of Recovery Console commands, enter help at the prompt or read about the XP Recovery Console here:

A good idea before starting things is to first verify the integrity of your file system using the chkdsk command.

From the command prompt window run the chkdsk command on the drive where Windows is installed to try to repair any problems on the afflicted drive.

Running chkdsk is fine even if it doesn’t find any problems. It will not hurt anything to run it.

Assuming your boot drive is C, run the following command:

Let chkdsk finish and correct any problems it might find.

It may take a long time for chkdsk to complete or it may appear to be ‘stuck’. Be patient. If the HDD light is still flashing, chkdsk is doing something. Keep an eye on the percentage amount to be sure it is still making progress. It may even appear to go backwards sometimes.

You should run chkdsk /r again until it finds no errors to correct.

Источник

Windows could not start. Hardware configuration problem: Fix for Windows XP

Get the fix to the Windows could not start boot error message affecting Windows XP.

About the “Windows could not start” error

The following information on this error has been compiled by NeoSmart Technologies, based on the information gathered and reported by our global network of engineers, developers, and technicians or partner organizations.

Description and Symptoms

The error messages, alerts, warnings, and symptoms below are tied to this error.

Symptom 1: Windows could not start error screen on startup

When a computer is turned on, the BIOS picks an eligible, bootable hard drive and then calls code stored in the MBR at the start of that hard drive. That MBR code in turn loads the bootsector from the active partition. On Windows XP, this bootsector code is tasked with loading NTLDR (the Windows XP bootloader) and its dependencies, which are used to load the operating system kernel and start up Windows. The NTLDR file then loads the Boot.ini file that contains the list of operating systems. However, if an entry in the Boot.ini file points to a nonexisting drive or partition, then the system loading process is halted and the “Windows could not start” error screen is displayed.

For more information on how computers start up and how the Windows XP boot process works, please refer to the respective pages in our extensive wiki and knowledgebase.

Causes of this Error

This error has been known to occur as a result of the following cause:

Cause 1: An entry in Boot.ini file points to a nonexisting drive or partition

On Windows XP, this error may appear if the Boot.ini file becomes misconfigured or corrupt because of user errors, power outages or virus attacks. If NTLDR tries to access an inaccessbile drive or partition, then the whole boot process is halted.

Fixing “Windows could not start” on Windows

Windows Setup CD/DVD Required!
Some of the solutions below require the use of the Microsoft Windows setup CD or DVD. If your PC did not come with a Windows installation disc or if you no longer have your Windows setup media, you can use Easy Recovery Essentials for Windows instead. EasyRE will automatically find and fix many problems, and can also be used to solve this problem with the directions below.

Fix #1: Rebuild Boot.ini via Easy Recovery Essentials

Easy Recovery Essentials is guaranteed to fix the “Windows could not start” error automatically using its built-in Automated Repair option. EasyRE is currently available for Windows XP, Vista, 7 and 8 and can be downloaded and created on any PC.

Choose “Automated Repair” in Easy Recovery Essentials

Choose the drive associated with the Windows installation you’re trying to repair.

Easy Recovery Essentials searches for errors and makes corrections to the selected Windows installation.

Windows, booting up successfully.

You can download Easy Recovery Essentials from here.

Fix #2: Rebuild boot.ini file

Follow these steps to rebuild the boot.ini file manually:

Here is an example of what the PC’s console output should look like once the boot.ini file is properly restored:

Fixing Boot.ini file

More Information

Linked Entries

Support Links

It’s an easy-to-use and automated diagnostics disk. It’s available for Windows 8, Windows 7 and Windows Vista. It’s also available for Windows XP and Windows Server.

Applicable Systems

This Windows-related knowledgebase article applies to the following operating systems:

Источник

Видео

Дело было так: необходимо было переустновить Windows на компьютере. Я сделал флешку загрузочной и принялся переустанавливать, но как оказалось, материнская плата на компьютере старая, поэтому не воспринимала установку Windows с флешки (Windows XP). Но на флешке я нашел файл Setup.exe и запустил его, открылось окно с кнопкой «Установить Windows», я нажал и пошёл процесс установки. Все бы ничего, но при первом запуске вылезла вот такая ошибка: Windows could not start because of a computer disk hardware configuration problem. Затем я записал Windows на диск, вставил в дисковод — ничего не происходит. Погуглил, написано, что нужно вставить загрузочный диск. Загрузочный диск по идее исправляет ошибки? Выставленный диск в компьютере этого не делает почему-то. Далее я сделал следующее: вставил флешку, включил компьютер, в определённый момент нажал кнопку R, потом F8, вышло некоторое меню, нашел там такой пункт: Start Windows Normally, нажал, выбрал одну из двух кнопок Windows Professional XP RUS и точно такой же только без RUS, я выбрал RUS и запустился мой старый Windows, даже ничего не изменилось. Все те же файлы, все работает. Но работает только в режиме Start Windows Normally. Подскажите что делать и как избавиться от той ошибки, что выскакивает при запускe системы?