Article ID: 151376
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q151376
SUMMARY
When a Windows NT system is shut down improperly or stops responding,
Autochk runs against any volumes that are marked as being dirty. If the
operating system partition is marked dirty and Autochk tries to repair the
volume, and if the damaged volume causes Autochk to stop responding, it is
not possible to get back into Windows NT to perform recovery procedures.
Additionally, if an extremely large volume becomes corrupt it could take
many hours for Autochk to repair the volume (the time required depends on
the size of the partition and the number and size of the affected files).
In order to get back into Windows NT, you can disable the drive whose
partition/volume is causing Autochk to stop responding, then boot into
Windows NT and rename Autochk.exe, which is located in the
%systemroot%\system32 directory. Once Autochk.exe is renamed so it can't
run, you can perform a normal shutdown, re-enable the problem drive whose
volume caused Autochk to hang, then reboot the server. Once back in
Windows NT, you can perform data recovery procedures by running a manual
Chkdsk /F /R or by re-creating the partition and restoring data from a
current backup.
If the volume/drive causing Autochk to hang cannot be disabled because it
is the operating system drive or part of a hardware RAID 5 configuration,
it will be necessary to perform the following procedure to replace the
Autochk.exe file with a nonexecutable file also called Autochk.exe in
order to bypass the Autochk process.
Keywords: KB151376