RE: \WINNT\SYSTEM32\CONFIG\SYSTEM.ced
- From: "suzen" <suzen@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 10 Jun 2005 10:19:04 -0700
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: Scott Harding
- Re: \WINNT\SYSTEM32\CONFIG\SYSTEM.ced
- References:
- \WINNT\SYSTEM32\CONFIG\SYSTEM.ced
- From: suzen
- \WINNT\SYSTEM32\CONFIG\SYSTEM.ced
- Prev by Date: Re: Different security for different users
- 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
|
Loading
