CHKDSK at startup / Win2K

[Guest Riskman]

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.

[Guest Sid Elbow]

Re: CHKDSK at startup / Win2K

 

Riskman wrote:

> 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.

 

A bootdisk/CD that will enable you to access NTFS drives can be obtained

from:

 

http://www.bootdisk.com/ntfs.htm

[Guest John John (MVP)]

Re: CHKDSK at startup / Win2K

 

Did you try booting to the Last Known Good Configuration?

 

Can you mount the Windows 2000 disk in another Windows 2000 or Windows

XP machine. If yes then you can load the registry's System hive from

the C:\WINNT\system32\config folder and edit the Session Managers

BootExecute value in the proper (or all) ControlSetnnn key. For easy

instructions on how to Load a Remote registry hive see here:

http://www.rwin.ch/xp-live/regedit.htm

 

If you want to do this and need further instructions please post again.

 

Mind you, I'm not convinced that this will rid you of the 0x0A error.

 

John

 

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.

>

[Guest Riskman]

Re: CHKDSK at startup / Win2K

 

Thanks, Sid, I had already tried that to no avail. The product lets you read

c: but you cannot rename any file. Still trying all possibilities, though.

Any other suggestions are welcomed. - riskman

 

"Sid Elbow" wrote:

> Riskman wrote:

>

> > 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.

>

> A bootdisk/CD that will enable you to access NTFS drives can be obtained

> from:

>

> http://www.bootdisk.com/ntfs.htm

>

[Guest Dave Patrick]

Re: CHKDSK at startup / Win2K

 

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.

>

[Guest Riskman]

Re: CHKDSK at startup / Win2K

 

Booting from Last Known Good Config does not work, since current config is

good but just stuck in this loop. The problem seems to be that wherever this

command is in the registry it does not find the CHKDSK has satisfactorily

completed, so it continues to run it at each startup. I will try mounting it

as a slave disk in another Win2K machine, though, and follow your posted

instructions for another alternative. Then if that doesn't work, maybe I can

at least try to access the Autochk and Chkdsk files so if nothing else I can

maybe rename Chkdsk to disable it long enough to get my system working again.

Thanks for the assist. I'll f/u later to let you know results. - riskman

 

"John John (MVP)" wrote:

> Did you try booting to the Last Known Good Configuration?

>

> Can you mount the Windows 2000 disk in another Windows 2000 or Windows

> XP machine. If yes then you can load the registry's System hive from

> the C:\WINNT\system32\config folder and edit the Session Managers

> BootExecute value in the proper (or all) ControlSetnnn key. For easy

> instructions on how to Load a Remote registry hive see here:

> http://www.rwin.ch/xp-live/regedit.htm

>

> If you want to do this and need further instructions please post again.

>

> Mind you, I'm not convinced that this will rid you of the 0x0A error.

>

> John

>

> 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.

> >

>

[Guest Sid Elbow]

Re: CHKDSK at startup / Win2K

 

There is one method listed that purports to let you "View, Copy, Write,

And Edit Files On NTFS Drives" though I haven't looked at it myself.

 

It links (ultimately) to:

 

http://www.free-av.com/en/tools/11/avira_ntfs4dos_personal.html

 

 

 

Riskman wrote:

> Thanks, Sid, I had already tried that to no avail. The product lets you read

> c: but you cannot rename any file. Still trying all possibilities, though.

> Any other suggestions are welcomed. - riskman

>

> "Sid Elbow" wrote:

>

>> http://www.bootdisk.com/ntfs.htm

>>

[Guest Riskman]

Re: CHKDSK at startup / Win2K

 

 

 

"John John (MVP)" wrote:

> Did you try booting to the Last Known Good Configuration?

>

> Can you mount the Windows 2000 disk in another Windows 2000 or Windows

> XP machine. If yes then you can load the registry's System hive from

> the C:\WINNT\system32\config folder and edit the Session Managers

> BootExecute value in the proper (or all) ControlSetnnn key. For easy

> instructions on how to Load a Remote registry hive see here:

> http://www.rwin.ch/xp-live/regedit.htm

>

> If you want to do this and need further instructions please post again.

>

> Mind you, I'm not convinced that this will rid you of the 0x0A error.

>

> John

>

> 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.

> >

>

[Guest Riskman]

Re: CHKDSK at startup / Win2K

 

John John, I had to leave this job Sat p.m. but am back at it this Mon

morning. Your suggestion to mount the drive in another PC was great and I

was able to disable Autochk and Chkdsk. The actual culprit is Autochk and I

found 3 registry keys in the Session Manager in 3 ControlSet folders I want

to modify. They are specific to the BootExecute key you mentioned, and the

data desc apparently should simply say "autocheck autochk*" vs. the longer

line I found which indicates "autocheck autochk /r \??\C: autocheck

