Re: \WINNT\SYSTEM32\CONFIG\SYSTEM.ced

Make sure write cache is not enabled.

Possible Data Loss After You Enable the "Write Cache Enabled" Feature
http://support.microsoft.com/?id=281672

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q233541

--
Regards,

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

"suzen" wrote:
| We have tried that. In one particular case, we repaired the workstation,
| replacing the system hive, only to have it crash again moments later with
the
| same error.
|
| If is it a corrupt hive, how can we stop this from happening? What is
doing
| this? We have had this happen on three different Dell Precision 607's.
Each
| where install seperately. We have not seen it on any of our other
| workstations.
|
|
| "Scott Harding" wrote:
|
| > 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.
| >
| >
| >


.

Relevant Pages

  • Re: WINNTSYSTEM32CONFIGSYSTEM.ced
    ... Microsoft MVP - Windows NT Server ... Could anything else be causing this problem? ... >> We have several Dell Precision 670 workstations that have gotten the ... >> We got these computers for our power users because they urgently needed ...
    (microsoft.public.win2000.general)
  • RE: WINNTSYSTEM32CONFIGSYSTEM.ced
    ... Could anything else be causing this problem? ... > We have several Dell Precision 670 workstations that have gotten the ... > Windows 2000 Professional SP4. ... > We got these computers for our power users because they urgently needed more ...
    (microsoft.public.win2000.general)
  • Re: WINNTSYSTEM32CONFIGSYSTEM.ced
    ... "Scott Harding" wrote: ... Could anything else be causing this problem? ... >>> We have several Dell Precision 670 workstations that have gotten the ... >>> We got these computers for our power users because they urgently needed ...
    (microsoft.public.win2000.general)
  • Re: assigning users to the Power users group via Group Policy
    ... > set focus to the local machine, ... > Power Users group on workstations in the OU. ... >> Groups policy setting. ... >> Windows XP workstations are used to configure the policy. ...
    (microsoft.public.win2000.group_policy)
  • Re: Try to prevent installs
    ... to consider using the compatws.inf template on those workstations which will give ... users the same ntfs/registry permissions as power users, ... > users local group. ...
    (microsoft.public.win2000.security)