Vista has weird 0xc0000221 error

A

avallach

Trying to troubleshoot a problem with a Vista machine, clean install,
which, during the first boot-up each day, does the following:

Windows failed to Start.

File: \Windows\system32\ntoskrnl.exe
Status : 0xc0000221
Info: Windows failed to load because the kernel is missing, or
corrupt.

We reboot the machine, it brings up the "Windows failed to start"
screen that gives us the safe mode, last known good, normal etc boot
options, we choose Boot Normally and it boots right up, and has no
further issues (until the next day when it does it again).

Any ideas? So far I'm at a loss and don't want to reinstall because
of this. I've thought of trying a repair but haven't done so yet.
I've also thought about trying to simply copy the file from another
good Vista machine over, but that seems kinda scary.
 

My Computer

M

Mark L. Ferguson

The recovery option for a Command Prompt should let you do that, assuming
you can get a compatible copy of the file. Look over the TakeOwn technique:
Some Windows Vista functions may not work, or Windows Vista may stop
responding: http://support.microsoft.com/kb/929833

--
Was this helpful? Then click the "Yes" Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales/help/help_en-us.htm#RateAPost

Mark L. Ferguson

..
"avallach" <[email protected]> wrote in message
news:[email protected]

> Trying to troubleshoot a problem with a Vista machine, clean install,
> which, during the first boot-up each day, does the following:
>
> Windows failed to Start.
>
> File: \Windows\system32\ntoskrnl.exe
> Status : 0xc0000221
> Info: Windows failed to load because the kernel is missing, or
> corrupt.
>
> We reboot the machine, it brings up the "Windows failed to start"
> screen that gives us the safe mode, last known good, normal etc boot
> options, we choose Boot Normally and it boots right up, and has no
> further issues (until the next day when it does it again).
>
> Any ideas? So far I'm at a loss and don't want to reinstall because
> of this. I've thought of trying a repair but haven't done so yet.
> I've also thought about trying to simply copy the file from another
> good Vista machine over, but that seems kinda scary.
 

My Computer

ripbox

Nerd
Vista Pro
if you have a vista disc the i would try a repair... that should fic the problem 4 you
a quick google brought this up

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.
 

My Computer

System One

  • Manufacturer/Model
    Me :P
    CPU
    Core 2 Quad Q6600
    Motherboard
    Abit IN9 32X MAX
    Memory
    8 GB OCZ PC2-6400 nVIDIA SLI-Ready Edition (4X2GB)
    Graphics Card(s)
    AMP! GeForce GTX 260² 896MB 448-bit GDDR3 (650MHz/2100MHz
    Sound Card
    Realtek 7.1 CH HD Audio
    Monitor(s) Displays
    17" Fujitsu siemens TFT + 32" LG HD LCD TV
    Screen Resolution
    1280x1024 + 1360x768
    Hard Drives
    150GB Raptor HDD
    500GB Caviar HDD
    PSU
    Thermaltake W0133RB 1200W PSU
    Case
    Antec 900
    Cooling
    Stock + Antec 900 case fans
    Mouse
    Logitech MX Revolution
    Keyboard
    Logitech G15 (full layout)
M

Mick Murphy

Run the following: sfc /scannow

That should fix missing or corrupted files.
If that fails to fix it, boot from the DVD and do a Repair.
--
Mick Murphy - Qld - Australia


"avallach" wrote:

> Trying to troubleshoot a problem with a Vista machine, clean install,
> which, during the first boot-up each day, does the following:
>
> Windows failed to Start.
>
> File: \Windows\system32\ntoskrnl.exe
> Status : 0xc0000221
> Info: Windows failed to load because the kernel is missing, or
> corrupt.
>
> We reboot the machine, it brings up the "Windows failed to start"
> screen that gives us the safe mode, last known good, normal etc boot
> options, we choose Boot Normally and it boots right up, and has no
> further issues (until the next day when it does it again).
>
> Any ideas? So far I'm at a loss and don't want to reinstall because
> of this. I've thought of trying a repair but haven't done so yet.
> I've also thought about trying to simply copy the file from another
> good Vista machine over, but that seems kinda scary.
>
 

My Computer

A

avallach

On Feb 25, 11:52 am, Mick Murphy
<[email protected]> wrote:

> Run the following: sfc /scannow
>
> That should fix missing or corrupted files.
> If that fails to fix it, boot from the DVD and do a Repair.
> --
> Mick Murphy - Qld - Australia
>
>
>
> "avallach" wrote:

> > Trying to troubleshoot a problem with a Vista machine, clean install,
> > which, during the first boot-up each day, does the following:
>

> > Windows failed to Start.
>

> > File: \Windows\system32\ntoskrnl.exe
> > Status : 0xc0000221
> > Info: Windows failed to load because the kernel is missing, or
> > corrupt.
>

> > We reboot the machine, it brings up the "Windows failed to start"
> > screen that gives us the safe mode, last known good, normal etc boot
> > options, we choose Boot Normally and it boots right up, and has no
> > further issues (until the next day when it does it again).
>

> > Any ideas?  So far I'm at a loss and don't want to reinstall because
> > of this.  I've thought of trying a repair but haven't done so yet.
> > I've also thought about trying to simply copy the file from another
> > good Vista machine over, but that seems kinda scary.- Hide quoted text -
>
> - Show quoted text -

Thanks I will try that, you're the 2nd person who suggested something
along those lines. The only thing that's really strange to me is that
simply rebooting the system always fixes the problem. If the file
really is messed up I don't know why it wouldn't just fail again on
every boot attempt.
 

My Computer

E

Engel

See what Tim Quan - MSFT have to said about

Unable to boot up my new laptop - 0xc0000221

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2805120&SiteID=17

Good luck
- -- ---

"avallach" wrote:

> Trying to troubleshoot a problem with a Vista machine, clean install,
> which, during the first boot-up each day, does the following:
>
> Windows failed to Start.
>
> File: \Windows\system32\ntoskrnl.exe
> Status : 0xc0000221
> Info: Windows failed to load because the kernel is missing, or
> corrupt.
>
> We reboot the machine, it brings up the "Windows failed to start"
> screen that gives us the safe mode, last known good, normal etc boot
> options, we choose Boot Normally and it boots right up, and has no
> further issues (until the next day when it does it again).
>
> Any ideas? So far I'm at a loss and don't want to reinstall because
> of this. I've thought of trying a repair but haven't done so yet.
> I've also thought about trying to simply copy the file from another
> good Vista machine over, but that seems kinda scary.
>
 

My Computer

Top