Re: \WINNT\SYSTEM32\CONFIG\SYSTEM.ced
- From: "Scott Harding" <scrockel@**NO_SPAM**hotmail.com>
- Date: Fri, 10 Jun 2005 10:41:41 -0700
The other cause is that the System hive is corrupted. You should try the
other steps in the article to replace it.
--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server
"suzen" <suzen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B9956FB7-6D4B-48AF-B836-F1960E3F7F85@xxxxxxxxxxxxxxxx
> I've been told that our system hive is only 2 MB. It does not seem to be
> the cause of this problem. And we do not have the Promise Technology ATA66
> PCI Controller. Could anything else be causing this problem?
>
> "suzen" wrote:
>
>> We have several Dell Precision 670 workstations that have gotten the
>> following error on boot up: "Windows could not start because the
>> following
>> file is missing or corrupt: \WINNT\SYSTEM32\CONFIG\SYSTEM.ced" We are
>> using
>> Windows 2000 Professional SP4.
>>
>> This error appears randomly. A system can be working for a couple of
>> weeks
>> before it appears. Then one day the user will be booting up and she will
>> get
>> the error. After that the computer is unusable and we have to rebuild it.
>> What is causing this? How can we make it stop?
>>
>> NOTE: Our registry size is not too large.
>>
>> We got these computers for our power users because they urgently needed
>> more
>> power, but instead of helping them they have gotten less unreliable
>> workstations. We need to fix this quickly.
.
- Follow-Ups:
- Re: \WINNT\SYSTEM32\CONFIG\SYSTEM.ced
- From: suzen
- Re: \WINNT\SYSTEM32\CONFIG\SYSTEM.ced
- References:
- \WINNT\SYSTEM32\CONFIG\SYSTEM.ced
- From: suzen
- RE: \WINNT\SYSTEM32\CONFIG\SYSTEM.ced
- From: suzen
- \WINNT\SYSTEM32\CONFIG\SYSTEM.ced
- Prev by Date: RE: \WINNT\SYSTEM32\CONFIG\SYSTEM.ced
- Next by Date: Re: \WINNT\SYSTEM32\CONFIG\SYSTEM.ced
- Previous by thread: RE: \WINNT\SYSTEM32\CONFIG\SYSTEM.ced
- Next by thread: Re: \WINNT\SYSTEM32\CONFIG\SYSTEM.ced
- Index(es):
Relevant Pages
|