autochk*". Each of these ControlSetxxx\Control\Session Manager files also

contains an additional key lower down that shows

"PendingFileRenameOperations" with a data desc of

"\??\C:\WINNT\system32\spool\DRIVERS\BIDI\Old" that appears to me to be a key

that I can simply delete.

 

I am a little apprehensive, however, about trying to change the value of the

BootExecute key because it is posted in binary and each letter of the data

desc is a specific binary value. I obviously don't want to screw this up.

Would unloading and loading the hive as you mentioned earlier take care of

that easier, or do I need to try to edit the binary values for each letter

in the data desc?

 

"John John (MVP)" wrote:

> Did you try booting to the Last Known Good Configuration?

>

> Can you mount the Windows 2000 disk in another Windows 2000 or Windows

> XP machine. If yes then you can load the registry's System hive from

> the C:\WINNT\system32\config folder and edit the Session Managers

> BootExecute value in the proper (or all) ControlSetnnn key. For easy

> instructions on how to Load a Remote registry hive see here:

> http://www.rwin.ch/xp-live/regedit.htm

>

> If you want to do this and need further instructions please post again.

>

> Mind you, I'm not convinced that this will rid you of the 0x0A error.

>

> John

>

> 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.

> >

>

[Guest John John (MVP)]

Re: CHKDSK at startup / Win2K

 

How are you loading and viewing the remote hive? With an XP machine you

can use Regedit, with a Windows 2000 machine you have to use Regedt32.

Using these tools you can easily edit the Multi-String value. The value

should read: autocheck autochk *

 

John

 

Riskman wrote:

> John John, I had to leave this job Sat p.m. but am back at it this Mon

> morning. Your suggestion to mount the drive in another PC was great and I

> was able to disable Autochk and Chkdsk. The actual culprit is Autochk and I

> found 3 registry keys in the Session Manager in 3 ControlSet folders I want

> to modify. They are specific to the BootExecute key you mentioned, and the

> data desc apparently should simply say "autocheck autochk*" vs. the longer

> line I found which indicates "autocheck autochk /r \??\C: autocheck

> autochk*". Each of these ControlSetxxx\Control\Session Manager files also

> contains an additional key lower down that shows

> "PendingFileRenameOperations" with a data desc of

> "\??\C:\WINNT\system32\spool\DRIVERS\BIDI\Old" that appears to me to be a key

> that I can simply delete.

>

> I am a little apprehensive, however, about trying to change the value of the

> BootExecute key because it is posted in binary and each letter of the data

> desc is a specific binary value. I obviously don't want to screw this up.

> Would unloading and loading the hive as you mentioned earlier take care of

> that easier, or do I need to try to edit the binary values for each letter

> in the data desc?

>

> "John John (MVP)" wrote:

>

>

>>Did you try booting to the Last Known Good Configuration?

>>

>>Can you mount the Windows 2000 disk in another Windows 2000 or Windows

>>XP machine. If yes then you can load the registry's System hive from

>>the C:\WINNT\system32\config folder and edit the Session Managers

>>BootExecute value in the proper (or all) ControlSetnnn key. For easy

>>instructions on how to Load a Remote registry hive see here:

>>http://www.rwin.ch/xp-live/regedit.htm

>>

>>If you want to do this and need further instructions please post again.

>>

>>Mind you, I'm not convinced that this will rid you of the 0x0A error.

>>

>>John

>>

>>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.

>>>

>>

[Guest Riskman]

Re: CHKDSK at startup / Win2K

 

John John, please see my previous post in the thread, and thanks for your

advise. I did end up editing the binary values for the BootExecute keys to

where they all reflect "autocheck autochk*" only. It turned out that editing

in binary was not too difficult after all (I made sure I had good copies of

both the desired keys and existing keys I wanted to modify, just for guides

in case I needed to change things back). Anyway, since you pointed me in the

right direction I found the necessary registry keys to fix and

carefully/cautiously implemented the proper edits. Then I renamed all CHKDSK

and AUTOCHK files back to their original/correct names so as to restore their

functionality. Everything appears to be working fine. Thanks again for your

assistance. - riskman

 

"John John (MVP)" wrote:

> Did you try booting to the Last Known Good Configuration?

>

> Can you mount the Windows 2000 disk in another Windows 2000 or Windows

> XP machine. If yes then you can load the registry's System hive from

> the C:\WINNT\system32\config folder and edit the Session Managers

> BootExecute value in the proper (or all) ControlSetnnn key. For easy

> instructions on how to Load a Remote registry hive see here:

> http://www.rwin.ch/xp-live/regedit.htm

>

> If you want to do this and need further instructions please post again.

>

> Mind you, I'm not convinced that this will rid you of the 0x0A error.

>

> John

>

> 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.

> >

>

[Guest John John (MVP)]

