Results 1 to 5 of 5
2015-10-10, 22:37 #1
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
2015-10-11, 00:27 #2
- Join Date
- Jun 2014
- Queensland, Australia
- Thanked 318 Times in 276 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
Confuscius said: "no use running harder if you're on the wrong road" and "any problem once correctly understood is already half-solved".
2015-10-11, 01:52 #3
- Join Date
- Dec 2009
- Thanked 1,008 Times in 937 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".
2015-10-11, 04:25 #4
- Join Date
- Aug 2012
- Durham UK
- Thanked 908 Times in 867 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 ?
2015-10-11, 11:33 #5