Results 1 to 5 of 5
  1. #1
    New Lounger rdanner3's Avatar
    Join Date
    May 2010
    Location
    AL
    Posts
    8
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Question BSOD: Error code 0x24 (which scopes as NTFS.SYS related)

    Anyone have any idea how to run CHKDSK /F /V /R when nothing Windows-related will boot on the affected machine? The only thing I've had recommended was to pull the drive, connect it to another Windows machine and run the command from there, but I'm not 100% certain even that will solve the problem.

    Here's the issue in brief: I ran a free-space wiping program that my work requires every sixty days. I've never before had a problem with this... until this run. This time, the program crashed out about 2/3s of the way through and would not launch again. Not realizing what the problem was (corruption of the file system) I rebooted. Now, here's where it gets weird. It boots, to a point, after complaining about the BCD store being "weird" (seriously. That's the exact statement). Then hits me with a BSoD just prior to being able to log in. When I try to run CHKDSK (as the BSoD recommends), I get a second BSoD that shows the 0x24 error code. (No, I don't recall the exact code of the first one, but it's related to the boot manager.)

    I am running Linux Mint 17.2 right now from the drive, and Spinrite 6.0 has shown that the drive's hardware (and low-level formatting) are both flawless, so that narrows it down some. I think. Does anyone have any experience using a SATA/PATA-to-USB adapter? I've been informed that is the system I will need to get the drive capable of being seen by the second machine.
    Mr. Raymond Danner III

  2. #2
    WS Lounge VIP Coochin's Avatar
    Join Date
    Jun 2014
    Location
    Queensland, Australia
    Posts
    2,160
    Thanks
    31
    Thanked 307 Times in 267 Posts
    You could boot from a Win7 installation DVD or a Win7 "System Repair" disc (see Control Panel\Backup and Restore") and run chkdsk that way from a command prompt.
    Computer Consultant/Technician since 1998 (first PC was Atari 1040STE in 1988).
    Most common computing error is EBKAC: Error Between Keyboard And Chairback
    AMD FX8120 (8-core @ 3.1GHz) CPU, Gigabyte GA-990FXA-D3 motherboard, 8GB (2x4GB) DDR3 1866MHz RAM, ATI-AMD Radeon HD6770 PCI-E VGA, 480GB Kingston SSD, 2TB Seagate SATA3.0 HDD, ASUS DVD/RW.

  3. #3
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,207
    Thanks
    49
    Thanked 989 Times in 919 Posts
    Alternatively you could give the PC to the bods who came up with the rather odd wipe requirement and say "your tool broke it, let me know when you've recovered it, I'm off to have a coffee".

    cheers, Paul

  4. #4
    Super Moderator
    Join Date
    Aug 2012
    Location
    Durham UK
    Posts
    6,650
    Thanks
    147
    Thanked 884 Times in 845 Posts
    With the HDD in the affected machine can you boot up into the Advanced Boot options to select Safe Mode with Command Prompt ?

    If you can then enter chkdsk c: /r

    After the prompt to type and enter y enter shutdown /r /t 00 for it to reboot.

    This error code has also been known to be caused by bad memory and if the chkdsk doesn't resolve and the machine has more than one RAM module, try booting it with just either as a quick check.

    If this is a Works machine then follow Paul's advice and chuck it back to the IT department.

    Is CCleaner the free program you are using to wipe the free space ?

  5. #5
    Silver Lounger wavy's Avatar
    Join Date
    Dec 2009
    Location
    ny
    Posts
    2,383
    Thanks
    235
    Thanked 147 Times in 136 Posts
    Quote Originally Posted by rdanner3 View Post
    Then hits me with a BSoD just prior to being able to log in. When I try to run CHKDSK (as the BSoD recommends), I get a second BSoD that shows the 0x24 error code. (No, I don't recall the exact code of the first one, but it's related to the boot manager.)

    .
    How are you running CHKDSK if you can't boot the HDD?

    David

    Just because you don't know where you are going doesn't mean any road will get you there.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •