Question about PC Desktops

1 Answer

The following file is missing or corrupted; C:\WINDOWS\SYSTEM\VMM32.VXD type the name of the windows loader (e. g., C:\WINDOWS\SYSTEM\VMM32.VXD)

Posted by on

1 Answer

  • Level 2:

    An expert who has achieved level 2 by getting 100 points

    All-Star:

    An expert that got 10 achievements.

    MVP:

    An expert that got 5 achievements.

    Sergeant:

    An expert that has over 500 points.

  • Expert
  • 313 Answers

That is a special file, created during Windows installation. Every computer uses a different VMM32.VXD file, so you can't simply copy one from another system and expect it to work.

If you can't find that file by searching the system in DOS, you could wipe the drive and reinstall Windows again, or do a repair install, installing Windows on top of itself. That should force the creation of a new VMM32.VXD file, and that problem should be history.

If you DO find the file somewhere on the HDD through a DOS search, copy it into the Windows\System folder, then reboot the system.

Posted on Jul 23, 2008

Add Your Answer

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

1 Answer

I HAVE A GATEWAY DESKTOP COMPUTER WITH AN ERROR MESSAGE SYSTEM32\NTOSKRNL.EXE. HOW DO I FIX THIS PROBLEM?


NTOSKRNL.EXE is missing or corrupt. Issue NTOSKRNL.EXE is missing or corrupt.
Related errors

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:

C:\Winnt\System32\Ntoskrnl.exe
Cause

  1. Keyboard issue
  2. Miscellaneous corruption
  3. Corrupt boot.ini file.
  4. Missing boot.ini file.
  5. Missing or corrupt ntoskrnl.exe file.
  6. Windows NT installed on a partition bigger then 7.8GB
  7. Corrupted hard disk drive or severely corrupted Windows.
Solution

Keyboard issue

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 just disconnecting the keyboard from the computer.

Miscellaneous corruption

Before trying any of the below recommendations it's recommend that you load the last known good configuration.

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 its drive and partition is properly configured in the [boot loader] and [operating systems] section.

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.

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.

  1. Boot the computer with your Windows NT three setup diskettes or the Windows 2000 setup disc.
  2. In the setup menu, type R to start the repair.
  3. 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.

  1. 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.
  2. 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.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
  6. You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
  7. 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

Check the hard disk drive for any errors by running the chkdsk program. To do this follow the below steps.

  1. 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.
  2. 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.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Once at the recovery console type chkdsk /r
  6. 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 reinstall Windows.

Finally, if during the Windows installation you encounter errors it's likely that your hard disk drive is bad.


http://www.computerhope.com/issues/ch000646.htm

Mar 02, 2012 | Gateway GT5026E PC Desktop

Tip

Boot problems and their possible causes & resolutions


Symptoms:
Black screen
"Invalid Partition Table"
"Error loading operating system"
"Missing operating system"


Cause:
Corrupt Master Boot Record (MBR)

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

on May 03, 2010 | PC Desktops

Tip

NTOSKRNL.EXE is missing or corrupt.


Issue: NTOSKRNL.EXE is missing or corrupt.
Related errors:
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:
C:\Winnt\System32\Ntoskrnl.exe
Cause:
  1. Keyboard issue
  2. Miscellaneous corruption
  3. Corrupt boot.ini file.
  4. Missing boot.ini file.
  5. Missing or corrupt ntoskrnl.exe file.
  6. Windows NT installed on a partition bigger then 7.8GB
  7. Corrupted hard disk drive or severely corrupted Windows.
Solution: Keyboard issue
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.
Miscellaneous corruption
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 its 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.
  1. Boot the computer with your Windows NT three setup diskettes or the Windows 2000 setup disc.
  2. In the setup menu, type R to start the repair.
  3. 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.
  1. 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.
  2. 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.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
  6. You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
  7. 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 program. To do this follow the below steps.
  1. 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.
  2. 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.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Once at the recovery console type chkdsk /r
  6. 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.