Re: CHKDSK at startup / Win2K

 

You're welcome, I'm glad to see that you got things fixed.

 

John

 

Riskman wrote:

> John John, please see my previous post in the thread, and thanks for your

> advise. I did end up editing the binary values for the BootExecute keys to

> where they all reflect "autocheck autochk*" only. It turned out that editing

> in binary was not too difficult after all (I made sure I had good copies of

> both the desired keys and existing keys I wanted to modify, just for guides

> in case I needed to change things back). Anyway, since you pointed me in the

> right direction I found the necessary registry keys to fix and

> carefully/cautiously implemented the proper edits. Then I renamed all CHKDSK

> and AUTOCHK files back to their original/correct names so as to restore their

> functionality. Everything appears to be working fine. Thanks again for your

> assistance. - riskman

>

> "John John (MVP)" wrote:

>

>

>>Did you try booting to the Last Known Good Configuration?

>>

>>Can you mount the Windows 2000 disk in another Windows 2000 or Windows

>>XP machine. If yes then you can load the registry's System hive from

>>the C:\WINNT\system32\config folder and edit the Session Managers

>>BootExecute value in the proper (or all) ControlSetnnn key. For easy

>>instructions on how to Load a Remote registry hive see here:

>>http://www.rwin.ch/xp-live/regedit.htm

>>

>>If you want to do this and need further instructions please post again.

>>

>>Mind you, I'm not convinced that this will rid you of the 0x0A error.

>>

>>John

>>

>>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.

>>>

>>

[Guest Riskman]

Re: CHKDSK at startup / Win2K

 

{John John (and others), please forgive my couple of blank posts... Not sure

why those did not contain my replies.}

 

Please see my previous good post. Your suggestion led me in the right

direction to find the BootExecute keys that needed correction, which I did

edit successfully. I was a little apprehensive at first about editing the

binary value, but I made sure I had a backup and also good copies of the

desired multi-string values in order to edit each instance to "autocheck

autochk*". I did also remove the PendingFileRenameOperations key that

appeared to then be extraneous. Have also renamed the disabled AUTOCHK and

CHKDSK files back to their original/correct names so that they are again

functional and restarted system to test. Everything is now back to where it

should be and all is working well. WHEW! (Sigh of relief.) thank you again

for your kind assistance. - riskman

 

"John John (MVP)" wrote:

> How are you loading and viewing the remote hive? With an XP machine you

> can use Regedit, with a Windows 2000 machine you have to use Regedt32.

> Using these tools you can easily edit the Multi-String value. The value

> should read: autocheck autochk *

>

> John

>

> Riskman wrote:

>

> > John John, I had to leave this job Sat p.m. but am back at it this Mon

> > morning. Your suggestion to mount the drive in another PC was great and I

> > was able to disable Autochk and Chkdsk. The actual culprit is Autochk and I

> > found 3 registry keys in the Session Manager in 3 ControlSet folders I want

> > to modify. They are specific to the BootExecute key you mentioned, and the

> > data desc apparently should simply say "autocheck autochk*" vs. the longer

> > line I found which indicates "autocheck autochk /r \??\C: autocheck

> > autochk*". Each of these ControlSetxxx\Control\Session Manager files also

> > contains an additional key lower down that shows

> > "PendingFileRenameOperations" with a data desc of

> > "\??\C:\WINNT\system32\spool\DRIVERS\BIDI\Old" that appears to me to be a key

> > that I can simply delete.

> >

> > I am a little apprehensive, however, about trying to change the value of the

> > BootExecute key because it is posted in binary and each letter of the data

> > desc is a specific binary value. I obviously don't want to screw this up.

> > Would unloading and loading the hive as you mentioned earlier take care of

> > that easier, or do I need to try to edit the binary values for each letter

> > in the data desc?

> >

> > "John John (MVP)" wrote:

> >

> >

> >>Did you try booting to the Last Known Good Configuration?

> >>

> >>Can you mount the Windows 2000 disk in another Windows 2000 or Windows

> >>XP machine. If yes then you can load the registry's System hive from

> >>the C:\WINNT\system32\config folder and edit the Session Managers

> >>BootExecute value in the proper (or all) ControlSetnnn key. For easy

> >>instructions on how to Load a Remote registry hive see here:

> >>http://www.rwin.ch/xp-live/regedit.htm

> >>

> >>If you want to do this and need further instructions please post again.

> >>

> >>Mind you, I'm not convinced that this will rid you of the 0x0A error.

> >>

> >>John

> >>

> >>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.

> >>>

> >>

>

[Guest Riskman]

Re: CHKDSK at startup / Win2K

 

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.

> >

>

[Guest sia]

Re: CHKDSK at startup / Win2K

 

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.

> > >

> >

[Guest Riskman]

Re: CHKDSK at startup / Win2K

 

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.

> > > >

> > >