Re: CHKDSK at startup / Win2K
- From: Riskman <Riskman@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 7 Jul 2008 12:36:01 -0700
I always prefer to complete the thread in order to let others know the
outcome in case they might have a similar issue. My machine was on a
network, and it continued to loop and bluescreen. There might possibly have
been some impact from login scripts (that caused the bluescreen) that I never
really explored, but my main concern was to stop the loop so I could get the
machine past the utility and complete the boot-up so login was possible, then
I could correct the registry. John John gave me a great hint toward getting
to a place where we could correct the registry and stop the loop. I
appreciate all those who offered assistance. - riskman
"sia" wrote:
As I am running my chkdsk /r at the moment which seems to progress very.
slowly at some point like stuck at 50% for good 8 minutes before it continue.
Anywhere what I am going to say here is its very kind of you to spend the
time to summarise the corrective actions for the benefits of others likewise
to those who have offered the suggestions.
"Riskman" wrote:
Dave, I was unable to boot through to Safe Mode w/Recovery Console... I
might have possibly been able to boot from the CD or Recovery Disks to get to
that point, but as it turned out I got a workable start from John John...
His suggestions and colaboration led me to find the needed solution as posted
in the threads with him. Nevertheless, I appreciate your thoughtful
suggestions.
For others with a similar problem, the solution in this particular case was:
1) remount the volume in a second Win2K machine as a secondary disk, find
and rename all copies of AUTOCHK and CHKDSK (inserted a leading underscore)
so as to disable them temporarily, then return the HDD back to my original PC
so I could then boot up into windows without those services running, and then
allow access to edit the registry... Boot into Widows was successful, but
cleanup was needed...
2) John John had pointed me in the direction regarding the ControlSets &
Session Managers in the registry which I simply located by doing a find on
"autochk". The specific key(s) triggered was "BootExecute" that had a
Multi-String (binary) value and data description of "autocheck autochk /r
\??\C: autocheck autochk*"
3) ...Having determined the correct value for the "BootExecute" key should
simply be "autocheck autochk*", I was able to edit out the extra unwanted
detail listed in #2 above and restore the desired value.
4) Lastly, I renamed the disabled _AUTOCHK and _CHKDSK files back to their
original and correct names (removed the underscore) in all instances, then
restarted the PC to test. Everything worked as appropriate and desired.
Of course any time changes/edits are being made to the registry, extreme
caution is called for, and backups or good copies are essential.
To all those who gave any suggestions, thank you for assisting. - riskman
"Dave Patrick" wrote:
What happens if you run;
chkdsk /r
from the recovery console command line. (/r implies /f and /p)
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%
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Riskman" wrote:
I tried to run Error Checking (CHKDSK) on my Win2K Pro, and selected both
options to auto fix file system errors and scan/attempt recovery of bad
sectors. A popup window advised it would require running at startup, so I
OK'd the schedule, then restarted system to allow CHKDSK to scan, fix,
recover. CHKDSK proceeded thru its 5 phases, completed each to 100% with
no
apparent issue, but upon completing the last phase the system moved to a
blue
screen with the following stop error:
*** STOP: 0x0000000A (0xC0001C8C, 0x00000002, 0x00000000, 0x8043832C)
IRQL_NOT_LESS_OR_EQUAL
*** Address 8043832C base at 80400000, DateStamp 45ec3c8f - ntoskrnl.exe
"If this is the first time you've seen this Stop error screen, restart
your
computer. If this screen appears again, follow these steps:
"Check to make sure any new hardware or software is properly installed. If
this is a new installation, ask your hardware or software manufacturer for
any Windows 2000 updates you might need.
"If this problem continues, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
Check
your hard drive to make sure it is properly configured and terminated. If
you
need to use Safe Mode to remove or disable components, restart your
computer,
press F8 to select Advanced Startup Options and then select Safe Mode.
"Refer to your Getting Started manual for more information on
troubleshooting Stop errors."
OK, so following this blue screen I did restart, tried to envoke Safe Mode
but then the scheduled CHKDSK started again, during which the keyboard is
completely unresponsive and does not let you opt to bypass the CHKDSK
scan.
It goes thru the full scan with precisely the same results each time, each
phase 100% complete then jumps to the same blue screen. The result is an
endless loop of CHKDSK...
How can I get into a command prompt prior to CHKDSK starting so that I can
either rename the CHKDSK file ot the AUTOCHK file so that I can proceed to
booting into Windows? Otherwise, what other alternatives can you suggest?
If you suggest a quick boot disk, please advise specific files I would
need
(keep in mind this is Win2K and not the easier WinXP) in order to be able
to
see the NTFS files on C:.. A bootable disk I created with an XP machine
would not let me get beyond A: (i.e. I could not redirect to C: on the
Win2K
machine), so there must have been some necessary files missing, but I do
not
know which ones.
- References:
- Re: CHKDSK at startup / Win2K
- From: sia
- Re: CHKDSK at startup / Win2K
- Prev by Date: Problem deleting large files
- Next by Date: Re: Problem deleting large files
- Previous by thread: Re: CHKDSK at startup / Win2K
- Next by thread: Problem deleting large files
- Index(es):
Relevant Pages
|