on Dec 27, 2009 | PC Desktops

1 Answer

I deleted windows\system\vmm32.VXD on my etower633id


You must either recover that file from a backup, copletely reinstall windows, or use the Windows Recovery disk that came with your computer to repair the partition.

Mar 20, 2011 | E-Machines etower 633ids PC Desktop

3 Answers

Ntldr is missing press ctrl alt del to restart cant install o/s


This problem may occur if the basic input/output system (BIOS) on your computer is outdated, or if one or more of the following Windows boot files are missing or damaged: Ntldr
Ntdetect.com
Boot.ini To resolve this issue, verify that the BIOS on your computer is current, and then use one or more of the following methods, as appropriate to your situation, to repair the Windows 2000 startup environment.
Verify That the BIOS on the Computer Is Current loadTOCNode(3, 'summary'); Make sure that the latest revision for BIOS is installed on the computer. Contact the computer manufacturer to inquire about how to obtain, and then install the latest BIOS update that is available for the computer.
Method 1: Use a Boot Disk to Start the Computer loadTOCNode(3, 'summary');
  1. Create a Windows 2000 boot disk that contains the following files: Ntldr
    Ntdetect.com
    Boot.ini
    Ntbootdd.sys For more information about how to create a boot disk, click the following article numbers to view the articles in the Microsoft Knowledge Base: 301680 (http://support.microsoft.com/kb/301680/ ) How to create a boot disk for an NTFS or FAT partition in Windows 101668 (http://support.microsoft.com/kb/101668/ ) How to use a Windows boot disk to prevent boot failure
  2. Modify the Boot.ini file to point to the correct hard disk controller and to the correct volume for your Windows installation. For more information about how to create a boot disk, click the following article number to view the article in the Microsoft Knowledge Base: 311578 (http://support.microsoft.com/kb/311578/ ) How to edit the Boot.ini file in Windows 2000
  3. Insert the boot disk into the computer's floppy disk drive, and then restart the computer.
  4. Copy the Ntldr file, the Ntdetect.com file, and the Boot.ini file from the boot disk to the system partition of the local hard disk.
Method 2: Use the Recovery Console loadTOCNode(3, 'summary');
  1. Use the Windows 2000 Setup disks to restart the computer, or use the Windows 2000 CD-ROM to restart the computer.
  2. At the Welcome to Setup screen, press R to repair the Windows 2000 installation.
  3. Press C to repair the Windows 2000 installation by using the Recovery Console.
  4. Type the number that corresponds to the Windows installation that you want to repair, and then press ENTER. For example, type 1, and then press ENTER. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 229716 (http://support.microsoft.com/kb/229716/ ) Description of the Windows Recovery Console
  5. Type the Administrator password, and then press ENTER.
  6. Type map, and then press ENTER. Note the drive letter that is assigned to the CD-ROM drive that contains the Windows 2000 CD-ROM.
  7. Type the following commands, pressing ENTER after you type each one, where drive is the drive letter that you typed in step 4 of "Method 2: Use the Recovery Console," of this article: copy drive:\i386\ntldr c:\

    copy drive:\i386\ntdetect.com c:\If you are prompted to overwrite the file, type y, and then press ENTER.

    NOTE: In these commands, there is a space between the ntldr and c:\, and between ntdetect.com and c:\.
  8. Type the following command, and then press ENTER: type c:\Boot.iniA list similar to the following list appears: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect If you receive the following message, the Boot.ini file may be missing or damaged: The system cannot find the file or directory specified.
  9. If the Boot.ini file is missing or damaged, create a new one. To do so, follow these steps:
    1. Use a text editor, such as Notepad or Edit.com, to create a boot loader file similar to the following boot loader file: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect For more information, click the following article number to view the article in the Microsoft Knowledge Base: 102873 (http://support.microsoft.com/kb/102873/ ) Boot.ini and ARC path naming conventions and usage 301680 (http://support.microsoft.com/kb/301680/ ) How to create a boot disk for an NTFS or FAT partition in Windows
    2. Save the file to a floppy disk as Boot.ini.

      NOTE: If you used Notepad to create the file, make sure that the .txt extension is not appended to the Boot.ini file name.
    3. Type the following command at the Recovery Console command prompt to copy the Boot.ini file from the floppy disk to the computer: copy a:\Boot.ini c:\
  10. Type exit, and then press ENTER. The computer restarts.

Jul 07, 2009 | Compaq Evo D500 PC Desktop

3 Answers

Computer won't boot up


You Can Try Using The Safe Boot Option Or Obtain A Windows Xp Repair Disk.

Jan 17, 2009 | PC Desktops

1 Answer

Vmm32.vxd problem on windows millennuim edition its saying load windows loader dont knoe it please help have no disc omputer given to me thanks


just go to start button goto run type regedit and press ctrl F and then type vmm32.vxd and press find and if the file that type is showed delete the vmm32.vxd and press F3 to search again the if you find another file like that again just delete it and its finished restart your computer.

Nov 25, 2008 | PC Desktops

1 Answer

Error: windows root>\system32\ntoskrnl.exe


Issue: NTOSKRNL.EXE is missing or corrupt.
Related errors:
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:
C:\Winnt\System32\Ntoskrnl.exe
Cause:
  1. Keyboard issue
  2. Miscellaneous corruption
  3. Corrupt boot.ini file.
  4. Missing boot.ini file.
  5. Missing or corrupt ntoskrnl.exe file.
  6. Windows NT installed on a partition bigger then 7.8GB
  7. Corrupted hard disk drive or severely corrupted Windows.
Solution: Keyboard issue 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.
Miscellaneous corruption 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.
  1. Boot the computer with your Windows NT three setup diskettes or the Windows 2000 setup disc.
  2. In the setup menu, type R to start the repair.
  3. 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.
  1. 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.
  2. 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.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
  6. You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
  7. 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.
  1. 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.
  2. 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.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Once at the recovery console type chkdsk /r
  6. 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.

Oct 18, 2008 | PC Desktops

2 Answers

How do I...


NTOSKRNL.EXE is missing or corrupt.

Related errors:

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:
C:\Winnt\System32\Ntoskrnl.exe

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.
Solution:
Keyboard issue
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.

Miscellaneous corruption
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.

Oct 09, 2008 | Dell OptiPlex GX110 PC Desktop

1 Answer

ACER DESKTOP COMPUTER


Issue: NTOSKRNL.EXE is missing or corrupt.
Related errors:
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:
C:\Winnt\System32\Ntoskrnl.exe
Cause:
  1. Keyboard issue
  2. Miscellaneous corruption
  3. Corrupt boot.ini file.
  4. Missing boot.ini file.
  5. Missing or corrupt ntoskrnl.exe file.
  6. Windows NT installed on a partition bigger then 7.8GB
  7. Corrupted hard disk drive or severely corrupted Windows.
Solution: Keyboard issue 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.
Miscellaneous corruption 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.
  1. Boot the computer with your Windows NT three setup diskettes or the Windows 2000 setup disc.
  2. In the setup menu, type R to start the repair.
  3. 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.
  1. 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.
  2. 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.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
  6. You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
  7. 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.
  1. 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.
  2. 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.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Once at the recovery console type chkdsk /r
  6. 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.

best regards wish u give me a good rate ^^

Aug 15, 2008 | Acer PC Desktops

Not finding what you are looking for?
PC Desktops Logo

Related Topics:

60 people viewed this question

Ask a Question

Usually answered in minutes!

Top PC Desktops Experts

joecoolvette
joecoolvette

Level 3 Expert

5660 Answers

Brian Sullivan
Brian Sullivan

Level 3 Expert

27725 Answers

Les Dickinson
Les Dickinson

Level 3 Expert

18298 Answers

Are you a PC Desktop Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...