Blue Screen Of Death System File Corrupt

  • Thread starter Thread starter Dave Marden
  • Start date Start date
D

Dave Marden

At work we have several pc's that use windows 2000 professional for vision
systems, and for some reason when we have to shut down our sub-stations
invertently one of our pc's gets the bsod and upon restarting the pc's say
that the system file is corrupt. We have about 100 pc's and it wouldn't be
very possible to physically go around and shut off all the pc's as this
would require too much manpower and it would be less expensive to just
replace the pc and replace the hard drive and ghost the new one for later
use.

I am wondering if anyone has any ideas as to what would be causing this. I
suspect dirty hard drives, as I work in a foundry. Any help would be
appreciated. If the problem is the hard drives is it possible to use a USB
hard drive as our primary hard drive, or another type of hard drive which is
impervious to being dirty?

Dave Marden
 
If the system hive is corrupt, and assuming you already tried LKG (F8 and
choose Last Known Good), It may be possible to rename the system hive found
in
%systemroot%\system32\config\system
to system.old
then rename
%systemroot%\system32\config\system.alt
to
%systemroot%\system32\config\system

You can also try using the most recent backup found in
%systemroot%\repair\regback

If that fails you haven't much choice but to copy/ use the
original-as-installed system hive from
%systemroot%\repair\system
to
%systemroot%\system32\config\system
You'll need to reinstall the device drivers for any hardware added since the
original OS install.

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%


Make sure that your drive controller has Write Cache disabled.
http://support.microsoft.com/?id=281672

We use them in all areas of coal mining (very dirty, dusty conditions) and
don't have this problem. Usually we see the case cooling paths blocked
causing mobo and or power supply failures and of course floppy drives that
never work because of the coal dust.




--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
Thanks, I will try what you suggested and get back with you.

Thanks,
Dave


Dave Patrick said:
If the system hive is corrupt, and assuming you already tried LKG (F8 and
choose Last Known Good), It may be possible to rename the system hive
found in
%systemroot%\system32\config\system
to system.old
then rename
%systemroot%\system32\config\system.alt
to
%systemroot%\system32\config\system

You can also try using the most recent backup found in
%systemroot%\repair\regback

If that fails you haven't much choice but to copy/ use the
original-as-installed system hive from
%systemroot%\repair\system
to
%systemroot%\system32\config\system
You'll need to reinstall the device drivers for any hardware added since
the original OS install.

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%


Make sure that your drive controller has Write Cache disabled.
http://support.microsoft.com/?id=281672

We use them in all areas of coal mining (very dirty, dusty conditions) and
don't have this problem. Usually we see the case cooling paths blocked
causing mobo and or power supply failures and of course floppy drives that
never work because of the coal dust.




--

Regards,

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

Dave Marden said:
At work we have several pc's that use windows 2000 professional for
vision systems, and for some reason when we have to shut down our
sub-stations invertently one of our pc's gets the bsod and upon
restarting the pc's say that the system file is corrupt. We have about
100 pc's and it wouldn't be very possible to physically go around and
shut off all the pc's as this would require too much manpower and it
would be less expensive to just replace the pc and replace the hard drive
and ghost the new one for later use.

I am wondering if anyone has any ideas as to what would be causing this.
I suspect dirty hard drives, as I work in a foundry. Any help would be
appreciated. If the problem is the hard drives is it possible to use a
USB hard drive as our primary hard drive, or another type of hard drive
which is impervious to being dirty?

Dave Marden
Click to expand...
Click to expand...
 
Back
Top