NTOSKRNL BOOT FAILURE

[Carlos]

I installed win2k sp2 and update everything to SP4. My
problem is I install winmx and limewire basically to
download stuff but after a while of downloading I begin to
get errors of UNREADABLE or Damage or missing files and
makes my system go nuts. I constantly get NTOSKRNL MISSING
like if someone is hacking my pc. I am not sure if its
limewire or kazaa or winmx or maybe its when I install
xvid codec. But I constaly get thir problem. Not sure if
its my HDD maxtor 250gb. Is there a way of protecting my
system files from this and is there a way of checking the
surface of my HDD to see if its going to fail.

 

[Pat [MSFT]]

Those are very, very low level errors (typically associated with hardware
failures). Run chkdsk and see if it detects any problems on the HDD.

Pat

 

[Carlos again]

I was reading other articles regarding the issues I been
having and I saw one that made some kind of sense to me
and can help me but I need more advice read as follows
more at the end of message : I'm the serious-problem-
support person for a network of about 5000 machines, and
I've seen that error many times. In my experience,
despite what the error message and all of the Microsoft
Knowledge Base articles say, the problem is not with the
NTOSKRNL.EXE file nor BOOT.INI.

I've seen a few causes of this error message:

-- Under Windows NT, the boot partition is limited to
about 8 GB. If it's larger, and NTOSKRNL.EXE is
upgraded, it can be put in a different position on the
disk past the 8 GB barrier, causing this boot failure.
I'm not sure if that's an issue under Windows 2000 or
not, but I suspect not.

-- The System Registry is corrupted. Load the disk as a
secondary disk on another machine. Run REGEDT32.EXE and
Load Hive of <secondary>\Windows\System32\Config\system,
and if it gives an error, then that's your issue. Try
the same with the Software registry hive as well. Fixing
a registry corruption is another issue, however.

-- There is file system corruption causing problems
accessing the system registry. Again, load the disk as a
secondary and do a CHKDSK /F on it. The few times I've
hit this case, it's been able to fix the problem with no
data loss.
Carlos Talking: As you can see I have noticed that I
I cant go any higher than 8gb of saving data before I
start to loose my OS what can I do to fix my problem
meaning how do I partition my HDD of 250gb so I dont have
this problem anymore ie. do i have to partion my HDD for
8gb and the rest will be another partition? how do I do
this please help email is (e-mail address removed)

 

[Pat [MSFT]]

There is no problem w/a boot partition of >8GB. The vast majority of
installations from NT4 and later were on volumes of greater than 8GB (for
reference, my WinXP laptop has a single volume of 60GB).

Pat

 

[Greg Hayes/Raxco Software]

While you can install Win2k on a drive that is larger than 8GB, the Win2k
installer doesn't check to see if the BIOS will support addressing greater
than 7.8GB.

- Greg/Raxco Software
Microsoft MVP - Windows File System

Want to email me? Delete ntloader.