Re: CHKDSK at startup / Win2K

Tech-Archive recommends: Speed Up your PC by fixing your registry

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.



.

Relevant Pages

  • Re: CHKDSK at startup / Win2K
    ... John John, please see my previous post in the thread, and thanks for your ... I did end up editing the binary values for the BootExecute keys to ... Then I renamed all CHKDSK ... Can you mount the Windows 2000 disk in another Windows 2000 or Windows ...
    (microsoft.public.win2000.general)
  • Re: My experiences with a Dell D620 Laptop. Part 1.
    ... Specification of the Dell. ... highlights extra key functions on the keys accessible via the Fn key. ... Powerbook and MacBook screens. ... - There are the usual irritating Intel Core Duo and 'Windows Designed ...
    (comp.sys.mac.advocacy)
  • RE: The string universal unique identifier (UUID) is invalid.
    ... when you install multiple brands of cards in Windows XP. ... The issue may be caused by a corrupt winsock or TCP/IP ... Delete corrupted registry keys and reinstall TCP/IP protocol. ...
    (microsoft.public.windowsxp.network_web)
  • Re: My experiences with a Dell D620 Laptop. Part 1.
    ... This post is to show Mac Users just what they are missing compared to a 9 month old PowerBook G4/15.4/1.6Mhz and a white MacBook. ... On a number of occasions I've opened up the machine only to find the battery is drained or find a very hot laptop in my bag. ... It has a rather tacky looking two-tone appearance around the keyboard and trackpad with the keys being a different colour to the inner silver 'ring'. ... Why couldn't these go underneath with the WIndows XP license label? ...
    (comp.sys.mac.advocacy)
  • Re: Domain Local group and Require strong. GPO Problem
    ... Microsoft MVP (Windows Server System: ... >> controller that is not capable of encrypting secure channel traffic with ... >> that all such domain controllers must be running Windows 2000 or later ... >> Session keys used to establish secure channel communications between ...
    (microsoft.public.win2000.security)