Very odd Boot Failure...?

  • Thread starter Thread starter Kenneth
  • Start date Start date
K

Kenneth

Howdy,

I am experiencing a very strange boot failure on my Won 2K system.

Here are the (precise) details:

All was well, but I needed to re-boot for some reason. The boot failed
on the first black screen with the message:

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

\WINNT\System32\Config\SYSTEMced startup options for Windows 2000,
Press F8."

Please note that this is precisely what appeared on screen, with the
very oddly constructed "SYSTEMced startup options for Windows 2000,
Press F8." in the last part.

At that point, I simply attempted to boot again, but found the same
result.

Next, I decided to attempt to restore the offending file from the
Windows CD, but that failed as well.

Next, I restored a complete image that I had created about two hours
prior (Thank you Acronis...)

I installed the image, re-booted (twice), and all was well again.

But, later yesterday, I got an Update from the MS site, and after
installing it, had to re-boot.

That boot attempt failed with the error I have described.

Again, I tried to repair the offending file. Again, no luck.

I then restored a slightly older image (Thanks Acronis for your
scheduling functionality <g>) and was up and running again.

To be absolutely sure that all was well, I re-booted four times in
succession with no difficulties.

I worked the remainder of the day, and decided to re-boot one more time
to insure myself a relaxing evening.

The boot failed with the now familiar error...

Right at the moment, I am running extended diagnostic tests on the hard
disk, but to this point (nearly complete) everything passes.

My take on this is that I have some sort of intermittent failure of a
section of the hard disk, but, I would be most appreciative of any
other possible diagnoses.

Sincere thanks to all,

Kenneth
 
I'm guessing the size of the system hive is at it's limit.

http://support.microsoft.com/?kbid=269075

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Howdy,
|
| I am experiencing a very strange boot failure on my Won 2K system.
|
| Here are the (precise) details:
|
| All was well, but I needed to re-boot for some reason. The boot failed
| on the first black screen with the message:
|
| "Windows 2000 could not start because the following file is missing or
| corrupt:
|
| \WINNT\System32\Config\SYSTEMced startup options for Windows 2000,
| Press F8."
|
| Please note that this is precisely what appeared on screen, with the
| very oddly constructed "SYSTEMced startup options for Windows 2000,
| Press F8." in the last part.
|
| At that point, I simply attempted to boot again, but found the same
| result.
|
| Next, I decided to attempt to restore the offending file from the
| Windows CD, but that failed as well.
|
| Next, I restored a complete image that I had created about two hours
| prior (Thank you Acronis...)
|
| I installed the image, re-booted (twice), and all was well again.
|
| But, later yesterday, I got an Update from the MS site, and after
| installing it, had to re-boot.
|
| That boot attempt failed with the error I have described.
|
| Again, I tried to repair the offending file. Again, no luck.
|
| I then restored a slightly older image (Thanks Acronis for your
| scheduling functionality <g>) and was up and running again.
|
| To be absolutely sure that all was well, I re-booted four times in
| succession with no difficulties.
|
| I worked the remainder of the day, and decided to re-boot one more time
| to insure myself a relaxing evening.
|
| The boot failed with the now familiar error...
|
| Right at the moment, I am running extended diagnostic tests on the hard
| disk, but to this point (nearly complete) everything passes.
|
| My take on this is that I have some sort of intermittent failure of a
| section of the hard disk, but, I would be most appreciative of any
| other possible diagnoses.
|
| Sincere thanks to all,
|
| Kenneth
|
 
Hi Dave,

I appreciate the speedy response, and have followed the steps in the
article to reinstall the default hive...

The box booted, but is missing a few drivers. I should be able to get
those with little trouble.

Given what I have described, is this a problem that is likely to recur,
or, ones I have the missing drivers installed will I be in good ahspe
for a while?

Thanks for your further thoughts,

Kenneth
 
I would put a version back in that can boot then run
Programs|Accessories|System Tools|Backup, then choose ERD, then if you check
the box for "Also backup....", then the reg will also be backed up to
%windir%\repair\RegBack
leaving the
%windir%\repair\
directory files intact as original installation. This should compact the
hive during the backup.

Then compare the size of the system hive found in;
%windir%\repair\RegBack
with that of the in use hive found in;
%windir%\system32\config

If you see an improvement in size then you can replace registry hives from
within the recovery console by copying the files from
%windir%\repair\regback
to
%windir%\system32\config
(the system hive is all that should be necessary at this point)

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks. At
the "Welcome to Setup" screen. Press F10 or R to repair a Windows 2000
installation, and then press C to use the Recovery Console. The Recovery
Console then prompts you for the administrator password. If you do not have
the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %systemroot% or %windir%


--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Hi Dave,
|
| I appreciate the speedy response, and have followed the steps in the
| article to reinstall the default hive...
|
| The box booted, but is missing a few drivers. I should be able to get
| those with little trouble.
|
| Given what I have described, is this a problem that is likely to recur,
| or, ones I have the missing drivers installed will I be in good ahspe
| for a while?
|
| Thanks for your further thoughts,
|
| Kenneth
|
 
You're welcome.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Once again Dave, please accept my sincere thanks,
| --
| Kenneth
|
| If you email... Please remove the "SPAMLESS."
 
I'm guessing the size of the system hive is at it's limit.

http://support.microsoft.com/?kbid=269075
Click to expand...

Hi Dave,

A few weeks ago, you saved my bacon with the suggestion that
I read MSKB # 269075.

My boot had failed with the error ending with (what appears
to be) the very odd word \SYSTEMced.

I restored the default system hive, and all was well.

Until today...

I had to reboot, and when I did, I saw the error again, but
this time, the restore the system hive approach did not
work: The error repeated.

I then restored an image that I created yesterday, and the
system booted properly.

I am now looking further in the article and see the
suggestions to reduce the size of the system hive.

I will, of course, do that, but it brings me to my question:

Is it likely that all of this is just a temporary fix?

Sincere thanks for your thoughts,
 
Back
Top